bartMachineCV is very verbose, even with verbose = FALSE. I know some messages come from Java directly, but there are others that come from R and that, arguably, should not be produced with verbose = FALSE. Two main issues:
These are some screenshots of such a debugging session. Note the value of verbose is FALSE:
We run and this happens (note the verbose output)
Now, if we call bart_machine_cv explicitly passing verbose = verbose it honors the argument:
A second problem is that build_bart_machine_cv has many cats that are not surrounded by the if (verbose) construction that is present in, say, build_bart_machine itself . (I actually wonder if using cat, instead of message is best practice; but this is a different issue).
bartMachineCVis very verbose, even withverbose = FALSE. I know some messages come from Java directly, but there are others that come from R and that, arguably, should not be produced withverbose = FALSE. Two main issues:build_bart_machine_cv, here: https://github.com/kapelner/bartMachine/blob/67607dedeec186ea90eaa960224253d56f93a314/bartMachine/R/bart_package_builders.R#L682 , the call tobart_machine_cvdoes not pass theverboseargument (passing the...does not do here), and thusbart_machine_cvis run with its defaultverbose = TRUE.(How to reproduce: launch bartMachineCV and set a break point right before that call.
These are some screenshots of such a debugging session. Note the value of
verboseisFALSE:We run and this happens (note the verbose output)
Now, if we call
bart_machine_cvexplicitly passingverbose = verboseit honors the argument:build_bart_machine_cvhas manycats that are not surrounded by theif (verbose)construction that is present in, say,build_bart_machineitself . (I actually wonder if usingcat, instead ofmessageis best practice; but this is a different issue).