Page History

...

• 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

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.

...

The GUI also show other pieces of information (XY table, trigger) automatically collected from other data sources. The shifter should make its best to make sure that information is correct, though oit cannot be manually changed from the GUI.

The giudelines provided by the GUI itself (in the form of tooltips that are pop up when the mouse is over some widget and message/error boxes) should be enough for the shifter to be able to insert the information correctly.

 Data taking: a step by step howto

...

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;

1. Make sure that the hardware trigger is properly set (look at the NIM crate at the very top of the rack; the TRG->CU cable on the output of the TTL to NIM converter - third NIM module from the left - should be linked to the TRG->DAQ DAQ VETO cable). Refer to the separate documentation for more details.

1. 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.
2. Make sure that the User is the Run Control Main GUI is properly set.
3. Make sure the front ends are powered up and the detectors are biased.
4. Select the end2endBT.py application.

...

2. Start the Ancillary DAQ by entering the command (into wkxglast1)

   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...

...

 Starting a NON synchronized (standalone CU)  Run

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;

1. Make sure that the hardware trigger is properly set (look at the NIM crate at the very top of the rack; the TRG->CU cable on the output of the TTL to NIM converter - third NIM module from the left - should be linked to the TRG->DAQ W/O DAQ VETO cable). Refer to the separate documentation for more details.

1. Launch Run Control from the Run Control No Synchshortcut. At any time you can tell the aplpication 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.
2. Make sure that the User is the Run Control Main GUI is properly set.
3. Make sure the front ends are powered up and the detectors are biased.
4. Select the end2endBT.py application.
5. Press the start button in thr Run Control main GUI.
6. 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.
7. Put all relevant run-related information into the e-logbook.
8. When happy with the run, stop the Run Control pressing the STOP button. The Run Control should direclty go into the RESET state and the system is ready for a new run.