LArSoft at Nevis

• The Nevis copy of the LArSoft installation is currently in /a/data/westside/seligman/larsoft.
• The Nevis copy of the uboonecode installation is currently in /a/data/westside/seligman/products.

This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.

As of 07-Feb-2014, the following Fermilab LArSoft releases are maintained at Nevis:

v1_00_02 - Minor compilation fixes; use updated cetbuildtools.  
v1_00_01 - Freeze after switch to mrb+git   

Limitations of Nevis LArSoft installation

• Nightly builds are not yet available at Nevis (nor anywhere else outside of FNAL systems).
• The mrb+git scripts will only run in the bash shell. Other shells (tcsh and zsh) will be supported (someday), but FNAL CD is not yet ready.

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.

Setting up the Environment

The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:

source /a/share/westside/seligman/microboone/setup_uboone.sh

You only have to run this once per login session.

After you've run this command, you can follow the instruction in the !MicroBooNE guide.

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.