-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the colorFlow member from the MCParticle #389
base: main
Are you sure you want to change the base?
Conversation
We do not use Vector2i or colorFlow (i.e. we use Vector2i only to set colorFlow to some default value when we have to create MCParticles). We can get rid of it and work around it with preprocessor directives on the podio version. |
We should (hopefully) also export enough information through the pre-processor for EDM4hep to check on that directly (instead of making a proxy check via podio). |
Yes, sorry, we do indeed us |
Ah we don't do that yet via the pre-processor, but it's available as a #include <edm4hep/DatamodelDefinition.h>
if constexpr (edm4hep::meta::schemaVersion > 2) {
// do something
}
|
3031db0
to
3fd0daf
Compare
99168c8
to
607629b
Compare
BEGINRELEASENOTES
colorFlow
member variable from theMCParticle
since it is effectively unused (and should remain that way as there is no really correct way to use it without baking in generator specific assumptions).edm4hep::Vector2i
from the componentsENDRELEASENOTES
This is a follow up on #237 and another discussion with generator / HepMC3 authors. The only place where
colorFlow
is used in the iLCSoft / LCIO world is the TrueJet processor. However, also in there it has remained at the idea stage of an implementation, and is not actually used.Since this is effectively generator internal information and EDM4hep is not the format to exchange data between generators we decided to remove this.
edm4hep::Vector2i
is effectively only here because of this. Should we also remove it? @wdconinc do you actually use it in EDM4eic somewhere? -> removed