mirror of
https://github.com/hwchase17/langchain.git
synced 2025-05-22 23:47:36 +00:00
f907b62526
# Scores in Vectorestores' Docs Are Explained Following vectorestores can return scores with similar documents by using `similarity_search_with_score`: - chroma - docarray_hnsw - docarray_in_memory - faiss - myscale - qdrant - supabase - vectara - weaviate However, in documents, these scores were either not explained at all or explained in a way that could lead to misunderstandings (e.g., FAISS). For instance in FAISS document: if we consider the score returned by the function as a similarity score, we understand that a document returning a higher score is more similar to the source document. However, since the scores returned by the function are distance scores, we should understand that smaller scores correspond to more similar documents. For the libraries other than Vectara, I wrote the scores they use by investigating from the source libraries. Since I couldn't be certain about the score metric used by Vectara, I didn't make any changes in its documentation. The links mentioned in Vectara's documentation became broken due to updates, so I replaced them with working ones. VectorStores / Retrievers / Memory - @dev2049 my twitter: [berkedilekoglu](https://twitter.com/berkedilekoglu) --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com> |
||
|---|---|---|
| .. | ||
| analyticdb.ipynb | ||
| annoy.ipynb | ||
| atlas.ipynb | ||
| chroma.ipynb | ||
| clickhouse.ipynb | ||
| deeplake.ipynb | ||
| docarray_hnsw.ipynb | ||
| docarray_in_memory.ipynb | ||
| elasticsearch.ipynb | ||
| faiss.ipynb | ||
| lancedb.ipynb | ||
| matchingengine.ipynb | ||
| milvus.ipynb | ||
| mongodb_atlas_vector_search.ipynb | ||
| myscale.ipynb | ||
| opensearch.ipynb | ||
| pgvector.ipynb | ||
| pinecone.ipynb | ||
| qdrant.ipynb | ||
| redis.ipynb | ||
| sklearn.ipynb | ||
| supabase.ipynb | ||
| tair.ipynb | ||
| tigris.ipynb | ||
| typesense.ipynb | ||
| vectara.ipynb | ||
| weaviate.ipynb | ||
| zilliz.ipynb | ||