Last Updated on Wednesday, August 01, 2001 at 20:05:18. by Author: Pradeep Sarin
Nominal Choice of RunTypes :
| Run Type | Detector Setup |
| ALLBEAM | Silicon + Plastic (Normal data taking) |
| PADDLECOSM | Plastic Only, NO Silicon (Beam studies with Silicon turned OFF) |
No Calibration runs of any type during night or subsystem
expert present/beam imminent.
RUNNING with Silicon Detectors OFF
Start GUI by clicking on the
desktop icon titled 'PhatDAQRunControl'
Click 'OK' on the 'options'
popup window - don't enter anything
Wait for the message 'Ready
to Receive Initialization' in 'Si ROC Messages'
window
Immediately click on 'Expert
Menu' and select 'Init
Silicon'
'Si ROC
Messages' window should say :
Parsing 07 parameters per (FEC,String) for 42 FEC's
MasterMain() : MasterCE waiting for START_RUN
If Step 6 is not arrived at, do
Step 5 again
Select a suitable RunType, use
checkbutton to Enable/Disable Writing to Disk and hit 'Start
Run'
No need to quit GUI between
individual runs
RUNNING with Silicon Detectors ON
MUST Quit GUI completely
before switching on FEC Low Voltage Power supplies
Wait for the Low Voltage Power Supplies to turn
ON (Silicon Expert gives OK)
Start GUI by clicking on the desktop icon
titled 'PhatDAQRunControl'
Click 'OK' on the 'options' popup window -
don't enter anything
Wait for the message 'Ready
to Receive Initialization' in 'Si ROC Messages'
window
click on 'Expert Menu'
and select 'Reset Latchup'
Immediately after that, click on 'Expert
Menu' and select 'Init
Silicon'
'Si ROC Messages'
window should say :
Parsing 07 parameters per (FEC,String) for 42 FEC's
MasterMain() : MasterCE waiting for START_RUN
If Step 8 is not arrived at, do Step 7 again
Ramp the Silicon Bias voltages to Full Bias
(Silicon expert gives OK)
After Bias voltages are up, click on 'Expert
Menu' and select 'Reset
Latchup' again
Select RunType = ALLBEAM, use checkbutton to
Enable/Disable Writing to Disk and hit 'Start Run'
While run is in progress, keep a watch on the 'Events
Accepted' scaler. It should keep counting if there are collisions. If
it stops counting, look for error messages in the 'PhatDAQ
Messages' window : you may need to stop and start a new run. Note in
the RunLog that this happened and call DAQ expert.