Different inputs for different parts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- data-engineering
Research direction
Start by tracing how processing-step modes read default.input and how individual parts are represented and configured. Define the override behavior for sampled and unsampled parts, then verify that release mode can use the source input for parts that were not sampled.
Written by the indexing model from the issue text.
Description
Right now input source for a processing step (mode) is taken from default.input. It would be valuable to let individual parts override it.
Example: When sampling on propella we only do it on some parts for certain datasets (nemotron-cc-1.0). In the release mode it would be beneficial to say that input for the other parts not sampled are source.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from OpenEuroLLM/training-data-packer
-
Linter shall check annotation data integrityPossibly taken @mikemikimike claimed this 1 day ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
OpenEuroLLM/training-data-packer#132 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenEuroLLM/training-data-packer#94 ·
Maintainers usually reply within 1 day
-
Calculate time and array sizePossibly taken @mrunesson claimed this today. Open
OpenEuroLLM/training-data-packer#140 · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement idea
Difficulty 4/5 3-5 days Newbie friendliness 25/100
OpenEuroLLM/training-data-packer#71 ·
Maintainers usually reply within 1 day
-
idea
Difficulty 4/5 3-5 days Newbie friendliness 48/100
OpenEuroLLM/training-data-packer#61 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in OpenEuroLLM/training-data-packer
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ansys/pyansys-common-mcp#213 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
freedomofpress/dangerzone#1594 ·
Maintainers usually reply within 3 days
-
priority:P1 status:in-review type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
randomparity/kdive#3317 · 1 comment ·
Maintainers usually reply within 1 day
-
area:ci
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mesonbuild/meson#16281 ·
Maintainers usually reply within 1 day