Skip to content
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

prodsingle scripts have hardcoded T0 arrays #99

Open
wforeman opened this issue Apr 16, 2021 · 1 comment
Open

prodsingle scripts have hardcoded T0 arrays #99

wforeman opened this issue Apr 16, 2021 · 1 comment
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed maintenance simulation genie or geant4 (g4)

Comments

@wforeman
Copy link
Contributor

wforeman commented Apr 16, 2021

Prodsingle scripts should always inherit T0, since this value is subject to change with future TPC readout and cosmic sim adjustments. Multi-particle guns currently list out the array explicitly (T0: [blah, blah..]). Is it possible to slot in a fcl parameter via @local or @sequence or @table?

@marcodeltutto
Copy link
Member

Hi Will, I can take a look at this.

I see that the T0 should be set to zero with the current configuration. I think we should define a “singles_T0” fhicl param, and then use this in every particle-gun generation. I don’t see a way to have a variable-size variable in fhicl that could work for an arbitrary number of particles - so we would have [@local::singles_T0, @local::singles_T0] for two particles, and so on. I think this is fine, the important thing is that we don’t have to type the t0 value by hand.

@marcodeltutto marcodeltutto added good first issue Good for newcomers help wanted Extra attention is needed simulation genie or geant4 (g4) labels Jun 8, 2022
@bear-is-asleep bear-is-asleep self-assigned this Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed maintenance simulation genie or geant4 (g4)
Projects
None yet
Development

No branches or pull requests

4 participants