// PbPb 2010, period 10h.pass2
//TODO Needs further development const Bool_t is10hpass2 = period.Contains("LHC10H") && recopass == 2;
+
+ // In case of MC without(!) tune on data activated for the TPC, don't use the multiplicity correction for the moment
+ Bool_t isMCandNotTPCtuneOnData = fIsMC && !(fTuneMConData && ((fTuneMConDataMask & kDetTPC) == kDetTPC));
+
// If correction is available, but disabled (highly NOT recommended!), print warning
- if (!fUseTPCMultiplicityCorrection && !isPP) {
+ if (!fUseTPCMultiplicityCorrection && !isPP && !isMCandNotTPCtuneOnData) {
//TODO: Needs further development if (is10hpass2 || isPPb2013LowLuminosity) {
if (isPPb2013LowLuminosity) {
AliWarning("Mulitplicity correction disabled, but correction parameters for this period exist. It is highly recommended to use enable the correction. Otherwise the splines might be off!");
}
}
- if (fUseTPCMultiplicityCorrection && !isPP) {
+ if (fUseTPCMultiplicityCorrection && !isPP && !isMCandNotTPCtuneOnData) {
AliInfo("Multiplicity correction enabled!");
//TODO After testing, load parameters from outside
// directly and use it for calculations - which should still give valid results, even if
// the multiplicity correction is explicitely enabled in such expert calls.
+ TString reasonForDisabling = "requested by user";
+ if (fUseTPCMultiplicityCorrection) {
+ if (isPP)
+ reasonForDisabling = "pp collisions";
+ else
+ reasonForDisabling = "MC w/o tune on data";
+ }
+
AliInfo(Form("Multiplicity correction %sdisabled (%s)!", fUseTPCMultiplicityCorrection ? "automatically " : "",
- fUseTPCMultiplicityCorrection ? "pp collisions" : "requested by user"));
+ reasonForDisabling.Data()));
fUseTPCMultiplicityCorrection = kFALSE;
fTPCResponse.ResetMultiplicityCorrectionFunctions();