Changing Demand Specific Distribution every Time Period

[Aaron Belman Martínez]

Hello community!

I am interested to know if it is currently possible to change the demand specific distribution parameter every time period. I know that currently we can specify it depending on the season and time of day. But is there a way to add a time period key as well?

I am interested in analyzing a demand commodity whose distribution will change every time period. 

Would be enough to add that time_periods key to the DemandSpecificDistribution table in the SQL file? Or deeper model changes would be necessary to add this functionality?

Kind regards,

Aaron

[Katie Jordan]

Hi Aaron,

Thanks for reaching out. I think there are two ways you could approach this problem. First, and probably simpler, you could specify a unique demand for each time period (i.e., demand_2020, demand_2025, etc), and specify the distribution that way. Alternatively, you’d need to modify the constraint. The constraint can be found in the temoa_rules.py file (around line 429). You can get an idea of how to modify the constraint by looking at other constraints that are indexed by time period. If you do decide to go that route, you will also need to modify the temoa_config.py and temoa_model.py files to reflect your changes. Additionally, you’d then modify the database to add a column for t_periods. 

I hope this is helpful,

Katie

--
You received this message because you are subscribed to the Google Groups "Temoa Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to temoa-projec...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/temoa-project/a250771e-f6c4-4fdb-98c9-2d59803115d7n%40googlegroups.com.

[Cameron Wade]

Hi Aaron,

I've implemented this on a forked repository. You can find the particular commit here.

Let me know if you have any questions.

Best,

Cam

--

You received this message because you are subscribed to the Google Groups "Temoa Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to temoa-projec...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/temoa-project/a250771e-f6c4-4fdb-98c9-2d59803115d7n%40googlegroups.com.

--

Cameron Wade

Principal, Sutubra Research

p: 902-292-4478

[Aaron Belman Martínez]

Thanks a lot for sharing your repository Cameron!

That was exactly what I needed. Just one additional comment, although the changes you presented work well when performing a simulation in perfect foresight, when trying to do it myopically it throws an error. After a little bit of scouting, I tracked the error to:

temoa_model\temoa_myopic.py

In line 58:

tables_group1 = ['CostFixed','CostVariable','Demand','EmissionLimit','MaxActivity','MaxCapacity', \
'MinActivity','MinCapacity','TechInputSplit','TechInputSplitAverage','TechOutputSplit','CapacityCredit','MinGenGroupTarget']

It is necessary to include the Demand Specific Distribution parameter

tables_group1 = ['CostFixed','CostVariable','Demand','DemandSpecificDistribution','EmissionLimit','MaxActivity','MaxCapacity', \
'MinActivity','MinCapacity','TechInputSplit','TechInputSplitAverage','TechOutputSplit','CapacityCredit','MinGenGroupTarget']

Following this methodology, I could work with the Open Energy Outlook database (solving myopically), now with the possibility of changing the DemandSpecificDistribution parameter every time period.

Best,

Aaron

[Cameron Wade]

Great! Happy to hear you've got it working. And thanks for flagging the bug!

Cam

To view this discussion on the web visit https://groups.google.com/d/msgid/temoa-project/6d0e049a-3349-4309-94a4-665f81554596n%40googlegroups.com.