-
Notifications
You must be signed in to change notification settings - Fork 31
Feature/icarus bnb only #523
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
base: develop
Are you sure you want to change the base?
Conversation
Updates from develop
catch up w/ develop
Might need an additional PR to account for changes in the icarus pot label, still in the process of figuring out where that would be stored. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder the sense of leaving modules that are now plainly experiment-specific in sbncode
.
Comments on POTTools.h
:
- Thank you for extracting the common code, it's very useful and I hope will save time in the future.
- Could you move the description of the functions from the comments in the implementation file to the header in Doxygen format?
- I feel these functions may be better enclosed in their own namespace. In particular, a class named
TriggerInfo_t
can contain many different things, and I am not sure if we want to commit thesbn::TriggerInfo_t
name to this one (I can count at least threeTriggerInfo_t
in the ICARUS code stack, two are class members and one isicarus::trigger::details::TriggerInfo_t
); proposal:sbn::pot
(module files are allowed tousing namespace sbn::pot;
, although I still recommend against it).
TimePadding: 0.0333 #unit seconds, Booster Rep Rate is 15 Hz, so the closest spill could be 66ms away | ||
BESOffset: 0.036 #unit seconds, we expect the BES to be about 35 ms from $1D. Need to adjust search range accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️ From some tests it appears to be about 35.746 ms in ICARUS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is set now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(now you are going to kill me...)
My intention was to confirm the value that you inserted. On one side, 1 ms does not matter since when we match to the database we have elements 66 ms apart. On the other, if you put a number with four significant digits, that begs a reference, possibly something more reliable than "Gianluca wrote so in a chat"; I have not presented that value publicly yet, and I don't know when I will (and if then I will be told I did it all wrong).
In fact, also the previous 0.036
begs for a reference, just less loudly.
If nothing better, you can cite SBN DocDB 40669. Which does not exist, but I promise it will at a certain point in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries, references are always better to have than not imo, so I will put that link in when I get a chance.
sbncode/BeamSpillInfoRetriever/ICARUSBNBRetriever/ICARUSBNBRetriever_module.cc
Outdated
Show resolved
Hide resolved
sbncode/BeamSpillInfoRetriever/ICARUSBNBRetriever/ICARUSBNBRetriever_module.cc
Outdated
Show resolved
Hide resolved
sbncode/BeamSpillInfoRetriever/ICARUSBNBRetriever/ICARUSBNBRetriever_module.cc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have left one more comment that the author can take action upon, but I consider the PR approved.
trigger build |
✔️ 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 |
❌ CI build for ICARUS Failed at phase build ICARUS on slf7 for c14:prof -- details available through the CI dashboard 🚨 For more details about the failed phase, check the build ICARUS phase logs parent CI build details are available through the CI dashboard |
🚨 For more details about the warning phase, check the ci_tests ICARUS 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 |
|
||
process_name: BNBInfoGen | ||
process_name: ICARUSBNBInfoGen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative proposal following the suggestion from SBNSoftware/icaruscode#823:
process_name: ICARUSBNBInfoGen | |
process_name: BNBInfoGen |
@@ -28,17 +28,17 @@ source: { | |||
|
|||
physics: { | |||
producers: { | |||
bnbinfo: @local::bnbspillinfo | |||
icarusbnbinfo: @local::icarusbnbspillinfo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative proposal following the suggestion from SBNSoftware/icaruscode#823:
icarusbnbinfo: @local::icarusbnbspillinfo | |
bnbinfo: @local::icarusbnbspillinfo |
} | ||
|
||
simulate: [bnbinfo ] | ||
simulate: [icarusbnbinfo ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative proposal following the suggestion from SBNSoftware/icaruscode#823:
simulate: [icarusbnbinfo ] | |
simulate: [ bnbinfo ] |
stream1: [ out1 ] | ||
} | ||
|
||
outputs: { | ||
out1: { | ||
module_type: RootOutput | ||
fileName: "%ifb_%tc_bnbinfo.root" | ||
fileName: "%ifb_%tc_icarusbnbinfo.root" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative proposal following the suggestion from SBNSoftware/icaruscode#823:
fileName: "%ifb_%tc_icarusbnbinfo.root" | |
fileName: "%ifb_%tc_bnbinfo.root" |
(the change in this PR could actually affecting the workflow by changing the output file names)
Fixes #479, restructures code so SBND BNB modules and ICARUS BNB modules can share some code. Open to feedback on the best way to handle this, since I did not write the original BNBRetriever module.