Add option to pass bounding boxes to process_and_segment_image
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision
Research direction
Start in model.py at process_and_segment_image and inspect the handling referenced around line 45, especially how images larger than 1k are resized. Determine the expected bounding-box coordinate space and make that behavior explicit. Done means the function accepts bounding boxes and handles their relationship to image resizing consistently.
Written by the indexing model from the issue text.
Description
It would be great to have an option to pass in bounding boxes to this function. I believe this can be done by allowing a value other than None here.
I believe there is some resizing(rescaling?) of images that are larger than 1k that goes on under the hood. I think the bounding boxes will need to be similarly scaled and/or the expectations will need to be made explicit in some way.
- Dominant language
- Python
- Stars
- 220
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 vanvalenlab/cellSAM
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vanvalenlab/cellSAM#13 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
vanvalenlab/cellSAM#135 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
vanvalenlab/cellSAM#134 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
vanvalenlab/cellSAM#133 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
vanvalenlab/cellSAM#132 ·
All issues in vanvalenlab/cellSAM
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#414 ·
Maintainers usually reply within 1 day
-
bug v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelscope/evalscope#1836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100