Skip to content

Simulate Behavior: Current or next timestep ? #706

@nicolas-lair

Description

@nicolas-lair

Environment

  • Grid2op version: 1.11.0
  • System: windows

Bug description

obs.simulate() seems to simulate on current step and not the next one as the documentation suggests here

Thanks for the insight!

How to reproduce

Code snippet

I noticed that on rte_case_14_realistic that does not seem to support simulation further timesteps.

import grid2op
import pandas as pd
from pathlib import Path

env = grid2op.make("rte_case14_realistic")
# Simulate
sim_obs, *_ = env.get_obs().simulate(env.action_space({}))

# Load the forecast from files
load_p_forecasted = pd.read_csv(Path(env.chronics_handler.path) / f"{env.chronics_handler.get_name()}/load_p_forecasted.csv.bz2", sep=";", compression="bz2", dtype="float32")

# We would expect that when looking for the matching row, it would be row 1 that would match sim_obs.load_p but it is row 0 actually
print(np.where((load_p_forecasted == sim_obs.load_p).all(1))[0])

Current output

[0]

Expected output

[1]

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions