-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
docs(tutorial): polish image2image #3843
Conversation
Did we want to explain the indexer here? Instead we're just directing people to our concept docs
I'd suggest that instead of this, we can just link the first occurrence of Document, Executor and Flow to their respective docs page |
And/or mention that readers should check the basic concepts before they start |
I think we can remove the explanation. They would have gone through the basics before this tutorial |
Codecov Report
@@ Coverage Diff @@
## master #3843 +/- ##
==========================================
- Coverage 86.14% 80.59% -5.56%
==========================================
Files 156 156
Lines 12213 12223 +10
==========================================
- Hits 10521 9851 -670
- Misses 1692 2372 +680
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
We live in hope |
📝 Docs are deployed on https://docs-tutorial-similar-image-polish--jina-docs.netlify.app 🎉 |
1 similar comment
📝 Docs are deployed on https://docs-tutorial-similar-image-polish--jina-docs.netlify.app 🎉 |
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
We will use the **SimpleIndexer** Executor as | ||
our indexer (the one that stores and retrieves data). This Executor also returns the matching `Document` when we make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will use the **SimpleIndexer** Executor as | |
our indexer (the one that stores and retrieves data). This Executor also returns the matching `Document` when we make | |
The **Indexer** executor support vector search along with indexing. For this tutorial we will create our own **Indexer** based on `SimpleIndexer` executor available on Jina Hub. This Executor returns the matching `Document` when we make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Automated message
Capitalization
Please capitalize first letters of the following (when used to reference project or component):
- Flow
- Executor
- Document
- Jina
- Jina Hub
- Python
- Docker
- Kubernetes
Note!
This only applies outside a code or CLI context. If you're describing Python, YAML, any programming language, or command line input/output, please use the capitalization you would use in that context.
Right
from jina.flow import Flow
Wrong
from Jina.Flow import Flow
Made with GitHub saved replies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove "should"
getting the embeddings. Reader can replace this model with any other pre-trained models of their choice. When this | ||
executor is instantiated, the pre-trained weights are downloaded automatically. The `predict` function takes in | ||
the `DocumentArray` and extracts embeddings which is then stored in the `embedding` attribute of the | ||
To build an Encoder Executor we inherit the base `Executor` and use a decorator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To build an Encoder Executor we inherit the base `Executor` and use a decorator | |
To build an `Encoder` Executor we inherit the base `Executor` and use a decorator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to backtick Encoder or Executor here. We're talking about them as concepts, not code
Finally, comes the storage/retrieval step. We do this with the **Indexer** Executor. You can use any of the | ||
available indexers on [Jina Hub](https://hub.jina.ai) or define your own. To create an **Indexer** you need to have two | ||
endpoints: `/index` and `/search`. For this tutorial we will define a `SimpleIndexer` which is [also available on jina | ||
Hub](https://hub.jina.ai/executor/zb38xlt4). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finally, comes the storage/retrieval step. We do this with the **Indexer** Executor. You can use any of the | |
available indexers on [Jina Hub](https://hub.jina.ai) or define your own. To create an **Indexer** you need to have two | |
endpoints: `/index` and `/search`. For this tutorial we will define a `SimpleIndexer` which is [also available on jina | |
Hub](https://hub.jina.ai/executor/zb38xlt4). | |
Finally, comes the storage/retrieval step. You can use any of the | |
available indexers on [Jina Hub](https://hub.jina.ai) or define your own. To create an **Indexer** you need to have two | |
endpoints: `/index` and `/search`. We can create an Executor which supports vector search and indexing as follows: |
Just polishing up the wording a little bit