Add/update MicroBooNE samples#111
Open
mastbaum wants to merge 64 commits into
Open
Conversation
Implementing 2022 BNB Nue CC0pi Measurement
Fixed 0p vs Np signal definition in NueCC0pi
Code and data release provided by D. Barrow. Co-authored-by: D. Barrow <daniel.barrow@physics.ox.ac.uk>
Remove 2023 MicroBooNE_CC1ENp_XSec_1D_nu
* Implementing 2022 BNB NueCC0pi * Removing print statements used for debugging * Fixed 0p vs Np signal definition in NueCC0pi --------- Co-authored-by: Sarah Hawkins <shawkins@uboonegpvm01.fnal.gov>
…o mastbaum_cc2p-merge
…'t a function of bin number: validated against AR23-20i GENIE v 3_4_0
configuration file format for the bin definitions that matches the one used by the original analysis code. Also update the signal definition based on the latest version of the 2D CC0piNp analysis.
class. This will enable a check for double-counting effects.
…ev. D 112, 112004 (2025).
MicroBooNE_CC1MuNp_XSec_2025_nu
…ooNE CC0piNp measurement
mode strings when creating per-slice mode histogram names. The MicroBooNE_CC1MuNp_XSec_2025_nu class now reproduces chi^2 values from the publication. This was tested using the same NEUT input file that was used for the original paper.
Use a more predictable format for MicroBooNE measurement names, like:
MicroBooNE_[BEAM]_[FLAV][CCNC][CHANNEL]_[YEAR]_XSec_nu
Renamed new and existing classes accordingly:
MicroBooNE_NCpi0_XSec_nu/MicroBooNE_BNB_NCpi0_2024_XSec_nu
MicroBooNE_CCInc_XSec_2DPcos_nu/MicroBooNE_BNB_NumuCCInc_2019_XSec_nu
MicroBooNE_CC1MuNp_XSec_1D_nu/MicroBooNE_BNB_NumuCC0PiNp_2020_XSec_nu
MicroBooNE_CC1mu2p0pi_XSec_1D_nu/MicroBooNE_BNB_NumuCC0Pi2p_2022_XSec_nu
MicroBooNE_CC1Mu1p_XSec_1D_nu/MicroBooNE_BNB_NumuCC1p_2023_XSec_1D_nu
MicroBooNE_CC1Mu1p_XSec_2D_nu/MicroBooNE_BNB_NumuCC1p_2023_XSec_2D_nu
MicroBooNE_CC1MuNp_XSec_2025_nu/MicroBooNE_BNB_NumuCC0PiNp_2025_XSec_nu
MicroBooNE_CC1Mu3DInc_XSec_nu/MicroBooNE_BNB_NumuCCInc_2023_XSec_3D_nu
MicroBooNE_CC1Mu0pNp_XSec_nu/MicroBooNE_BNB_NumuCC0pNp_2024_XSec_nu
Add a paper reference and DOI to the sample description for all MicroBooNE measurements.
Remove debugging couts, add citation, normalize formatting.
Move the measurement-specific signal definition code into each measurement's isSignal function, rather than standalone functions in a separate source file.
|
There is a bug where the ROOT file is not updated. L539 in MicroBooNE C++ file for 2023 CC1mu1p should say: std::string inputFileName = FitPar::GetDataBase() + |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
This pull request adds a few new MicroBooNE measurements and updates the existing ones.
These and the existing measurements follow some new conventions:
Also included is some slight refactoring (e.g., moving signal definitions into their respective measurement classes) and some new MicroBooNE-specific helper code for ease of adding future measurements.