Changes between Version 1 and Version 2 of HowToUseNUISMIN-GENIE

Timestamp:

Jun 13, 2017, 3:05:34 PM (8 years ago)

Author:

Patrick Stowell

Comment:

--

HowToUseNUISMIN-GENIE

@@ -11 +11 @@
 [[PageOutline(1-3,Wiki content,inline,numbered)]]
 
-== Running NUISMIN == 
+= Running NUISMIN =
 
 {{{
@@ -28 +28 @@
 - [wiki:HowToUseNUISMIN-GENIE I want to use GENIE]
 
-== Running a GENIE Minimization ==
-
-=== Preparing Event Samples ===
-
-=== Choosing our samples ===
+= Running a GENIE Minimization =
+
+In this example we will take pregenerated GENIE events as our starting model and run a tuning to find a best fit value for some of the CCQE Reweight dials in GENIE ReWeight.
+
+== Generating GENIE Events ==
+If we want to see how a given GENIE model behaves, first we need to generate events. This can be done using the standard gevgen application, using the appropriate target and flux for a given data sample. 
+
+If all you want to do is check your NUSIANCE is built correctly, you can skip this step by downloading MC files from our online storage area by following the steps found here:LinkToNUISANCEMCFiles
+
+=== Running gevgen ===
+
+The standard gevgen application options can be ran using
+{{{
+ $ gevgen -h
+Syntax:
+
+      gevgen [-h]
+              [-r run#]
+               -n nev
+               -e energy (or energy range)
+               -p neutrino_pdg
+               -t target_pdg
+              [-f flux_description]
+              [-o outfile_name]
+              [-w]
+              [--seed random_number_seed]
+              [--cross-sections xml_file]
+              [--event-generator-list list_name]
+              [--message-thresholds xml_file]
+              [--unphysical-event-mask mask]
+              [--event-record-print-level level]
+              [--mc-job-status-refresh-rate  rate]
+              [--cache-file root_file]
+}}}
+
+We need to provide a flux and target list to GENIE when running gevgen.
+
+We want to run comparisons to MiniBooNE muon-neutrino scattering data on a mineral oil target, therefore to generate events we pass it the default GENIE splines, the MiniBooNE flux in root format, and the required target and beam peg settings
+{{{
+$ source $GENIE_DIR/environment_setup.sh
+$ export GXMLPATH=${GENIE_DIR}/genie_xsec/v2_12_0/NULL/DefaultPlusMECWithNC/data/
+$ gevgen -n 2500000 \
+                -t 1000060120[0.85714],1000010010[0.14286] \ 
+                -p 14 --cross-sections $GXMLPATH/gxspl-FNALsmall.xml \
+                --event-generator-list Default -f MiniBooNE_numu_flux.root,numu_mb \
+                -e 0,10 -o gntp.2063030.ghep.root
+}}}
+For more information on how to generate events in GENIE please see: https://arxiv.org/abs/1510.05494
+
+Once our events have been generated we can check that they have finished correctly by opening the output event file and checking it has a ‘gtree’ object and the checking flux spectrum file contains the correct histogram.
+
+
+{{{
+$ root gntp.2063030.ghep.root
+root [0]
+Attaching file gntp.2063030.ghep.root as _file0...
+Warning in <TClass::TClass>: no dictionary for class genie::NtpMCEventRecord is available
+Warning in <TClass::TClass>: no dictionary for class genie::NtpMCRecordI is available
+Warning in <TClass::TClass>: no dictionary for class genie::NtpMCRecHeader is available
+Warning in <TClass::TClass>: no dictionary for class genie::EventRecord is available
+Warning in <TClass::TClass>: no dictionary for class genie::GHepRecord is available
+Warning in <TClass::TClass>: no dictionary for class genie::Interaction is available
+Warning in <TClass::TClass>: no dictionary for class genie::InitialState is available
+Warning in <TClass::TClass>: no dictionary for class genie::Target is available
+Warning in <TClass::TClass>: no dictionary for class genie::ProcessInfo is available
+Warning in <TClass::TClass>: no dictionary for class genie::Kinematics is available
+Warning in <TClass::TClass>: no dictionary for class genie::XclsTag is available
+Warning in <TClass::TClass>: no dictionary for class genie::KPhaseSpace is available
+Warning in <TClass::TClass>: no dictionary for class genie::GHepParticle is available
+Warning in <TClass::TClass>: no dictionary for class pair<genie::EKineVar,double> is available
+root [1] _file0->ls();
+TFile**         gntp.2063030.ghep.root
+ TFile*         gntp.2063030.ghep.root
+  KEY: genie::NtpMCTreeHeader   header;1        GENIE output tree header
+  KEY: TFolder  gconfig;1       GENIE configs
+  KEY: TFolder  genv;1  GENIE user environment
+  KEY: TTree    gtree;1 GENIE MC Truth TTree, Format: [NtpMCEventRecord]
+}}}
+
+{{{
+$ root input-flux.root
+root [0]
+Attaching file input-flux.root as _file0...
+root [1] _file0->ls();
+TFile**         input-flux.root
+ TFile*         input-flux.root
+  KEY: TH1D     spectrum;1      neutrino_flux
+}}}
+
+Now that the event samples have been generated correctly, we need to prepare them for use in NUISANCE.
+
+=== Running PrepareGENIE ===
+
+The standard gevgen application doesn’t save the total event rate predictions into the event file itself. NUISANCE needs these to correctly normalise predictions so before we can use these new events we need to prepare them.
+
+The PrepareGENIE application is built when NUISANCE is built with GENIE support should be available after the NUISANCE environmental setup script is ran. 
+
+{{{
+$ PrepareGENIE -h
+PrepareGENIEEvents NUISANCE app.
+Takes GHep Outputs and prepares events for NUISANCE.
+
+PrepareGENIEEvents  [-h,-help,--h,--help] 
+                                    [-i inputfile1.root,inputfile2.root,inputfile3.root,...] 
+                                    [-f flux_root_file.root,flux_hist_name] 
+                                    [-t target1[frac1],target2[frac2],...]
+
+Prepare Mode [Default] : Takes a single GHep file, reconstructs the original GENIE splines,  and creates a duplicate file that 
+also contains the flux, event rate, and xsec predictions that NUISANCE needs.
+Following options are required for Prepare Mode:
+ [ -i inputfile.root  ] : Reads in a single GHep input file that needs the xsec calculation ran on it.
+ [ -f flux_file.root,hist_name ] : Path to root file containing the flux histogram the GHep records were generated with. A 
+simple method is to point this to the flux histogram genie generatrs '-f /path/to/events/input-flux.root,spectrum'.
+ [ -t target ] : Target that GHepRecords were generated with. Comma seperated list. E.g. for CH2 
+target=1000060120,1000010010,1000010010
+}}}
+
+The PrepareGENIE application, when ran, loops over all the events, extracts the cross-section as a function of energy for each discrete interaction mode and uses this information to reconstruct the cross-section splines for each target that were used to generate events.
+
+These splines are then multiplied by specified flux and added according to the target definition provided to produce total flux and event rate predictions as a function of energy for the sample and saves them into the events file.
+
+We want to prepare our MiniBooNE events so we pass in the event files, the input flux, and the CH2 target definition.
+
+{{{
+ $ PrepareGENIE -i gntp.2063030.ghep.root -f input-flux.root,spectrum -t  1000060120,1000010010,1000010010  
+}}}
+
+Now when we open our event file again, we should see the flux and event rate histograms are now saved into the file ready for NUISANCE to read them.
+
+{{{
+  KEY: genie::NtpMCTreeHeader   header;1        GENIE output tree header
+  KEY: TFolder  gconfig;1       GENIE configs
+  KEY: TFolder  genv;1  GENIE user environment
+  KEY: TTree    gtree;1 GENIE MC Truth TTree, Format: [NtpMCEventRecord]
+  KEY: TDirectoryFile   IndividualGENIESplines;1        IndividualGENIESplines
+  KEY: TDirectoryFile   TargetGENIESplines;1    TargetGENIESplines
+  KEY: TH1F     nuisance_xsec;1
+  KEY: TH1F     nuisance_events;1
+  KEY: TH1F     nuisance_flux;1
+}}}
+
+
+== Choosing our samples ==
+
+Now that we have an event sample we can load them load them into NUISANCE so that it can use them to form a joint likelihood by specifying them at run time. 
+
+=== Writing a card file ===
+
+To specify samples we need to write a NUISANCE card file that lists all comparisons that should be made and the event files that should be used for each one.
+
+We want to produce comparisons to MiniBooNE CCQE data, so first we should search the NUISANCE sample list.
+
+The ‘nuissamples’ script is provided for easy access of the sample list. Running it without any arguments will return a full sample list of available data comparisons. Providing an additional argument will return only samples containing the provided substring.
+
+We can list the MIniBooNE samples using
+{{{
+[stowell@hepgw1 ~]$ nuissamples MiniBooNE
+MiniBooNE_CCQE_XSec_1DQ2_nu
+MiniBooNE_CCQELike_XSec_1DQ2_nu
+MiniBooNE_CCQE_XSec_1DQ2_antinu
+MiniBooNE_CCQELike_XSec_1DQ2_antinu
+MiniBooNE_CCQE_CTarg_XSec_1DQ2_antinu
+MiniBooNE_CCQE_XSec_2DTcos_nu
+MiniBooNE_CCQELike_XSec_2DTcos_nu
+MiniBooNE_CCQE_XSec_2DTcos_antinu
+MiniBooNE_CCQELike_XSec_2DTcos_antinu
+MiniBooNE_CC1pip_XSec_1DEnu_nu
+MiniBooNE_CC1pip_XSec_1DQ2_nu
+MiniBooNE_CC1pip_XSec_1DTpi_nu
+MiniBooNE_CC1pip_XSec_1DTu_nu
+MiniBooNE_CC1pip_XSec_2DQ2Enu_nu
+MiniBooNE_CC1pip_XSec_2DTpiCospi_nu
+MiniBooNE_CC1pip_XSec_2DTpiEnu_nu
+MiniBooNE_CC1pip_XSec_2DTuCosmu_nu
+MiniBooNE_CC1pip_XSec_2DTuEnu_nu
+MiniBooNE_CC1pi0_XSec_1DEnu_nu
+MiniBooNE_CC1pi0_XSec_1DQ2_nu
+MiniBooNE_CC1pi0_XSec_1DTu_nu
+MiniBooNE_CC1pi0_XSec_1Dcosmu_nu
+MiniBooNE_CC1pi0_XSec_1Dcospi0_nu
+MiniBooNE_CC1pi0_XSec_1Dppi0_nu
+MiniBooNE_NC1pi0_XSec_1Dcospi0_antinu
+MiniBooNE_NC1pi0_XSec_1Dcospi0_rhc
+MiniBooNE_NC1pi0_XSec_1Dcospi0_nu
+MiniBooNE_NC1pi0_XSec_1Dcospi0_fhc
+MiniBooNE_NC1pi0_XSec_1Dppi0_antinu
+MiniBooNE_NC1pi0_XSec_1Dppi0_rhc
+MiniBooNE_NC1pi0_XSec_1Dppi0_nu
+MiniBooNE_NC1pi0_XSec_1Dppi0_fhc
+MiniBooNE_NCEL_XSec_Treco_nu
+}}}
+
+We only care about CC1pip data therefore the following samples are of interest
+{{{
+[stowell@hepgw1 ~]$ nuissamples MiniBooNE_CCQE_
+MiniBooNE_CCQE_XSec_1DQ2_nu
+MiniBooNE_CCQE_XSec_1DQ2_antinu
+MiniBooNE_CCQE_CTarg_XSec_1DQ2_antinu
+MiniBooNE_CCQE_XSec_2DTcos_nu
+MiniBooNE_CCQE_XSec_2DTcos_antinu
+
+}}}
+
+In this example we will compare to the CCQE 1DQ2 distributions, but we could provide a large number of the samples seen in the lists if we wanted. When we specify multiple samples nuismin will automatically calculate the likelihood for each one and **add them uncorrelated** to form a joint likelihood.
+
+We write our card file with these two datasets using the following sample object format:
+{{{
+sample NAME_OF_SAMPLE  INPUT_TYPE:FILE_INPUT    
+}}}
+
+So if our GENIE file is called 'MiniBooNE_FHC_numu_2.5M.root', our card file will be :
+
+**genie_tutorial.card**
+{{{
+sample MiniBooNE_CCQE_XSec_1DQ2_nu GENIE:MiniBooNE_FHC_numu_2.5M.root
+sample MiniBooNE_CCQE_XSec_1DQ2_antinu GENIE:MiniBooNE_FHC_numu_2.5M.root
+}}}
+
+If you want to check this is valid you could run this card file with 'nuiscomp' as shown in the tutorial here [wiki:HowToUseNUISCOMP-GENIE] and check the nominal prediction looks okay.
 
 === Setting up our reweight dials ===