http://mimosa.astro.indiana.edu/minos/simulation/labyrinth.html
Theseus & the Labyrinth
MINOS Software at Fermilab
This document describes the general use repository of the MINOS software at
Fermilab.
It is located on the afs file system for convient access across
the different available platforms. Other afs sites should also
be able to access the code with only minor modifications.
This setup has been designated the labyrinth.
There is also a directory, theseus,
containing scripts to help the average user conquer the labyrinth.
Getting Started
The first step in accessing the labyrinth is to setup the
environment. Assuming one is using a csh shell (or derivative,
eg. tcsh ) as your login shell, one should issue the command:
source /afs/fnal.gov/files/code/e875/sim/labyrinth/labyrinth.setup
The script determines the architecture of the machine you are using
and points the paths to the appropriate areas.
Three versions of the executables and libraries will be available:
| current |
a stable version |
| test |
the most up-to-date version |
| old |
the previous current version |
By default the current version is setup. Users can force a
particular choice by appending the source command with the
appropriate keyword (current,test,old)
If the keyword nofnal is also listed, then the script will
skip the step that initializes the paths for:
cern, geant, lund, stdhep, cvs, gtools. Failure to have paths to
these items will not prevent non-FNAL users from running the
pre-built executables,
but they will prevent users from using the standard scripts to link
their own executable. Users at other sites can try to duplicate
the appropriate paths.
If there are any MINOS collaborators that use a Bourne-like shell
(eg. sh, ksh, bash) as their normal interactive shell at FNAL,
they should inform
Robert Hatcher
so that a script can be written with the appropriate syntax.
(He won't bother if the collection of such individuals is the null set).
Important locations
The three most important environment variables that get defined are:
| LABYRINTH_BIN |
executables including:
gminos_inter,
gminos_batch,
mad,
tip.
|
| LABYRINTH_LIB |
link libraries and selected .o files for the minos packages
and adamo |
| LABYRINTH_INC |
all the include files; both stand-alone and those derived
from the .ddl files (consistent with the corresponding
libraries in LABYRINTH_LIB). |
FNAL platforms / software status
The current status (at FNAL) of the
labyrinth is documented. One table records the available
machines, the other gives the dates when the software was compiled
for that platform.
Scripts for the "average user"
Theseus left behind scripts of
instructions to help others who venture into the labyrinth.
Why is the script area named theseus?
The story of Theseus and the Labyrinth
is an ancient Greek legend. Once you've ventured into the Labyrinth and
come out safely, don't forget to raise the white sail as you return
home in triumph.
Daedalus' blueprint
Daedalus was the architect of the labyrinth. Luckily, we managed to
obtain a copy of Daedalus' blueprint
to the Labyrith. Look it over before entering or risk becoming lost.
A warning
It is rumored that the Minotaur still roams the labyrinth. And he does
not take kindly to trash and litter. Upon encountering files that do not
belong he unceremoniously stomps them to bits.
The executables, libraries and include files will be unadulterated versions
of what is stored in the CVS respository. They will be plain vanilla;
users desiring a more individual flavor are invited to add their own
flavors but in some other directory structure. The theseus
scripts should help you do this, but they should be copied, modified and
run in your own area. Please do not confuse things by working in this
common area.
Robert Hatcher <hatcher@astro.indiana.edu>
Last modified: Thu Oct 17 17:23:20 1996