ShishirPatil/gorilla

De-duplicate APIBench eval data (?)

Open

#87 opened on Aug 7, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (1,397 forks)batch import
good first issuehelp wantedquestion

Repository metrics

Stars
 (12,996 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The evaluation data for APIBench is duplicated between data/apibench/*_eval.json and eval/eval-data/questions/. I think the only difference is formatting. Maybe we should just keep the eval/eval-data/responses and have data/apibench for only data used to train the model.

Initially we made two copies with the following rationale: apibench should have all the data self-contained, which the community is using to train/benchmark their LLMs. eval/ would have the eval data in a format that would be easy to eyeball and understand what is going on.

Maybe this is one of those few cases where it might be ok to have the same data twice in the repository in different formats?

Starting this issue in case anyone has comments on this.

Contributor guide

Research direction
Investigate the differences between the two copies of APIBench evaluation data and decide which format to keep, considering ease of training vs. readability.
Tech stack
python
Domain
data
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70