-
Notifications
You must be signed in to change notification settings - Fork 238
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
Update IPOPT version to 3.14 #1248
Comments
My understanding of what needs to happen for this is:
I'm not sure exactly what changes we've made to Ipopt 3.13 and why these changes are necessary, but our Ipopt 3.13 is about 30 commits ahead of coin-or Ipopt 3.13. Also, when I merge stable/3.14 into our stable/idaes-3.13 branch and test the resulting binaries, I don't see the "IDAES header" that we display along with the Ipopt header. I'm not exactly sure where this header comes from. |
The # Set a few basic things
export IPOPT_BRANCH="idaes-3.13"
export IPOPT_REPO="https://github.com/idaes/Ipopt"
export IPOPT_L1_BRANCH="restoration_mod"
export IPOPT_L1_REPO="https://github.com/idaes/Ipopt"
export PYNU_BRANCH="main"
export PYNU_REPO="https://github.com/pyomo/pyomo"
export K_AUG_BRANCH="default"
export K_AUG_REPO="https://github.com/idaes/k_aug"
export CC="gcc"
export CXX="g++" This branch seems not to exist? The branch I see on https://github.com/IDAES/Ipopt is |
This is waiting for IDAES/idaes-ext#262 |
The IDAES-Ipopt copyright header is included in |
Correct. Updating the Ipopt version raises the following questions:
Because these questions make updating the version not completely trivial, we will make the idaes-ext updates in two stages:
|
The Ipopt source actually gets pulled down with |
We should try to update the version of IPOPT we distribute and use as one of the first things after the August release. This will give us three months to work out any kinks that come up during the change over.
The text was updated successfully, but these errors were encountered: