yujunjun/haystack
1
0
Fork 0
mirror of https://github.com/deepset-ai/haystack.git synced 2026-01-06 12:07:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

ipynb: inserted links to graph images (#2309)

Browse Source 
* ipynb: inserted links to graph images

* Update Documentation & Code Style

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
mkkuemmel 2022-03-15 11:20:31 +01:00 committed by GitHub
parent 11cf94a965
commit 06497da748
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/_src/tutorials/tutorials/11.md
View File

@ -224,7 +224,7 @@ with the keyword based `ElasticsearchRetriever`.
See our [documentation](https://haystack.deepset.ai/docs/latest/retrievermd) to understand why
we might want to combine a dense and sparse retriever.
![image]()
![image](https://github.com/deepset-ai/haystack/blob/master/docs/_src/img/tutorial11_custompipelines_pipeline_ensemble.png?raw=true)
Here we use a `JoinDocuments` node so that the predictions from each retriever can be merged together.
@ -285,7 +285,7 @@ Decision Nodes help you route your data so that only certain branches of your `P
One popular use case for such query classifiers is routing keyword queries to Elasticsearch and questions to EmbeddingRetriever + Reader.
With this approach you keep optimal speed and simplicity for keywords while going deep with transformers when it's most helpful.
![image]()
![image](https://github.com/deepset-ai/haystack/blob/master/docs/_src/img/tutorial11_decision_nodes_pipeline_classifier.png?raw=true)
Though this looks very similar to the ensembled pipeline shown above,
the key difference is that only one of the retrievers is run for each request.

4
tutorials/Tutorial11_Pipelines.ipynb
View File

@ -438,7 +438,7 @@
"See our [documentation](https://haystack.deepset.ai/docs/latest/retrievermd) to understand why\n",
"we might want to combine a dense and sparse retriever.\n",
"\n",
"![image]()\n",
"![image](https://github.com/deepset-ai/haystack/blob/master/docs/_src/img/tutorial11_custompipelines_pipeline_ensemble.png?raw=true)\n",
"\n",
"Here we use a `JoinDocuments` node so that the predictions from each retriever can be merged together."
]
@ -537,7 +537,7 @@
"One popular use case for such query classifiers is routing keyword queries to Elasticsearch and questions to EmbeddingRetriever + Reader.\n",
"With this approach you keep optimal speed and simplicity for keywords while going deep with transformers when it's most helpful.\n",
"\n",
"![image]()\n",
"![image](https://github.com/deepset-ai/haystack/blob/master/docs/_src/img/tutorial11_decision_nodes_pipeline_classifier.png?raw=true)\n",
"\n",
"Though this looks very similar to the ensembled pipeline shown above,\n",
"the key difference is that only one of the retrievers is run for each request.\n",