Project

General

Profile

Muon Counter System - Experts Only

The muon counter system is currently in the top-top configuration, with both muon detector boxes on the platform. The detector boxes each have x-y segmented scintillator strip bi-layers that are used to form a 4-fold coincidence and send a trigger to the Liz rack. Note that the triggers are only sent when the system is in a running state. Runs must be started manually and require interaction with the laptop on the MCS rack on the platform (there is no network connectivity for this system). This documentation includes lists of checks to make before starting a run and steps to take when starting a run. All runs and system work should be elogged under the Muon tagger category. The MuCS runs (run started on the MuCS laptop) are also recorded in a google doc: https://docs.google.com/spreadsheets/d/11XsZOU9kNe363-j1mTPTD-sKoNshvGotC5yMcyzXv18/edit#gid=877291547.

Hardware Checks Before Starting a Run

Before starting a run, the expert should check that the hardware is ready for the run to start:
  1. Low voltage power supply is on and no errors reported on the LV power supply.
  2. When the low voltage power supply is on, the readout window on the laptop should show a connected device (id=37) and a low rate (~28).
    1. If the readout window will not start due to an already running process, ctrl-alt-del into task manager and kill the existing readout process.
    2. If the readout window does not show a connected device or it shows no data rate, power cycling the LV, with the HV off, should re-connect the USB box.
  3. High voltage power supply can now be turned on. The HV should be turned on last since we don't want to power the LV on/off with the HV enabled.

Login info

Login with the dcdaq account, password 'doublechooz'

Starting MuCS run

  1. You will need to be able to access the platform at LArTF, which requires ODH training and that you have someone to access the platform with you. This also requires approval from the run coordinator.
  2. Before visiting LArTF, make sure you know how long of a run needs to be executed and what the next MuCS group number should be, and the password for the MuCS laptop.
  3. Startup the MuCS laptop and login. You should know the password already.
  4. Update the system time 'via the internet' in time and date settings (double click the clock). Note this will require an internet connection, which may or may not work.
  5. Ensure that the wireless connection is turned OFF.
  6. Check that the readout executable is running on the MuCS laptop and a low rate (~28) is being reported.
  7. Check the duration of a run at the top of the fourboards_loop.pl script, make sure it's 3600.
  8. Execute the "megamini_multiple_runs_4_pmt" batch script on the desktop.
  9. Choose the number of 3600 s runs to be executed.
  10. Label the run: "Run at LArTF ->#xxx!" where xxx is the next group number after the last group number recorded in the elog and MuCS data spreadsheet.
  11. The run will now start. It will take baseline readings for each PMT so wait until the run starts before moving to the next step.
  12. Check that there are 4-fold coincidences being generated:
    1. Turn on the gate on the top channel of the scaler and ensure the counter is increasing.
    2. Check that triggers are being propagated through the Cu->Fib converter. There should be a green indicator on the trigger output if there are triggers being sent.
    3. Check and record the rate by simply running the scaler for 60 seconds.
  13. If this run is in coordination with a TPC run, call back to the control to let them know to start the run.
  14. Record in the elog, under the "Muon tagger" category:
    1. MuCS group number and corresponding uboone run number.
    2. Trigger rate measured using the scaler.
    3. Duration of run.
    4. Run start time.
  15. Also populate the MuCS data spreadsheet: https://docs.google.com/spreadsheets/d/11XsZOU9kNe363-j1mTPTD-sKoNshvGotC5yMcyzXv18/edit#gid=877291547

Once the run is finished:

  1. Collect the data from the MuCS laptop: Copy the run files, located in the folder linked by a shortcut named "Data" on the desktop, to a usb key. You will know which runs to copy by the dates in the folder names.
  2. Copy the files from the usb key to the '/uboone/data/users/kalousis/MuCS/data' folder via a uboonegpvm node: e.g. "cd <USBFOLDER>; scp -r * <yourusername>@uboonegpvm04.fnal.gov:/uboone/data/users/kalousis/MuCS/data/"
  3. Add a comment to the existing elog entry saying this has been done.
  4. Update the MuCS run spreadsheet to mark this set of group,run,seq as copied.

Powering down the system

To power off the MCS rack the following steps should be followed by a MuCS expert:
  1. Ramp down the HV for the PMTs. Set switches on the HV PS to "off" (NOT the "kill") or middle position so that the voltages ramp down slowly.
  2. Turn off the LV.
  3. Shut down the laptop.
  4. Open rear door and flip the power switch on the RPS to the off position (looking from the back of the rack it's at the top right).
  5. Power off the SurgeX by flipping the switch on the front of the rack.

Powering on the system

To power on the MCS rack the following steps should be followed by an MuCS expert:
  1. Power on the SurgeX.
  2. Open rear door and power on the RPS.
  3. Power on the laptop. Make sure it boots and logs into the the dcdaq account. Should so so automatically, if not log into that account. This will start a vnc server so that experts can access the machine remotely.
  4. Turn on the LV. This required both turning on the LV PS and turning on the LV power output. There is a light on the LV PS to indicate if LV is on as well as three LEDs on the front banana plugs to indicate that the LV is on.
  5. Once the LV is confirmed to be on (LED lights are on) then the HV can be turned on by setting the switches on the HV supply to the "on" (up) position.
  6. After a reset, you should take a test run (use Ghost mode) to ensure that triggers are coming out unprescaled (top counter) and prescaled (bottom counter). Often the prescaled triggers do not come through and the prescaler has to be reset. To reset the prescaler (second trigger module from left, labeled "Trigger Divider"), set the top counter to 000 and then back to 100 (the nominal prescale factor for MuCS triggers).

Ghost Mode

MuCS can be set in a Ghost Mode meaning that no MuCS data is saved. Ghost Mode allows the MuCS daq to run continuously along with TPC runs. Now MuCS daq has a small storage of 300GB. Anyway, when necessary, one can switch MuCS to normal mode to save MuCS data with the following steps.
  1. Stop the current MuCS Run
  2. In file DCsubroutinemysql.pm of directory Macro, search for lines with
    new $usb
    and comment them back
  3. Save the pm file and kick off a new MuCS run
  4. Check if the output file in data directory is increasing with magnitude of MB

To switch MuCS back to Ghost Mode, redo the same steps but comment out lines with new $sub

Processing binary MuCS output using Leonidas' Code

  1. cd /uboone/app/users/kalousis/MuCS/builder
  2. execute: source auto_process_data.sh
  3. make sure the appropriate entries are in /uboone/app/users/kalousis/MuCS/preselection/lartf_logfile.txt
  4. execute: export MEGA_MICRO_DATA=/uboone/data/users/kalousis/MuCS/data/
  5. execute: source auto_analyse_data.sh

Accessing VNC Session

There is now a VNC server running on the MuCS laptop at 192.168.144.176. Password is "mucs". There is also an ftp server (filezilla) running (mucs:mucs) available to retrieve output files.

You can access the VNC session by setting up a tunnel through ws01.
ssh -K -L 5900:192.168.144.176:5900 <yourusername>@ubdaq-prod-ws01.fnal.gov

MAPMT High Voltage Settings

The drogues should be set to the following HV values:

Channel 0 -> Box Connection 2A -> PMT 3 -> 765 V
Channel 1 -> Box Connection 2B -> PMT 7 -> 818 V
Channel 2 -> Box Connection 1A -> PMT 1 -> 810 V
Channel 3 -> Box Connection 1B -> PMT 2 -> 825 V