• Table of contents
• Preliminaries
• Using LArSoft
  • Information on GitHub and pull request testing
  • Some hints
• Documentation
• How-to

• Quick_Links * Concepts in LArSoft

Preliminaries¶

• Fermilab computing accounts: see instructions on how to request Fermilab primary accounts and Fermilab computing access. You may also want to examine this article on getting started with computing services at Fermilab
• See Load Balanced Access to General Purpose VMs for information on accessing experiment VMs at Fermilab (e.g., lbnegpvm0X, uboonegpvm0X, etc., collectively known as GPCF.)
• Supported platforms
• To join the LArSoft mailing list, please follow these instructions using the list name LARSOFT.

Using LArSoft¶

First-time, or infrequent, users will be well-served to go through the following steps in order:

1. Start by reading Concepts in LArSoft, the training material at larsoft.org and other information available at larsoft.org
   • Also look at your experiment's Experiment-specific information.
2. Choose the correct release from the List of LArSoft Releases and Release Notes.
   • If you can use a tagged release as is (aside from fcl files which can be modified and used from any directory), you can now run LArSoft.
   • If you need to modify the code locally, or use code not yet in a tagged release, then additional steps (below) are required.
3. Create a working area. This is described in the presentation from the 2019 workshop session on LArSoft technical details.
   • To find out which repositories contain the code you need to modify for your task, examine the List of repositories and their relationships.
   • If you have questions, ask the LArSoft module authors and release managers and offline coordinators.
4. To modify the code, clone the reference software into your working area from the central repositories for core LArSoft.
   • This is where to find Experiment-specific code.
   • And this is the Sub-package locations (e.g., in which repository can I find the HitFinder sub-package?)
5. To install a local copy of the pre-built products, or to build and install a local copy of the products for the core LArSoft suite, follow the Installation Procedures on the Getting LArSoft page.
   • To use cvmfs to access the binaries and header files in a tagged release (thereby avoiding the need to install or build a local copy), follow the LArSoft cvmfs instructions.
   • Sometimes your local code will fail to build against a new LArSoft release because there are “breaking changes” in the release, which are modifications that require adaptations to the code that references that modified code. These changes and the corrective actions needed are documented on the Breaking Changes page.
   • Comments in the code are incorporated into documentation at LArSoft Doxygen using the Doxygen tool.
6. Recommended.
   • Install and run igprof profiler.

Information on GitHub and pull request testing¶

Start by reviewing the information on the overview page for using LArSoft with GitHub. The current GitHub repositories are for testing purposes only, so feel free to exercise the system with arbitrary commits. Contact your experiment offline management to identify acting Level 2 managers. Send any comments to scisoft-team@fnal.gov, or via Remind issues.

Some hints¶

• Rerun part of all a job on an output file of that job.
• Tips on Interactive GPVM sessions with terminal multiplexers
• Reproducing jobs using the same random number sequences
• Rerunning a job starting from its output
• About fast cloning
• Working With LArSoft GitHub Repositories

Documentation¶

• Description of Event Displays options with links to further information.
• Description of The user environment with examples.
• Description of The developer environment with a picture.

How-to¶

• Getting started with an analysis task: an example
• Running Jobs