Jan Kwakkel

Thanks for the suggested fix, I will have to test this once I have a bit more time.

You can add test_simio to this list, even if no test for it yet exist. The bigger question is how we want to approach it. It seems some form of...

Currently, the logging is handled in the call method of AbstractCallback (https://github.com/quaquel/EMAworkbench/blob/2.1-inprogress/ema_workbench/em_framework/callbacks.py). Would it be possible to put the progress bar in this location?

not sure what you mean with the call having to be higher up. I guess you mean because of the `with` statement? This activates a context manager. A context manager...

minor additional point. `__exit__` simply calls `close` so we could call that directly as well. the run stats info is a separate issue. But since the tqdm instance is an...

the progress bar stuff now works. this issue however started with a request for run stats, so do you still want that in addition to the tqdm based progress bar?...

if it is a log message, the sensible thing would be to have it printed by default in which case it can be tied to close method on `ProgressBarMixin` or...

Implementing this is largely straightforward. Basically move most of the current code in `inspect` into some protected function `_inspect`, and then possibly loop over this depending on whether `i` is...

The easiest next step for the visualization would be to modify `scenario_discovery_util.plot_box` to take an optional axes instance as a kwarg (similar to how you can do this in seaborn)....

probably have a dict keyword argument that is passed to seaborn allows users to control this for their case