Version 4 (modified by 8 years ago) (diff) | ,
---|
NuWro Inputs
This page aims to outline how to use NuWro to create a sample of interactions on your favourite target. We'll also outline how to feed this generated sample through the NUISANCE framework and get good results.
The latest version of the NuWro generator is setup to automatically save the predicted event rate and flux distributions for the generated events. This is everything NUISANCE needs to make properly normalised cross-section predictions with the standard NuWro output.
The latest version of NuWro with recently developed reweight engine can be obtained from here:
Note: If you would like to use events generated with an older version of NuWro this is still possible. Please see:
Generate NuWro Events for NUISANCE
Loading NuWro v12+ events into NUISANCE
NUISANCE's input handlers are setup to automatically load in the standard output of NuWro v12 onwards. Once you have generated events the MC sample can be loaded in by specifying the "NUWRO" type in the NUISANCE sample input field. An example of this is shown in the following card file.
nuwro_v12_comparison.card:
#sample sample_id type:input_file ########################################## sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/nuwro/events.root
nuwro_v12_comparison.card(without comments):
sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/nuwro/events.root
Loading NuWro <v12 events into NUISANCE
For versions of NuWro less than v12 there are no flux and event rate histograms saved into the generator output. It is still possible to use these events but NUISANCE must reconstruct the histograms at runtime (a slow process).
This must be done by using the flag input.regen_nuwro_plots=1 at runtime. When this is set NUISANCE will extract the flux histogram spectrum from the NuWro parameters class. It will then bin all the events as a function of Enu and use the NuWro event weight to normalise this event spectrum to a properly normalised predicted event rate for the given input flux.
The following cardfile is an example of how to setup this type of input for the MiniBooNE CCQE dataset.
nuwro_oldversion_comparison.card:
# Config Name Value ########################## config input.regen_plots 1 #sample sample_id type:input_file ########################################## sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/old/nuwro/events.root
nuwro_oldversion_comparison.card (without comments):
config input.regen_plots 1 sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/old/nuwro/events.root
Using NuWro reweight for comparisons
Support for the NuWro reweight package is built into NUISANCE. It has immediate access to any reweight dial available in the version of NuWro you built NUISANCE against. An example of a nuiscomp cardfile that will generate predictions with alternate model predictions is shown below:
nuwro_reweighted_comparison.card:
# par_type dial_name value ########################### nuwro_paramater MaCCQE +1.0 # sample SAMPLE_ID TYPE:INPUT_TYPE ######################################## sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/nuwro/events.root
nuwro_reweighted_comparison.card(without comments):
neut_paramater MaCCQE +1.0 sample MiniBooNE_CCQE_XSec_1DQ2_nu NUWRO:/path/to/nuwro/events.root
A list of available dial strings
Using NuWro reweight for dial tuning
As for all other reweight engines any dial can be treated as a free parameter for dial tuning studies in nuismin. The following cardfile when used with nuismin will vary the CCQE and Resonant axial mass parameters until a best fit is found to the MiniBooNE CCQELike dataset.