Replies: 3 comments 1 reply
-
Hello @tk3016! Can you post the error message? Also, include the version of IDAES you are using. |
Beta Was this translation helpful? Give feedback.
-
@tk3016 As @adowling2 said, we really need to see the error you are encountering to help you fix the issue. The short answer is yes, you can use different solvers. However you should think a bit about which solver you want to use and pick one suited to the class of problem you are solving. E.g. BARON is a mixed-integer solver, and for initialization you generally should not have any integer components active in the system, thus BARON not be the best choice as it is focused on a different class of problems. However, there are some caveats to this. The most notable caveat is that many IDAES models make use of "external functions" to handle some of the more complex non-linear calculations (notably root finding algorithms for cubic and Helmholtz equations of state). Not all solver interfaces support these, so if you are using these in your model then you will need to use a solver that supports these (anything using the ASL interface should work (which notably does not include BARON)). Another caveat is that the current IDAES scaling tools are tailored narrowly to IPOPT, and do not work as expected with some other solvers. If you are using the |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
As far as I understand, the initialization routine uses IPOPT as the default solver when initializing the units. Going through the documentation I figured out that I can use a different solver such as CONOPT or SCIP by using the solver argument. However, I run into an error when I try to use BARON/OCTERACT or even GAMS as the solver (the way it is used in Pyomo).
Is there a possibility to use these solvers for initializing unit models or even simulating or optimizing the flowsheets in IDAES?
Beta Was this translation helpful? Give feedback.
All reactions