You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am using Spine to model the GB electricity system for one year on an hourly basis. I am currently facing troubles with long run times so would like to run it on a monthly basis. Is there a way i can ensure that the nodestates of the storage nodes of the previous models be translated to the next runs? The reason is that in some months, there is not enough generation to meet demands, leading to an infeasible model. Is there a way around this problem or should i attempt to minimize the runtime for one year?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I am using Spine to model the GB electricity system for one year on an hourly basis. I am currently facing troubles with long run times so would like to run it on a monthly basis. Is there a way i can ensure that the nodestates of the storage nodes of the previous models be translated to the next runs? The reason is that in some months, there is not enough generation to meet demands, leading to an infeasible model. Is there a way around this problem or should i attempt to minimize the runtime for one year?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions