Skip to content

feat: bundled per-task base configs + EloReport.task - #90

Open
kargibora wants to merge 1 commit into
feat/ja-data-plumbingfrom
feat/ja-base-configs
Open

feat: bundled per-task base configs + EloReport.task#90
kargibora wants to merge 1 commit into
feat/ja-data-plumbingfrom
feat/ja-base-configs

Conversation

@kargibora

Copy link
Copy Markdown
Collaborator

Add some default missing configs. One principle of this PR is when we release container we want people to be just specify the task and their own model easily. On high level, we would want users to not "know" about configs and only use "tasks" we have defined. They can of course write and add their own configs but this customazibility comes second compared to presets.

Also this PR adds the missing .task field to EloReport class.

  • configs/{alpaca-eval,arena-hard-v2.0,mt-bench,elo-lmarena-100k}.yaml: self-documenting base configs, EuroLLM-9B default candidate, gemma-4-31b judge, explicit per-task baselines
  • estimate_elo_ratings.py: EloReport.task field (which ELO task produced the report)
  • configs/alpaca_eval.yaml: fix model/baseline order

- configs/{alpaca-eval,arena-hard-v2.0,mt-bench,elo-lmarena-100k}.yaml:
  self-documenting base configs, EuroLLM-9B default candidate,
  gemma-4-31b judge, explicit per-task baselines
- estimate_elo_ratings.py: EloReport.task field (which ELO task produced the report)
- configs/alpaca_eval.yaml: fix model/baseline order
- tests: EloReport.task coverage
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