Joshua Pulsipher

> This is because a new logger is created for every expression to be evaluated, so no state is kept between invocations (https://github.com/JuliaDocs/IOCapture.jl/blob/d8b27045cec8953e0e5a8d719ca1692b3a6d0d02/src/IOCapture.jl#L91). Thanks for the explanation. > Note though...

This should probably just use `Interpolations.jl`. To avoid adding too many dependencies, it might be better to do this in a separate package.

Pull requests are more than welcome. Please review our docs on contributing to learn more: https://pulsipher.github.io/InfiniteOpt.jl/stable/develop/start_guide/. For the particulars of this addition, I can jot down some FAQs later as...

This should probably correspond to the transcription/transformation interface. However, the problem here is that different solvers use different MOI models, so this may not be very doable, since we use...

With #105, this addition should become obsolete as we fully decouple transformation/solution schemes from `InfiniteModel`s.

Using JuMP's indicator modeling might be sufficient here.

We can leverage DifferentialEquations.jl to tackle this. This should at least be able to handle problems with differential operators that depend on only 1 infinite parameter. We will also need...

DifferentialEquations.jl is able to handle more general models that just dynamic ones, so I think we can readily expand the scope of this contribution. Also, ModelingToolkit.jl might make a convenient...

The stochastic optimal economic control problem I recently setup with @azev77 in https://github.com/pulsipher/InfiniteOpt.jl/issues/131#issuecomment-892964519 (look at the conversation starting from this comment) might be a good fit. Naturally, the difference here...

I am running into the same problem, is there a way to properly use this function such that it works?