Fabian Fröhlich

> `trace_save_iter` from class `pypesto.HistoryOptions`? (I think this is wrong, but maybe isn't.) That attribute controls how frequently results are stored, but it needs to activated in the first place.

> @FFroehlich okay -> Concerning my related problem, I presume saving a `results.h5` file collecting all already finished optimization runs (Let's say I'm doing 100 total runs and I want...

https://github.com/ICB-DCM/pyPESTO/blob/808fe96e351864bbed4c977012c2305d029058e8/pypesto/optimize/optimizer.py#L87 I propose to add a way to visualize the message field in OptimizerResult. Currently the clustering information is used for coloring, so marker is probably the thing to go...

https://bitbucket.org/DavidPenas/sacess-library/src/master/ looks like good old C to me, not matlab.

Has anybody ever looked at the actual code? I would imagine that just reimplementation of some of the features in python wouldnt be too much hassle might be much easier...

Tensorflow can do that, just needs an interface to the objective.

> Tensorflow can do that, just needs an interface to the objective. Which we will need anyway for pymc4

Shouldn't this be possible by simply providing a custom sampling routine that shrinks boundaries passed in https://github.com/ICB-DCM/pyPESTO/blob/f74b4d0b54b2f159260664284da5e49709a8245a/pypesto/startpoint/util.py#L50?

I was trying to imply that I believe that a good way to do this would be to provide more custom startpoint sampling methods. Should avoid any clashes with full...

Yes.