Ancillary DAQ
This section is meant to be a practical reference for running ancillary data taking during the shifts.
Pedestal run
- working directory: /home/glast/DAQ-v3.00/CAENVMETest
- on the console write: PEDEmain
- insert when requested the number of events (suggested value 500)
- on the "Buttons Canvas" press the button:"Open Canvas"
- on the "Buttons Canvas" press the button."Start Pede"
- on the console insert a brief comment to the run
- when the run is enden press on the "Button Canvas" the button: "Stop"
- if tou want to abort the run press "Ctrl-c" on the keyboard. (In this case the threshold mask for the zero.suppression acquisition will not be saved. You need to perform again a pedestal run)
- the pedestal data will be saved in the direcotry:/home/glast/DAQ-v3.00/CAENVMETest/pede in ROOT format and in binary format,
- a text file will be produced for a quick inspection of the pedstal and noise of all the channels
Acquisiton run not synchronized with the CU
- working direcotory: /home/glast/DAQ-v3.00/CAENVMETest
- on the console write: ANCmain
- insert when reqeusted the number of events
- on the "Button Canvas" press the button:"Open Canvas"
- on the "Button Canvas" press the button."Start ACQ"
- on the console insert a brief comment to the run
- when the run is enden press on the "Button Canvas" press the button:"Stop"
- if tou want to abort the run press "Ctrl-c" on the keyboard. (all the data excpet the last spill will be saved anyway)
- the data will be saved in the direcotry:/home/glast/DAQ-v3.00/CAENVMETest/data in ROOT format and in binary format
Acquisiton run synchronized with the CU
- working direcotory: /home/glast/DAQ-v3.00/CAENVMETest
- on the console write: ACQmain
- insert when reqeusted the number of events
- on the "Button Canvas" press the button:"Open Canvas"
- on the "Button Canvas" press the button."Start ACQ"
- on the console insert a brief comment to the run
- wait a Client from RunControl ("Starting server socket on port 2345 -> waiting for a client...")
- on the console you will be prompted with: "Press enter when RC is ready"
- when RunCOntrol is on PASSED status and the sweep event has been acquired you can press "enter" to start the syncronized acqusition
- when the run is enden press on the "Button Canvas" the button: "Stop"
- if tou want to abort the run press "Ctrl-c" on the keyboard. (all the data excpet the last spill will be saved anyway)
- the data will be saved in the direcotry:/home/glast/DAQ-v3.00/CAENVMETest/data in ROOT format and in binary format.
- the data will be onlime merged with the CU data.
In case of shut down of "wkxglast1" (Ancillary ACQ PC)
- login as superuser
- go into the following directory: /usr/local/CAENVME-Rev2.4/Linux/driver/v2718
- on the console write: ./a2818_load.2.6
- logout as superuser
Directory structure
- main directory: /home/glast/DAQ-v3.00
- function direcorties: /home/glast/DAQ-v3.00/ACQFUNC - /home/glast/DAQ-v3.00/ancDAQ
- main programs directory: /home/glast/DAQ-v3.00/CAENVMETest
- data directory: /home/glast/DAQ-v3.00/CAENVMETest/data
- pedestal directory: /home/glast/DAQ-v3.00/CAENVMETest/pede
Canvas
In this canvas are shown the raw data of 4 QDC ch
1) Cherenkov 1
2) Cherenkov 2
3) NaI Front Section
4) NaI Back Section
In this canvas are shown the charge raw data of the 4 SSDs modules
1-2 SSD0 Vertical - Horizontal
3-4 SSD1 Vertical - Horizontal
5-6 SSD2 Horizontal - Vertical
7-8 SSD3 Horizontal - Vertical
In this canvas are shown the hit maps of the 4 SSDs modules
1-2 SSD0 Vertical - Horizontal
3-4 SSD1 Vertical - Horizontal
5-6 SSD2 Horizontal - Vertical (the vertical plot is inverted up-down)
7-8 SSD3 Horizontal - Vertical (the vertical plot is inverted up-down)
!
In this canvas are shown the hit maps whighted with the charge of the 4 SSDs modules
The plot is refrashed at each spill
1-2 SSD0 Vertical - Horizontal
3-4 SSD1 Vertical - Horizontal
5-6 SSD2 Horizontal - Vertical (the vertical plot is inverted up-down)
7-8 SSD3 Horizontal - Vertical (the vertical plot is inverted up-down)
In this canvas are shown the scaler counts for 3 relevant ch.
1) S0 counts per cycle (to monitor all beam intensity)
2) S0*C1*C2 counts per cycle (to monitor the elctron content of the beam)
3) HW Triggers per cycle (to monitor the acqusition rate)
In this canvas are shown the number of strips over threshold for each SSDs (to monitor the pedestal drfit of SSDs)
1) SSD0
2) SSD1
3) SSD2
4) SSD3
If this number is greater then 128 or it si 0 for a long period (more then a couple of cycles) you shuold stop the run, perform a new pedestal run and start the run again