Versions Compared

Old Version 11

changes.mady.by.user Luca Baldini

Saved on

compared with

New Version Current

changes.mady.by.user Carmelo Sgro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Here is a short introduction on how to launch and operate the Run Control for standard data taking. The following instructions assume that the e-logbook and the environmental monitoring are already running and - more important - the 28 V power supply which powers the CU is on.  If they're not, or you're not sure, don't continue with the below.

The last section of this page is a step by step howto  that can be used as a refernce during shifts.

...

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:

...

  • The particle type.
  • The nominal momentum of the beam.
  • The current of the bending magnet.
  • The test category (it's there for historical reason, there's no choice other than BT).
  • The test number (refer to the relative documentation for more information).

Only the following particle type are allowed:

  1. "All Particles"
  2. "Tagged Photons"
  3. "Full brem Photon'
  4. "Electrons"
  5. "Positrons"
  6. "Protons"
  7. "Pions"
  8. "Muons"
  9. "Cosmics (no beam)'
  10. "Test"

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 section is meant to be a practical reference for running data taking during the shifts. Refer to the previous sections for setails on the single items. We explicitly note that the way a run is started, again, depends on wheter the CU is operated in syncro with the Ancillary Systems of by itself (see the Launch Run Control section). 

 

  Starting a synchronized Run
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;

  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.
  2. Launch Run Control from the Run Controlshortcut. 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.
  3. Make sure that the User is the Run Control Main GUI is properly set.
  4. Make sure the front ends are powered up and the detectors are biased.
  5. Select the end2endBT.py application.
  6. 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...
     
  7. Go back to lat-btserver and press the START button in the Run Control main GUI.
  8. 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.
  9. 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. Also, the state (seen in the text box below the RESET, STOP, RUN and PAUSE buttons) should have changed from RESET or STOPPED to RUNNING.  At this point the system is really ready to start.
  10. Back again to wkxglast1 and, when prompted with the message
    No Format
    
Press enter when RC is ready
     
    follow the instruction and press enter.
  11. Put all relevant run-related information into the e-logbook.
  12. The run should stop by itself when the number of events preset in the ancillary DAQ has been collected (neve press the STOP button, remember!). At that point Run Control should pass automatically into the RESETstate. If, for whatever reason, you need to stop the acquisition, press CTRL+C on wsxglast1 first, then stop Run Control. Don't forget to record the forced stop of the run in the e-logbook!
  13. Note that in synchronized mode you should never ever push the PAUSE button.  Pausing a LATTE run will completely confuse the merging code and spoil the run.
  14. Close and restart Run Control for a new run.

 

 Starting a NON synchronized (standalone CU)  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.
  2. 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.
  3. Make sure that the User is the Run Control Main GUI is properly set.
  4. Make sure the front ends are powered up and the detectors are biased.
  5. Select the end2endBT.py application.
  6. Press the start button in thr Run Control main GUI.
  7. 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.
  8. Put all relevant run-related information into the e-logbook.
  9. When happy with the run, stop the Run Control pressing the STOP button.  Run Control should go directly into the RESET state and the system is ready for a new run.
  10. To start another run, just press the START button.  There is normally no need to exit Run Control in order to start another run.