Diego Alejandro Tejada Arango
Diego Alejandro Tejada Arango
I realized that you need to add the SpineJuliaRegistry to install version from there, otherwise it fails since SpineOpt and SpineInterface are not in the JuliaRegistry: ```julia using Pkg #...
Changes in the code are available in the following discussion: https://github.com/spine-tools/SpineOpt.jl/discussions/476
Close in favour of implementing the multi-year investment through data; see las comment #476
Changes in the code are available in the following discussion: https://github.com/spine-tools/SpineOpt.jl/discussions/476
Close in favour of implementing the multi-year investment through data; see las comment #476
> Here it would be nice to have a comprehensive list of all the new variables and constraints, and their purpose. For the constraint formulation we could use math assuming...
# Changes for the units ## New variables - units_decommissioned(unit,stochastic_scenario,t) - units_decommissioned_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_demothballed_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_early_decommissioned_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_invested_available_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_invested_state(unit,stochastic_scenario,t) - units_invested_state_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_mothballed_state_vintage(unit,stochastic_scenario,**t_vintage**,t) - units_mothballed_vintage(unit,stochastic_scenario,**t_vintage**,t) ## New constraints ###...
Close in favour of implementing the multi-year investment through data; see las comment #476
@DillonJ I suggest you define a minimum up and down time of 1 unit of time (e.g., 1 hour). German's tight and compact formulation works for this case, and I'm...
**Conclusion of the discussion:** Add a constraint `units_started_up + units_shut_down 1 (i.e., cluster units), we add a warning that simultaneous starts/shutdowns can't be avoided with this constraint. Adding a minimum...