IRE_PRICE on Timeslice level

[Lukas]

Dear all, I would like to set a timeslice-specific price for the import and export of electricity. VEDA/TIMES ignores the IRE_price attribute on the timeslice level. I have tried to use the ACT_COST for the process instead, but it seems that only the last value is read and treated as an ANNUAL price.

Is there a way how to set a timeslice-specific price for the import and export, please?
Thank you, Lukas

[AKanudia]

Information - TIMES and Veda attributes will confirm that IRE_PRICE does support the timeslice index. How did you conclude that it is ignored?

[Lukas]

Information - TIMES and Veda attributes will confirm that IRE_PRICE does support the timeslice index. How did you conclude that it is ignored?

Yeah, that is true. TIMES and Veda attributes confirm that IRE_PRICE does support the timeslice index. Before I noticed that, I had defined IRE_PRICE in the timeslices and it was not taken into account in the model. If I do the same for ACT_COST, based on what I see in Browse, only the last value from the timeslices is read.

Is there a way how to define the cost of import and export on a timeslice level, please? 

[Antti-L]

> Is there a way how to define the cost of import and export on a timeslice level, please?

What do you mean "on a timeslice level" ?
All timeslices are on some timeslice level, and you can use IRE_PRICE, by timeslice.  As you have confirmed knowing now, IRE_PRICE does indeed support the timeslice index.    I have been using it in my models, and it works well. But of course, you could also use FLO_COST, by timeslice.

[Lukas]

> Is there a way how to define the cost of import and export on a timeslice level, please?

What do you mean "on a timeslice level" ?
All timeslices are on some timeslice level, and you can use IRE_PRICE, by timeslice.  As you have confirmed knowing now, IRE_PRICE does indeed support the timeslice index.    I have been using it in my models, and it works well. But of course, you could also use FLO_COST, by timeslice.

Sorry, I have not been clear. I mean day-night level.

[Antti-L]

Whatever values are specified for IRE_PRICE, they are always levelized by TIMES onto the process timeslice level, PRC_TSL.  Consequently, if the PRC_TSL is DAYNITE, IRE_PRICE will be levelized onto the DAYNITE timeslice level (the level of the process flows), and you can thus define any day-night price profiles for imports and exports. However, if PRC_TSL is ANNUAL, the values will be levelized onto the ANNUAL level, thereby effectively losing any day-night price profiles in your data; maybe that is the cause of your problem.

[Lukas Novak]

Whatever values are specified for IRE_PRICE, they are always levelized by TIMES onto the process timeslice level, PRC_TSL.  Consequently, if the PRC_TSL is DAYNITE, IRE_PRICE will be levelized onto the DAYNITE timeslice level (the level of the process flows), and you can thus define any day-night price profiles for imports and exports. However, if PRC_TSL is ANNUAL, the values will be levelized onto the ANNUAL level, thereby effectively losing any day-night price profiles in your data; maybe that is the cause of your problem.

Hello Antti,

thank you for the clarification. Apparently, the problem did not have anything to do with the IRE_PRICE not recognized on DAYNITE level, but the IMP/EXP index missing in the specifications of our processes. The thing was that we were confused by the TIMES and Veda Attributes information where for the IRE_PRICE (and other cost attributes) stands "ANNUAL" as TimeSlice. So we were afraid that it fails when it comes to defining prices on the DAYNITE level. To confirm your words, I managed to check that IRE_PRICE works on the DAYNITE level in results by defining specific scenarios for it. So I believe that this "ANNUAL" statement in the attributes information stands for reporting level.

Have a great weekend!
Lukas Novak

[Antti-L]

Ok, I see.  However, in the VEDA online documentation, the following is mentioned:

----
TIMES Attributes
   ● This is a comprehensive list of all TIMES parameters that can be used in Veda.
   ● For each index, like Timeslice and Currency, it shows the default values that are used for each parameter.
-----
Based on the above, my understanding is that the meaning of the "ANNUAL" in the table is that ANNUAL is the default timeslice used for IRE_PRICE, if no timeslice is specified. But whenever a timeslice is explicitly specified, the default will be overridden by the user-specified timeslice.