SpineOpt.jl
SpineOpt.jl copied to clipboard
spine-tools
Add warning in documentation about history flows
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 window, which can be unconstrained which can result in free energy for the model.
In my case with storage investments, the model was using this to fill up an energy store for free.
A work around presently is to use fix_connection_flow to fix the flow to zero for the history timeslices.
Regarding an enduring solution... I can only really think of one option and that is to fix the history flows to zero automatically in pre-processing but I feel this isn't ideal as perhaps it would result in infeasibilities in come cases. Another option may be to warn the user about this potential problem in the documentation.
Yes, I remember this. To me, it always made sense to fix the flows manually in the history. For my hydro use case, this flow was not zero but some other value corresponding to the average water discharge (so it was never an option for me to fix flows to zero when I implemented this).
I think in general, our policy is not to fix stuff automatically in the history? So in this case, a note in the documentation of the parameter could be preferred solution. Should I go for it?
@manuelma on another note, did we ever figure out if it would be possible to add links to the more detailed documentation for entities in toolbox?
Just following up on this: IS this already in the docs? (couldn't find it but maybe I overlooked it)
