LLMpediaThe first transparent, open encyclopedia generated by LLMs

LArSoft

Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: ProtoDUNE Hop 5 terminal

This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.

LArSoft
NameLArSoft
DeveloperFermi National Accelerator Laboratory; Brookhaven National Laboratory; SLAC National Accelerator Laboratory; Lawrence Berkeley National Laboratory
Released2010s
Programming languageC++; Python
PlatformScientific Linux; CentOS; Ubuntu
LicenseBSD license; MIT License

LArSoft LArSoft is a software toolkit developed to support liquid argon time projection chamber experiments and collaborations such as MicroBooNE, ICARUS, DUNE, ProtoDUNE and SBND. It provides a shared framework for simulation, reconstruction and analysis used at laboratories including Fermi National Accelerator Laboratory, Brookhaven National Laboratory, Lawrence Berkeley National Laboratory and SLAC National Accelerator Laboratory. LArSoft integrates with experiment-specific codebases and common high-energy physics tools to enable reproducible workflows across institutions such as University of Chicago, Columbia University, University of Oxford and University of Geneva.

Overview

LArSoft delivers modular components for event simulation, detector response, hit-finding and particle reconstruction employed in collaborations like MicroBooNE, ICARUS, DUNE, ProtoDUNE and SBND. It interfaces with frameworks and tools from ROOT, Geant4, GENIE, art and Gaudi while being used by institutions such as Fermilab, CERN, CERN partners, University of California, Berkeley and Massachusetts Institute of Technology. Development and validation involve researchers from experiments and facilities like Argonne National Laboratory, Lawrence Livermore National Laboratory and university groups at University of Minnesota.

Architecture and Design

The architecture uses the art event processing framework to organize modules, services and producers analogous to designs in Gaudi. Data products are stored in containers compatible with ROOT and managed using conventions influenced by HEPData practices seen at CERN and DESY. LArSoft employs object-oriented C++ classes and Python configuration steered by generator interfaces such as GENIE and detector descriptions comparable to those used in GEANT4-based experiments at SLAC National Accelerator Laboratory and Brookhaven National Laboratory. The modular design supports collaborations across experiments including MicroBooNE, DUNE, ICARUS and SBND and integrates with continuous integration systems used by GitHub and GitLab hosts.

Simulation and Reconstruction Tools

Simulation pipelines combine particle event generation from GENIE and propagation through detectors with Geant4-based geometry and physics lists similar to practices at CERN test beams. Detector response simulation models electronics and noise frameworks comparable to those in MicroBooNE and ICARUS and ties to waveform digitization methods used at Fermilab. Reconstruction algorithms include signal processing, deconvolution, hit-finding, clustering, pattern recognition and track/shower reconstruction drawing on methods used by DUNE and ProtoDUNE groups. Tools for particle identification leverage techniques from collaborations such as NOvA and T2K and incorporate machine learning workflows compatible with frameworks from TensorFlow, PyTorch and resources at Oak Ridge National Laboratory.

Data Formats and I/O

LArSoft uses event data models that serialize into ROOT files with branches and trees adopted by experiments like MicroBooNE and DUNE. Metadata conventions align with standards practiced at CERN and Fermilab for provenance, geometry and calibration records similar to approaches used by ATLAS and CMS. Input interfaces accept generator outputs from GENIE and NuWro and export reconstructed objects for analysis suites employed by university groups at University of Cambridge and University of California, Irvine. I/O performance considerations follow experience from large collaborations such as NOvA and MINOS and integrate with storage systems used at Fermilab, CERN and NERSC.

Software Development and Collaboration

Development follows collaborative models practiced by projects hosted on platforms like GitHub and GitLab with continuous integration patterns similar to those used by ATLAS and CMS. Contributions come from institutions including Fermilab, Brookhaven National Laboratory, SLAC National Accelerator Laboratory, Lawrence Berkeley National Laboratory, University of Chicago and international partners at CERN, University of Oxford and University of Geneva. Documentation and issue tracking adopt conventions used by JIRA and Read the Docs in coordination with working groups from experiments such as MicroBooNE and DUNE. Release engineering parallels practices at Linux Foundation-hosted projects and experimental software collaborations like ROOT.

Applications in Experiments

LArSoft supports reconstruction and analysis in experiments including MicroBooNE, ICARUS, SBND, ProtoDUNE and DUNE, enabling tasks from calibration to oscillation analyses similar to published results from T2K and NOvA. It is used in test beam campaigns associated with CERN and Fermilab and for prototype studies at facilities such as CERN SPS and Fermilab Test Beam Facility. Physics analyses leveraging LArSoft products include cross-section measurements, sterile neutrino searches and supernova neutrino detection efforts analogous to programs at Super-Kamiokande and IceCube.

Performance and Validation

Validation exercises compare simulated distributions against calibration data and test-beam measurements from ProtoDUNE and MicroBooNE, and use techniques refined in collaborations like MINERvA and NOvA. Performance benchmarks assess CPU, memory and I/O using compute resources at Fermilab, NERSC and CERN and leverage profiling tools similar to those adopted by ATLAS computing groups. Continuous validation is coordinated with experiment analysis groups at institutions such as Brookhaven National Laboratory, Lawrence Berkeley National Laboratory and University of Chicago to ensure reproducibility for physics results reported in conferences like Neutrino and journals exemplified by Physical Review Letters and Journal of Instrumentation.

Category:High-energy physics software