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
Finalizing JSON monitoring for 2016 #14030
Finalizing JSON monitoring for 2016 #14030
Conversation
A new Pull Request was created by @avetisya (Aram Avetisyan) for CMSSW_8_0_X. It involves the following packages: HLTrigger/JSONMonitoring @Martin-Grunewald, @perrotta, @cmsbuild, @fwyzard, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please test |
PR for 81X needed as well. |
The tests are being triggered in jenkins. |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
This is hopefully the final form of the JSON monitoring for this year. TriggerJSONMonitoring has been split into L1TriggerJSONMonitoring and HLTriggerJSONMonitoring. The HLT JSON file is very similar to what it was (the only difference is that the prescale index is no longer stored there). The L1 JSON file is completely different: technical triggers are gone, algorithm tables are now 512 bits and the prescale index has been moved to here.
The old TriggerJSONMonitoring is still there for now so as to be able to easily revert in case we run into problems. The only change to it is the one of the namespace names. It will be deleted once the new way is proven to work.