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
Currently to relate two collections or objects of two collections a dedicated type is necessary. This datatype usually has a float weight as single datamember and then two OneToOneRelations to connect two objects.
edm4hep::MCRecoParticleAssociation:
Description: "Used to keep track of the correspondence between MC and reconstructed particles"Author: "C. Bernet, B. Hegner"Members:
- float weight // weight of this associationOneToOneRelations :
- edm4hep::ReconstructedParticle rec // reference to the reconstructed particle
- edm4hep::MCParticle sim // reference to the Monte-Carlo particle
LCIO allows for arbitrary relations between two objects, via the LCRelation. In order to handle all of the relations that are used in the wild many new Association types have to be introduced to EDM4hep, e.g.
It might be simpler to implement a generic (templated) association or relation type in podio that then allows to use (and persist) arbitrary relations between objects.
The text was updated successfully, but these errors were encountered:
tmadlener
changed the title
Allow for arbitrary relations between two types
Allow for relations between two arbitrary types
Jan 24, 2022
Currently to relate two collections or objects of two collections a dedicated type is necessary. This datatype usually has a
float weight
as single datamember and then twoOneToOneRelation
s to connect two objects.E.g. from EDM4hep
LCIO allows for arbitrary relations between two objects, via the
LCRelation
. In order to handle all of the relations that are used in the wild many newAssociation
types have to be introduced to EDM4hep, e.g.It might be simpler to implement a generic (templated) association or relation type in podio that then allows to use (and persist) arbitrary relations between objects.
The text was updated successfully, but these errors were encountered: