Adding MINERvA NukeCC1pip #54
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Converting this to draft; I am double-checking the signal definition |
|
did we finish this? (sorry its taken a year to get around to looking at the PRs...) |
Hi Luke, yes I converted this to "ready for review" status. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here I added MINERvA ME, numu cc 1pi+ measurements on various targets
Table_Var_Xsec.csv) to nuisance-readable txt files;data/MINERvA/NukeCC1pip/MakeTextFiles.pyBelow are the histograms from
nuiscompthat can be compared to Fig. 2. of the paper (Solid lines are my test MC samples; here we only care about the data points):MINERvA_NukeCC1pip_CH_XSec_1Dpmu_nu_Xsec.pdf
MINERvA_NukeCC1pip_Fe_XSec_1Dpmu_nu_Xsec.pdf
MINERvA_NukeCC1pip_Pb_XSec_1Dpmu_nu_Xsec.pdf