MuTr Calibration DAQ Procedure

• These "special" runs should be taken when we are not taking data for a good beam store, there is no run with the "Big partition" going, and in consultation with the shift leader (if any).
  • Other non-MUTR standalone runs can be going on simultaneously
  • MuTr HV should be off or at standby if there is beam !
• Launch the muTr calibration GUI's from the calibration button on the oncsTools GUI
  
  • and then push the MUTR/North, MUTR/South button (full calibration), they can run in parallel.
• Alternatively log into the phnxrc account on phoncsb; use a fresh window
  • Open a terminal and type : ssh phnxrc@phoncsb
  • Go to the working directory : cd mutr/calib
  • type "docalib.pl &" to start the muTr calibration GUI
  • punch the "South" button to start a South calibration
  • start a second GUI as above for the "North" arm and punch the "North" button
  • Calibration data taking for south and north should to be run at the same time.
  • When each is finished use the EXIT button on the GUI to exit.
  • To use this fast calibration, type "doped.pl &" instead of docalib.pl to start the GUI.
• Each should finish in about 18 (full) or 4 (fast) minutes and progress can be tracked via the GUI progress bar
  • you will also see short messages in the original window from which the GUI was run reporting the progress and how many events were obtained for each run.
  • each DAC setting run stops after 120 or more collected events. The procedure will try up to 3 times at each DAC setting to obtain this many events. If you see it getting only 8 events per run repeatedly than the DAQ is not working and you will need to debug it using standalone run control.
  • Then make sure that rc -standalone works and try again. You may need to do a quick feed for the relevant muon tracker arm. Also, presently, due to a memory problem in the crate controller, if the north calibration fails and memory errors are shown in the iocondev5c ts window, then reboot iocondev5c and try again.
  • a normal calibration run involves one series of runs for each arm with 13 different DAC settings (13 * 4 prdf files should be taken per arm.
• Data will be automatically analyzed with DAQ thresholds and the database being updated and results appearing on the web.
  • http://logbook.phenix.bnl.gov/va078/calib_results/calib_results.html (takes up to 15 minutes, new directory with the current date should appear in ~phnxmutr/calib/. In that subdirectory, view output.txt to check completion.)
  • Status links at the top of the page will contain a list of averages if all went ok, or an error message if not. The changes of the pedestals, gains and rms values wrt the previous calibration are shown in the last 3 columns - they should be small, if not consult a muTr expert.
  • Plots of pedestals and rms values vs time are shown on clickable pictures on the main calibration results web page. Here you can see whether large changes for the most recent calibration have occured wrt the the norm. E.g. a large increase in average rms noise can signal a FEM problem that needs expert attention.
  • If results do not appear on the web the nfs mount of the web area on va078 from logbook may be down.

• Pictures of the docalib.pl calibration GUI at the begining, in progress and after finishing.

More detailed information:

• Automatic DAQ and Analysis procedures explained.