What is the labyrinth
The labyrinth is an umbrella for managing several packages that
make up the FORTRAN based MINOS simulation and reconstruction framework code.
The major components are:
- is the framework for the GEANT3 based simulation of MINOS
(and any other sandwich active-passive plane neutrino detector). It supplies
a means of configuring the geometry via data cards, selecting neutrino flux
from a variety of methods, calling event generators (neutrino and cosmic muons),
passing the events to GEANT3 for tracking, recording hits/digits and the initial event
into ADAMO data structures/files, MINOS specific digitizing routines for simulating
the two electronics configurations.
- is the code supplied by the Soudan2 collaboration
that provides total cross sections and individual event generation based on
a neutrino + nucleon.
- a variety of MINOS steel maps.
- David Petyt's neutrino oscillation library.
- a framework for analyzing GMINOS generated events.
This is mostly I/O and user hooks, but includes some basic reconstruction algorithms.
It also include the maw program which combines paw with tip
(ADAMO) and RECO_MINOS code.
- various subroutines/functions used by GMINOS and/or RECO_MINOS.
Also supplies source for fsplit.
For the most part there are three executables that one will run.
executable is the standard GMINOS program. This is highly configurable using FFREAD
data cards and for many uses the user does not need a private (modified) copy of the
executable -- though one can further extend GMINOS with some minimal effort.
The second executable is maw which provides useful quick
access to the output of a GMINOS run; as this incorporates
paw,one can access the data structures using COMIS
(interpreted pseudo-FORTRAN). This is useful for many quick-and-dirty
tests including histogramming of variables and the development of
Finally there are reconstruction/analysis programs that are built by
the user (the default name is theseus.exe). In these
programs the user supplys additional code that is called by predefined
hooks in the RECO_MINOS framework.
Both GMINOS and RECO_MINOS are generally driven by FFREAD data card
files; they share some card definitions, used mostly for controlling
the scintillation hit digitization, but in general their card files
are quite different.
general GMINOS &RECO_MINOS info
MINOS specific and/or specialized info
Robert Hatcher <firstname.lastname@example.org>