search

Project-OMOTES / rtc-tools-heat-network

GNU Lesser General Public License v3.0
2 stars 2 forks source link

Minimum operational constraint #126

Open FJanssen-TNO opened 7 months ago

FJanssen-TNO commented 7 months ago

Add option for constraints that ensure a minimal operational percentage for sources at every timestep. So either source in operation above this percentage or is turned off. Example is geothermal with minimal operational percentage of 30%. (Use constraints in esdl to parse this option)

jimrojerTNO commented 7 months ago

we lack an ESDL feature for this.

@edwinmatthijssen & @ewoudwerkman could sources have a minimum power attribute, or something similar to capture a minimum production level?

edwinmatthijssen commented 7 months ago

I think this relates to control strategies and not necessarily constraints. And this might be combined with setting priorities.

jimrojerTNO commented 7 months ago

@edwinmatthijssen I was actually more thinking along the lines of adding an additional attribute for minimum power as it is not so much a strategy but more a physical property of the asset, like maximum power.

edwinmatthijssen commented 7 months ago

If this minimal operating percentage is a physical property then it must be an attribute indeed. This needs more discussion first....

edwinmatthijssen commented 7 months ago

Can you think about what assets require this property? Producers, conversion assets, but does this relate to storage and consumption as well?

jimrojerTNO commented 6 months ago

At least all producers and conversion assets should need this in my opinion. I don't think we can argue for a general minimum power for a consumption or storage asset. An ATES for example has a pump which will have some minimum operating point, but I think these will be specific cases