MLMI2-CSSI / MLMI2-CSSI/foundry
handle data loading when no targets are specified
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 88
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
sometimes users want to publish datasets that are only meant to be inputs to models, and don't have any targets.
Currently, users can add datasets where every key is an "input", but f.load_data() still expects targets, which can result in odd behavior when the user unpacks a split, such as:
X,y = res['train']
Add logic to handle f.load_data() appropriately when there are no targets specified
Contributor guide
No contributing guide indexed for this repository
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 tracing f.load_data() and the res['train'] split unpacking path. Check how datasets with only input keys are represented, then define and verify the expected result for a dataset with no targets while preserving existing target-bearing behavior. Done means target-only-free datasets load without requiring targets and their splits can be consumed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100