azure-sdk-for-python
azure-sdk-for-python copied to clipboard
[evaluation] Add passing_score param to quality evaluators
Description
All AI quality metrics evaluators will now output a label indicating whether or not the evaluation score is greater than or equal to the passing_score - which is a new kwargs parameter being introduced in this PR. passing_score will be set to 3.0 (float) by default.
List of evaluators updated here:
CoherenceEvaluatorSimilarityEvaluatorRelevanceEvaluatorFluencyEvaluatorRetrievalEvaluatorGroundednessEvaluator
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
- [ ] The pull request does not introduce [breaking changes]
- [x] CHANGELOG is updated for new features, bug fixes or other significant changes.
- [x] I have read the contribution guidelines.
General Guidelines and Best Practices
- [x] Title of the pull request is clear and informative.
- [x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
Testing Guidelines
- [x] Pull request includes test coverage for the included changes.
API change check
APIView has identified API level changes in this PR and created following API reviews.
if they don't already have it, we need to expand the return type hints to include bool. Could you update the docstrings? That's how we're picking up the type hints currently
Hi @diondrapeck. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.
Hi @diondrapeck. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing /reopen if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the no-recent-activity label; otherwise, this is likely to be closed again with the next cleanup pass.