Add expert mode with custom values - #18
Open
eguegain wants to merge 3 commits into
Open
Conversation
Added a new endpoint for estimating environmental impacts of LLM requests with detailed input parameters.
Added a test for the POST /expert-estimations endpoint to validate the response against expected impacts.
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
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.
Adds a new route for direct model invocation with user defined metrics (rather than fixed provider/model/datacenter metrics)
Bypasses the requirements for a specific provider/model, and thus allows the model to be used for custom deployments or non-supported models.
User must bring their own electricity-mix impacts, data center properties, and model properties.
Implemented as a direct call to compute_llm_impacts, in the same way that ecologits-calculator directly calls compute_llm_impacts in expert mode
Changes:
Add a route for direct model invocation
Add test
Limits:
No support for ValueOrRange as API input
Possible evolution:
add support for the optional model metrics (quantization/batch size/embodied impacts...) but the endpoint will get heavy