MCParticle dependency
Currently we depend on the full history of every PixelHit
including thousands of PropagatedCharge
s in order to be able to access the MCParticle
ancestry. At some point it would be nice to change this so we can simply store the two and keep their relation.
As this also holds true for previous steps, maybe it would be useful to always relate the ancestor MCParticle
to new objects?