use different embedding model
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.5k
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Were the effects of using different embedding models considered or tested? I'm just curious about it.
Related: https://github.com/lm-sys/RouteLLM/issues/23 https://github.com/lm-sys/RouteLLM/issues/39
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
Begin with this issue and the related issues #23 and #39; no files, tests, or entry points are named. Determine which embedding models should be compared and what evaluation result would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100