Fix issues with ROOTService
@dovombru and I had the some idea as clear from !728 (closed). I went a bit further and refactored the ROOTService to only open ROOT files once and write TTrees once at the end instead of for each batch of events.
In addition, a property has been added to disable the tree writing by default in the KsToPiPi
and RICH1Calibration
lines. For the stack/production builds ROOT will always enabled and making tuples should not be enabled.
To avoid a crash in the SVMonitor
it has been disabled. That monitoring code needs to anyway be migrated to a dedicated monitoring algorithm to properly take into account event masks.
Closes #289 (closed)
Merge request reports
Activity
requested review from @dovombru
- Resolved by Roel Aaij
- Resolved by Dorothea Vom Bruch
- Resolved by Dorothea Vom Bruch
- Resolved by Roel Aaij
removed review request for @raaij
assigned to @raaij
added 2 commits
added RTA label
assigned to @abrearod
mentioned in merge request !728 (closed)
mentioned in issue Moore#362 (closed)
added hlt1-throughput-decreased label
added 1 commit
- 27b4349b - Refactor to use the same monitoring file everywhere except the checkers
removed hlt1-throughput-decreased label
added hlt1-throughput-decreased label
- Resolved by Rosen Matev
/ci-test
added ci-test-triggered label
- [2021-12-20 15:13] Validation started with lhcb-master-mr#3381
- [2022-01-10 19:57] Validation started with lhcb-master-mr#3411
Edited by Software for LHCbremoved hlt1-throughput-decreased label
added hlt1-throughput-decreased label
removed hlt1-throughput-decreased label
added hlt1-throughput-decreased label
removed hlt1-throughput-decreased label
@raaij could you rebase on master, which should hopefully fix the pipeline?
added 14 commits
Toggle commit list- Resolved by Rosen Matev
thanks! The last test was already okay but let's give it a final spin
/ci-test
added hlt1-throughput-decreased label
removed hlt1-throughput-decreased label
added Monitoring bug fix hlt1-throughput-decreased labels
mentioned in commit 501ae5a5
mentioned in issue #289 (closed)
mentioned in issue Moore#375 (closed)
mentioned in issue Moore#377 (closed)