...
Note that the sequence of operations for starting (and stopping) a run is, to many respects, different in the two cases, so that one should always make sure what's the configuration he's running with before starting a run.
Typically Run Control should be launched at the beginning of the shift and, unless problems occur, multiple runs can be made without closing and re-open it. So there shouldn't be any reason for restart Run Control during the shift. Upon double click on the icon, two different windows are pop up:
...
- CAL: this is done through the CAL tab in the Run Control main GUI. There's a button at the bottom of the tab for refreshing the BIAS DAC setting. The nominal value should be
No Format 0x5800
- TKR: this is done through the TKRtab in the Run Control main GUI. There's a button for refreshing the level of the TKR bias voltage. The nominal value shuold be around
No Format 100 V
Again: under normal conditions the bias voltages to the detectors should be on all the times and the shifters should not have to turn it on/off manually.
...
The test application is choosen by pressing the Select Applicationbutton, which opens a file browser. Under normal circumstances the shifter should always select the application called
| No Format |
|---|
end2endBT.py |
which, by the way, is the only test application into the default directory of the file browser. After the Open button is pressed, the file browser is closed and Run Control is ready to start.
...
| No Format |
|---|
This assumes that the user launches Run Control through the Run Control shortcut on the Desktop of lat-btserver. |
...
Here is the (time ordered!) sequence of operatios for starting a non sysnchronized run;
...
- Launch Run Control from the Run Control shortcut. At any time you can tell the application you're running (wheter it's normal or no synch) by the title of the X terminal popping up along with the Run Control main GUI.
- Make sure that the User is the Run Control Main GUI is properly set.
- Make sure the front ends are powered up and the detectors are biased.
- Select the end2endBT.py application.
- Sit in front of the ancillary DAQ machine (wkxglast1) and start the acquisition by entering the command:
No Format > ACQmain
You will be prompted to insert the number of events to be acquired and you'll have to properly start the run from a specific GUI (refer to the separate documentation for more details). Wait until the following message is prompted:No Format Starting server socket on port 2345 -> waiting for a client...
- Go back to lat-btserver and press the start button in the Run Control main GUI.
- Fill out ALL the fields in the GUI which is prompted to you for collecting the run information and press OK in the GUI itself.
- Wait until the event counter on the right end of the Run Control GUI is incremented to one (it may take quite a few seconds for that) and the status changes from UNDEFINED to PASSED. At this point the system is really ready to start.\
- Back again to wkxglast1 and, when prompted with the message
No Format Press enter when RC is ready
follow the instruction and press enter. - Put all relevant run-related information into the e-logbook.
- The run should stop by itself when the number of events preset in the ancillary DAQ has been collected (neve press the STOP button, remeber!). At thet point Run Control should pass automatically into the RESET state and the system is ready .
- Restart Run Control for a new run.
Starting a NON synchronized (standalone CU) Run
| No Format |
|---|
This assumes that the user launches Run Control through the Run Control No Synch shortcut on the Desktop of lat-btserver. |
...
Here is the (time ordered!) sequence of operatios for starting a non sysnchronized run;
...