[Scenario] photo catalog sorting wizard
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision
Research direction
No files, tests, or entry points are identified in the issue. First define how photo similarity, sharpness, scene size, computer-specific weights, grouping, and output columns should work; done means an agreed implementation scope and validated catalog output.
Written by the indexing model from the issue text.
Description
Purpose: simplify sorting of big photo catalog
Stages:
- Detect similar photos
- Select best photo among similar photos (according to different score and weights per computer)
- compute sharpest quality
- compute largest scene
- any other computer weights
- Select the best photo (if no ambiguity) or a subset of best photos
- Outputs will be a text file with columns:
photo-pathgroup-id(identify the similar photos)score-total(taking in account weight parameters)score-<computer-name>raw result of each computer (allow to avoid computing again if value exists)
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. 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 edeforas/DarkMap
-
Add cloud sourcesOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in edeforas/DarkMap
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day