Open Zehvogel opened 9 months ago
This is probably more of a podio technicality indeed ;) I am not sure if this is worth the effort, but maybe you have a more specific use case (or an example of where this would benefit things in general) in mind?
A few considerations from my side:
This might be more of a podio technicality but I think this is the better place to discuss this... In most cases associations between edm4hep objects, like the
MCRecoParticleAssociation
will always be associations between objects of a collection A and a collection B e.g. between PandoraPFOs and MCParticles. However, we store the collection ID separately for every single entry in the association collection, even though they should all have the same collection ID. It might be worthwhile to consider only saving the collection ID once and check for consistency during creation of the association collection... This would also have caught something like https://github.com/key4hep/k4MarlinWrapper/issues/113 earlier.