-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
If, when I initialize BoptestGymEnv
, I select a scenario like this:
env = BoptestGymEnv(
start_time = 0,
scenario = {'electricity_price': 'dynamic', 'time_period': 'peak_heat_day'})
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 inpeak_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
Metadata
Metadata
Assignees
Labels
No labels