class AliTPCPIDResponse: public TNamed

  The default constructor

 Destructor

copy ctor

assignment

 This is the Bethe-Bloch function normalised to 1 at the minimum
 WARNING
 Simulated and reconstructed Bethe-Bloch differs
           Simulated  curve is the dNprim/dx
           Reconstructed is proportianal dNtot/dx
 Temporary fix for production -  Simple linear correction function
 Future    2 Bethe Bloch formulas needed
           1. for simulation
           2. for reconstructed PID

 Set the parameters of the ALEPH Bethe-Bloch formula

 Set the relative resolution  sigma_rel = res0 * sqrt(1+resN2/npoint)

 Deprecated function (for backward compatibility). Please use
 GetExpectedSignal(const AliVTrack* track, AliPID::EParticleType species, ETPCdEdxSource dedxSource,
                   Bool_t correctEta, Bool_t correctMultiplicity);
 instead!


 Calculates the expected PID signal as the function of
 the information stored in the track, for the specified particle type

 At the moment, these signals are just the results of calling the
 Bethe-Bloch formula.
 This can be improved. By taking into account the number of
 assigned clusters and/or the track dip angle, for example.

charge factor. BB goes with z^2, however in reality it is slightly larger (calibration, threshold effects, ...)
 !!! Splines for light nuclei need to be normalised to this factor !!!

 Deprecated function (for backward compatibility). Please use
 GetExpectedSigma(onst AliVTrack* track, AliPID::EParticleType species,
 ETPCdEdxSource dedxSource, Bool_t correctEta) instead!


 Calculates the expected sigma of the PID signal as the function of
 the information stored in the track, for the specified particle type

 Set the relative resolution  sigma_rel = res0 * sqrt(1+resN2/npoint)

 Calculates the expected PID signal as the function of
 the information stored in the track and the given parameters,
 for the specified particle type

 At the moment, these signals are just the results of calling the
 Bethe-Bloch formula plus, if desired, taking into account the eta dependence
 and the multiplicity dependence (for PbPb).
 This can be improved. By taking into account the number of
 assigned clusters and/or the track dip angle, for example.

 Calculates the expected PID signal as the function of
 the information stored in the track, for the specified particle type

 At the moment, these signals are just the results of calling the
 Bethe-Bloch formula plus, if desired, taking into account the eta dependence
 and the multiplicity dependence (for PbPb).
 This can be improved. By taking into account the number of
 assigned clusters and/or the track dip angle, for example.

get response function

the splines are stored in an array, different scenarios

reset the array with splines

get the index in fResponseFunctions given type and scenario

 Calculates the expected sigma of the PID signal as the function of
 the information stored in the track and the given parameters,
 for the specified particle type

 Calculates the expected sigma of the PID signal as the function of
 the information stored in the track, for the specified particle type
 and dedx scenario

Calculates the number of sigmas of the PID signal from the expected value
for a given particle species in the presence of multiple gain scenarios
inside the TPC

Calculates the number of sigmas of the PID signal from the expected value
for a given particle species in the presence of multiple gain scenarios
inside the TPC

 Calculates the right parameters for PID
   dEdx parametrization for the proper gain scenario, dEdx
   and NPoints used for dEdx
 based on the track geometry (which chambers it crosses) for the specified particle type
 and preferred source of dedx.
 returns true on success

 NOTE: For expert use only -> Non-experts are advised to use the function without the "Fast" suffix or stick to AliPIDResponse directly.

 Get eta correction for the given parameters.

 Get eta correction for the given track.

 Get eta corrected dEdx for the given track. For the correction, the expected dEdx of
 the specified species will be used. If the species is set to AliPID::kUnknown, the
 dEdx of the track is used instead.
 WARNING: In the latter case, the eta correction might not be as good as if the
 expected dEdx is used, which is the way the correction factor is designed
 for.
 In any case, one has to decide carefully to which expected signal one wants to
 compare the corrected value - to the corrected or uncorrected.
 Anyhow, a safer way of looking e.g. at the n-sigma is to call
 the corresponding function GetNumberOfSigmas!

 NOTE: For expert use only -> Non-experts are advised to use the function without the "Fast" suffix or stick to AliPIDResponse directly.

 Get parameter 1 of sigma parametrisation of TPC dEdx from the histogram for the given track.

 Get parameter 1 of sigma parametrisation of TPC dEdx from the histogram for the given track.

 Load map for TPC eta correction (a copy is stored and will be deleted automatically).
 If hMap is 0x0,the eta correction will be disabled and kFALSE is returned.
 If the map can be set, kTRUE is returned.

 Load map for TPC sigma map (a copy is stored and will be deleted automatically):
 Parameter 1 is stored as a 2D map (1/dEdx vs. tanTheta_local) and parameter 0 is
 a constant. If hSigmaPar1Map is 0x0, the old sigma parametrisation will be used
 (and sigmaPar0 is ignored!) and kFALSE is returned.
 If the map can be set, sigmaPar0 is also set and kTRUE will be returned.

 Extract the tanTheta from the information available in the AliVTrack

 NOTE: For expert use only -> Non-experts are advised to use the function without the "Fast" suffix or stick to AliPIDResponse directly.

 Calculate the multiplicity correction factor for this track for the given multiplicity.
 The parameter dEdxExpected should take into account the eta correction already!

 Get multiplicity correction for the given track (w.r.t. the mulitplicity of the current event)

 Get multiplicity corrected dEdx for the given track. For the correction, the expected dEdx of
 the specified species will be used. If the species is set to AliPID::kUnknown, the
 dEdx of the track is used instead.
 WARNING: In the latter case, the correction might not be as good as if the
 expected dEdx is used, which is the way the correction factor is designed
 for.
 In any case, one has to decide carefully to which expected signal one wants to
 compare the corrected value - to the corrected or uncorrected.
 Anyhow, a safer way of looking e.g. at the n-sigma is to call
 the corresponding function GetNumberOfSigmas!

 Get multiplicity and eta corrected dEdx for the given track. For the correction,
 the expected dEdx of the specified species will be used. If the species is set
 to AliPID::kUnknown, the dEdx of the track is used instead.
 WARNING: In the latter case, the correction might not be as good as if the
 expected dEdx is used, which is the way the correction factor is designed
 for.
 In any case, one has to decide carefully to which expected signal one wants to
 compare the corrected value - to the corrected or uncorrected.
 Anyhow, a safer way of looking e.g. at the n-sigma is to call
 the corresponding function GetNumberOfSigmas!

 NOTE: For expert use only -> Non-experts are advised to use the function without the "Fast" suffix or stick to AliPIDResponse directly.

 Calculate the multiplicity sigma correction factor for the corresponding expected dEdx and for the given multiplicity.
 The parameter dEdxExpected should take into account the eta correction already!

 Get multiplicity sigma correction for the given track (w.r.t. the mulitplicity of the current event)

 Default values: No correction, i.e. overall correction factor should be one

calculate the sector numbers (equivalent to IROC chamber numbers) a track crosses
for OROC chamber numbers add 36
returned angles are between (0,2pi)

calculate sector number

Print info

return the radius of the outermost padrow containing a cluster in TPC
for the track

calculate the coordinates of the apex of the track

 Evaluate the dEdx response for given entry

 register spline to be used for drawing comparisons

Better prevent user from setting fMIP != 50. because fMIP set fix to 50 for much other code: