Supersed issue

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

Supersed issue

Sinisa Matetic
Hi,

does anybody know exactly when the tariff that is superseded should be revoked from the tariff market. There are two possible options:

1) immediately after we send a message to the server with the new tariff (that superseded the old one) we send a revoke message

2) after we receive a message from the server that our new tariff is published with success, we initiate the revoke message with the old tariff specification


I used the first option from above, but encountered every time that all the customers after revoke are transfered to the default broker and not to the superseded tariff.
Reply | Threaded
Open this post in threaded view
|

Re: Supersed issue

grampajohn
Administrator
Sinisa Matetic wrote
does anybody know exactly when the tariff that is superseded should be revoked from the tariff market. There are two possible options:

1) immediately after we send a message to the server with the new tariff (that superseded the old one) we send a revoke message

2) after we receive a message from the server that our new tariff is published with success, we initiate the revoke message with the old tariff specification

I used the first option from above, but encountered every time that all the customers after revoke are transfered to the default broker and not to the superseded tariff.
It should work both ways. Could you please send me the server logs (both trace and state) from a game where this did not work. Probably it's best to post them somewhere and let me download them.

Thanks.

John
Reply | Threaded
Open this post in threaded view
|

Re: Supersed issue

Sinisa Matetic
This post was updated on .
Hi,

the logs can be acquired here:

https://www.dropbox.com/s/6kdt835gb5njy42/server-logs.rar

superseds occured in timeslots 400 and 430.



One example is here from timeslot 400:
number of subscriptions for 300000006 is 27

819904:org.powertac.common.Rate::300001333::-rr::300001331::-1::-1::-1::-1::0.0::false::-0.03::-0.1845::3::-0.12::0.0
819904:org.powertac.common.TariffSpecification::300001331::-rr::207::CONSUMPTION::50065408::-500.0::0.0::0.0
819904:org.powertac.common.Tariff::300001331::new::300001331
819904:org.powertac.common.TariffTransaction::22189::new::207::400::PUBLISH::300001331::null::0::0.0::-3032.5732810101044
819904:org.powertac.common.msg.TariffStatus::22190::new::207::300001331::300001331::success
819904:org.powertac.common.msg.TariffRevoke::300001335::-rr::207::300000006
819905:org.powertac.common.msg.TariffStatus::22191::new::207::300000006::300001335::success

Where the tariff 300001331 is published in order to supersed the 300000006.
After that in timeslot 401:
number of subscriptions fo 300000006 is 0, and for 300001331 is also 0.



The more obvious example is in the timeslot 430 where we lose arroung 9000 customers in one timeslot (after the tariff that they have been subscribed to was revoked). Moreover, the price in the superseded (new tariff) was lower than in the revoked one - so there is no possible explanation why, all the customers are transffered to the default broker...


BR,

Sinisa
Reply | Threaded
Open this post in threaded view
|

Re: Supersed issue

grampajohn
Administrator
In reply to this post by Sinisa Matetic
Sinisa and all -

This is now issue #687 - I modified the sample broker and was able to reproduce it. I hope to have a fix quickly, but probably not tonight.

Thanks for finding this, Sinisa.

John
Reply | Threaded
Open this post in threaded view
|

Re: Supersede issue

grampajohn
Administrator
In reply to this post by Sinisa Matetic
I'm afraid my memory is failing. The superseding behavior was disabled for a good reason. Before we re-enable it, we have to decide what the correct behavior should be. It appears that superseding can only work if the customer has an opportunity to re-evaluate its subscription options, with little or none of the usual inertia, before the first time it makes use of the superseding tariff. Since this requires a change to all the customer models, we put it off, and I don't see having time to resolve it before the July competition.

If anyone can suggest what the protocol should be for superseding tariffs, please let us know. If it's a complex change, it will be especially welcome if we have a volunteer to do the work.

Thanks.

John