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

Add stacking action options #218

Open
tdixon97 opened this issue Jan 2, 2025 · 1 comment · May be fixed by #222
Open

Add stacking action options #218

tdixon97 opened this issue Jan 2, 2025 · 1 comment · May be fixed by #222
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@tdixon97
Copy link
Collaborator

tdixon97 commented Jan 2, 2025

It might be nice to give the user the possibility to kill certain tracks, for example betas or alphas for sources where we only care about gammas. Consider eg. simulations for HPGe screening.
This could be done with a custom stacking action.
An alternative approach would be custom production cuts for different regions/ volumes (sounds more tricky to me).

@tdixon97 tdixon97 added enhancement New feature or request help wanted Extra attention is needed labels Jan 2, 2025
@EricMEsch
Copy link
Collaborator

This can be done pretty easily by just adding an optional OutputScheme, as they have a hook into RMGStackingAction::ClassifyNewTrack() (Similar to how OpticalPhotons are treated in the current OutputSchemes). This way, they would also only be registered when activated by the user and otherwise would have no impact on performance.

Although on the other hand, i do find it quite extensive to have a whole entire OutputScheme to just filter out certain particles, which in the end is like 2 lines of code. But i guess it would be the most "structured" approach. (alternatively we could add something directly to RMGStackingAction coupled with some macros)

If no one else is working on it, i can do it if i find some time (should be really simple)

@EricMEsch EricMEsch linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants