- The purpose of the Algorithm package is to provide framework
support for concrete reconstruction Algorithms. These
classes inherit from the abstract AlgBase class. AlgBase
provides abstract base class support for common interfaces
and traits of concrete Algorithm classes.
- Basic classes for the Candidate I/O Record containing
reconstructed objects. These classes inherit from Record
abstract base classes.
- Basic reconstructed digit Candidate class, Algorithms
- Obsolete package for reconstructed events - ignore
- Obsolete package for reconstructed vertices - ignore
- The purpose of the Candidate package is to provide framework
support for reconstructed objects. These classes inherit
from the CandBase class. CandBase provides abstract base
class support for common interfaces and traits of concrete
- The Conventions/Munits.h (Minos units) header defines a
namespace in which a number of conversion factors are given.
- The DatabaseInterface package provides optimised read and write
access to database tables of Detector Description (e.g. calibration
constants) and Algorithm Configuration (e.g. track fitting module).
To read data, the user provides an event context (basically the type of
detector and the date and time of the event) and the package assembles
a table in memory containing all rows that are suitable for the event.
To write data the user provides the package with a validity range (a set
of detector types and dates) and the table rows that have that validity
- A suite of tools designed to look for interdependencies in
the code, in order to better organize it and control compile-time
- The purpose of the dispatcher package is to handle the distribution
of data from the online systems (DAQ & DCS) to the near-online
client applications which need access to that data. The package
supports a subscription mechanism by which clients may subscribe
to certain subsets of data. The package also supports data
transfer over the internet, so that clients may be remote from
the data sources.
- A set of scripts and executable that uses the ROOT
self-documentation system to generate an HTML version of the
code for browsing.
- A framework class to dynamically link, catalog in a "loan pool"
and serve out objects of prearranged categories. Currently
only used to manage (Algorithm, AlgConfig) pairs in connection
with the AlgFactory class in the Algorithm package.
- Modules to read detector data from different streams into the
- Construction and configuration of reconstruction and analysis
jobs. Provides a framework for users to plug their reconstruction
and analysis code into the framework.
- The Lattice package is provides a transient method for defining an
arbitrary n:m relationship between two sets of objects. No restrictions
are placed on the types of objects in the relationship but the interface
is not type safe and users are urged to use the Navigation package to
navigate a Lattice once it has been built.
- The LeakChecker package is a very simple leak checker facility
developed as part of the framework to provide the first level of defense
against memory leaks. It can be used to allow basic leak checking to be
built into package validation. The user has to add probe points to their
code (which can be turned off at compile time) and can request summaries
of the total number (high-water mark and current) for a given class or
- (Minos Interactive Data Analysis and Display): A mini
framework for building MINOS event displays.
- A legacy package to support the Minfast interactive event
display program "minfastjob". Minfastjob displays data from the
REROOT_Classes package for "rerooted" GMINOS MC data.
- Coordinates the printing of error/warning/debug messages.
Allows for routing and throttling of messages based on senders and
- A legacy package used to build the "minfastjob executable for
interactive display of "rerooted" MC event data.
- The purpose of the Navigation package is to aid navigation of the
event and detector object structures. The navigation objects are
transient, that is to say they are created as necessary and are not
stored permanently. The idea is that designers of the event and detector
object structures provide code to create the navigation objects on
demand. The end user sees a uniform interface via these navigation
objects and can select and sort without needing write access to the
- The purpose of the persistency package is to provide a set of
tools for managing the I/O of event data from user processes
to data file. It makes use of the persistency tools provided
by ROOT to serve this purpose. The Persistency package exists
as an intermediate layer between the IoModules package and
plexus n., pl. -us or -uses Anat. A
structure in the form of a network, esp. of nerves, blood vessels,
or lymphatics; the solar plexus. [< Lat. p.p. of
plectere, to plait.]
The purpose of this package is to handle the logical connection
between elements of the detector above the physical level. It would
not be concerned with the placement of physical strips and steel,
but instead be responsible for providing the navigation from strips
to fibers to pixel spots to pixels (anodes) to tube and/or
electronics chip. It should also allow a reverse navigation.
- a very basic utility that allows the oconversion of a ROOT file
containing TNtuple objects into an HBOOK file. It has been written
solely as a stop gap so that physicists, who have not had the time to
learn to use ROOT as an analysis tool, can use it to look at first
Calibration Detector data. TNtuples (ROOT's equivalent of the HBOOK
row-wise n-tuple ) are the only type of object the utility can convert.
- A legacy package to represent GMINOS MC event data (originally
in ADAMO format) in "rerooted" ROOT format. Each ADAMO
<table> has a corresponding
- Framework base class support for I/O record classes like
RawRecord, CandRecord and HistRecord.
- A heterogeneous type-safe collection of mappings from
strings (keys) to arbitrarily typed values.
- A legacy package used to build the "rerootjob" executable.
This executable converts GMINOS' ADAMO table output files to
"rerooted" ROOT files of REROOT_<table>
- The rotorooter is a server that accepts buffers of data
from the MINOS DAQ (Data Acquisition) or DCS (Detector Control System)
or their proxies and turns those buffers into MINOS standard
RawRecord objects containing RawDataBlocks. It manages
naming, opening and closing the files and the streams (TTrees)
within a file.
- Given a validity context (Bfield & Geometry) and a particle's
mass, charge, initial position and momentum, this package
traces the particle until a user-provided condition (z-position,
momentum) is met.
- A legacy package which illustrates techniques for passing
function pointers (between C++ and CINT) for data navigation
- A legacy package containing a class useful for pulling
neutrinos (random type and energy) from envelope flux spectra,
with constant relative proportions.
- To supply a single, unified access to the geometry of the detector.
There are three major users of the geometry, each of which has different
requirements but all of which must not see substantially different
interpretations when referring to the same physical object.
The three classes of users are the:-
which uses the geometry for tracking particles. Simulations should
have sufficient detail but might rely on external package
(e.g. GEANT) for volume navigation.
- Event Display
which generally uses a simplified representation that omits
- Reconstruction Algorithms
which use the geometry for a variety of purposes.
- This package helps manage the validity of parameters of other