The MARPLE package is a part of ARTE. To run MARPLE the standard ARTE rules should be used. It means that the marple package must be initialized, then called for each event and at the end of program it should be correctly terminated.
There are 3 ways to go :
- The default reconstruction (rc99Aevnt) which works on real data (ARTE-03-05 - ... ). The necessary calls are done automaticaly. User could steer the program using kuip commands in user kumac file. Possible commands :
- MATCH marple vds pc
- - match of VDS and PC-OTR subdetectors
- MATCH marple vds otr
- - match of VDS and OTR subdetectors
- MATCH marple vds ecal
- - match of VDS and ECAL subdetectors
- MATCH marple vds rich
- - match of VDS and RICH subdetectors
- MATCH marple rich ecal
- - match of RICH and ECAL subdetectors
- MATCH marple otr rich
- - match of OTR and RICH subdetectors
- MATCH marple otr ecal
- - match of OTR and ECAL subdetectors
- MATCH marple rtra rich
- - match of RTRA tracks and ECAL subdetector
- MARPLE/SOFT 1
- - chooses soft cuts for matching instead of default(0) ones. It helps to see correlation between parts but the ghost rate is higher. For SVD-PC match one can set parameters from 1(softest) to 5 (hardest), the default in this case 3 (equal 0).
- MARPLE/MAKERSEG 1
- - requires the result of matches to be saved as independent segment in the RSEG table. For the rc99Aevnt it is done by default.
- MARPLE/MASVDECALNORTRA <Int> <Int>
- - switches to apply Match SVD - ECAL to all/unmatched SVD and ECAL :
- 0 0
- - all SVD segments and all ECAL are matched
- 0 1
- - all SVD and only ECAL NOT used in RTRA
- 1 0
- - only SVD NOT used in RTRA and all ECAL
- 1 1
- - both SVD and ECAL should NOT be used in RTRA
Please, note, that from ARTE-03-09-r5 the option does not affect clusters with Et > 0.9 GeV. Those are matched in standard way.
- MARPLE/MARICHSIGMASQR <Float>
- -set a cut on the RISE identification for SVD-RICH match.
- MARPLE/MASVDECALET <Float>
- - the threshold on ET of cluster for SVD-ECAL match it is considered as Ktrig cut if the value > 200.
- MARPLE/DEBUG <N>
- - gives printout of the match on the screen (N=0,1,2). For MC it also calculates number of good and ghost pairs. For N=10,20 the hbook ntuples are created without printout. N=-1 means no printout, no ntuples.
- There is a concurent reconstruction chain designed for complete detector rcZevnt_() . in the ARTE-03-05 it worked only on MC data. The marple algorithm used here is matchsvdmt_(), which is match of VDS and Main Tracker. It is called if you choose rcZevnt_(). The kuip command :
- RECO/alg/Activate MARPLE
- - might be necessary. The commands :
- MARPLE/SOFT, MARPLE/MAKERSEG, MARPLE/DEBUG
- are valid for this version as well.
- In case you need to build your own code, or you would like to call marple explicitly without any reconstruction chain, the following functions are needed :
- Initialization (e.g. in usinit_() )
- All Supplied Products could be called directly from usevnt_() routine (they are both C++ and FORTRAN callable). The rc99Match() routine (ARTE-03-04-..) allows to use kuip match commands (C++ callable).
- To terminate marple correctly call from usstop_() :
alphabetic index hierarchy of classes
generated by doc++