LegsMakerDeadOrAlife

class LegsMakerDeadOrAlife : public LegsMaker

    public:

                            LegsMakerDeadOrAlife(int add = 1)
                            LegsMakerDeadOrAlife(const LegsMakerDeadOrAlife&)
                    virtual ~LegsMakerDeadOrAlife()
             static TClass* Class()
               virtual void Init()
            virtual TClass* IsA() const
               virtual bool Make()
      LegsMakerDeadOrAlife& operator=(const LegsMakerDeadOrAlife&)
               virtual void RunEnd()
               virtual void ShowMembers(TMemberInspector& insp, char* parent)
               virtual void Streamer(TBuffer& b)
                       void StreamerNVirtual(TBuffer& b)

Data Members

    public:

      TH1F* fHistPol  

Class Description

 The LegsMakerDeadOrAlife class is first attempt to design a user class
 which would contain a user cut and all necessay data for the
 cut. Details of data input-output, event display, and other
 standard functions are supposed to be implemented elsewhere. Once
 certain part of user class becomes standard it should move into
 appropriate standard place.  Anyway, LegsMaker class has standard
 member functions which have to exist for proper linking to LegsRun
 class ( major analysis class). They get called from LegsRun at certain
 times.  These are: LegsMaker() (constructor), ~LegsMaker() (destructor),
 Init() (called only once at the beginning of data stream), Make()
 (called every event), PostProcessing() (called only once at the
 end of data
 stream). User may modify contents of existing functions as he
 wishes (except changing type of the function or number of its'
 parameters) or/and add unlimited number of other member
 functions. If two separate functions are believed to be necessary
 to call separately from LegsRun class then it is probably possible
 to split them into two different classes ( LegsMakerDeadOrAlifea and LegsMakerDeadOrAlifeb
 say). Also, class LegsMakerDeadOrAlife has to have standard data-members: NONE
 ( at the moment 12-18-1999). User may add any number of
 additional data members. All data-members may be saved into file
 by simple call to LegsMakerDeadOrAlife.Write(). This way, user does not have to
 bother with IO at all. Everything gets written into ROOT file
 automatically. WORD OF CAUTION : STL templates cannot be handled
 by ROOT nicely. So I am scratching my head on what to do - STL is
 nice and standard, but I don't want to trouble myself with the
 IO...
______________________________________________________________________

 user initialization, create histos  etc

 called by LegsRun every event when LegsRun::Loop() is called.
 this is the main function from which other functions can be called.

 executed at the end of run

Inline Functions

                         void ~LegsMakerDeadOrAlife()
                      TClass* Class()
                      TClass* IsA() const
                         void ShowMembers(TMemberInspector& insp, char* parent)
                         void Streamer(TBuffer& b)
                         void StreamerNVirtual(TBuffer& b)
         LegsMakerDeadOrAlife LegsMakerDeadOrAlife(const LegsMakerDeadOrAlife&)
        LegsMakerDeadOrAlife& operator=(const LegsMakerDeadOrAlife&)