Yes, I think that in many cases this is what it boils down to.
Unfortunately one has to either
- do a retraining for this to take effect since a rederivation of the output histograms are beyond the current capabilities of the
TMVA::Gui
, or - manually evaluate the classifier using the
TMVA::Reader
constructing the histograms manually and finally running the KS test on this.
To change the binning for a retraining use (TMVA::gConfig().GetVariablePlotting()).fNbinsMVAoutput = 300;
at the top of the training file.
Cheers,
Kim