Stray cout in TMVA::MethodCategory::GetMvaValue?

Dear ROOTers,
after switching my project to use ROOT 6.26/02 and recompiling I now see a huge amount of output on stdout, such as

...
Event  is for method 0 spectator is 0.465203  0 classID 1 value -0.770011 type 0
Event  is for method 0 spectator is 0.29381  0 classID 1 value -0.999643 type 0
Event  is for method 0 spectator is 0.29381  0 classID 1 value -1 type 0
Event  is for method 0 spectator is 0.806349  0 classID 1 value -0.855285 type 0
Event  is for method 0 spectator is 0.806349  0 classID 1 value -0.248902 type 0
Event  is for method 0 spectator is 0.684604  0 classID 1 value -0.941092 type 0
Event  is for method 0 spectator is 0.684604  0 classID 1 value -0.224969 type 0
Event  is for method 1 spectator is 2.71182  0 classID 1 value -0.990149 type 0
Event  is for method 1 spectator is 2.71182  0 classID 1 value -0.524937 type 0
Event  is for method 1 spectator is 2.54111  0 classID 1 value -0.989283 type 0
Event  is for method 1 spectator is 2.54111  0 classID 1 value -0.348608 type 0
Event  is for method 1 spectator is 2.9538  0 classID 1 value -0.973136 type 0
...

Grepping around this seems to be caused by a debug cout in MethodCategory.cxx:633, which can also be seen again, commented out, in line 702.

Doesn’t seem intentional, is it still present upstream?


ROOT Version: 6.26/02
Platform: CentOS7
Compiler: gcc 9.3.0

@moneta could you have a look here, please?

Thank you for reporting this problem.
I have opened a PR, [TMVA] Fix printout message in MethodCategory::GetMvaValue by lmoneta · Pull Request #10707 · root-project/root · GitHub
fixing this problem

Best regards

Lorenzo

1 Like