Eval/bugfix/optional eval inputs #37425
Open
+179
−9
Conversation
This file contains 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
github-actions
bot
added
the
Evaluation
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
singankit
reviewed
Sep 17, 2024
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/evaluate/_evaluate.py
Outdated
Show resolved
Hide resolved
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 the creation of a default column mapping as a guaranteed behavior to the
evaluatefunction, instead of having it be dependent on a target being set. The default mapping directly maps input data and target output names directly to evaluator inputs, with target outputs taking priority over data inputs if they share a name.Also adds 2 tests that check this behavior against a several simple evaluators with differing default-ness on their arguments.