Trigger Emulation Bug Fix and smaller updates#885
Conversation
… over threshold vector to events, updated Baseline to Run 2 Baseline, and checks that we are not considering any XArapuca channels
fjnicolas
left a comment
There was a problem hiding this comment.
Thanks @npallat for putting this in!
My request before this gets in is reverting back to use run 1 baseline, since currently all our processing is based on run 1.
I left some other suggestions that I think should get address before a full scale production, but given the time constraint for the validation II samples I'd rather getting this in by now. Any thoughts @nathanielerowe @linyan-w?
| // resize | ||
| int ReadoutSize = fWaveforms[0].size(); | ||
| int ReadoutSize; | ||
| if (PMT_Channels.empty()) { std::cout<<"Warning: Please provide PMT channels list."<<std::endl; ReadoutSize = fWaveforms[Pair1[0]].size(); } |
There was a problem hiding this comment.
Is the cout here really a warning? It is expected that the PMT_Channels vector is empty when you call it fom the PMTDecoder module.
There was a problem hiding this comment.
The PMTDecoder has to assign the ReadoutSize differently because it is using data not MC:
int NumFlash = fWaveforms.size() / (fTotalCAENBoards * PMTPerBoard);
int FirstReadoutIndex = 0 + FlashCounter*PMTPerBoard + 0*PMTPerBoard*NumFlash;
int ReadoutSize = fWaveforms[FirstReadoutIndex].size();
I could change this to just assign the ReadoutSize as ReadoutSize = fWaveforms[Pair1[0]].size() though since a warning will appear later when we loop through the channels if PMT_Channels is empty.
|
thanks for the catch @asanchezcastillo! my suggestion then is:
Otherwise we'd need to have two configurations for the TriggerEmulation service, one for data, one for MC. |
…gitizerSBND_module.cc
fjnicolas
left a comment
There was a problem hiding this comment.
Thank you so much Nikki! Ready for CI!
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_14_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06 SBNSoftware/sbn*@SBN_SUITE_v10_14_00 |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
❌ CI build for SBND Failed at phase build SBND on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build SBND phase logs parent CI build details are available through the CI dashboard |
|
❌ CI build for SBND Failed at phase ci_tests SBND on slf7 for e26:prof - ignored failure for unit_test -- details available through the CI dashboard 🚨 For more details about the failed phase, check the ci_tests SBND phase logs parent CI build details are available through the CI dashboard |
|
trigger build LArSoft/lar*@LARSOFT_SUITE_v10_14_00 SBNSoftware/sbndaq-artdaq-core@v1_10_06 SBNSoftware/sbn*@SBN_SUITE_v10_14_00 |
|
✔️ CI build for LArSoft Succeeded on slf7 for e26:prof -- details available through the CI dashboard |
|
✔️ CI build for LArSoft Succeeded on slf7 for c14:prof -- details available through the CI dashboard |
|
❌ CI build for SBND Failed at phase build SBND on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build SBND phase logs parent CI build details are available through the CI dashboard |
|
🚨 For more details about the warning phase, check the ci_tests SBND phase logs parent CI build details are available through the CI dashboard |
|
Approved |
Description
Trigger Emulation Bug Fix includes:
Checklist
Reviewers,AssigneesDevelopementThis affects the ongoing validation release.
Relevant PR links (optional)
Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
It does not require merging with another PR. However, here is a link to the original PR including this work, for reference.
Link(s) to docdb describing changes (optional)
Is there a docdb describing the issue this solves or the feature added?
Here is a relevant presentation about this to the Trigger Working Group meeting.