Muon
Object Oriented REconstruction
This page provides examples
and instructions for installing and running MOORE.
Basic familiarity with Athena concepts is implied below.
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.....
What release do you want to use?
It depends if you are (or would like to be) a Moore
developer or if you are
just willing to perform ``physics validation'',
using Moore for reconstructing.
In the following you find the versions we suggest you to use in both cases.
- 7.0.1 has been used for a first round
of physic validation see plots
- 7.0.2 similar to
7.0.1 except for a bug fix in TGC Detector Description interface.
- physics validation reference version : known problems: CSC hits.
- 7.2.0 Development
version (CSC and TGC problem solved?) to be checked
- 7.3.0 Not yet out (it is in build with
CMT v1r14p20031027)
Run MOORE as a part of the ATHENA
reconstruction
IMPORTANT
unless you need to modify MOORE, you do not need to check it out.
MOORE is part of the official software, so you may
just want to reconstruct
only muons in the muon spectrometer, using MOORE,
or to run the full
reconstruction (or part of it) in ATHENA.
- For running the full Athena reconstruction, see the instructions
given here.
These instructions includes also the customization
of your running chain, so in case you
want to select only part of the Athena
reconstruction read a bit more.
omitting the steps from 3 to 6.
Getting the Moore code
- Create a clean
working directory with the path you have specified in the TestArea (see: Getting started), and
cd to it
- Checkout the
TestRelease code
- Check which version of Moore correspond
to the release (let's assume you want to use release 7.2.0):
- ls /afs/cern.ch/atlas/software/dist/7.2.0/MuonSpectrometer/Moore/
- will show you:
MooAlgs MooEvent Moore-00-00-64 MooStatistics
- Moore is a container package Moore-00-00-64 is the version of the package
- MooAlgs, MooEvent,
MooStatistics are sub-containers
- Checkout the
Moore container package
- cmt co -r Moore-00-00-64 MuonSpectrometer/Moore
- Check which versions of the subcontainers
are linked by this package:
- more MuonSpectrometer/Moore/Moore-00-00-64/cmt/requirements
- contains the use specifications, where
the versions of the subcontainers are expressely given
- in the specific case: MooAlgs-00-00-64 MooEvent-00-00-64 MooStatistics-00-00-64
- Checkout the
code (the code is included in the subcontainers)
- cmt co -r MooAlgs-00-00-64 MuonSpectrometer/MooAlgs
- cmt co -r MooEvent-00-00-64 MuonSpectrometer/MooEvent
- cmt co -r MooStatistics-00-00-64
MuonSpectrometer/MooStatistics
- Build
- cd TestRelease/TestRelease**/cmt
- cmt broadcast cmt
config
- cmt broadcast gmake
- Define environment
variables (to be repeated in any new window)
- cd ../run
- source ../cmt/setup.(c)sh
- Setup auxilliary files (only once in a given directory,
and whenever new packages are checked out) and a dataset
- 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
- the previous is only an example
dataset. If you would like to use an own dataset check here for how to link your data.
- And finally
run:
- athena Moore_jobOptions.txt > TestOut.t
Running in batch
Please have a look
at the instructions given for RecExample, adopting them to the
Moore 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, adopting them to the Moore case.
Please
send comments, suggestions to me (Gabriella.Cataldi@le.infn.it).
Last modified, 12th September 2003