When using GEKKO and APOPT solver with integer=True to estimate time-varying variables, the solution may be unstable and not accurate due to the integer constraint. To solve this issue, follow these steps:
Change the solver to IPOPT or BPOPT. These solvers do not require integer=True and can handle time-varying variables more effectively.
If you must use APOPT solver, try reducing the time horizon and/or increasing the number of time points to improve the accuracy of the solution.
Use a warm start to the optimization, which means using the solution from the previous time point as the initial guess for the next time point. This approach can improve the stability and accuracy of the solution.
Change the objective function to penalize large changes in the time-varying variables across time points. This approach can help to smooth out the solution and improve stability.
Consider using different constraints or objectives that do not require the use of the integer=True option, such as a mixed-integer linear programming (MILP) formulation or a piecewise-continuous optimization. These approaches can be more suitable for time-varying variables.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2021-08-24 11:00:00 +0000
Seen: 10 times
Last updated: Oct 18 '21
The emulator process for the AVD has ended.
How can I resolve the issue of my website displaying a white screen?
What is the issue related to API that involves request with insufficient scope permissions?
When I run expo start --dev-client, my application is unable to establish a connection.
What is the issue of truncation that occurs with UIDatePicker in Xamarin.Forms iOS?