A question about COM_FR

[xiao.li8@mcgill.ca]

Hi,


I'm a bit confused about how COM_FR works when comparing two different setups for the timeslice of the demand commodity—annual versus daynite:

1. In other TIMES models, demand commodities are typically set to annual with COM_FR. When I applied this to space heating—assuming demand occurs only in winter and is zero in the other three seasons—I still observed that space heating technologies remained active and produced output during the non-winter seasons.
   


2. However, when I defined the demand commodity as daynite, the space heating technologies only became active in winter, regardless of how the technologies themselves were assigned across timeslices.
   

Best,
Xiao

[Antti-L]

>  In other TIMES models, demand commodities are typically set to annual with COM_FR. When I applied this to space heating—assuming demand occurs only in winter and is zero in the other three seasons—I still observed that space heating technologies remained active and produced output during the non-winter seasons.

I have not seen such happening in "other TIMES models", and neither have I seen it in my models: I can verify that the demand load profiles are being correctly imposed on the demand technologies, just as they should. I therefore suspect it is again an issue only in your model, but if you disagree, could you please point me to an "other model" where you can see such happening, so that I would be able to verify the issue you are seeing (I assume at least some of those other models are publicly accessible models)?

[xiao.li8@mcgill.ca]

>  In other TIMES models, demand commodities are typically set to annual with COM_FR. When I applied this to space heating—assuming demand occurs only in winter and is zero in the other three seasons—I still observed that space heating technologies remained active and produced output during the non-winter seasons.

I have not seen such happening in "other TIMES models", and neither have I seen it in my models: I can verify that the demand load profiles are being correctly imposed on the demand technologies, just as they should. I therefore suspect it is again an issue only in your model, but if you disagree, could you please point me to an "other model" where you can see such happening, so that I would be able to verify the issue you are seeing (I assume at least some of those other models are publicly accessible models)?

Hi,

Thanks for the reply. Maybe I misunderstood the default set in TIMES. As you can see in EU-TIMES [just as an example], you can see there is no DAYNITE or WEEKLY or SEASON noted in TSLVL, so I assume it's annual timeslice by default? [although within COM_FR]. 

Best,
Xiao