Change the output interface of evaluate #8003
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
TomeHirata
commented
Mar 24, 2025
39 tasks
chenmoneygithub
approved these changes
Mar 25, 2025
| if isinstance(other, (float, int)): | ||
| return self.__float__() == other | ||
| elif isinstance(other, Prediction): | ||
| return self.__float__() == float(other) |
There was a problem hiding this comment.
nit: shall we do float(self) == float(other) for consistency?
There was a problem hiding this comment.
I guess this should be consistent with how __ge__ or __le__ are implemented?
TomeHirata
force-pushed
the
feat/evaluate-response
branch
from
7aeb618 to
ed8fd13
Compare
chenmoneygithub
approved these changes
Mar 27, 2025
TomeHirata
force-pushed
the
feat/evaluate-response
branch
from
2f7a26e to
ce1ea2d
Compare
22 tasks
|
please merge the PR to be able to get the individual example level evaluation score. This will be useful for mlflow tracing. |
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.
In this PR, we change the output interface of
Evaluate.__call__.Instead of returning either score, (score, outputs), (score, scores, outputs) based on arguments, it will always return dspy.Prediction containing the following fields:
Since this is a breaking change, this should be released in the next minor release rather than a patch release.