Switching from Autotrigger Running (beam or cosmics) to LED calibration

  1. Ask the HGCAL people to stop the run. Inform them, that you are going to do the LED calibration
  2. In Labview, make sure that run is stopped
  3. go to "4) Calibration"  tab,
     in "Enable Section", set "Trig_Ext synchr. (1)" on, "TCALIB1 (5)" on and "Pre_Bias 2" off, click "Set"
  4. go to "2) System Setup" tab,
    in "II) CCC Setup", choose for "CCC mode"="HGCAL independent", click "Configure CCC"
    in "I) x-LDA Setup", set "Timestamps" off, click "Configure x-LDAs". Make sure that all LEDs in the fields "Mini-LDA >A< Config" in I) and "Probe" in II) turn to green. Otherwise call Expert.
  5. go to "3) Slow Control" tab,
    put "\ET_IC" to the field "Add suffix to path" and press "Autopopulate SCs". Press "Write SC" Afterwards. All LEDs should turn green after ~30 s.
  6. Goto tab "5) Take Data" and put detector to Lab mode by: Set "Trigger Distance" to "100" and "No. ext. Triggers" to "16". Press "Set afterwards.
  7. Switch "Temp. Compensation" off.
  8. Press "Measurement_start" in order to start a test run. No special filename has to be defined, maybe "testrun".
  9. Goto tab "Expert/Debug"
  10. Switch on the Detector Overview graph by clicking on "Occupancy On (consumes CPU)". Button turns green. The display should show 16 ASICs (intensity coloured bars ranging from 0 to 15) without any empty (white) or blinking spots between 0 and 15. Only the two not equipped layers 7 and 35 may (and do) show empty slots between 0 and 15.
  11. If there are modules that do not show complete entries 0 to 15: Go back to tab "5) Take Data". Stop the testrun by clicking "Stop data taking". Wait till the run has stopped. Go back to tab "Expert / Debug". Press "SC → ASIC". Go back to step 7 and repeat steps 7 to 9 until all modules (except Module 7 and 35) show complete bars in the display below knob "Occupancy On" ranging from 0 to 15.
  12. When all modules (except Module 7 and 35) show complete bars in the display below knob "Occupancy On" on tab "Expert / Debug", switch off the display by clicking "Occupancy On (consumes CPU)" to off (off: the knob turns red). Goto tab "Take Data" and press "Stop data taking". Wait till the testrun is stopped.
  13. Goto tab "4) Calibration" and enable (switch on) "Pre_Bias 2". Press "Set" afterwards.
  14. Goto tab "5) Data taking" and switch on "Temp. Compensation" (button turns to green). Set "Write temperature to output file" to "on" and set "Period[cycles]" to "1100".
  15. Now the detector is ready for the LED run. Start only with EUDAQ:

  16. start EUDAQ on flchcallab4 (if it is not running):
    in /home/calice/eudaq do "./STARTRUN_AHCAL_LED201810.sh"
  17. in the GUI, make sure that 3 processes have connected: DataCollector dc1, Producer AHCAL1 and LogCollector log (order is irrelevant)
  18. if EUDAQ was initialized before, following step is not necessary: make sure that "/home/calice/eudaq/conf/ahcal.ini" is the Init file (if needed, change by clicking on "Load" next to it), click "Init", wait until all processes show "UNCONF" as state.
  19. click on "Load" next to the Config file, choose "/home/calice/eudaq/conf/LED_short/LED_000.conf" (or LED_long for long run),
  20. click "Config", wait until all processes show "CONF" as state and the message says "configured"
  21. Make sure, that is can't be beam (put absorber in the beam by opening the door 172 from CESAR GUI).
  22. click on "Start"
  23. EUDAQ will go through 4 files: pedestal, and 3 LED voltages. After that it will go back to another pedestal. You can check the current LED voltage in the EUDAQ log collector, or in Labview in the "4) Calibration" tab.
  24. when you have reached the additional pedestal run, stop run after a ~20 events by clicking "Stop" in EUDAQ.
  25. in case of problems, terminate EUDAQ and re-start from step 15.
  26. Eudaq will report following errors, that can be ignored: "ERROR EB: Matching LDA timestamp information not found for ROC ...", "error: unexpected paket" and sometimes "Error: Wrongs LDA packet length" and "footer ABAB invalid"
  27. make an ELOG entry with run numbers

Now you can go back to beam settings

Switching from LED calibration to Autotrigger Running (beam or cosmics)

  1. Go back to Labview on the windows PC. Make sure on tab "5) Take Data" that the run is stopped.
  2. Goto tab "4) Calibration". Switch off "Trig_Ext synchr. (1)", "TCALIB1 (5)" and "Pre_Bias 2" (all 3 must be off). Press "Set".
  3. On the same tab "4) Calibration" in section "DACs (VCALIB)" set the drop down switch "DAC setup" to "First for all". Swich DAC1 off by pressing the knob in line DAC1 on the right hand side of the label "mV" to off. Press "Set".
  4. go to "2) System Setup" tab, in "II) CCC Setup", choose for "CCC mode"="HGCAL independent", click "Configure CCC". In "I) x-LDA Setup", set "Timestamps" on, click "Configure x-LDAs". Make sure that all LEDs in the fields "Mini-LDA >A< Config" in I) and "Probe" in II) turn to green. Otherwise call Expert.

  5. go to "3) Slow Control" tab, put "\AT_AG350_TR260_LG1200_PP2" to the field "Add suffix to path" and press "Autopopulate SCs". Press "Write SC" Afterwards. All LEDs should turn green.

  6. Goto tab "5) Take Data" and put detector to Testbeam Mode: Set "Wait for SPILL", "Validation" and "LED AT" to off. Set "Dummy Trgs" to "2" and "Meas.-Length" to "200". Press Set.
  7. switch off "Temp. Compensation" (button turns to red). Set "Write temperature to output file" to "off"
  8. Press "Measurement_start" in order to start a test run. No special filename has to be defined, maybe "testrun".
  9. Goto tab "Expert / Debug".
  10. Switch on the Detector Overview graph by clicking on "Occupancy On (consumes CPU)". Button turns green. The display should show 16 ASICs (intensity coloured bars ranging from 0 to 15) without any empty (white) or blinking spots between 0 and 15. Only the two not equipped layers 7 and 35 may (and do) show empty slots between 0 and 15.
  11. If there are modules that do not show complete entries 0 to 15: Go back to tab "5) Take Data". Stop the testrun by clicking "Stop data taking". Wait till the run has stopped. Go back to tab "Expert / Debug". Press "SC → ASIC". Go back to step 8 and repeat steps 8 to 10 until all modules (except Module 7 and 35) show complete bars in the display below knob "Occupancy On" ranging from 0 to 15.
  12. When all modules (except Module 7 and 35) show complete bars in the display below knob "Occupancy On" on tab "Expert / Debug", switch off the display by clicking "Occupancy On (consumes CPU)" to off (off: the knob turns red). Goto tab "Take Data" and press "Stop data taking". Wait till the testrun is stopped.
  13. Goto tab "4) Calibration" and enable (switch on) "Pre_Bias 2". Make sure that "Trig_Ext synchr. (1)" is off as well. Press "Set" afterwards.
  14. Goto tab "5) Take Data" and switch on "Temp. Compensation" (button turns to green). Set "Write temperature to output file" to "on" and set "Period[cycles]" to "50000". Set "Dummy Trgs" to "0". Press "Set"
  15. go to "2) System Setup" tab, in "II) CCC Setup", choose for "CCC mode"="HGCAL veto+stop+wait", click "Configure CCC".
  16. Now the detector is ready for data taking with EUDAQ, controlled from HGCAL colleagues or from our EUDAQ.


  • No labels