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
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).
The text was updated successfully, but these errors were encountered:
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)
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).
The text was updated successfully, but these errors were encountered: