Closed PetrilloAtWork closed 5 months ago
:flushed: There was clearly an issue with my final branching (noted the three PR in a row coming from the same working area?). In fact, I pretty much lost the source of this PR, except that luckily I had tarballed it for grid jobs.
I have updated it now... thank you for catching this!!
There may or may not be a following commit rebasing this same code to the current develop
branch.
trigger build
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard
:x: CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard
:rotating_light: For more details about the failed phase, check the build ICARUS phase logs
parent CI build details are available through the CI dashboard
:x: CI build for ICARUS Failed at phase build ICARUS on slf7 for e26:prof -- details available through the CI dashboard
:rotating_light: For more details about the failed phase, check the build ICARUS phase logs
parent CI build details are available through the CI dashboard
trigger build
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard
:x: CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard
:rotating_light: For more details about the failed phase, check the build ICARUS phase logs
parent CI build details are available through the CI dashboard
:x: CI build for ICARUS Failed at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard
:rotating_light: For more details about the failed phase, check the ci_tests ICARUS phase logs
parent CI build details are available through the CI dashboard
trigger build
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard
:heavy_check_mark: CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard
:x: CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard
:rotating_light: For more details about the failed phase, check the build ICARUS phase logs
parent CI build details are available through the CI dashboard
:warning: CI build for ICARUS Warning at phase ci_tests ICARUS on slf7 for e26:prof - ignored warnings for build -- details available through the CI dashboard
:rotating_light: For more details about the warning phase, check the ci_tests ICARUS phase logs
parent CI build details are available through the CI dashboard
With the new adder-based trigger, the PMT diagnostic tree should know whether the light collected at beam gate was coming from an adder or a majority trigger. This commit adds that information to the tree, one piece of information per cryostat, directly from the trigger information.
Edit: it also adds a count of triggers from the beginning of the run and the gates from the previous trigger. This tree is being used for trigger studies as well. And a job configuration to create such trees, for the benefit of grid jobs.
Reviewer: @mvicenzi as PMT decoder insider.