Save consumption and production data as attributes of assets

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by reading issue #612, which this issue identifies as the prerequisite context. Then trace how assets currently represent consumption and production data. Done means those values are stored as asset attributes in the manner required by #612, but the issue does not specify files, tests, or acceptance criteria.

Written by the indexing model from the issue text.

Description

infrastructure

Needed to tackle #612

Dominant language
Python
Stars
29
Forks
12
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from EnergySystemsModellingLab/MUSE_OS

All issues in EnergySystemsModellingLab/MUSE_OS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.