You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this leads to errors and unstable behavior, because 'peak_heat_day' scenario includes a start_time and this start_time is not zero. So the request above (create a 'peak_heat_day' scenario with a start_time of 0) is inconsistent, however BoptestGymEnv doesn't raise any exception immediately, instead what happens is:
the start time in dockerized BOPTEST simulator is set to 1382400, as specified in peak_heat_day scenario
the start time variable in BOPTEST gym is set to 0 as specified in the constructor
this conflict leads to hard to catch bugs down the line
The text was updated successfully, but these errors were encountered:
If, when I initialize
BoptestGymEnv
, I select a scenario like this:this leads to errors and unstable behavior, because 'peak_heat_day' scenario includes a
start_time
and thisstart_time
is not zero. So the request above (create a 'peak_heat_day' scenario with a start_time of 0) is inconsistent, howeverBoptestGymEnv
doesn't raise any exception immediately, instead what happens is:1382400
, as specified inpeak_heat_day
scenario0
as specified in the constructorThe text was updated successfully, but these errors were encountered: