Jody Dillon
Jody Dillon
When one uses the `connection_flow_delay` parameter the initial flows on the output side of the relevant connection are related to flows on the input side for timeslices before the model...
Right now, even if many constraints have indices which are a null set, the SpineOpt code to figure that out takes a long time to execute. For example, if a...
During the Mopo meeting this week, I believe we had concensus that we should make backup of a user's SpineOpt DB when carrying out a migration. I think it's ok...
At the moment, specifying a `node_state_min` will force an investment if the storage is an investment candidate. One solution would be to revise the formulation to interpret `node_state_min` as relative...
In https://github.com/spine-tools/SpineOpt.jl/issues/545 @elinaspyrou points out that you can have a time varying value for fix_unit_flow_op because the value needs to be an array. Other than being able to define the...
I have a model with 500 nodes and 700 branches. It's performs pretty well considering but it takes 30 seconds per window at "updating variables". Feels like we should be...
The only thing that will change between Benders iterations are the investment variables... the subproblem solution from the previous benders iteration should at least provide a feasible starting point for...
Sometimes the objective function improvement between successive Benders iterations becomes very small... we could add a convergence criteria where if the relative difference in objective lower bound values between successive...
**Is your feature request related to a problem? Please describe.** Users frequently fall foul of duration parameters - either entering them as symbols (e.g. typing "1D" into the value field)...
If you create an investment storage and specify a non-zero `frac_state_loss` and non-zero initial_node_state it creates an infeasibility when using Benders or may force an investment if using the standard...