Claire Foster

Another thought: the following markdown version would be cute if it worked (but it might also be a bad idea :-) ) ```julia @logprogress 0.1 """# $(i)/100 fooing: at element...

> Another thought: the following markdown version would be cute if it worked (but it might also be a bad idea :-) ) On further consideration I think this would...

> The markdown based approach is neat, but maybe a little too cute. Yes I was worried about that, but I think there's some benefits beyond being cute. Generally I...

> So, I think another possible solution is to put message field in the Progress struct. I was somewhat opposed to it before but now I think it's a good...

> Though to be honest I still feel a bit uncomfortable that there is only a single namespace to put things. Maybe that's good enough and achieves a good balance,...

> I think I half agree. On one hand, obviously it's good to make things composable. But on the other hand I want to make `Progress` and its fields concrete...

> Something like `Convergence`? This sounds good to me. Convergence logging may also be interesting to TensorBoardLogger users and devs who at the moment have their own custom wrapper types...

My thought about `threshold` is that there's a lot of different ways to measure convergence and it would be nice to have a more general wrapper for convergence measures. I...

See also https://github.com/JuliaNLSolvers/Optim.jl/issues/442

> We can have multiple Descent instances with different IDs On the other hand, it's a single computational process with multiple convergence criteria which apply. So I would have thought...