-
Notifications
You must be signed in to change notification settings - Fork 119
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
1. KeyError using state_of storage; 2. cannot sum curtail_actions #340
Comments
Hello Thanks for raising this bugs to our attention. It seems you are totally correct in your understanding and that these are indeed grid2op bugs. I'll fix them ASAP. The fix (for these bugs and possibly following ones) will be used for the Validation and Test phases of the L2RPN 2022 competitions. (I will not release a new grid2op version just yet because of possibly different bugs that people might find in the future) |
In the mean time issue 1You can call
Issue 2You can do (which is a bit more verbose...), but again it's just before the validation and test phase competition start: sum = curtail_actions[0].copy()
sum += curtail_actions[10] # usefull only if you have more "component" of the action (eg set_powerline_status, or change_bus) but not in this case
effective_cutail = curtail_actions[10].curtail >= 0.
sum.curtail = [(gen_id, curtailment) for gen_id, curt in enumerate(curtail_actions[10].curtail) if effective_cutail[gen_id]] |
Just to mention that you can use the "pre release" version of grid2op if you want to with
This should install the first "release candidate" for the 1.7.2 grid2op version, that includes some fix for the bugs you spotted :-) |
Environment
1.7.1
0.7.0
Ubuntu 18.04.4 LTS
Bug description
Two issues:
How to reproduce
Issue 1
Issue 2
This happens because Grid2Op BaseAction Line 1262 implements = instead of +=
Now I'd expect the addition of two curtail actions on different generators to affect both generators. If this rule (curtail_action1 + curtail_action2 -> curtail_action2) is intended, it should be reflected in the documentation (or did I miss it?).
The text was updated successfully, but these errors were encountered: