Allow Studies (Suites) to have versions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
I would like Suites to have versions, so they can change over time while having one consistent link.
For the AutoML Benchmark we want to have a Benchmark Suite on OpenML with challenging AutoML datasets. We don't want a stale benchmark - we want to gradually change the benchmark over time (to avoid overfitting, make sure problems reflect current challenges, ...). There is currently no support for this in OpenML, the best we can do is maintain an external page and create new suites for each deviation and link the latest.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the Suite and version-related implementation and API behavior; done means a Suite can evolve through versions while retaining one consistent link, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100