|
Online Tutorial Welcome and Introduction
|
|
|
Introduction to art and LArSoft
|
Art provides the tools physicists in a large collaboration need in order to contribute software to a large, shared effort without getting in each others’ way.
Art helps us keep track of our data and job configuration, reducing the chances of producing mystery data that no one knows where it came from.
LArSoft is a set of simulation and reconstruction tools shared among the liquid-argon TPC collaborations.
Running these tools on existing files works under AL9 and the dune-prototype Spack environment; building or modifying them still needs the SL7 container.
|
|
Bonus episode -- Code-makeover on how to code for better efficiency
|
|
|
Multi Repository Build (mrb) system
|
The multi-repository build (mrb) tool allows code modification in multiple repositories, which is relevant for a large project like LArSoft with different cases (end user and developers) demanding consistency between the builds.
mrb keeps source, build, and localProducts areas separate, and puts localProducts first on the UPS path so a locally built package shadows the central one.
Building code with mrb needs the SL7 container; it does not yet work under Spack on AL9.
|
|
Expert in the Room - LArSoft How to modify a module
|
DUNE’s software stack is built out of a tree of UPS products.
You don’t have to build all of the software to make modifications – you can check out and build one or more products to achieve your goals.
You can set up pre-built CVMFS versions of products you aren’t developing, and UPS will check version consistency, though it is up to you to request the right versions.
mrb is the tool DUNE uses to check out software from multiple repositories and build it in a single test release.
mrb uses git and cmake, though aspects of both are exposed to the user.
|
|
End of the larsoft basics lesson - Continue on your own to learn how to submit batch jobs
|
|
|
Closing Remarks
|
|