class AliAnalysisTriggerScalers: public TObject

 ctor using a single run number

 ctor using a vector of run numbers

 ctor using a set of run numbers

 ctor from a run list (txt file)

 dtor

 Check if a trigger scaler record should be kept for our
 luminosity computations

 Draw a yellow box to indicate a run range

 Draw the fill ranges corresponding to the list of runs
 Note that this method will scan the OCDB to get the run -> fill number relationship,
 so it's better in this case to use a local copy of the OCDB if you have one. Otherwise
 it will be long.

 Draw the period ranges corresponding to the list of runs
 Note that this method will scan the OCDB to get the run -> fill number relationship,
 so it's better in this case to use a local copy of the OCDB if you have one. Otherwise
 it will be long.

 For a given run, get the CTP objects we need to do our work

 FIXME: this is the method that should probably be virtualized so
 we can get those objects from either OCDB or run based container in AODs/ESDs

 Given a list of runs get the fills they are in

 Get the fill number of a run

 Helper method to get an object from the OCDB

 Get a list of LHC periods from a list of run numbers

 For one given run, get the trigger class name to be used as the luminometer,
 and its corresponding cross-section

 FIXME: all is hard-coded for now... (use OADB for this ?)

 Given a list of runs get the fills they are in

 Get one trigger input for a given run

 Tries to estimate the duration of the Pause and Configure phase(s) in a given run
 Probably not really accurate for the moment though.

 Printout the pile-up factors for the runlist, including some purity if needed

 Get the mean pile-up correction factor for the given run

 Get the scaler for a given trigger class and a given trigger level.
 Returned object must be deleted by the user.

 Get the integrated luminosity graph for one trigger

 Get the integrated luminosity graph for one trigger for the given run

 the triggerClassNameForPACEstimate is only used if triggerClassName is,
 for the given run, the same as the luminometer trigger class name,
 and should be the trigger class with the higher and non-zero L0A rate (except during PACs)

 Compute the luminosity for a set of triggers

 Build a graph from a set of stl vectors

 L0B = trigger rate before any veto
 Nb = number of crossing bunches

 Extract the number of colliding bunches from the LHC data
 Use mainSat = true if the collisons were main - satellite ones

 Plot one of the scalers (L0A,L0B,L0AOVERB,etc...) of a given triggerClass
 Get one value per run.

 Make a graph of "what" for a given trigger class.

 What can be :

 - L0B (level 0 before any veto applied)
 - L0A (level 0 after all vetoes)
 - L0AOVERB (L0A/L0B)
 - mu ( = -TMath::Log( 1 - P(0) ) where P(0) is the proba to have zero collisions in a bunch crossing)
 - pileupfactor = mu/(1-exp(-mu)) : the factor to apply to correct the cint1b count rate
 - vsnb = L0B/(NumberOfInteractingBunches*11245)
 - NBCX = NumberOfInteractingBunches

 Plot the ratio of two scalers.
 Get one value per run.

 Plots the evolution of one trigger ratio

 print our runlist

 print a list of integers

 Read integers from filename, where integers are either
 separated by "," or by return carriage

 Make the runlist be a single run

 Make the runlist be a single run

 Make the runlist be a single run

 Read the runlist from an ASCII file or a comma separated list
 or a space separated list