Make this as usable as clip-retrieval
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
#1 #2 #3 #4 might make this as usable as clip-retrieval inference
I'd advise to implement it by following the same structure as clip retrieval inference
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 reading issues #1–#4 and the existing clip-retrieval inference implementation, since the issue names no files or tests. Map the current inference structure against clip-retrieval and clarify which usability gaps are in scope. Done should mean the framework is comparably usable for inference, but the issue does not define specific acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100