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

Remove tracker position dependency, add wire/straw position info #125

Merged
merged 2 commits into from
May 21, 2024

Conversation

bonventre
Copy link
Contributor

@brownd1978
Copy link
Contributor

What is this PR waiting on? New digis?

@bonventre
Copy link
Contributor Author

Once I fix the new conflicts it should be ready

@bonventre bonventre marked this pull request as ready for review April 19, 2024 17:26
Copy link
Contributor

@brownd1978 brownd1978 left a comment

Choose a reason for hiding this comment

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

A presentation to describe the intended use cases for these new leafs and how they will appear with old/new digis would be helpful.

@brownd1978
Copy link
Contributor

my understanding is this change requires new mcs files. As such it shouldn't be merged until those are available (after the re-digitization campaign).

@brownd1978
Copy link
Contributor

brownd1978 commented May 16, 2024

We now have significant samples of MDC2020 collections digitized with the data needed for these changes. Mixed samples are in preparation. Are we ready to merge this PR? In particular, are there any risks or warnings we need to give to users about how this affects their analysis of older collections?

mcs.mu2e.CeEndpointOnSpillTriggered.MDC2020ae_best_v1_3.art
mcs.mu2e.CosmicCRYExtractedCatTriggered.MDC2020ae_best_v1_3.art
mcs.mu2e.CePlusEndpointOnSpillTriggered.MDC2020ae_perfect_v1_3.art
mcs.mu2e.CePlusEndpointOnSpillTriggered.MDC2020ae_best_v1_3.art

@bonventre
Copy link
Contributor Author

We should be ready to merge. I've added instructions to https://mu2einternalwiki.fnal.gov/wiki/CalibrationSets for how to configure the database to run reco on v1_1 digi datasets and maintain consistent reconstruction and MC truth information. Older reco datasets will require using a previous TrkAna release.

@brownd1978
Copy link
Contributor

brownd1978 commented May 16, 2024 via email

@brownd1978
Copy link
Contributor

brownd1978 commented May 16, 2024 via email

@AndrewEdmonds11
Copy link
Collaborator

Sorry, I missed this discussion (I will update my notifcation settings). I think we should tag the current head as v05_01_00 just in case anyone wants to run on the older datasets with any of the recent TrkAna updates (e.g. a working MakeClass). Then I will merge this PR and tag v05_02_00.

I will also ask for the releases TrkAna v05_02_00 backing to MDC2020ae and TrkAna v05_01_00 backing to MDC2020ac (the same backing as v05_00_00)

I will also note on the TrkAna wiki page which should be used with which

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.

None yet

3 participants