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
As discussed offline, it would be useful to have an additional object layer between ParticleStateful and PhaseSpacePoint, something like a ParticleList. It would essentially be a wrapper around the current Tuples of in/out particles in the PhaseSpacePoint. As such it should introduce zero overhead to the existing definition, both space and time-wise.
It would also allow the utility (such as the type checking/assembling, definitions, and construction from coordinates) to be used elsewhere, for example in QEDevents when generating multi-particle samples.
The text was updated successfully, but these errors were encountered:
As discussed offline, it would be useful to have an additional object layer between
ParticleStateful
andPhaseSpacePoint
, something like aParticleList
. It would essentially be a wrapper around the currentTuple
s of in/out particles in thePhaseSpacePoint
. As such it should introduce zero overhead to the existing definition, both space and time-wise.It would also allow the utility (such as the type checking/assembling, definitions, and construction from coordinates) to be used elsewhere, for example in QEDevents when generating multi-particle samples.
The text was updated successfully, but these errors were encountered: