The LArSoft software is designed to work for all planned and running liquid argon experiments at Fermilab. It is written in C++ and built on the ROOT data analysis software, and the art analysis framework supported by the Fermilab Scientific Computing Division for intensity frontier experiments.


  • Fermilab computing accounts: see the [[larsoftsvn:Fermilab Computing Access]] page if you need an account.
  • See [[larsoftsvn:Load Balanced Access to General Purpose VMs]] for information on accessing experiment VMs at Fermilab (e.g., lbnegpvm0X, uboonegpvm0X, etc., collectively known as GPCF.).
  • See the documentation section for information on working with LArSoft, and using git, git flow, mrb and other tools you will need.
  • Supported platforms
  • To join the LArSoft mailing list, please follow these instructions using the list name LARSOFT
  • To get write access to the repositories, send email to , , , .

Where to find the software

LArSoft Doxygen - comments in the code are incorporated into documentation by Doxygen


List of LArSoft releases. (Temporarily includes lbnecode and uboonecode)
LArSoft release management (instructions for the release manager)
Breaking Changes (or "after the update my code shows 179 compiling errors! HEEELP!!")


Overview of the user and developer environment

Working with LArSoft

How to use the repositories and the build system

The framework and the LArSoft suite

  • [[larsoftsvn:Using the Framework]] * ART Tutorial * [[larsoftsvn:NuSoft and LArSoft|nutools and LArSoft]] * Using LArSoft on the GPVM nodes * [[larsoftsvn:Package Documentation]] * [[larsoftsvn:Geometry]] * [[larsoftsvn:Reconstruction]] * [[larsoftsvn:Simulation]] * [[larsoftsvn:Space Points]] * [[larsoftsvn:Seed Finding and Bezier Tracking]] * [[larsoftsvn:Optical Simulations]]

Links to the tools used to work with the software

git and git flow:
  • git flow quick start (edited 2/4/2013).
  • Git Tips and Tricks (Note that "git help" works, but "man git" and "git help <command>" does not on any of the gpvm machines. Nor do any of the "git <command> -h" commands.) For the purposes of LArSoft development, please please ignore the workflow advice as anything other than an example of how to use various git commands to do specific tasks.
Understanding CMakeLists.txt and product_deps files mrb and ups:


Advanced technical how-to's

Release procedures

LArSoft cvmfs

Walk-through exercises

LArSoft code management and distribution

LArSoft continuous integration system

Legacy Redmine project sites

These were the sites used when LArSoft was developed under cvs and svn + SoftRelTools, respectively:

LArSoft-cvs wiki for the legacy cvs-based LArSoft project
[[larsoftsvn:| LArSoft-svn wiki for the legacy svn-based LArSoft project]]

As of Jan 24, 2014, LArSoft transitioned from svn / SRT to git / mrb / ups, but we retain the legacy projects for historical reasons.

Working areas

Detailed documentation on using and developing LArSoft code : under development -- not a resource

Draft quick start revisions

Profiling LArSoft

Random number generators in art

Debugging LArSoft

Old pages that are no longer relevant or maintainted: