When the level of verbosity is changed with respect to the default to avoid the display of ProgressBar (i.e., mit.set_verbose(2)), the indentation of some "subinfo" messages is wrong (as shown in the attached screenshot).
This happens when the subinfo is followed by an undefined preogressBar, so in the parts about:
- loading kernels
- loading data structure
- operator
- fit
- seving results
When the level of verbosity is changed with respect to the default to avoid the display of ProgressBar (i.e.,
mit.set_verbose(2)), the indentation of some "subinfo" messages is wrong (as shown in the attached screenshot).This happens when the subinfo is followed by an undefined preogressBar, so in the parts about: