LArSoft at Nevis

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.


  • 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.


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   

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/

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.


Regular development work

The MicroBooNE guide contains several procedures, but most of them are not commands that you'd type in every day. If your typical work flow is to login and start editing code in something you've already checked out, you may be interested in this script that WilliamSeligman wrote:


Let's assume that you've previously set up (via mrb newDev) and checked-out (via mrb gitCheckout) some code that you're working on into your directory ~/mydev, and that code is part of LArSoft release v1_00_02. Then a typical use of this script would be:

source /a/share/westside/seligman/microboone/ ~/mydev v1_00_02 e4 debug

This becomes handy if you set up an alias in ~/.bashrc, the script that gets automatically executed when you login to bash:

alias MBD="source /a/share/westside/seligman/microboone/ ~/mydev v1_00_02 e4 debug"

Then you just have to type MBD after you login, and you're ready to work.

Look at ~seligman/.bashrc for more ideas.

Finding packages

One potentially-confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.

For a guide as to which package is in which group, see LArSoft dependencies.

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.

Limitations of Nevis LArSoft installation

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

Setting up ROOT and Geant4

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.

Edit | Attach | Watch | Print version | History: r18 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2014-02-10 - WilliamSeligman
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback