Use TRAIN_TILES variable as expected
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- data-engineering, machine-learning
Research direction
Trace the pipeline code that uses TRAIN_TILES, LABEL_RATIO, remove-bad-images, and ZOOM_LEVEL, focusing on how train.txt and samples.txt are generated. Reproduce the filtering scenario, then verify that train.txt contains the requested number of tiles while samples.txt contains every tile at the selected zoom level.
Written by the indexing model from the issue text.
Description
Currently, TRAIN_TILES sets the size of sample.txt. This results in unexpected and undesirable behavior. After running remove-bad-images and setting a LABEL_RATIO greater than zero, many or most images are filtered from some datasets. Thus, even though the user may set TRAIN_TILES to 1000, they can end up with only a hundred images. TRAIN_TILES should set the size of train.txt - samples.txt should be every tile at the user's set ZOOM_LEVEL.
- Dominant language
- JavaScript
- Stars
- 168
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 developmentseed/skynet-data
-
Drop tippecanoe dependencyPossibly taken @drewbo claimed this 3100 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
developmentseed/skynet-data#4 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
developmentseed/skynet-data#2 · 6 comments ·
All issues in developmentseed/skynet-data
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
bug code-annotation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
quarto-dev/quarto-cli#15215 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
521xueweihan/HelloGitHub#4133 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Hugo-SA/receita-random#20 ·
Maintainers usually reply within 1 day