Closed GNCGenie closed 5 months ago
The replace
doesn't do anything because it acts on the JuMP expressions, not the numeric values.
You need to formulate the problem so that you do not have the undefined values. For example, by adding appropriate bounds and scaling variables appropriately.
As one example, instead of @constraint(model, X[1,:] .>= 6.5e6) # Minimum altitude
do
set_lower_bound.(X[1,:], 6.5e6) # Minimum altitude
This question might be better asked on the forum: https://jump.dev/forum. It is not a bug in Juniper.
I am using Juniper to solve an orbital insertion problem for a LEO satellite. Treating it as a non-linear and non-convex optimisation problem. However introducing the first-order hold dynamics constraints for orbital mechanics leads to the problem giving the following error:
Pasting the code to reproduce the issue below: