Ratio between PerHour Demand and Supply in PowerTAC

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Ratio between PerHour Demand and Supply in PowerTAC

SPOT
This post was updated on .
Hi

I am trying to calculate the supply/demand ratio in PowerTAC simulation. Please correct me if I am wrong anywhere.  

1. If I want to calculate the each timeslot's demand of the customers from a state log file of a simulation, should I just sum all the TariffTransaction.Type.CONSUME objects to compute the demand for the specific timeslot? I get this when I do that...

Demand 57016.637081321314 KWh at TimeSlot 362
Demand 54708.76362154187 KWh at TimeSlot 363
Demand 64058.03684773132 KWh at TimeSlot 364
Demand 85770.03745874426 KWh at TimeSlot 365
Demand 73150.0693467125 KWh at TimeSlot 366
Demand 63747.34359343093 KWh at TimeSlot 367
Demand 71591.25659111344 KWh at TimeSlot 368
Demand 69754.55807242818 KWh at TimeSlot 369
Demand 65369.02767762344 KWh at TimeSlot 370


2. To calculate the energy supply for a specific timeslot, I am summing all the orders mwh submitted by the lmp broker in the wholesale market for that specific timeslot's all hourAhead auctions. Is that right?

For example, I get this when I extract lmp brokers orders for a specific hourAhead auction.  

Hour HourAhead MWh Price
0 0 -97.59408417 32.98735112
0 0 -87.29256899 38.85346068
0 0 -79.42073112 44.78672373
0 0 -29.89266676 67.00775935
0 0 -29.23829907 78.9898623
0 0 -28.29887138 90.79339868
0 0 -27.72889823 102.9556462
0 0 -26.9548213 114.8611954
0 0 -26.2351272 126.874238
0 0 -25.92491272 138.7826018
0 0 -25.03846974 150.8163573
0 0 -24.85638975 162.7342169
0 0 -24.16073561 174.9478835
0 0 -23.96135224 186.94479
0 0 -23.24453103 198.7449936
0 0 -22.92248802 210.8623205
0 0 -22.47066977 222.8802491
0 0 -22.19904742 234.8807385
0 0 -21.84291679 246.9727912
0 0 -21.41739013 258.9619972
0 0 -21.22135149 270.9078222
0 0 -20.9771721 283.0955805
0 0 -20.48138469 294.8171568
0 0 -20.17091192 306.9280555
0 0 -19.95707239 319.053842
0 0 -19.57339567 330.872859

So summing all the 24 hourAhead auctions ask MWh, I can calculate the avg supply on per hour/timeslot.

I tried to calculate per hour supply in this way and I got this for 10 different boots.
Boot   PerHourSupply(MWh)
1   19101.62883323072,
2   18293.125975105755,
3   18331.592021124594,
4   18973.371305311557,
5   18834.452073050285,
6   19505.45457199779,
7   18627.507877193282,
8   18706.227854240216,
9   19448.886783917103,
10   18935.55321496863

It looks like the ratio is more than 300 per boots. Am I doing the calculation right?

Thanks in advance,
Porag
GL
Reply | Threaded
Open this post in threaded view
|

Re: Ratio between PerHour Demand and Supply in PowerTAC

GL
Hi Porag,

I think I might have some help for your 1st question.

Take a look in the trace files, for instance in finals_2017_06_1.tar.gz you will find these kind of lines:

134537 INFO  DistributionUtilityService: Total net consumption for ts 372 = 21369.101230173375.

If you are using linux try this command (wherever your .tar.gz file is located):

tar xzfO finals_2017_06_1.tar.gz log/finals_2017_06_1.trace | grep -i "Total net con" | less

It will show you the total net consumption per time slot.

PS.
I'm not part of the developers so take my word with caution I might be wrong, though I doubled checked and the consumption quantities in the state and trace files added up.

 
Reply | Threaded
Open this post in threaded view
|

Re: Ratio between PerHour Demand and Supply in PowerTAC

SPOT
Thanks GL.

JFYI, I found that wholesale market has two built-in agents called "MISO" and "buyers". These two agents create 10 times higher demand than the actual powertac demand to prevent market cornering. When I analyzed an auction, I found this:

Order : AgentName Timeslot PostedTimeslot [MWh,$]
Order : buyer 360 384 [40.75183597144248;-12.269385859090697]
Order : lmp 360 384 [-357.94239109866453;13.309131598420787]
Order : lmp 360 384 [-158.3786634328152;19.146286367167516]
Order : lmp 360 384 [-120.48590737194655;25.366532695676494]
Order : lmp 360 384 [-101.69405353113147;31.323919816746137]
Order : lmp 360 384 [-89.68220643883397;37.24810513301245]
Order : lmp 360 384 [-81.0312974852743;43.45034551800871]
Order : lmp 360 384 [-30.281625830379063;52.09386515813346]
Order : lmp 360 384 [-29.570702395160083;63.92065110910752]
Order : lmp 360 384 [-28.874714626157;76.17713871579016]
Order : lmp 360 384 [-28.139975794259712;88.16670208588779]
Order : lmp 360 384 [-27.275735383636704;100.38853420349227]
Order : lmp 360 384 [-26.796701638110214;112.16922520881079]
Order : lmp 360 384 [-25.829267462217025;124.48234017981335]
Order : lmp 360 384 [-25.146590169177585;136.35518966535906]
Order : lmp 360 384 [-24.711581157687064;148.18187982759466]
Order : lmp 360 384 [-24.151269846034527;160.1645039836755]
Order : lmp 360 384 [-24.010859452512097;172.35876239579954]
Order : lmp 360 384 [-23.284183920356565;184.39204397015797]
Order : lmp 360 384 [-23.01190003523084;196.36696245558127]
Order : lmp 360 384 [-22.53258563085684;208.50693490940026]
Order : lmp 360 384 [-22.159795920677272;220.4551465396216]
Order : lmp 360 384 [-21.765443444302637;232.41154303715368]
Order : lmp 360 384 [-21.373450502716647;244.5313987045759]
Order : lmp 360 384 [-21.142927572555557;256.2822842753788]
Order : lmp 360 384 [-20.764377177300627;268.29745805576897]
Order : lmp 360 384 [-20.49855112330806;280.50788848003987]
Order : lmp 360 384 [-20.15882314553761;292.71641875247843]
Order : lmp 360 384 [-19.986448855599228;304.7615024540949]
Order : lmp 360 384 [-19.601030239370647;316.4985332957313]
Order : lmp 360 384 [-19.36898870315874;328.6491425324082]
Order : lmp 360 384 [-19.126297682705683;340.6346294298438]
Order : lmp 360 384 [-18.813542253028583;352.74314075883325]
Order : miso 360 384 [673.7453686106045;null]
Order : default broker 360 384 [44.74537366448115;-12.809777402277241]

ClearedTrade : 361 384 [673.7453686106045;37.588703780095365]
Reply | Threaded
Open this post in threaded view
|

Re: Ratio between PerHour Demand and Supply in PowerTAC

grampajohn
Administrator
Porag and all -

I'm not sure what the question is here. The lmp supplier always offers much more energy in the market than any combination of buyers would want to buy. If it did not, the market would occasionally fail to clear. We should never observe the top of its price curve.

The MISO buyer simulates roughly 10 other cities that participate in the wholesale markets, in addition to the city represented by the Power TAC models. Its demand is modeled on the regional demand observed in north-central U.S., and is fairly weather-dependent. It's a region with cold winters and fairly hot summers, and demand is more dependent on temperatures above the comfort zone than on temperatures below the comfort zone. In other words, there's much more electric-powered air conditioning than there is electric heat.

The "buyer" is just there to provide some liquidity. It generates bids based on an exponential distribution - high quantities at very low prices (which hardly ever clear), and low quantities at higher prices. Since the introduction of the MISO buyer, its effect is vanishingly small.

So the ratio of 30 for supply/demand sounds about right. It needs to be over 11 just to cover the average demand from Power TAC plus the MISO buyer. The real question is what is the ratio between supply and the combined peak demand from Power TAC and the MISO buyer. I have not (yet) tried to determine the combined peak over all the games in the finals; that sounds like a useful exercise. Does this make sense?

John