-
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
obs.simulate and env.step check cooldown differently #374
Comments
Hello, Indeed that's not a correct behavior. I'll have a look and implement a fix for the new release (hopefully sooner rather than later) Thanks for the issue 😊 |
May I ask which one is the correct behavior by design, |
Cooldowns are carefully checked and tested for the Unless there is an obvious bug in env.step (which can happen of course, this software, like every other is not perfect) it should be used as the reference. So env.step is correct in this case. |
Bug should be fixed, and i clarify the doc for the correct behaviour, see https://grid2op.readthedocs.io/en/latest/rules.html#behaviour and following subsection for more information :-) |
Environment
1.7.2
ubuntu
Bug description
There are two types of cooldown in the game:
time_before_cooldown_sub
andtime_before_cooldown_line
. When cooldown of a sub or a line is 1,obs.simulate
thinks an action on this sub or line is OK, butenv.step
thinks it is illegal.How to reproduce
Current output
Expected output
I expect
obs.simulate
andenv.step
to be consistent on cooldown check of sub or line. For example, following the logic ofobs.simulate
, the output should be:The text was updated successfully, but these errors were encountered: