X-Git-Url: http://git.uio.no/git/?a=blobdiff_plain;f=MUON%2FREADME;h=2f0c8d4d5df871ee5fc344f068dbea62236a5d71;hb=9473b3715f3084bf837da37810ec5d2b9bd2c546;hp=01bb0378d41815022602d4bb6d0e30d64b81bf9b;hpb=88cb7938ca21d4a80991d4e7aa564008c29340f7;p=u%2Fmrichter%2FAliRoot.git diff --git a/MUON/README b/MUON/README index 01bb0378d41..2f0c8d4d5df 100644 --- a/MUON/README +++ b/MUON/README @@ -1,3 +1,20 @@ +/************************************************************************** + * Copyright(c) 1998-1999, ALICE Experiment at CERN, All rights reserved. * + * * + * Author: The ALICE Off-line Project. * + * Contributors are mentioned in the code where appropriate. * + * * + * Permission to use, copy, modify and distribute this software and its * + * documentation strictly for non-commercial purposes is hereby granted * + * without fee, provided that the above copyright notice appears in all * + * copies and that both the copyright notice and this permission notice * + * appear in the supporting documentation. The authors make no claims * + * about the suitability of this software for any purpose. It is * + * provided "as is" without express or implied warranty. * + **************************************************************************/ + +/* $Id$ */ + ========================================================== Please add to this README file all information concerning config files, simulation, digitalization, clusterization, @@ -13,7 +30,6 @@ root [0] gAlice->Run(10,"$ALICE_ROOT/MUON/Config_MUON_test.C"); acceptance will be simulated using geant3. Hit information will be store in the root file in the execution directory. - If you want to change the option or to define a new directory for hits, you have to do the following before: root [0] gAlice->SetConfigFunction("Config( \"/home/martinez/aliroot/work_NewIO/test/\" , \"box\" );"); @@ -24,44 +40,55 @@ root [0] gAlice->SetConfigFunction("Config( \"/home/martinez/aliroot/work_NewIO/ To process the digitalization of hits the AliRunDigitizer framework is used: -root [0] AliRunDigitizer * manager = new AliRunDigitizer(1,1); -root [1] manager->SetInputStream(0,"galice.root"); -root [2] AliMUONDigitizerv1* dMUON = new AliMUONDigitizerv1(manager); -root [3] manager->AddDigitizer(dMUON); -root [4] manager->Exec("deb"); +AliRunDigitizer * manager = new AliRunDigitizer(1,1); +manager->SetInputStream(0,"galice.root"); +AliMUONDigitizerv1* dMUON = new AliMUONDigitizerv1(manager) +manager->AddDigitizer(dMUON); +manager->Exec("deb"); ============================================================ How to run MUON RecPoint clusterization ============================================================ aliroot -b << EOF -root [0].L $ALICE_ROOT/MUON/MUONrawclusters.C -root [1] MUONrawclusters("galice.root",0,2); - -First event and last event are given by hand, but this will change. +.includepath $ALICE_ROOT/STEER +.includepath $ALICE_ROOT/MUON +.L $ALICE_ROOT/MUON/MUONrawclusters.C++ +MUONrawclusters("galice.root",0,9999); +to Load +gSystem->Load("$ALICE_ROOT/MUON/MUONrawclusters_C.so") ============================================================ How to run MUON Trigger ============================================================ -root [0].L $ALICE_ROOT/MUON/MUONtrigger.C -root [1] MUONtrigger("galice.root",0,9); ->> IMPORTANT NOTE: in the present version, one can only have either ->> rawclusters or trigger information written in MUON.RecPoints.root ->> but not both of them i.e. running MUONtrigger after MUONrawclusters ->> will erase rawclusters from TreeR and vice versa. - -First event and last event are given by hand, but this will change. - -============================================================ - How to run MUON Tracking reconstruction +.includepath $ALICE_ROOT/STEER +.includepath $ALICE_ROOT/MUON +.L $ALICE_ROOT/MUON/MUONtrigger.C++ +MUONtrigger("galice.root",0,9999); +To Load +gSystem->Load("$ALICE_ROOT/MUON/MUONtrigger_C.so") ============================================================ - -root [0] .includepath $ALICE_ROOT/STEER -root [1] .includepath $ALICE_ROOT/MUON -root [2] .L $ALICE_ROOT/MUON/MUONrecoNtuple.C++ -root [3] MUONrecoNtuple(0,1,0,"galice.root") - + How to run MUON Tracking reconstruction (old output) +=========================================================== +.includepath $ALICE_ROOT/STEER +.includepath $ALICE_ROOT/MUON +.L $ALICE_ROOT/MUON/MUONrecoNtuple.C++ +MUONrecoNtuple(0,9999,0,"galice.root") +To Load +gSystem->Load("$ALICE_ROOT/MUON/MUONrecoNtuple_C.so") First event and last event are given by hand, but this will change. +=========================================================== + How to run MUON Tracking reconstruction (new output) +=========================================================== +.includepath $ALICE_ROOT/STEER +.includepath $ALICE_ROOT/MUON +.L $ALICE_ROOT/MUON/MUONTracker.C++ +MUONTracker("galice.root",0,9999); +To Load +gSystem->Load("$ALICE_ROOT/MUON/MUONTracker_C.so") +Output in MUON.Tracks.root using the new IO +as a TClonesArray of AliMUONTrack + ============================================================ How to run MUONCheck macro ============================================================ @@ -69,21 +96,26 @@ To check the content of a root data file, the MUONCheck provides a ascii output on screen. To compile MUONCheck.C -root [0] .includepath $ALICE_ROOT/STEER -root [1] .includepath $ALICE_ROOT/MUON -root [2] .L $ALICE_ROOT/MUON/MUONCheck.C++ +.includepath $ALICE_ROOT/STEER +.includepath $ALICE_ROOT/MUON +.L $ALICE_ROOT/MUON/MUONCheck.C++ +To Load +gSystem->Load("$ALICE_ROOT/MUON/MUONCheck_C.so") + +To print Kine : (default file is galice.root ) +MUONkine() To print hits : (default file is galice.root if not MUONhits("toto.root""); ) -root [3] MUONhits() +MUONhits() To print digits : (default file is galice.root) -root [4] MUONdigits() +MUONdigits() To print rawcluster : (default file is galice.root) -root [5] MUONrecpoints() +MUONrecpoints() To print trigger : (default file is galice.root) -root [5] MUONTestTrigger() +MUONTestTrigger() =========================================================== Still working ..............