Update README.md
Browse files
README.md
CHANGED
|
@@ -79,7 +79,7 @@ SPLADE models are a fine balance between retrieval effectiveness (quality) and r
|
|
| 79 |
4. For Industry setting: Effectiveness on custom domains needs more than just **Trading FLOPS for tiny gains** and The Premise "SPLADE++ are not well suited to mono-cpu retrieval" does not hold.
|
| 80 |
5. Owing to query-time inference latency we still need 2 models one for query & doc, This is a Doc model and Query model will be **released soon.**
|
| 81 |
|
| 82 |
-
<img src="./ID.png" width=
|
| 83 |
|
| 84 |
*Note: The paper refers to the best performing models as SPLADE++, hence for consistency we are reusing the same.*
|
| 85 |
|
|
|
|
| 79 |
4. For Industry setting: Effectiveness on custom domains needs more than just **Trading FLOPS for tiny gains** and The Premise "SPLADE++ are not well suited to mono-cpu retrieval" does not hold.
|
| 80 |
5. Owing to query-time inference latency we still need 2 models one for query & doc, This is a Doc model and Query model will be **released soon.**
|
| 81 |
|
| 82 |
+
<img src="./ID.png" width=750 height=650/>
|
| 83 |
|
| 84 |
*Note: The paper refers to the best performing models as SPLADE++, hence for consistency we are reusing the same.*
|
| 85 |
|