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

Handling of EFlowTrack, EFlowPhotons, EFlowNeutralHadrons? #76

Open
andresailer opened this issue May 8, 2022 · 1 comment
Open

Handling of EFlowTrack, EFlowPhotons, EFlowNeutralHadrons? #76

andresailer opened this issue May 8, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@andresailer
Copy link

andresailer commented May 8, 2022

  • Currently these are the names of the edm4hep::Track and edm4hep::Cluster collections, which can be confusing, because the actual edm4hep::ReconstructedParticles live in the "global" reco particle collection. Additionally the edm4hep::Clusters have no "real" information currently, and serve mainly as a tag.
  • Raised by FCC, proposed solution (Valentin, Thomas): Make these collections a subset collection as well and rename the edm4hep::Track and edm4hep::Cluster collection to reduce confusion.
@andresailer andresailer added the enhancement New feature or request label May 8, 2022
@tmadlener
Copy link
Contributor

As discussed at the meeting on May 10:

Technically this should be fairly straight forward to do. However, for RDataFrame analyses subset collections are essentially another relation that needs to be resolved. On the other hand @clementhelsens confirmed that this should not be a major concern and we should aim for compatibility with full sim / reco. For that we decided to do the following:

  • Look at the structure of the output of full / sim reco output for CLIC / ILC (e.g. DST or miniDST).
  • For the information that is available from Delphes there should probably be a fairly straight forward mapping of this information into that structure.
  • Finally for information that is not available from Delphes we will have to decide how to deal with that (e.g. fill with dummy values or leave empty?)

More detailed discussion will happen in this issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants