Add possibility to set a global time in the `DepositionPointChargeModule` (Follow-up from "Distinguish between Global and Local Timeframe")
Description
Currently, when using the DepositionPointChargeModule
, the global time of the MCParticle
is set to 0
. Timing simulations could require setting a timestamp even when using this module. See initial MR:
The following discussion from !363 (merged) should be addressed:
-
@pschutze started a discussion: (+1 comment) I wonder whether it would make sense to allow for a time to be read/set. However I don't see a clear use case yet.. Have you thought about it?
Proposal
The global timestamp could be defined via the configuration, either via a fixed value or with a dispersion.
In addition, when using the MIP
type, the particle could be propagated with the speed of light as an approximation, such that all DepositedCharge
s are assigned a local timestamp.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Discuss necessity -
Implement global timestamp -
Implement local timestamp for MIP -
Documentation -
Covered by test cases