Skip to content

feat: PyomoDynamicOptProblem, docs #3676

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

Merged
merged 22 commits into from
Jun 9, 2025
Merged

Conversation

vyudu
Copy link
Member

@vyudu vyudu commented May 29, 2025

@AayushSabharwal @ChrisRackauckas This is mostly the last of it, the refactor, Pyomo, and docs stuff are in here

@vyudu
Copy link
Member Author

vyudu commented Jun 2, 2025

The collocation tests pass on latest but fail on lts - should I try to fix that?

@ChrisRackauckas
Copy link
Member

Does Pyomo.jl fail on LTS? It would be good to keep LTS working when possible.

@ChrisRackauckas
Copy link
Member

I think this is good for now. Looking at all of this, I do wonder if there could be a common problem type that the different solvers build from, but there is some unique codegen for them so it is difficult.

@ChrisRackauckas ChrisRackauckas merged commit 61cd5a7 into SciML:master Jun 9, 2025
30 of 47 checks passed
@vyudu
Copy link
Member Author

vyudu commented Jun 9, 2025

I think we could, would just need to initialize the model and all the constraints at the time solve is called and not when the problem is created.

@vyudu
Copy link
Member Author

vyudu commented Jun 9, 2025

Also down the line, it seems like another class of solvers we could add ones based on the Pontryagin maximum principle, see things like https://link.springer.com/article/10.1007/s10589-011-9454-7

@ChrisRackauckas
Copy link
Member

yes we should, can you open an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants