Changes between Version 11 and Version 12 of HowToUseNUISCOMP-GENIE

Timestamp:

Jun 12, 2017, 7:06:27 PM (7 years ago)

Author:

Patrick Stowell

Comment:

--

HowToUseNUISCOMP-GENIE

@@ -28 +28 @@
 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 ==
+=== Running gevgen ===
 
 The standard gevgen application options can be ran using
@@ -35 +35 @@
 }}}
 
-We need to provide a flux and target list to GENIE when running gevgen. To see our list of compiled flux and target combinations for each sample please see here:
+We need to provide a flux and target list to GENIE when running gevgen.
 
 Note: If building NUISANCE v2r0 or higher against GENIE 2-12-0 or higher an option is provided to use an easier and quicker gevgen_nuisance application to generate NUISANCE-ready event files. Please see section 2.3 if you would like to use this.
@@ -86 +86 @@
 Now that the event samples have been generated correctly, we need to prepare them for use in NUISANCE.
 
-== Running PrepareGENIE ==
+=== 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.
@@ -136 +136 @@
 }}}
 
-== Running gevgen_nuisance (optional) ==
+=== Running gevgen_nuisance (optional alternative) ===
 
 Other than the standard gevgen application, if built against GENIE events later than GENIE 2.12.0, NUISANCE can also provide a gevgen_nuisance app, with additional features to support the creation of ‘NUISANCE-ready’ events.
@@ -160 +160 @@
 gevgen_nuisance also provides extra support for mixed target and flux specifications. For further notes on these see: 
 
-== Setting up a GENIE Comparison ==
-
-Now that we have an event sample we can load them load them into NUISANCE by specifying them at run time. To do that 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.
+== Making a GENIE Comparison ==
+
+Now that we have an event sample we can load them load them into NUISANCE 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 pion production data, so first we should search the NUISANCE sample list.
@@ -235 +239 @@
 }}}
 
+
+=== Running a comparison ===
+
 We can now run our cardfile using the standard nuisance application like so:
 {{{
@@ -287 +294 @@
 If you see something similar to this then the comparisons should have ran successfully.
 
-== Analysing the output ==
+=== Analysing the output ===
 
 When we open the NUISANCE output file in ROOT we can see that it contains a series of histograms all with names similar to the sample names we specified in our card file. By default NUISANCE preppends the name of the sample to any histogram when writing it so that you know from what sample each histogram originated from. 
@@ -327 +334 @@
 
 
-== Providing reweight parameters ==
+=== Reweighting GENIE Comparisons ===
 The comparisons application also allows different GENIE reweight parameters to be provided in our card file.