-
Notifications
You must be signed in to change notification settings - Fork 45
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
Cosmic InTime Workflow with Refactored LArG4 #192
Conversation
…on with the new larg4
trigger build LArSoft/larg4#30,LArSoft/larsim#76 |
CI build for LArSoft on slf7 for c7:prof is in progress -- details available through the CI dashboard |
CI build for LArSoft on slf7 for e20:prof is in progress -- details available through the CI dashboard |
✔️ CI build for LArSoft Succeeded on slf7 for c7:prof -- details available through the CI dashboard |
CI build for SBND on slf7 for c7:prof is in progress -- details available through the CI dashboard parent CI build details are available through the CI dashboard |
✔️ CI build for LArSoft Succeeded on slf7 for e20:prof -- details available through the CI dashboard |
CI build for SBND on slf7 for e20:prof is in progress -- details available through the CI dashboard 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 |
✔️ CI build for SBND Succeeded on slf7 for e20:prof -- details available through the CI dashboard parent CI build details are available through the CI dashboard |
CI tests look good |
Hi @pgreen135, larsoft |
great, thanks @marcodeltutto; I saw there are some "known issues" mentioned in larsoft v09_35_00 release notes -- are these impacting this? |
@pgreen135 They are not impacting this PR or the InTime workflow in general, but they limit our ability to use larg4 if we want to have two larg4 instances in the same job (in this PR I have 2 instances, but in two separate fcls). For the dirt workflow PR #203 for example is annoying to have this issue, but it's ok to have it fixed later. |
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.
Okay, in which case this looks good from my side. I'll wait for @jzennamo to also approve before merging.
This looks excellent! One quick question, does the CI test the in-time cosmic workflow laid out here? Have we tested that it does in fact run? |
@jzennamo no, the CI does not run this -- you/Marco should definitely test this is working locally before we merge it! |
OK! I merged this branch into v09_35_00 and I'll see if I can complete the same workflows Marco laid out above |
OK, my findings: Then I ran In 4 events there is on average ~11 tracks which seems reasonable and they are reasonably distributed across the TPC. one comment, the gen stage creates a "hist file" with Save this one very minor comment I am happy for this to move forward! |
Approved! Thanks again! |
This PR adds a workflow for making intime samples with the new larg4 simulation. Fixes #147.
Depends on:
With the new larg4 we have a proliferation of modules that we need to run to get all the TPC, PDS, and CRT simulated products. It's much harder to bookkeep all of this when dealing with our intime workflow, where we first simulate in-time cosmics, then out-time ones, and then we merge them together. I made this flowchart to try and not forget anything, which I hope will be useful for the future as well.
The fcls to run are:
prodcorsika_proton_intime_filter.fcl
, orprodcorsika_proton_intime_filter_sce.fcl
g4_simphotontime_filter.fcl
standard_detsim_sbnd.fcl
and the usuals...