Skip to content

Fix: Use Prices and Features Correctly in Battery Environment #69

@ADGEfficiency

Description

@ADGEfficiency

Description

Currently, the battery model uses only \ as input. We need to update the implementation to correctly use both prices and features in the environment observation and reward model.

Background

The recent rebuild (see commit 0f7e6b0) moved to Gymnasium and Stable Baselines 3, but we need to extend the model to properly handle both price data and additional features.

Proposed Changes

  • Modify the battery environment to accept both prices and features as input
  • Update observation space to include feature dimensions
  • Ensure rewards calculation properly uses both inputs
  • Update tests to verify feature integration

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions