Installation on Unix/Linux :

1. Install required external software
   1. You must have a FORTRAN77 compiler
   2. You must have the CERN libraries
   3. You must have a moderately recent version of CVS
   4. The CMT utility will be installed automatically, if not already available on your system.  You do not need to do anything explicit to install it, although a C++ compiler is required if it must be built for you during installation of Nuance.
2. Pre-configuration
   1. Make sure the environment variable CERN_ROOT is defined and points to the top directory of the CERN program library, such that library files are found in the directory:
      $CERN_ROOT/lib
      The installation script will abort if CERN_ROOT is not properly defined.
   2. Due to an annoying change of naming convention, the parton distribution function library of CERNLIB (PDFLIB) can have a numerical identifier in its name, or not, depending on the version of CERNLIB you have installed. For the present you must manually determine the name of this library on your site (by scanning the contents of the $CERN_ROOT/lib directory). If the file has a version number in its name (e.g., libpdflib804.a) you must define an environment variable pdfVersion in your login script:
      setenv pdfVersion 804 [cshell]
      export pdfVersion=804 [bourne/bash shell]
      If there is no version number (e.g. libpdflib.a) then this variable should be left undefined.
      The installation script will abort if PDFLIB does not have the expected name (i.e. if pdfVersion is incorrectly set).
   3. If your local network configuration requires use of a proxy server to view the web, you must set the environment variable http_proxy to the full web address of the proxy in order for the automatic installation to work:
      setenv http_proxy "http://proxy.domain:8080" [cshell]
      export http_proxy="http://proxy.domain:8080" [bourne/bash shell]
3. Download and Install Nuance
   1. Download the shell script install_nuance.sh to the directory on your machine you want to be the top of the Nuance directory tree.  It is probably a good idea to create a new directory to contain the entire package, for instance a directory called nuanceMc.
   2. Make sure the script file is executable with the command:
      chmod +x install_nuance.sh
      Note that this file is (internally) a bash script. A C-shell script may be created in the future.
   3. Launch the script. CMT will be installed automatically if not already present in your path. The Nuance source code will be retrieved from the repository, then compiled and linked.  You will be prompted for a password, but any value allows read-only access to the repository.
4. Test the Program
   1. The executable program is located at: Nuance/v2/$CMTCONFIG/nuanceMc.exe
      You may want to place this directory in your path if you run the program frequently.
   2. The most convenient directory to run the program is the data directory
      Nuance/v2/data
      created automatically by the installation. Navigate to that directory.
   3. Take the program out for a spin with the following command:
      nuanceMc.exe -mono 14 1000. -nevt 2000 -h nm1000.hbk !
      Be sure to exactly duplicate the punctuation, including decimals and the exclamation at the end of the command line.
      (You may have to prepend the explicit binary directory ../$CMTCONFIG/ if you didn't add it to your path.)
   4. The above command says to generate 2000 mono-energetic neutrino interactions by 1000 MeV u_m  (PDG particle code 14) with water (the default target given in the program database nuance_defaults.cards) and write the output to an HBOOK file named nm1000.hbk. The exclamation point at the end of the line is a place-holder for the job-steering cards file you would normally specify, since all necessary parameters are given on the command line.  Unlike runs involving a continuous spectrum of neutrinos, in mono-energetic mode you often just calculate the cross-sections "on the fly".  This process is time-consuming but is usually done only once (for a given flux) with the results stored in a file for reuse in any number of event-generation jobs.  Depending on the speed of your machine, it may take 10-20 minutes for this particular job to complete.  When it does, you can inspect the event records in Ntuple ID=1 of the HBOOK file.

Contact: D. Casper, University of California, Irvine