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

Synchronizing name for the Cell ID encoding string #32

Closed
wants to merge 2 commits into from

Conversation

kjvbrt
Copy link

@kjvbrt kjvbrt commented Oct 30, 2023

BEGINRELEASENOTES

  • Synchronizing name for the Cell ID encoding string between the converter and k4RecCalorimeter algorithms

ENDRELEASENOTES
Found by:
@SwathiSasikumar and @Zehvogel

@andresailer
Copy link
Contributor

@tmadlener
Copy link
Contributor

tmadlener commented Oct 30, 2023

I don't know why but the String suffix was at some point added during the conversion, and then also ended up in the k4FWCore DataHandles (here). I tried to synchronize this as much as possible and also to stay with the same name as LCIO as much as possible. I think this should now only be accessible with Legacy components and using Frame based I/O (and the MetaDataHandles) everything should be consistent again.

@andresailer
Copy link
Contributor

I tried to synchronize this as much as possible and also to stay with the same name as LCIO as much as possible.

This == CellIDEncoding?

I think this should now only be accessible with Legacy components and using Frame based I/O (and the MetaDataHandles) everything should be consistent again.

This == ?????

@andresailer
Copy link
Contributor

https://github.com/HEP-FCC/k4SimGeant4/blob/7f1dd936fc0442d1023bb63b0585ce2785170839/Detector/DetComponents/src/RedoSegmentation.h#L70-L72

The LAr digitiser don't write to the MetaData frame, or is that ending up in the same place?

@tmadlener
Copy link
Contributor

I tried to synchronize this as much as possible and also to stay with the same name as LCIO as much as possible.

This == CellIDEncoding?

Yes, exactly.

I think this should now only be accessible with Legacy components and using Frame based I/O (and the MetaDataHandles) everything should be consistent again.

This == ?????

In this case the name of the parameter would be CellIDEncodingString, but it will only be accessible with Legacy components, and will simply throw an exception if tried on a DataHandle otherwise.

In the LAr digizer the name of the MetaDataHandle needs to be changed to CellIDEncoding and things should work (:crossed_fingers:) . MetaDataHandles write to the metadata frame.

@andresailer
Copy link
Contributor

As discussed in the Key4hep meeting today, we are going to converge on CellIDEncoding without the String and key4hep/EDM4hep#234 will help to keep things consistent.

@andresailer andresailer closed this Nov 1, 2023
@kjvbrt kjvbrt deleted the cell_id_string branch November 1, 2023 16:53
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.

3 participants