You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From conversation with @henrylay97: our current "standard" fhicl workflow has become messy and would need a major refactoring in the near future. This issue is just to remind ourselves to work on that after the about to start workshop production and before the next mayor production.
What data products do we want/need to keep after G4?
It may be different for the different workflows we currently have available (legacy gen+g4, rockbox, recently added scrubs, recently added Wire Cell...)
We'd probably need to differenciate what's needed for production level vs user level
Revisit what's drop by the lite fhicls
Standarize a workflow for WC?
Better organize the fhicl directories foe each stage
E.g. standard/g4 currently has more than 100 fhicls. It makes complicated to easily find the relevant/essential fhicls. Maybe add more subdirectories for each specific set of fhicls (eg recomb_variations, timelife_variations, etc)
One thing I have already thought to add to this when we do this is try and move things that are high level reco that currently reside in cafmaker into reco2 (things like PID tools, CRUMBS, MCS etc).
From conversation with @henrylay97: our current "standard" fhicl workflow has become messy and would need a major refactoring in the near future. This issue is just to remind ourselves to work on that after the about to start workshop production and before the next mayor production.
A non complete list of things to do:
scrubs
, recently added Wire Cell...)lite
fhiclsTo be discussed in AI meetings.
The text was updated successfully, but these errors were encountered: