cms-l1-dpg / l1certification Goto Github PK

We should be able to open also the total dead time plot, for example
https://cmswbm.cern.ch/cmsdb/servlet/ChartDeadtimeCounters?runID=306460&scalerID0=1

The shifter needs to check that dead time is not >10% for multiple LS.

Hello,

I noticed on run 320500 that the "Bpix Ready" would sometimes show a red X within the LS range that was stated and physically meaningful. It reports that LS 127-478 are meaningful, but Bpix is not ready for 148-149, 159, 169, 180, 190, 200, 210, 231, 241-242, 252, 263, 274... and more.

I've included the log file generated as well as the PFE.json file from lxplus as "PFE.txt". This file only has run 320500, but I saw this during my shift with a wide range of runs as well. I've also included the relevant section of the run log.
PFE.txt

Please let me know if there is anything else I can provide.

Thanks,

Jamal

## Run 320500 (Collisions18, fill 6998) -- L1T GOOD

Detector components: CTPPS STANDBY, CASTOR EXCLUDED, 
Physically meaningful LS range: [127, 478]
L1 key: l1_trg_collisions2018/v49

L1A Physics rate: <++>kHz
Average PU: <++>

Rates as a function of pileup:
- L1_SingleMu22                  : <++>
- L1_SingleJet180                : <++>
- L1_ETMHF120                    : <++>
- L1_HTT360er                    : <++>
- L1_SingleEG40er2p5             : <++>
- L1_SingleIsoEG32er2p5          : <++>
- L1_DoubleIsoTau32er2p1         : <++>


L1T DQM: <++>
L1TEMU DQM: <++>

Currently the script mixes cosmic and collision runs, which makes it difficult to read the resulting elogs.
See e.g. http://cmsonline.cern.ch/cms-elog/1057885

Could we order the runs according to their types? First we would have collision runs and only after that all cosmic runs.