[PWGLF] Add TOF PID + LS background #11853
+42
−7
Merged
Annotations
10 errors and 2 notices
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L56
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L1
Name of a workflow file must match the name of the main struct in it (without the PWG prefix). (Class implementation files should be in "Core" directories.)
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L49
Use UpperCamelCase for names of structs.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L34
Use UpperCamelCase for names of structs.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L273
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L219
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L157
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L273
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L219
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
PWGLF/Tasks/Resonances/lambda1405analysis.cxx#L50
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
|
|
|
The logs for this run have expired and are no longer available.
Loading