LArG4: Sparsifying sometimes cuts out 2nd to last trajectory point
In larg4's ParticleListAction, the final trajectory point is always defined to have ~0 KE. The true ending information can usually be recovered by accessing the 2nd to last point. However, Sparsifying has a chance to cut this out based on the positions of the traj points.
One fix is to change the Sparsify method in MCTrajectory to preserve the last 2 points rather than just the final point (this will add, at most, one point to the trajectory object after sparsification) but a fix might be available right in the ParticleListAction. I'll investigate more today, but wanted to bring this to attention.
#5 Updated by Jacob Calcutt about 1 month ago
There's a feature branch (feature/drivera_store_penultimate_point) in nusimdata with these changes. These are ready to be merged in.
Some changes will also have to be made in LArG4, but the ones in nusimdata have to be done first of course. Should I submit a pull request in LArG4 and refer to this, or should I just wait until this is merged in?