This page has links to the versions of external products
that are required by the MINOS offline software.
The following are instruction how to install external packages required for the MINOS Offline Framework. Most packages will be installed in the $INSTALLATION directory. This installation does not require admin privileges. If you have such privileges, you can opt to install all external packages in the "/usr" area. To do so, you need to substitute all occurrences of $INSTALLATION in these instructions with "/usr".
Tar files of the recommended version of the external packages can be found at:
Note: you should install these packages in the order listed here.
The recommended compiler for MINOS offline software is gcc 3.4,
although other 3.x versions may work. If a suitable version is
not provided as part of your system there are some
dCache (http://dcache.desy.de/) is a disk caching system that provides access to the FNAL Mass Store http://www-numi.fnal.gov/minwork/computing/enstore.html. To integrate this with ROOT one must install the associated library (dcap.so) and header file (dcap.h) prior to building ROOT.
DATABASESWe use ROOT interface to the MySQL database. See the Installation instructions further details.
libsigc++Libsigc++ is a small library which provides a templated, type safe signal/slot mechanism. A recipe for installation of this software is here.
Pythia6In order to use the ParticleTransportSim and G3PTSim one will need pythia6 built into ROOT. This presents a bit of a chicken-and-egg situation as the script to build pythia6 is distributed as part of the minossoft code base, so you'll need to check that out before you can proceed with this step.
It will then create a directory 'v6_412' and it will download from remote sites all that it needs and build the routines/libraries.
You'll then need to
ROOT is required by all the MINOS software
Frozen releases are tied to specific versions of ROOT. See the frozen release page for this tie. The development release will likely need the latest pre-built ROOT release, if not ROOT from Subversion.
NOTE! After 2007-11-01 ROOT will no longer be available via CVS. Instead CVS usage will be replaced by Subversion which is the new-and-improved CVS. Most of the commands look very similar though there are some differences. How to get/install Subversion is in the next section if it is not already installed on your system.
There are two ways to install ROOT, the "ROOTSYS" method and the "prefix" method. Both should work but the former is preferable as most people use it and assume it is the only way. The latter is used in Debian or Red Hat package installations. Each method is described belowFor both methods, getting the source is the same:
For both installation approaches it is important that some flags set by SRT are disabled. If minossoft SRT has been setup you must
unset MAKEFLAGS MAKEFILESFailure to do so will interfere with the ability to build the AsImage subpackage of ROOT. Certain bits of the MINOS code subtly rely on this subpackage getting built -- though most will work fine. After ROOT is built remember to re-setup SRT if you are going to proceed to build minossoft.
Then continue for the ROOTSYS method:
SubversionSubversion is the code management system that is supplanting CVS in the open source community. This not just a change of the client but the whole structure behind the scenes. In many ways it works in a similar fashion to cvs but it is incompatible in others; there are tools for exporting and importing svn repositories to/from cvs repositories as long as certain more advanced svn features are not used. But a client (code user) can not use one system to access a repository of the other type.
On some platforms you may find it already installed, on others you'll need to install it. The primary executable is svn.
Instructions for installing and using subversion can be found here.
NOTEAdditional external products are required for installing the Labyrinth. The Labyrinth is the old Fortran77 GEANT3 based GMINOS and a fortran based reconstruction framework (now obsolete). Unless one actually plans to generate GMINOS events or convert existing ADAMO files to ROOT files, installation of Labyrinth is not necessary.
See the instructions for the Labyrinth for more detail.
The package Rerootjob, the ADAMO file to ROOT file converter, requires ADAMO to build a working executable. AMAMO is the data structure and I/O package used by the Labyrinth. Rerootjob will correctly handle the non-existence of the Labyrinth (and ADAMO) as long as environment variables that should point at those packages are not defined.
There is also a small dependency on some BField data files that are distributed with the Labyrinth, but can also be independently checked out of CVS.
|Security, Privacy, Legal||