Feature/manual impact estimations#229
Open
Popidge wants to merge 3 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
ecologits.estimationsecologits.tracers.utils.ImpactsOutputas a documented compatibility class for existing tracer docs and importsDetails
This introduces
estimate_llm_impacts, which lets users estimate LLM request impacts directly from provider/model/request metadata without patching a supported client library.The tracer utility path now delegates to the shared estimation logic while preserving the existing
ImpactsOutputpublic API and documentation target.This is in response to issue #188
AI Assistance transparency - most of this PR is generated through promting GPT-5.5 (medium) via Codex CLI. Validation mentioned below. I appreciate this is my first PR, and given the ai-prompting, it may come under warranted extra scrutiny - I'm happy to take any and all feedback (I'm not a drive-by slop-merchant!) and make changes - I found this project while brainstorming my own eco-aware compute dev tools, and I'm keen to contribute more in future.
Validation
uv run pytestuv run mkdocs build --strictuv run ruff check ecologits/estimations/modeling.py ecologits/tracers/utils.py