TrigMoore
This page provides examples
and instructions for installing and running TrigMoore.
Basic familiarity with Athena concepts is implied in the following.
A useful and regularly updated
source of information is the RecExample web
page where several information
on how to run a generic reconstruction package are given. In the
following frequent links to this page are given.
Getting started
- please check the instructions given here for knowing how to:
- set up your CMT area
- select an optimized build
- and more.....
- Releases Vs TrigMoore
What release do you want to use? To answer this first of all have a look here
and check the release status.TrigMoore is a package in development, and so are, several other packages related to
the so colled Trigger Muon Slice. Therefore we are unable to ``point'' you towards a
release that you can just run as a ``black box'' from the repository.
If you are willing to work on TrigMoore, you are willing to become a TrigMoore developer.
The version we suggest you to use at the time this
page has been written is:
7.3.0
Getting the TrigMoore code for release 7.2.0
- Create
a clean working directory with the path you have specified in the TestArea (see: Getting started), and
cd to it
- Check which version of TriggerRelease correspond to the release 7.2.0:
- ls /afs/cern.ch/atlas/software/dist/7.2.0/Trigger/TriggerRelease
- will show TriggerRelease-00-00-94
- Check out the TriggerRelease code:
- cmt co -r TriggerRelease-00-00-94 Trigger/TriggerRelease
- Check
which version of TrigMoore corresponds to the release 7.2.0:
- ls /afs/cern.ch/atlas/software/dist/7.3.0/Trigger/TrigAlgorithms/TrigMoore
- will show you:
TrigMoore-00-00-04
- Check
out the TrigMoore code (because of bug fixes please check out the 00-00-08
tag):
- cmt co -r TrigMoore-00-00-08 Trigger/TrigAlgorithms/TrigMoore
- Build only TrigMoore
- cd Trigger/TrigAlgorithms/TrigMoore/TrigMoore-00-00-08/cmt
- cmt config
- gmake
- Then setup the TriggerRelease area :
- cd ../../../../TriggerRelease/TriggerRelease-00-00-97/cmt
- cmt broadcast cmt config
- cmt broadcast gmake
- source setup.csh
- From the TriggerRelease run directory:
- copy the correct maps for MDT and RPC region selector:
-
cp ../../../TrigAlgorithms/TrigMoore/TrigMoore-00-00-08/share/MdtMap.txt MDTMapIdAndHash.txt
-
cp ../../../TrigAlgorithms/TrigMoore/TrigMoore-00-00-08/share/RpcMap.txt RPCMapIdAndHash.txt
- Create a link with fieldmap and data
file:
ln -s /afs/cern.ch/atlas/offline/data/bmagatlas02.data fieldmap.dat
stagein -M /castor/cern.ch/atlas/project/dc1/simul/data/001108/dc1.001108.simul.0001.test.mu_plus_20.zebra ZEBRA.P - Run
- athena TrigMoore/MooreHLT_wrap_jobOptions.txt
- athena TrigMoore/MooreHLT_seed_jobOptions.txt
Running in batch
Please have a look
at the instructions given for RecExample, adapting them to the
TrigMoore case.
Using valgrind (only release 6.3.0
and above)
valgrind is a tool to find memory leaks and other run time errors like
branch on uninitialized variables.
For using it please follow the instructions given here for RecExample, adapting them to the TrigMoore
case.
Comments to (Gabriella.Cataldi@le.infn.it).
Last modified, 16th December 2003