Skip to content
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

Make the event number 64 bits and unsigned #398

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

tmadlener
Copy link
Contributor

BEGINRELEASENOTES

  • Make the EventHeader::eventNumber a 64 bit unsigned integer to avoid issues with the range of 32 bit integers.

ENDRELEASENOTES

This is another small fix that came out of the discussion with HepMC folks (and their experience from LHC). We are likely to run into issues with the range of 32 bit integers and the exepected event numbers. LHC is going beyond 32 bit range already in long runs.

@tmadlener
Copy link
Contributor Author

This breaks backwards compatibility for RNTuple as that does not have the necessary schema evolution support to do this on the fly (at least for RC2 of RNTuple).

@jmcarcell
Copy link
Member

But I guess it's quite unlikely someone has RNTuples files and a file with event headers at the same time. So recreate the RNTuple file for version 0.99 with a 64 bit event number? It will be unreadable by EDM4hep 0.99, but is that even going to happen?

@tmadlener
Copy link
Contributor Author

So recreate the RNTuple file for version 0.99 with a 64 bit event number?

Yes that is also what I would do. We should also go to the release RNTuple format there, i.e. ROOT >= 6.34, I think.

Likely to run into issues with the range of 32 bit integers and the
exepected event numbers. LHC is going beyond 32 bit range already in
long runs.
edm4hep.yaml Outdated
@@ -222,7 +222,7 @@ datatypes:
Description: "Event Header. Additional parameters are assumed to go into the metadata tree."
Author: "EDM4hep authors"
Members:
- int32_t eventNumber // event number
- uint64_t eventNumber // event number
- int32_t runNumber // run number
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the run number should be uint32_t?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants