CPP DAQ/Monitoring Test Spring 2022

From GlueXWiki
Jump to: navigation, search

Overview

These are plans for some short tests to be done prior to the start of data taking to establish that the DAQ and online monitoring systems are configured and working properly. This will be done in 2 parts:

  1. DAQ Cosmic test: This will exercise the full DAQ and online monitoring systems using cosmic rays. It will ensure all detectors are being read out and that the data is being both stored properly on tape and passed through the online monitoring system.
  2. Online Monitoring High Rate Test: This will pass raw data files through the monitoring system at high rate to ensure the online monitoring is working and that the new plugins function properly under high rate.


Schedule

Important dates

  • Mon. May 9 : AI/ML models trained and installed on gluons (Andrew, Nikhil, David)
  • Tue. May 10 : Drift Chamber Atmospheric Pressure Alarm active (Naomi, David, Hovanes)
  • Thu. May 12 : FMWPC_online, and FMWPC_performance production histos and macros in GitHub (all)
  • Fri. May 13 : AIEC run-sync'd HV control tested (Thomas, David)
  • Mon. May 16 : halld_recon updated and plugins built (Alex)
  • Tue. May 17 : DAQ Cosmic Test starts (let run until 5/19 or 5/20)
  • Fri. May 20 : Online Monitoring High Rate Test
  • Mon. May 23 : GlueX - software/analysis tutorial for students
  • Tue. May 24 : GlueX - Collaboration meeting starts (ends 5/26)
  • Mon. Jun 6 : CPP run starts

DAQ Cosmic Test configuration: May 17

  1. Use the standard DAQ configuration for CPP.
  2. Solenoid OFF
  3. BCAL, CDC, FDC, TOF, FCAL, FMWPC, CTOF all on
  4. Trigger: TOF, CTOF, BCAL-cosmic
  5. Online monitoring, HOSS, and Incoming Data systems active
  6. AIEC CDC dynamic control active (fully automated, not run-sync'd)
  7. Establish run and allow to continue for ~2-3 days in order to gather large cosmic data set

Online Monitoring High Rate Test configuration: May 20

  1. DAQ system OFF (data will come from pre-existing files)
    •  ?? Can we start DAQ but pause run and feed from file into DAQ's ET system??
  2. Online monitoring, HOSS active*
    • HOSS configuration modified to write data files to scratch directories on RAID so they do not get transferred to tape
  3. Run in high rate mode for 2-4 hours to ensure operation for normal run duration


AIEC planning

Questions/to-do things

Looking for similar HVB current from past runs RCDB search


CPP test run 60907 50nA on 47um diamond, 2 Pb sheets

HDOPS gluon47:aiec> myStats -b '2019-02-20 20:47:36' -e '2019-02-20 20:48:36' -l @epicslist_short.txt -m history
            Name               Min     Mean    Max      Sigma  
IBCAD00CRCUR6                     42 46.0022      51    1.56705
RESET:i:GasPanelBarPress1    100.671 100.688 100.693 0.00906494
GAS:i::CDC_Temps-CDC_D1_Temp      26      26      26          0
CDC:hv:A:1:imon                  1.1  1.6599     2.2   0.220041
CDC:hv:A:2:imon                  1.3 1.65102       2   0.132387
CDC:hv:A:3:imon                  1.1 1.57294     2.2   0.213989
CDC:hv:A:4:imon                  1.3  1.6482       2   0.158336
CDC:hv:A:5:imon                  1.8     1.8     1.8          0
CDC:hv:A:6:imon                  1.1 1.28011     1.5  0.0740467
CDC:hv:A:7:imon                  1.3 1.46318     1.6  0.0743186
CDC:hv:A:8:imon                  1.5 1.51575       2  0.0873408


CPP test run 60900 50nA on 47um diamond, 1 Pb sheet

HDOPS gluon47:aiec> myStats -b '2019-02-20 17:44:03' -e '2019-02-20 17:45:03' -l @epicslist_short.txt -m history
            Name               Min     Mean    Max     Sigma  
IBCAD00CRCUR6                   49.5 52.9538    55.5   1.34659
RESET:i:GasPanelBarPress1    100.758 100.758 100.758         0
GAS:i::CDC_Temps-CDC_D1_Temp      26      26      26         0
CDC:hv:A:1:imon                  1.7 1.87625       2 0.0786569
CDC:hv:A:2:imon                  1.9 1.93592       2 0.0479752
CDC:hv:A:3:imon                  1.8 1.87775       2  0.056745
CDC:hv:A:4:imon                  1.7 1.86677       2 0.0625312
CDC:hv:A:5:imon                  1.9 1.96803       2 0.0466378
CDC:hv:A:6:imon                  1.3 1.52555     1.6 0.0747073
CDC:hv:A:7:imon                  1.5 1.70936       2  0.093217
CDC:hv:A:8:imon                  1.5 1.96266       2  0.131439


GlueX luminosity scan run 51679 50nA on 4.5e-4 Al

HDOPS gluon47:aiec> myStats -b '2018-11-22 19:00:37' -e '2018-11-22 19:01:37' -l @epicslist_short.txt -m history
            Name               Min    Mean    Max    Sigma  
IBCAD00CRCUR6                  43.5 49.2407     54   1.96851
RESET:i:GasPanelBarPress1    101.87  101.87 101.87         0
GAS:i::CDC_Temps-CDC_D1_Temp     26 26.0656   26.1 0.0474937
CDC:hv:A:1:imon                 1.1  1.3736    1.6 0.0833091
CDC:hv:A:2:imon                 1.3 1.45188    1.8 0.0906597
CDC:hv:A:3:imon                 1.2 1.38985    1.7  0.065498
CDC:hv:A:4:imon                 1.1 1.30549    1.5 0.0836216
CDC:hv:A:5:imon                 1.2  1.4653    1.5 0.0569653
CDC:hv:A:6:imon                 0.9 1.08219    1.3 0.0785599
CDC:hv:A:7:imon                   1 1.23875    1.4 0.0905561
CDC:hv:A:8:imon                 1.5     1.5    1.5         0


Better Look Back Ideas

  • Beam has been so unstable that many of the EPICS-gatherings were made when the beam had tripped.
  • Fortunately CPP beam current is so low that this only makes a little difference to the HVBi this time.
  • The HVBi during initialization should be reliable, as one of us performs the initialization while watching the beam current to make sure that it is stable. This would be more difficult with a longer look-back.
  • Usually the experiment aims to keep the flux & rates constant, so the beam current could be considerably different between full and empty target runs, or between diamond and amorphous, however the HVB current should be similar.
  • Using a longer lookback could give a lower mean if the beam is part on, part off.
  • Should the AI be used during special tasks like intensity scans? I'm not sure now.
  • Possible strategies:
    1. Implement a more intelligently timed EPICS gathering, to avoid beam trips.
      1. Repeat the EPICS-gathering again and again until beam current sigma is less than some threshold.
      2. Look back repeatedly for short chunks (5 sec) until the HVBi agrees with initialized value (or some time limit is reached).
      3. Use the HVBi from initialization if the measured HVBi looks fishy (fishy = more than how much different from initial value, 20%?)
    2. Use max HVBi instead of mean HVBi and use a longer look-back time (1 minute?). Would this require re-training?
    3. Use the code that is used to calculate beam_on current for RCDB, adapt that to give beam_on HVBi.
    4. Fix the HVBi at the value found during initialization value throughout the run. If the experimental program has a planned large change in data rate, re-initialize. This is Naomi's preferred option as it seems simple and foolproof.

Actual plan

  1. Done. Thomas: share location of init script.
  2. Done. Naomi: find location of HV graph scripts. ~/aiec/hvscan21/fit_hv.C
  3. Done. Naomi: add the initialization instructions to the CDC HV scan instructions. It could be done during the 2125V run, or during Sean's detector checkout. Done
  4. All: Look to see what the HVB current is after the initialization, stored in /group/halld/AIEC/utilities/CDC_control_ai/cpp/AIEC_CDC.cfg
  5. Naomi: redraw the relative HV graph after the HV scan. Hopefully it will be exactly the same as previously. Adjust the function if not.
  6. Activate the AI after the detector checkout (if that is after the HV scan).