mlco2 / mlco2/codecarbon

[DRAFT] Make clear how the measure was made

Open
#1,280 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
1.9k
Forks
323
Avg merge
1d 12h
Merged PRs (30d)
12

Description

Is your feature request related to a problem? Please describe.
Some users does not look at logs, and we could not blame them for that.

Describe the solution you'd like
We need a solution to make it clear outside logs. For example in the output and in the dashboard.

Describe alternatives you've considered
The info is in the log.

Additional context
TBD

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 reviewing how the measurement is currently recorded in logs and where results appear in the output and dashboard. Define what users need to see outside the logs, then verify that the measurement method is clearly represented in both requested surfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.