Skip to content

docs: fix 'accurancy' typo in legacy benchmark comments - #789

Open
Avicennasis wants to merge 1 commit into
OpenHands:mainfrom
TypoScan3000:docs/fix-typos
Open

Avicennasis wants to merge 1 commit into
OpenHands:mainfrom
TypoScan3000:docs/fix-typos

Conversation

@Avicennasis

Copy link
Copy Markdown

Summary

Fix the accurancy → accuracy typo in the copy-pasted comment

# modify_params must be False for evaluation purpose, for reproducibility and accuracy of results

It appears once in each of these 19 files under legacy/, and every file gets the same one-word change:

  • legacy/EDA/run_infer.py
  • legacy/agent_bench/run_infer.py
  • legacy/aider_bench/run_infer.py
  • legacy/biocoder/run_infer.py
  • legacy/bird/run_infer.py
  • legacy/discoverybench/run_infer.py
  • legacy/gorilla/run_infer.py
  • legacy/gpqa/run_infer.py
  • legacy/humanevalfix/run_infer.py
  • legacy/lca_ci_build_repair/run_infer.py
  • legacy/logic_reasoning/run_infer.py
  • legacy/mint/run_infer.py
  • legacy/ml_bench/run_analysis.py
  • legacy/ml_bench/run_infer.py
  • legacy/nocode_bench/run_infer_nc.py
  • legacy/scienceagentbench/run_infer.py
  • legacy/swe_perf/run_infer.py
  • legacy/swefficiency/run_infer.py
  • legacy/toolqa/run_infer.py

No functional changes — comments/documentation only.

Notes

  • One more typo was left alone on purpose: legacy/gorilla/utils.py L24 has Computer Vision Zero-Shor Image Classification inside the APIBench domain list that encode_question() copies from Gorilla's prompt. Changing it would change the evaluation prompt, so I left it for you to decide.
  • Checks: each edited file still parses (ast.parse), and no other accurancy remains in the repo. I did not run uv run pytest or pre-commit for this comment-only change; legacy/ is excluded from linting and type-checking per legacy/README.md.

Signed-off-by: Léon Avic Simmons <Avicennasis@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant