Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: The first reranked chunk is incorrect when using the Nvidia reranker model #2552

Closed
1 task done
Defozo opened this issue Sep 24, 2024 · 0 comments
Closed
1 task done
Labels
bug Something isn't working

Comments

@Defozo
Copy link
Contributor

Defozo commented Sep 24, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Branch name

v0.11.0

Commit ID

2f33ec7

Other environment information

AWS
r7i.xlarge EC2 Instance
Ubuntu
Docker container

Actual behavior

The re-ranked chunks are incorrect when using the nvidia/rerank-qa-mistral-4b model for reranking. Typically, the second least relevant chunk is mistakenly placed first, while the second chunk (which should be the most relevant) is ranked lower than it should be.

Expected behavior

The chunks should be returned in the same order they are received from the Nvidia API endpoint.

Steps to reproduce

1. Upload some documents, and preprocess them.
2. Enter the API key to RAGflow from https://build.nvidia.com/nvidia/rerank-qa-mistral-4b
3. Run retrieval test.

Additional information

rerank_model.py seems to be working correctly, the problem is most likely in rag/nlp/search.py.

@Defozo Defozo added the bug Something isn't working label Sep 24, 2024
KevinHuSh added a commit that referenced this issue Sep 24, 2024
### What problem does this PR solve?

#2552

### Type of change

- [x] Performance Improvement
Halfknow pushed a commit to Halfknow/ragflow that referenced this issue Nov 11, 2024
### What problem does this PR solve?

infiniflow#2552

### Type of change

- [x] Performance Improvement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants