mlco2 / mlco2/codecarbon

Power measurements in emissions.csv

Open
#559 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

  • CodeCarbon version: 2.3.1
  • Python version: 3.9.2
  • Operating System: Debian GNU/Linux 11
Description

I have a question regarding the cpu_power, gpu_power, and ram_power values in the emissions.csv file generated by CodeCarbon. I noticed that these values represent the latest instantaneous power measurements for each component. Is this the normal operating behavior, or is it an error? If not, it would be helpful to clarify this in the documentation, as it can be misleading. Users might mistakenly assume that these values reflect the mean power consumption of each component over the measurement period.

Alternatively, would it be more useful to compute these power values as the mean power? This would involve dividing the energy consumption of each component by the duration of the measurement period. However, I realize that this approach may not be as informative, given that this information is already available in the emissions.csv file.

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 cpu_power, gpu_power, and ram_power are described and generated for emissions.csv. Confirm whether they are instantaneous values or means, then update the relevant documentation so the units and measurement semantics are explicit; the issue is done when users cannot mistake these fields for average power.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.