Einar Elén

This bug shows up in the workspaces function as well. Seems to come from this part of `+workspace/switch-to` ```emacs-lisp (ivy-read "Switch to workspace: " (+workspace-list-names) :caller #'+workspace/switch-to :preselect (+workspace-current-name)) ```...

Geant4 has a feature that lets you "pre-assign" decay products to particles. Would that be helpful for this? If you use this, you don't need to calculate the endpoint yourself,...

That's mixing up two things! The pre-assigned decay products are a property of `G4DynamicParticle` and it is a public method. When `G4Decay` runs, it will prioritize any pre-assigned products. G4VExtDecayer...

I think the reason for most documentation talking about primary particles is just... LHC bias. Where other than in the primary collision would you ever create weird particles

I've been looking around a bit for these things, @cmantill is a negative TOA value ever reasonable? If not, I might have an idea of where to look into

I'll mess around and see what I can find!

I went through one call to getTOA that yields a negative TOA. The loop variables unfold as seen in the end of this comment (the counter is the sample number)....

It shouldn't have been possible that it would have been caused by this update 0d1e4b437909f3c1bfee220b52f065bf1f8466da but I checked to confirm. Issue is still there.

Ok the energy is just a factor 2 larger than before. I'm guessing this is because the voltage is defined as ```c++ // set voltage as the sum of both...

That would work for me, but wouldn't that create issues for single ended readout which would then get half the energy?