Changes between Version 26 and Version 27 of HowToNeut

Timestamp:

Feb 27, 2017, 10:29:49 AM (8 years ago)

Author:

Clarence Wret

Comment:

--

HowToNeut

@@ -115 +115 @@
 
 
-= Compiling NUISANCE against NEUT =
+== Compiling NUISANCE against NEUT ==
 Once you have a working NEUT installation and generated events (see [#point_compile above], you can link NUISANCE against NEUT.
 
-To run NUISANCE with NEUT you'll need to specify the `$NEUT_ROOT`, `$CERNLIB` and `$CERN_LEVEL` variables. 
-
-When building, set the environment variables and specify `-DUSE_NEUT=1` when generating the makefiles with `cmake`. Do:
+=== Environment variables ===
+To run NUISANCE with NEUT you'll need to provide environment variables `$NEUT_ROOT`, `$CERNLIB` and `$CERN_LEVEL`.
+
+When building, set the environment variables and specify `-DUSE_NEUT=1` when generating the makefiles with `cmake`.
+
+=== Compiling ===
 
 {{{
@@ -133 +136 @@
 }}}
 
-For multiple generator support (e.g. NEUT and GENIE enabled), simply set the environment variables for the generators, and compile with
+For multiple generator support (e.g. NEUT and GENIE enabled), set the environment variables for the other generators, and compile with
 
 {{{
@@ -142 +145 @@
 
 
-= NEUT inputs for NUISANCE =
-
-The output of `neutroot2`, contains a ROOT file containing `nevents` `neutvect` objects which has all the information about each event in it. This is read in by NUISANCE to generate predictions. `neutroot2` also saves the predicted flux (`flux_numu`) and event rate (`evtrt_numu`) predictions automatically into the output file so NUISANCE already has everything it needs.
-
-To read NEUT inputs the NEUT type just needs to be specified in the NUISANCE input card file, e.g. for MiniBooNE CCQE
+== NEUT inputs for NUISANCE ==
+
+=== NEUT output required by NUISANCE ===
+The output of `neutroot2`, contains a ROOT file containing `nevents` `neutvect` objects which has all the information about each event in it. This is read in by NUISANCE to generate predictions.
+
+`neutroot2` also saves the predicted flux (`flux_numu`) and event rate (`evtrt_numu`) predictions into the output file, which NUISANCE also uses to convert event rates into cross-sections.
+
+=== Using NEUT events with NUISANCE ===
+To read NEUT inputs the generator needs to be specified in the NUISANCE input card file when specifying a sample. e.g. for MiniBooNE CCQE
 
 {{{
@@ -153 +160 @@
 
 
-= Using NEUT !ReWeight =
-NUISANCE has full support of running NEUT with its reweighting engine. We can generate error-bands, perform generator tunings to specific data-sets, and so on all through NUISANCE.
-
-== Compiling the reweight classes in NEUT ==
-To compile NEUT's reweighting engine, make sure you've got the main executables compiled (see [#point_compile above]), and
+== Using NEUT !ReWeight with NUISANCE ==
+NUISANCE has full support of running NEUT with its reweighting library. 
+
+Users can generate error-bands, perform generator tunings to specific data-sets, and so on all through NUISANCE.
+
+=== Compiling the reweight classes in NEUT ===
+To compile NEUT's reweighting engine, make sure you've got the main executables compiled (see [#point_compile above]), set your `$ROOTSYS` environment varaible and do
 
 {{{
@@ -165 +174 @@
 }}}
 
-to compile the reweighting engine.
-
-== Running NUISANCE with NEUT !ReWeight ==
+to compile the reweighting engine on top of NEUT itself.
+
+=== Running NUISANCE with NEUT !ReWeight ===
 {{{
 #!div class="important"
@@ -173 +182 @@
 }}}
 
-The syntax for running NEUT with reweighting in NUISANCE is very similar to how it's done in [wiki:HowToGenie GENIE] and [wiki:HowToNuWro NuWro] too.
-
-The user specifies the parameter(s) and the range which should be varied as:
+The syntax for running NEUT with reweighting in NUISANCE is very similar to how it's done in [wiki:HowToGenie GENIE] and [wiki:HowToNuWro NuWro].
+
+The user specifies the parameter(s) and the range which should be varied in the card file as:
 
 {{{
@@ -183 +192 @@
 where `MaCCQE` is the parameter to be varied, `0.0` is the starting values, `-4.0` is the minimum value, `4.0` is the maximum value, `1.0` is the step-size to take, and `FREE` means the parameter is free to vary in the minimisation. 
 
-We can also specify `FIX` for the parameters if we want to reweight a systematic parameter to some value other than nominal and keep it there. This is useful for using best-fit parameter constraints from one experiment to predict another experiment (e.g. fit to MiniBooNE and predict MINERvA data, or fit to bubble-chamber data to predict T2K data).
-
-The whole list of parameters can be found in `$NEUT_ROOT/src/reweight/NSyst.h` and the `return`ed `std::string`s (e.g. `MaCCQE` and `CA5RES`). 
+We can also specify `FIX` for the parameters if we want to reweight a systematic parameter to some value other than nominal and keep it there. 
 
 {{{
 #!div class="important"
+'''The parameters:'''
+
+The whole list of tunable parameters can be found in `$NEUT_ROOT/src/reweight/NSyst.h`. The user specifies the `return`ed `std::string`s (e.g. `MaCCQE` and `CA5RES`) in the card file.
+
 The starting, minimum, maximum and step values are all in units of 1-sigma uncertainties. So `-4.0` for the minimum means -4*1-sigma ranges, and `0.0` for the starting value means the nominal value nominal.
 
@@ -204 +215 @@
 }}}
 
-= Joint Flux Inputs =
-
-`neutroot2` does not yet natively support combined beams or targets so if you want to use the measurement classes that require this (e.g. MINERvA CC0pi nue+nuebar) you will have to setup a JOINT input. See [wiki:HowToJointInput this] for more information on how to achieve this.
-
-
-
+
+== Joint Flux Inputs ==
+
+`neutroot2` does not natively support combined beams or targets. 
+
+If you want to use measurement classes that require this (e.g. MINERvA CC0pi nue+nuebar) you will have to setup a JOINT input. See [wiki:HowToJointInput this] for more information on how this can be done.