Skip to content

CC Analysis Branch#382

Open
jminock wants to merge 10 commits intoANNIEsoft:Applicationfrom
jminock:CCPR
Open

CC Analysis Branch#382
jminock wants to merge 10 commits intoANNIEsoft:Applicationfrom
jminock:CCPR

Conversation

@jminock
Copy link
Copy Markdown
Collaborator

@jminock jminock commented Apr 6, 2026

Describe your changes

PR that encompasses Tools used for CC Analysis. All CC Analysis related plots come from ntuples generated from this ToolChain. All changes from original CC branch have been rectified and merged in such that THIS branch/PR will generate identical files to those used for the CC analysis. Once again, THIS TOOLCHAIN HAS BEEN TESTED AND MATCHES THE ESTABLISHED CC PHYSICS ANALYSIS.
Added Tools:
Charge Isotropy - returns a value representing the isotropy of the charge in the tank, useful for 0pi selection
CCMCRecoEventLoader - like MCRecoEventLoader but hacked up to provide additional truth information of other particles. I made a new Tool because it diverged too far from the original.
CCMCCorrections - provides correction factors to the MRD and Dirt muon scaling as presented. Corrections and uncertainties are unique to CC Analysis. But infrastructure exists if one wanted to do their own corrections.
Documentation for my ToolChain does NOT CURRENTLY exist. I wanted to include this for reference purposes so any internal notes can link back to a specific tag/PR/commit. I plan to fill out the README files and make a low-level guide for ALL my code after/during paper writing.

Checklist before submitting your PR

  • This PR implements a single change (one new/modified Tool, or a set of changes to implement one new/modified feature)
  • This PR alters the minimum number of files to affect this change
  • If this PR includes a new Tool, a README and minimal demonstration ToolChain is provided
  • If a new Tool/ToolChain requires model or configuration files, their paths are not hard-coded, and means of generating those files is described in the readme, with examples provided on /pnfs/annie/persistent
  • For every new usage, there is a reason the data must be on the heap
  • For every new there is a delete, unless I explicitly know why (e.g. ROOT or a BoostStore takes ownership)

Additional Material

Attach any validation or demonstration files here. You may also link to relavant docdb articles.

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.

1 participant