Muon Identification 

This page provides examples and instructions for installing and running MuonIdentification.
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 MuonIdentification

What release do you want to use? To answer this first of all have a look here
and check the release status. 
Your choice depend mainly if you are a MuonIdentification developer or if you are
willing to perform ``physics validation'', using MuonIdentification as reconstruction package.
In the following you find the versions we suggest you to use in both cases, at the time this
page has been written.

• 7.0.3 replaces the 7.0.2. In the contents, it is fairly similar to 7.0.1 except
  for a bug fix in TGC Detector Description interface.
  physics validation reference version : known problems: CSC hits.
  see presentation for Moore/MuID reference plots on efficiency and resolution.
  
  

• 7.3.0 Development version

• 7.4.0 Just out ( build with CMT v1r14p20031120)
  

---

Run MuonIdentification 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. 

• If you want to run MuonIdentification alone, from release 7, follow the previous instruction until the
  execution command in the run area, that in this case will be:

• athena MuonIdentification/Muid_jobOptions.txt

---

Getting the MuonIdentification code

1. Create a clean working directory with the path you have specified in the TestArea (see: Getting started), and cd to it
2. Checkout the RecExCommon code following the instructions given here
• cmt co -r RecExCommon-xx-xx-xx Reconstruction/RecExample/RecExCommon
3. 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/Reconstruction/MuonIdentification/
• will show you: MuonIdentification-01-04-09
4. Checkout the MuonIdentification package
• cmt co -r MuonIdentification-01-04-69 Reconstruction/MuonIdentification
5. Build only MuonIdentification 
• cd Reconstruction/MuonIdentification/MuonIdentification-01-04-69/cmt
• cmt config
• gmake
6. From this point please follows the instructions from Build  on, as from RecExCommon (see here  )
7.  For the  final  run you can use directly the Muid_jobOptions as explained in the previoud paragraph:
• athena MuonIdentification/Muid_jobOptions.txt > TestOut.t 

---

MuonIdentification JobOptions parameters

MuonIdentification JobOptions  file contains a brief reminder of the parameters adjustable run-time. Only the parameters relevant 
for users are reported here.

---

MuonIdentification Output

At present, by default, MuonIdentification output consists of an ntuple.

---

Running in batch

Please have a look at the instructions given for RecExample, adapting them to the MuonIdentification 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 MuonIdentificationcase.

---

Comments to (Gabriella.Cataldi@le.infn.it).

---

Last modified, 16^th December  2003