Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: a problem about the 'PointBid' #206

Open
sjtu-jason opened this issue Apr 12, 2016 · 2 comments
Open

Question: a problem about the 'PointBid' #206

sjtu-jason opened this issue Apr 12, 2016 · 2 comments

Comments

@sjtu-jason
Copy link

When I using the 'PointBid' class, I met with a problem.

I built a device agent. And I used ‘PointBid’ class to build its bidcurve by adding pricepoints.

If the quantity of pricepoints is small (e.g. 2 or 3..), it is okay. But, if the quantity of pricepoints is large (e.g. 7 or 8..), an error will appear: 'ERROR n.p.c.c.Concentrator$MatcherPart - doBidUpate failed for matcher concentrator'.

Would you please tell me what's wrong?

@wilcowijbrandi
Copy link
Member

For me it is not really clear what your question is. Could you maybe show us some of your code?
Also, the structure of the Bid (or PointBid) is going to change a bit in PowerMatcher 2.1, which we want to release soon. If you like to you can checkout the powermatcher-2.1RC branch, maybe it helps.

@sjtu-jason
Copy link
Author

If I use the below code, it is okay.
publishBid(new PointBid.Builder(mb).add(mb.getMinimumPrice(), 0.0) .add((price1 - 1e-5), 0.0) .add(price1, d1) .add(mb.getMaximumPrice(), d1) .build());

But if I increase the quantity of pricepoints, an error will appear. For example:
publishBid(new PointBid.Builder(mb).add(mb.getMinimumPrice(), 0.0) .add((price1 - 1e-5), 0.0) .add(price1, d1) .add((price2 - 1e-5), d1) .add(price2, d2) .add((price3 - 1e-5), d2) .add(price3, d3) .add(mb.getMaximumPrice(), d3) .build());

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants