Spencer Lyon
Spencer Lyon
oh ok cool, thanks for posting the hack. I can do that for now. Thanks!
ok, thanks for keeping me in the loop. Hopefully we can resolve it!
Getting this also. From what I can see [here](https://github.com/EconForge/NLsolve.jl/blob/master/src/mcp.jl) it appears that with either the smooth or min max reformulation of the problem the objective is evaluated at the proposed...
Hey @tpapp thanks for opening this issue. It sounds like we have similar use cases for this library :) One thing that we (@pkofod and I) have talked about is...
I think this is a good idea. Then it is easy for algorithms to have their own set of algorithm-specific parameters that are easy for users to set.
I think `Newton` and `NewtonTrustRegion` are good suggestions. Also prefixing with the module name is totally reasonable if both are loaded
At some point we talked about having a package that holds all the test cases. An "easy" first step at this would be to consolidate all tests into a single...
I've noticed similar things, but without code representing your objective function (and derivatives if you have them analytically) it will be hard for us to do any debugging. Any chance...
> Is there a way I could decrease the scope of the problem to make it more manageable? @djsegal I'm not sure -- I was going to ask the same...
I wish there was a more satisfactory answer for you, but I think that as long as you've found _something_ that works -- it might be the best you can...