[PWGCF] FU: PID selection and corr. bkgs update #25931
Annotations
10 errors, 1 warning, and 2 notices
|
[root/lorentz-vector]:
PWGCF/FemtoUniverse/TableProducer/femtoUniverseProducerTask.cxx#L59
Do not use the TLorentzVector legacy class. Use std::array with RecoDecay methods or the ROOT::Math::LorentzVector template instead.
|
|
[magic-number]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L470
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L467
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L464
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[pdg/explicit-code]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L470
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L467
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L464
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L462
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L460
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[using-directive]:
PWGCF/FemtoUniverse/Core/FemtoUniverseParticleHisto.h#L31
Do not put using directives at global scope in headers.
|
|
O2 linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: thollander/actions-comment-pull-request@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
O2 linter
To tolerate certain issues in a directory, add a line with the test name in "o2linter_config".
|
|
O2 linter
Exceptionally, you can disable a test for a line by adding a comment with "o2-linter: disable=" followed by the name of the test and parentheses with a reason for the exception.
|