-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAQ - adding DCS validity bitfield for high voltage in FED 1022 (12_1_X backport) #36296
Conversation
…ormation with the unit test
A new Pull Request was created by @smorovic (Srecko Morovic) for CMSSW_12_1_X. It involves the following packages:
@jpata, @cmsbuild, @emeschi, @smorovic, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
@cmsbuild please test |
-1 Failed Tests: UnitTests Unit TestsI found errors in the following unit tests: ---> test testDataFormatsOnlineMetaData had ERRORS Comparison SummarySummary:
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-245386/20880/summary.html Comparison SummarySummary:
|
+1 |
+reconstruction
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@smorovic this PR was not mentioned at the ORP meeting on Tuesday amongst the ones we should have waited for before building CMSSW_12_1_1. Therefore, I imagine it is not needed now (I would say so, since it is meant for data taking), and we can start building the release even without it. Please speak up in case you need it urgently in 12_1_1, instead (and justify it, in that case). |
@perotta, |
+1 |
DCS HV validity field added to the DCSRecord for discerning if information was available to the data reader.
PR validation:
Added a unittest with the FED dump containing the new format. Test was set to require status seen in the application creating the payload, and it passes.
The whole chain (input source, unpacker) was also tested on the raw file from a cosmic run (with DCS v1 only).
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport of #36294