enforcing good practices for data splitting
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.3k
- Forks
- 4.4k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 4
Description
I was hoping that maybe the examples should contain an explicit split of the data at least into train/valid/test in order to enforce good practices overall and not mislead by accident any new comers. I'm referring to this conversation for more details and discussions.
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
Start by reviewing the repository's examples and the linked PyTorch forum discussion about common data-splitting patterns. Done should mean the relevant examples explicitly separate data into train, validation, and test sets without misleading newcomers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100