Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Nonlinear] consider passing Nonlinear.Model to solvers #1998

Closed
odow opened this issue Sep 13, 2022 · 1 comment
Closed

[Nonlinear] consider passing Nonlinear.Model to solvers #1998

odow opened this issue Sep 13, 2022 · 1 comment
Labels
Project: next-gen nonlinear support Issues relating to nonlinear support Submodule: Nonlinear About the Nonlinear submodule

Comments

@odow
Copy link
Member

odow commented Sep 13, 2022

@kaarthiksundar and I talked about how it'd be good to pass the MOI.Nonlinear.Model straight to the solver (e.g., Alpine).

We kinda do at the moment, in the NLPBlockData you can access data.evaluator.model, but this might not be the most robust approach. We could add a new AbstractModelAttribute to pass the model directly, and the update JuMP https://github.com/jump-dev/JuMP.jl/blob/6a358d193d5d6e168afdaf104f5a5972add59bae/src/optimizer_interface.jl#L163-L170 to pass the model instead of the evaluator. I'm a bit worried that these are half-baked ideas though. We probably should wait until we understand the NLP expression representation at the JuMP level first.

@odow odow added Project: next-gen nonlinear support Issues relating to nonlinear support Submodule: Nonlinear About the Nonlinear submodule labels Sep 13, 2022
@odow
Copy link
Member Author

odow commented Oct 20, 2022

I think the answer is no. We should do #846 instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Project: next-gen nonlinear support Issues relating to nonlinear support Submodule: Nonlinear About the Nonlinear submodule
Development

No branches or pull requests

1 participant