RMI / RMI/dispatch

`charge_storage` raises `AssertionError`

Open
#157 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
9
Forks
1
Avg merge
9m
Merged PRs (30d)
9

Description

Details to follow...
Problem BAs:

  • Duke
  • CAISO
  • ...

assert state_of_charge <= max_state_of_charge

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the charge_storage entry point and the assertion state_of_charge <= max_state_of_charge. Reproduce the failure for the listed BAs—Duke and CAISO—and identify the expected behavior before determining that the assertion no longer raises unexpectedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.