You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Agenda

  1. ECAL online software                             — Nathan

  2. SVT  online software                              — Omar/Sho

  3. Monitoring app / db                                — Jeremy

  4. Trigger software                                     — Kyle

  5. DQM                                                       — Matt G

  6. Questions?                                               -- All

Notes

ECAL & SVT Summary:

Mostly, the existing monitoring plots are extensive, lots of plots, this has not been changed from the 2015 run. The setup is expected to work.

ECAL:

  • LED version was recently run by Andrea, and made to work.
  • Shake-down plan: 
    • Run DAQ for pedestals
    • cosmic runs. 
    • Do a gain calibration. 
    • Revisit the FEE calibration code, make sure we can run it.

Trigger: (comment from Nathan)

Trigger efficiency monitoring needs to be simplified. It should be only a few numbers for shifters to look at.  Kyle's new efficiency calculation based on the TI should be added if there's enough statistics in one run. 

SVT:

  • There is a system status plot from 2015 run. See slide 4 in Sho's Orsay talk. System checks every 5 minutes for anomaly and will ring alarm if one is found, e.g. an APV dropped out.
  • A true test of the tracker requires looking at tracks. Only DQM will give enough tracks for meaningful test, monitoring app is too slow.
  • Shake-down will happen as part of current DAQ work at JLab.

Monitoring App:

  • Jeremy will run the monitoring app and check that everything still works.
  • Jeremy will travel to JLab before the run and make sure monitoring app works in counting house. 
    • He will check DB connectivity. There should be better fail safe now.
    • He will make sure monitoring app installation is easily located and there is some startup documentation.
  • There is a list of "could be added" features. Not clear if these are worth pursuing right now.

 

Request: Save the pdf in a consistent manner. Currently the order of the plot changes depending on the tabs last looked at.

DQM:

  • The framework is OK and has been for a while.
  • There are database hooks, but these are nor really used. It is up to sub-system experts to make use of this.
  • Lots and lots of plots, probably too many. Some re-organization of plots could be useful to make checking easier.
    • ECAL plots need to be looked at and improved (question)
  • Some "quantities" are calculated. These should probably go into the DB.

Running DQM:

  • Steering file in same batch job as processing data.
  • Runs slow because processing is slow. The suggestion is to only process 10k events per file in near real time.
  • Output should be AIDA and ROOT files.
    • Scripts to sum these output histograms for a run would be useful.

Organization:

  • We really need a DQM Coordinator. Get fame and glory while working from the comfort of your own home! Sign up now!
  • This needs buy-in from the sub-system experts.
  • Matt G will be able to mentor the new DQM Coordinator to get started.

 

 

 

  • No labels