Skip to content

[PWGLF] fix INEL evsel #18271

[PWGLF] fix INEL evsel

[PWGLF] fix INEL evsel #18271

Triggered via pull request October 6, 2025 15:06
@rspijkersrspijkers
opened #13253
Status Failure
Total duration 14s
Artifacts

o2-linter.yml

on: pull_request_target
O2 linter
11s
O2 linter
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 notices
[const-ref-in-for-loop]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L936
Use constant references for non-modified iterators in range-based for loops.
[const-ref-in-for-loop]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L853
Use constant references for non-modified iterators in range-based for loops.
[const-ref-in-for-loop]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L690
Use constant references for non-modified iterators in range-based for loops.
[const-ref-in-for-loop]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L689
Use constant references for non-modified iterators in range-based for loops.
[pdg/known-mass]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L469
Use o2::constants::physics::Mass... instead of calling a database method for a known PDG code.
[pdg/explicit-mass]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L427
Avoid hard-coded particle masses. Use o2::constants::physics::Mass... instead.
[pdg/explicit-code]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L1007
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
[pdg/explicit-code]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L469
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
[pdg/explicit-code]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L316
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
[root/lorentz-vector]: PWGLF/Tasks/Strangeness/cascadecorrelations.cxx#L43
Do not use the TLorentzVector legacy class. Use std::array with RecoDecay methods or the ROOT::Math::LorentzVector template instead.
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.