Observations

Observations are the information available to a controller at a timestep. They combine calendar and weather inputs, building/asset state, and configured forecasts or service signals. Some come from the dataset; others depend on the actions already applied.

In flat mode, each vector follows env.observation_names. Central-agent mode combines buildings and includes shared observations once. In entity mode, identified tables and edges describe buildings, chargers, EVs and other assets.

observations, info = env.reset(seed=0)
print(env.observation_names)  # Flat-vector names.
# In entity mode, inspect env.entity_specs for IDs, columns, units and edges.

Choose active observations in the schema or constructor. Observation bundles can add forecasts, electrical headroom, service deadlines and action feedback. Robustness events can alter what the controller sees.

See Observations Reference for available signals, Flat and Entity Interfaces for payloads, and Entity v1 Contract for timing and lifecycle semantics.