YoungFaithful / CapacityExpansion.jl

Capacity Expansion Problem Formulation for Julia

Home Page:https://youngfaithful.github.io/CapacityExpansion.jl/stable

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Storage: storage_type + conversion

holgerteichgraeber opened this issue · comments

What is the reason that the conversion parameter is exposed to the user? It seems to me that this is true if we model storage, and false if we don't model storage. In that case, I think it would be beneficial to not expose the parameter to the user, and just have it assigned somewhere under the hood.

Or am I missing some case where we want to actually play with the conversion parameter when running the optimization model?

The thought is that conversion is necessary without storage if one e.g. models AC - you need to convert electricity to cooling demand but there is no need to store. That is why I thought about a separation.

Let's talk about this on the phone next time.

I can see this to be under the hood, but may not be high priority, depending on the amount of work to make it that.

Under the hood for storage, optional for special use cases