Open nelliputkonen opened 1 year ago
Yes, this would be very nice. We cannot do this nicely before Toolbox adds more support to mapped parameters. At the moment, there is no reasonable way to distinguish whether the price is given for periods or for timesteps. We could do a hack around it.
The workaround at the moment is to use efficiency time series.
There is now an easier workaround. Just use a unit with one output, no inputs, and time-varying other_operational_cost
costs. conversion_method
for the unit needs to be set to none.
Great! This workaround is easy, but for findability should be added to "how to" section as well. Maybe "how to set a electricity import/export connection" would work?
We're also very interested in this feature! We'll try this workaround for now!
Just reminding about solving this issue. I would estimate that using electricity trade commodity time series is among the 10 first typical things a new user wants to do with FlexTool. That's why it's very peculiar for the user that this basic feature is not included while so many advanced features are.
In my opinion the easiest way to do this would be to just have two separate parameters (price/price_constant and price_time). If used at the same time, the time series would just override (or give an error). It is not a "nice way" to do this, but it shouldn't be too confusing to the user as there are now just two parameters for commodities: price and C02_content. (and quite easy to implement)
Commodity would need to allow price as time series. Currently only constant/period, but would be very useful e.g. in electricity trade