= Card File Examples =

{{{
#!div class="important" 
'''Author:''' Patrick Stowell

'''Date:''' June 2017

'''Versions:''' `NUISANCE v2r0`, `GENIE 2.12.6`
}}}

The NUISANCE applications require card files to be written that list different comparison specifications you would like to run with.

We call an entry in the card file a 'structure' and there are a number of these structures available to the user when writing card files. These are listed below, with their required and optional arguments. Some structures are valid only for certain routines or apps, so where appropriate these have been labelled.

NUISANCE Versions >v2r0 contain support for the card file to be specified in xml format, also opening up additional options to be passed in the structures. To look at examples for the older 'simple card' format that can be saved as a text file, please see the 'Simple Card Structures' section.

[[PageOutline(1-3,Wiki content,inline,numbered)]]

== XML Card Structures ==

== Simple Card Structures ==

=== Sample Structure === 
Data comparison samples are specified by including the 'sample structure, listing the name of the sample and the input.
{{{
sample   NAME   TYPE:/path/to/FILE   [OPTION]   [NORM]
}}}
- **NAME** : Name string of the sample of interest specified in src/FCN/SampleList.cxx. 
- **TYPE** : Generator Input Type string telling NUISANCE what the file type is (e.g. GENIE)
- **OPTION** : (Option Argument) Specifying extra sample options that change the way the sample behaves at run time (e.g. SHAPE). If none given, this is left as DEFAULT.
- **NORM** : Starting sample normalisation value used to shift total MC normalisation. If none given this is left at the value 1.0.

{{{
#!div class="important" 
NOTE: Reading in Generators requires that Generator to be built and have NUISANCE built against it. E.g. to read GENIE files, you need to have a working install of GENIE and NUISANCE built against that version.
}}}


**Example 1** : MiniBooNE CCQE comparison using a GENIE file
{{{
sample  MiniBooNE_CCQE_XSec_1DQ2_nu  GENIE:/path/to/my/geniefile.root  
}}}

**Example 2** : MiniBooNE CCQE comparison using a NuWro file
{{{
sample  MiniBooNE_CCQE_XSec_1DQ2_nu  NEUT:/path/to/my/nuwrofile.root  
}}}

**Example 3** : MiniBooNE CC1pi comparison using a NEUT file
{{{
sample  MiniBooNE_CC1pi_XSec_1DTpi_nu  NEUT:/path/to/my/neutfile.root  
}}}

**Example 4** : MiniBooNE CC1pi comparison using a GiBUU file and the SHAPE option
{{{
sample  MiniBooNE_CC1pi_XSec_1DTpi_nu  GiBUU:/path/to/my/gibuufile.root  SHAPE
}}}

**Example 5** : MINERvA CCQE comparison using a NEUT file and shifting the MC normalisation by 1.0 / 0.9.
{{{
sample  MINERvA_CCQE_XSec_1DQ2_nu  NEUT:/path/to/my/neutfile.root  DEFAULT  0.9
}}}

**Example 6** : MiniBooNE CCQE comparison using a NuWro, shifting the MC by 0.9 / 1.0 buy also adding a normalisation penalty (option=NORM)
{{{
sample  MiniBooNE_CCQE_XSec_1DQ2_nu  NEUT:/path/to/my/neutfile.root  NORM  0.9
}}}


=== Fixed Parameter Structure ===
Fixed parameters can be specified by using any of the 'parameter' type structures. You must specify the type of parameter first, before listing the name, starting value, and state.
{{{
TYPE_parameter  NAME   VALUE  STATE
}}}

- **TYPE** : Type of RW parameter, (e.g. genie_parameter, neut_parameter, norm_parameter)
- **NAME** : Name of RW parameter, can be any string given in the RW engine. In GENIE this list is given in $GENIE/src/ReWeight/GSyst.h. 

For normalisation parameters the name of the dial corresponds to SAMPLENAME_norm. (e.g. 'MiniBooNE_CCQELike_XSec_1DQ2_nu_norm')

- **VALUE** : Starting value for the dial. In general for RW engine parameters this is given in terms of 1-sigma variations away from the nominal, so that VALUE=0.0 is the nominal generator value. For everything else, like normalisation parameters, this value is in units of the true value.

- **STATE** : State of the dial. This should always be left as FIX as this is the only support option for the time being.



**Example 1** : Fixed GENIE RW 'MaCCQE' to +1 sigma
{{{

}}}

=== Free Parameter Structure ===

{{{
TYPE_parameter  NAME  VALUE  LOW  HIGH STEP STATE 
}}}


=== Covariance Structure ===
{{{
covar ID   TYPE:INPUT   STATE
}}}


{{{
covar  ID   DIAL:NAME;CENTRAL;WIDTH   STATE
}}}


{{{
covar  ID   ROOT:FILEPATH;DIAL_HIST;COVARIANCE_HIST   STATE
}}}


=== Config Structure ===

{{{
config   NAME   VALUE
}}}


=== Comments Structure ===
{{{
# Insert my comments here

# These are my config options
config  VERBOSITY  4
}}}