A tool for calculating coherent neutrino scattering discovery limits
C++ C Makefile
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Conudl v1.0

July 2016

Conudl is a tool for the calculation of coherent neutrino-nucleus scattering rates and derivation of discovery limits on BSM physics.


Dependancies: GSL (the GNU Science Library) If you do not have the GSL package installed, install it by typing (on Debian systems):

sudo apt-get install libgsl0-dev

or otherwise try:

sudo yum install gsl-devel

Optional dependancy: git

Either download the code from GitHub and extract it from the archive, or clone the git repository by typing:

git clone https://github.com/jaydenn/Conudl.git

future updates can be obtained by typing:

git pull origin master

Once GSL is installed you can build Conudl by typing 'make' in the main directory.

Running Conudl

There are two ways to run Conudl:

  1. Run in interactive mode by typing
./Conudl -i

In this mode the program will ask you questions about what you would like it to compute.

  1. Run in config file mode by typing


./Conudl -c configFile.dat

In this mode the program will compute based on information specified in the configuration file. Typing "./Conudl" runs with the default config.dat file. Alternatively you can use the -c flag to specify your own configuration file (useful for running batch jobs), see the config.dat file for the required format.

Output files

The output files will be placed in the location specified by the root variable, the default is ./results/CN_. All output files will then by found in the results directory with filenames prepended by CN_

Output filenames are created dynamically and will contain information about the type of computation completed. The files will also contain a header line(s) with more information.


The detectors are specified in the file 'detectors.ini', feel free to modify these or add your own detector (just give it a unique name), it can then be refered to by name in the config.dat file.