-
Notifications
You must be signed in to change notification settings - Fork 19
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
Transfer EventHeader information to LCIO event #111
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nicely spotted the problem!
Should we consider moving the actual "conversion" to k4EDM4hep2LCIOConv and simply put the necessary Gaudi wrapper code in here? |
Yes, you are correct, we should put the "conversion" in k4EDM4hep2LCIOConv and call it from here. |
could you specificy which part of the "conversion" I should move? Should the function in k4EDM4hep2LCIOConv return the 4 values or also set them in the LCIO event? The latter would be contrary to how the other functions are while the former seems overly complicated? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "conversion" in this case is effectively the 4 lines of setting information in the LCEvent. The interface in k4EDM4hep2LcioConv should probably looks something like:
void setEventHeaderInfo(lcio::LCEventImpl* evt, const edm4hep::EventHeaderCollection* const evtHeaderColl);
so that the k4MarlinWrapper side of this would effectively boil down to getting the handle and passing it on.
I made the suggested changes and also opened key4hep/k4EDM4hep2LcioConv#13 |
Unrelated clang-format issues should be fixed with #112 |
I moved the size check + error message to this side now and got rid of the unrelated format changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Looks good to me. I would just like to have at least one successful build in CI before merging this.
2c30dd1
to
6df1c73
Compare
6df1c73
to
ff81b4e
Compare
Can we get this merged? It builds successfully in the nightlies and I think the failing test is also failing on master and caused by #113. |
BEGINRELEASENOTES
ENDRELEASENOTES
There are still some TODOs in here where I was not sure what the best option to warn the user would be.
Depends on key4hep/k4EDM4hep2LcioConv#13