[PWGJE] Configurable GNN input feature transform function #22400
Annotations
10 errors and 2 notices
|
Run tests:
PWGJE/Tasks/bjetTaggingGnn.cxx#L549
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
PWGJE/Tasks/bjetTaggingGnn.cxx#L426
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
PWGJE/Tasks/bjetTaggingGnn.cxx#L425
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
PWGJE/Tasks/bjetTaggingGnn.cxx#L419
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
Run tests:
PWGJE/TableProducer/jetTaggerHF.cxx#L1
Specify task name only when it cannot be derived from the struct name. Only append to the default name.
|
|
Run tests:
PWGJE/TableProducer/jetTaggerHF.cxx#L708
Device names jet-taggerhf-mcd-charged and jet-taggerhf-m-c-d-charged generated from the specified task name jet-taggerhf-mcd-charged and from the struct name JetTaggerhfMCDCharged, respectively, differ in hyphenation. Consider fixing capitalisation of the struct name to JetTaggerhfMcdCharged and removing TaskName.
|
|
Run tests:
PWGJE/TableProducer/jetTaggerHF.cxx#L707
Specified task name jet-taggerhf-data-charged and the struct name JetTaggerhfDataCharged produce the same device name jet-taggerhf-data-charged. TaskName is redundant.
|
|
Run tests:
PWGJE/Core/MlResponseHfTagging.h#L470
Use constant references for non-modified iterators in range-based for loops.
|
|
Run tests:
PWGJE/Core/MlResponseHfTagging.h#L415
Use constant references for non-modified iterators in range-based for loops.
|
|
Run tests:
PWGJE/Core/MlResponseHfTagging.h#L213
Use constant references for non-modified iterators in range-based for loops.
|
|
Run tests
To tolerate certain issues in a directory, add a line with the test name in "o2linter_config".
|
|
Run tests
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.
|
Loading