Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: expose running evaluators via API to playground #1956

Conversation

aybruhm
Copy link
Member

@aybruhm aybruhm commented Aug 1, 2024

Description

This PR exposes the ability to run evaluators via an API.

Evaluators that have been tested

The following evaluators have been tested by the backend tests (and from the UI):

  • exact match
  • similarity match
  • regex test
  • webhook test
  • AI critique
  • starts with
  • contains
  • contains any
  • contains all
  • contains JSON
  • JSON diff
  • Levenshtein distance
  • RAG faithfulness
  • RAG context relevancy

The following evaluators have only been tested from the UI:

  • field match
  • custom code

What to QA

The QA process should involve running the evaluators mentioned above from the UI.

Related Issue

Closes AGE-491

Copy link

vercel bot commented Aug 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
agenta ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 29, 2024 8:25am
agenta-documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 29, 2024 8:25am

@aybruhm aybruhm changed the base branch from rag to main August 1, 2024 20:40
@aybruhm aybruhm changed the title Feature/age 491 poc 1e expose running evaluators via api to playground [Feature][DRAFT]: expose running evaluators via API to playground Aug 1, 2024
@aybruhm aybruhm changed the base branch from main to rag August 2, 2024 13:50
@aybruhm aybruhm changed the title [Feature][DRAFT]: expose running evaluators via API to playground [Feature]: expose running evaluators via API to playground Aug 2, 2024
aybruhm and others added 5 commits August 22, 2024 01:04
- Removed `requires_llm_api_keys` from evaluators that don't require LLM API keys
- Ensured evaluators requiring LLM keys have `requires_llm_api_keys` set to `True` by default
aybruhm and others added 3 commits August 26, 2024 10:31
…i-to-playground' into feature/age-532-poc-1e-add-llm-api-key-checks-in-llm-based-evaluators
…m-api-key-checks-in-llm-based-evaluators

[Enhancement] Add LLM API key checks to LLM-based evaluators
@bekossy bekossy changed the base branch from main to AGE-587/-implement-evaluation-main-page August 30, 2024 15:39
@bekossy bekossy merged commit f563103 into AGE-587/-implement-evaluation-main-page Aug 30, 2024
6 checks passed
@bekossy bekossy deleted the feature/age-491-poc-1e-expose-running-evaluators-via-api-to-playground branch August 30, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend feature lgtm This PR has been approved by a maintainer size:XXL This PR changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants