List of ICARUS code releases

Here we enumerate the impressive number of code releases by the ICARUS army.

The army has also filled a [list of dependencies], after the list of releases below.

List of icaruscode releases

Release managers: Matthew Rosenberg, Sergey Martynenko

This is an outdated list of the icaruscode releases:

Dependencies

The ICARUS code repository (icaruscode) currently depends on icarusutil, icarus_data, larsoft, sbndaq_artdaq_core and cetbuildtools (for building). In all releases the icaruscode release tag matches the underlying larsoft version. Note that in general, icarusutil versions are independent though generally also match. Also, icarusutil is an “optional” dependency. So, on Fermilab GPVMs it will be set up but offsite it will not be set up unless it is available: usually it is not. If you are building your own icaruscode with MRB, you can check out also icarusutil (mrb g icarusutil) and when you build the area icarusutil will be available to you.

Summary of dependencies; all are mandatory (even when “not necessary”) unless otherwise specified:

• icaruscode is the main ICARUS simulation and reconstruction software repository;
• icarus_signal_processing includes algorithms for readout signal processing;
• larsoftincludes, well, LArSoft; you won’t go very far without this;
• icarus_data includes data files of moderate size (e.g. for signal processing); it is often necessary, but not always so;
• genie_xsec to allow our experiment to choose which GENIE cross section set to use; necessary when running GENIE;
• sbndaq_artdaq_core (mandatory since icaruscode v08_32_00) connects to data acquisition (see below);
• icarusutil (optional) includes scripts and facilities for job submission to the grid(s);

sbndaq_artdaq_core quirks

If you need to check out sbndaq_artdaq_core in your working area, the effective MRB command is:

mrb gitCheckout -d sbndaq_artdaq_core sbndaq-artdaq-core

which checks out the repository sbndaq-artdaq-core from the default repository in GitHub (SBNSoftware), and puts it into sbndaq_artdaq_core directory because if it is true, as it is, that UPS hates underscores, it is just as true that LArSoft build system cet_build_tools hates hyphens. (also, this seems still not to be enough to make cetbuildtools happy…)