Time-dependent histogram for monitoring SciFi hits
Implement a histogram with time (in seconds) on the x axis since the start of the Run (job), and average number of SciFi hits per layer on the y axis.
@rmatev As discussed some time ago. I don't know if the monitoring is restarted after a run change, I now made an x axis of 5000 seconds, but it might need to be more.
Needs Moore!2500 (merged)
Merge request reports
Activity
added RTA label
mentioned in merge request Moore!2500 (merged)
- Resolved by Christopher Rob Jones
/ci-test Moore!2500 (merged)
added ci-test-triggered label
- [2023-07-11 12:42] Validation started with lhcb-master-mr#8515
- [2023-07-14 11:27] Validation started with lhcb-master-mr#8546
- [2023-07-17 14:31] Validation started with lhcb-master-mr#8578
Edited by Software for LHCbadded 1 commit
- 8732c786 - fix wrong understanding of histogram filling
Ok, I'm passing it to @jonrob for merge.
@decianm ping - Are there any QMT tests that exercise this monitor ?
Anything that runs the monitoring runs this monitor, e.g.
hlt2_light_reco_pr_kf_with_mcchecking
Edited by Michel De CianTurns out this did need a ref update. See the Rec today ...
https://lhcb-nightlies.web.cern.ch/nightly/lhcb-master/2097/
assigned to @mzdybal
assigned to @jonrob
added FT Monitoring labels
@decianm I think if you want to ensure the histograms are reset on a run change, you probably need to do this yourself in the monitor, by e.g. detecting when the run changes and do a manual reset.
One other thing to bear in mind is when running at the pit, run changes as seen by any online task is not a black and white transition. Due to the way the events get sent to the monitoring from HLT1 you can get for a short period a mixture of old and new events coming. You might also need to think about how to deal with this as well.
- Resolved by Christopher Rob Jones
I think if you want to ensure the histograms are reset on a run change
What do you mean? I don't think any monitor resets histograms when there is a run change (?)
- Resolved by Christopher Rob Jones
you can get for a short period a mixture of old and new events coming
That should then affect only the last or the first bin, and I assume the overlap only exists for some events, and not for seconds in a row. So I simply assume that this effect will be small.
mentioned in issue Moore#623 (closed)
added 66 commits
-
de777024...fedc4020 - 59 commits from branch
master
- 663c1ddb - first attempt at time-dependent histogram for monitoring SciFi hits
- 8f40752b - Fix wrong use of 'second'
- 34293dd0 - fix wrong understanding of histogram filling
- d1891f3c - fix for calculation of number of hits
- b9e52adb - Fixed formatting
- bbfa7cee - split histograms in top and bottom
- f0a8775c - Fixed formatting
Toggle commit list-
de777024...fedc4020 - 59 commits from branch
mentioned in commit 04416cac
mentioned in issue Moore#627 (closed)