-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add surface ID member to edm4eic::TrackPoint #39
Comments
cc @c-dilks regarding the projection business |
Likely you want the acts surface id, right? |
Following this discussion on Mattermost, it was my plan to populate this field with the detector IDs defined here. However, I am having issues with the implementation (see new EICrecon branch and explanation of the problem) |
I'm not sure how we can take advantage of this feature for our particular use cases in the RICHes, but good to keep in mind in case we ever need this. CC @chchatte92 @alexander-kiselev @kkauder |
### Briefly, what does this PR introduce? This adds two data members to TrackPoint to identify the detector and surface on which the TrackPoint lies (implemented for track projections but could be used more generally). This change replaces the original change which added a single 32-bit integer. This was done following a discussion in the S&C meeting on August 23, 2023. Summary of proposed options can be [found here](https://indico.bnl.gov/event/20352/contributions/80021/attachments/49313/84184/followup_edm4eic_trackpoint_PR%20copy.pdf). ### What kind of change does this PR introduce? - [x] New feature (issue #39)
For the purposes of track projections, it would be useful to add a member to TrackPoint that could be used to store the name/ID of the detector/surface the track was projected to.
The simplest solution would be an integer member that could store the detector ID as defined in https://github.com/eic/epic/blob/main/compact/definitions.xml.
The text was updated successfully, but these errors were encountered: