Adding codecarbon detect CLI and the ability to report on hardware without running measurements
#1031
+150
−52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… without running measurements. * Add `detect` command to CLI to report system hardware without starting a tracker. * Create `EmissionsTracker.get_detected_hardware()` to return basic hardware information. * Update internal logging to use `get_detected_hardware()`. * Create `examples/print_hardware.py` and unit tests. * Add documentation for the `detect` command in README and usage guide.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
EmissionsTracker.get_detected_hardware()to return basic hardware information.get_detected_hardware().examples/print_hardware.pyand unit tests.detectcommand to CLI to report system hardware without starting a tracker.detectcommand in README and usage guide.Related Issue
Please link to the issue this PR resolves: #1000
Motivation and Context
Feature request to make it easier to get hardware information.
How Has This Been Tested?
New unit test as well as an example script.
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist:
Go over all the following points, and put an
xin all the boxes that apply.