AliPHOSPIDv1

class description - source file - inheritance tree

class AliPHOSPIDv1 : public AliPHOSPID


    public:

         AliPHOSPIDv1 AliPHOSPIDv1()
         AliPHOSPIDv1 AliPHOSPIDv1(AliPHOSPIDv1&)
         virtual void ~AliPHOSPIDv1()
              TClass* Class()
      virtual TClass* IsA() const
         virtual void MakeParticles(TrackSegmentsList* trsl, RecParticlesList* rpl)
                 void Print()
         virtual void SetDispersionCutOff(Float_t Dcut)
         virtual void SetShowerProfileCuts(Float_t l1m, Float_t l1M, Float_t l2m, Float_t l2M)
         virtual void ShowMembers(TMemberInspector& insp, char* parent)
         virtual void Streamer(TBuffer& b)

  Data Members
    private:

      Float_t fLambda1m         minimum value for first elips axis
      Float_t fLambda1M         maximum value for first elips axis
      Float_t fLambda2m         minimum value for second elips axis
      Float_t fLambda2M         maximum value for second elips axis
      Float_t fCutOnDispersion  cut on the shower dispersion to distinguish hadronic from EM showers

Class Description

 Implementation version v1 of the PHOS particle identifier
 Identification is based on information from PPSD and EMC

*-- Author: Yves Schutz (SUBATECH)

void MakeParticles(TrackSegmentsList * trsl, RecParticlesList * rpl)

 Makes a RecParticle out of a TrackSegment

void Print()

 Print the parameters used for the particle type identification

void SetShowerProfileCuts(Float_t l1m, Float_t l1M, Float_t l2m, Float_t l2M)

 Modifies the parameters used for the particle type identification

Inline Functions

        AliPHOSPIDv1 AliPHOSPIDv1()
                void SetDispersionCutOff(Float_t Dcut)
             TClass* Class()
             TClass* IsA() const
                void ShowMembers(TMemberInspector& insp, char* parent)
                void Streamer(TBuffer& b)
        AliPHOSPIDv1 AliPHOSPIDv1(AliPHOSPIDv1&)
                void ~AliPHOSPIDv1()

ROOT page - Class index - Top of the page

This page has been automatically generated. If you have any comments or suggestions about the page layout send a mail to ROOT support, or contact the developers with any questions or problems regarding ROOT.