clarification required for the validation split
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- jupyter-notebook
- Domain
- documentation
Research direction
Review how the benchmark currently represents each dataset's fields, especially the test_split value, and check the corresponding OpenML information. Document where the validation split is defined and how the train, validation, and test splits can be recreated, then verify the explanation against the dataset records.
Written by the indexing model from the issue text.
Description
it is unfortunately not clear how the validation split is defined for each dataset. As the list of fields only indicate 'test_split'. Are we to find this information on OpenML website? Also, there appears no information on how to recreate the train/val/test splits.
- Dominant language
- Jupyter Notebook
- Stars
- 36
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from automl/LCBench
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
Not Image FoundOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ianktoo/project-monitor#14 ·
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
steerion-labs/bounded-agent-runtime#93 ·
Maintainers usually reply within 1 day
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
:watch: Not Triaged dotnet-csharp/svc fundamentals/subsvc
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
daniel-ospina/tortoise#9038 ·
Maintainers usually reply within 1 day