chunk_id stringlengths 36 36 | source stringclasses 35
values | source_url stringlengths 0 290 | upstream_license stringclasses 1
value | document_id stringlengths 36 36 | chunk_index int64 0 324k | retrieved_at stringclasses 2
values | chunker_version stringclasses 4
values | content_hash stringlengths 15 64 | content stringlengths 50 44.7k | namespace stringclasses 9
values | source_name stringclasses 35
values | raw_text stringlengths 50 44.7k | cleaned_text stringlengths 50 44.7k | tags stringclasses 49
values | collection_name stringclasses 11
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
fa748d9f-040b-42eb-9a84-23dc7f68867f | OPEA Documentation | file://datasets/opea-docs/developer-guides/docbuild.rst | unknown | 79ac608d-35c0-4052-8cd9-8db245f8f0a0 | 7 | opea-semantic-v1 | 5989d426aa61597a | other project repos, for example a link to a document in the GenAIInfra repo from a document in the GenAIExamples repo would look like this:
See [GMC Install](https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector/README.md). | ai_ref_knowledge | OPEA Documentation | other project repos, for example a link to a document in the GenAIInfra repo from a document in the GenAIExamples repo would look like this:
See [GMC Install](https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector/README.md). | other project repos, for example a link to a document in the GenAIInfra repo from a document in the GenAIExamples repo would look like this:
See [GMC Install](https://github.com/opea-project/GenAIInfra/tree/main/microservices-connector/README.md). | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fc0c062d-7b6f-492e-90da-c3ef2c7ab4f4 | OPEA Documentation | file://datasets/opea-docs/developer-guides/docbuild.rst | unknown | 79ac608d-35c0-4052-8cd9-8db245f8f0a0 | 68 | opea-semantic-v1 | 96f7bfef9bca2d8b | the top of the left nav panel. The contents of this version selector are defined in the ``conf.py`` sphinx configuration file, specifically something like this:
html_context = {
'current_version': current_version,
'docs_title': docs_title,
'is_release': is_release,
'versions': ( ("latest", "/latest/"),
("1.0", "/1... | ai_ref_knowledge | OPEA Documentation | the top of the left nav panel. The contents of this version selector are defined in the ``conf.py`` sphinx configuration file, specifically something like this:
html_context = {
'current_version': current_version,
'docs_title': docs_title,
'is_release': is_release,
'versions': ( ("latest", "/latest/"),
("1.0", "/1... | the top of the left nav panel. The contents of this version selector are defined in the ``conf.py`` sphinx configuration file, specifically something like this:
html_context = {
'current_version': current_version,
'docs_title': docs_title,
'is_release': is_release,
'versions': ( ("latest", "/latest/"),
("1.0", "/1... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fd34bdfc-d168-4291-ab4a-f2b229e09497 | OPEA Documentation | file://datasets/opea-docs/developer-guides/docbuild.rst | unknown | 79ac608d-35c0-4052-8cd9-8db245f8f0a0 | 24 | opea-semantic-v1 | ae24c90ee27e1f78 | After that, you'll have ``origin`` pointing to your cloned personal ``docs`` repo and ``upstream`` pointing to the project ``docs`` repo.
#. Return to the parent directory with ``cd ..`` | ai_ref_knowledge | OPEA Documentation | After that, you'll have ``origin`` pointing to your cloned personal ``docs`` repo and ``upstream`` pointing to the project ``docs`` repo.
#. Return to the parent directory with ``cd ..`` | After that, you'll have ``origin`` pointing to your cloned personal ``docs`` repo and ``upstream`` pointing to the project ``docs`` repo.
#. Return to the parent directory with ``cd ..`` | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ff98ccee-1a7a-41db-a2ab-32acd673f8c4 | OPEA Documentation | file://datasets/opea-docs/developer-guides/docbuild.rst | unknown | 79ac608d-35c0-4052-8cd9-8db245f8f0a0 | 81 | opea-semantic-v1 | 13fa66643363737a | No new errors/warnings.
The output from the Sphinx build is processed by the Python script
``scripts/filter-known-issues.py`` together with a set of filter
configuration files in the ``.known-issues`` folder. (This
filtering is done as part of the ``Makefile``.) | ai_ref_knowledge | OPEA Documentation | No new errors/warnings.
The output from the Sphinx build is processed by the Python script
``scripts/filter-known-issues.py`` together with a set of filter
configuration files in the ``.known-issues`` folder. (This
filtering is done as part of the ``Makefile``.) | No new errors/warnings.
The output from the Sphinx build is processed by the Python script
``scripts/filter-known-issues.py`` together with a set of filter
configuration files in the ``.known-issues`` folder. (This
filtering is done as part of the ``Makefile``.) | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fffc5f6d-09e7-4a27-b541-f47cce9f4930 | OPEA Documentation | file://datasets/opea-docs/developer-guides/docbuild.rst | unknown | 79ac608d-35c0-4052-8cd9-8db245f8f0a0 | 78 | opea-semantic-v1 | 9661917477f54f72 | /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:5: WARNING: Non-consecutive header level increase; H1 to H4 [myst.header] /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:111: WARNING: Non-consecutive header level increase; H3 to... | ai_ref_knowledge | OPEA Documentation | /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:5: WARNING: Non-consecutive header level increase; H1 to H4 [myst.header] /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:111: WARNING: Non-consecutive header level increase; H3 to... | /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:5: WARNING: Non-consecutive header level increase; H1 to H4 [myst.header] /home/david/opea-project/docs/_build/rst/GenAIInfra/kubernetes-addons/Observability/README.md:111: WARNING: Non-consecutive header level increase; H3 to... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1a8843f5-853a-4bca-b77f-27ac3d3e2aea | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 7 | opea-semantic-v1 | 1e7557ee10dd2a34 | You can change the following attributes:
* Graph layout (from top-to-bottom to left-to-right)
* Node shapes (rectangles, circles, houses, stars, etc.)
* Style (filled, rounded)
* Colors
* Text displayed in the node
* Placement of the resulting image on the page (centered) | ai_ref_knowledge | OPEA Documentation | You can change the following attributes:
* Graph layout (from top-to-bottom to left-to-right)
* Node shapes (rectangles, circles, houses, stars, etc.)
* Style (filled, rounded)
* Colors
* Text displayed in the node
* Placement of the resulting image on the page (centered) | You can change the following attributes:
* Graph layout (from top-to-bottom to left-to-right)
* Node shapes (rectangles, circles, houses, stars, etc.)
* Style (filled, rounded)
* Colors
* Text displayed in the node
* Placement of the resulting image on the page (centered) | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
27d8516b-fae6-423a-b9a3-d6ac05464453 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 10 | opea-semantic-v1 | db0faa1d0d9baead | Adding Edge Labels ******************
Here's an example of a drawing with labels on the edges (arrows) between
nodes. We also show how to change the default attributes for all nodes and
edges within this graph: | ai_ref_knowledge | OPEA Documentation | Adding Edge Labels ******************
Here's an example of a drawing with labels on the edges (arrows) between
nodes. We also show how to change the default attributes for all nodes and
edges within this graph: | Adding Edge Labels ******************
Here's an example of a drawing with labels on the edges (arrows) between
nodes. We also show how to change the default attributes for all nodes and
edges within this graph: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2844e89d-7dde-48d7-af2c-7a1a10249e00 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 3 | opea-semantic-v1 | 78d7da0b5afaca58 | .. graphviz:: images/boot-flow.dot
Let's look at some more examples and then we'll get into more details about
the dot language and drawing options. | ai_ref_knowledge | OPEA Documentation | .. graphviz:: images/boot-flow.dot
Let's look at some more examples and then we'll get into more details about
the dot language and drawing options. | .. graphviz:: images/boot-flow.dot
Let's look at some more examples and then we'll get into more details about
the dot language and drawing options. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
36b14d4c-852b-459c-85a0-9e27e1800cfe | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 12 | opea-semantic-v1 | 4a7aee36462d1354 | Tables ******
For nodes with a ``record`` shape attribute, the text of the label is
presented in a table format: a vertical bar ``|`` starts a new row or
column and curly braces ``{ ... }`` specify a new row (if you're in a
column) or a new column (if you're in a row). For example: | ai_ref_knowledge | OPEA Documentation | Tables ******
For nodes with a ``record`` shape attribute, the text of the label is
presented in a table format: a vertical bar ``|`` starts a new row or
column and curly braces ``{ ... }`` specify a new row (if you're in a
column) or a new column (if you're in a row). For example: | Tables ******
For nodes with a ``record`` shape attribute, the text of the label is
presented in a table format: a vertical bar ``|`` starts a new row or
column and curly braces ``{ ... }`` specify a new row (if you're in a
column) or a new column (if you're in a row). For example: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4f9c4b70-ba08-4008-8a6e-b2d590952acd | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 1 | opea-semantic-v1 | db0cdab53bf3250a | drawings is that the source for a drawing is a text file that can be edited and maintained in the repo along with the documentation.
These source ``.dot`` files are generally kept separate from the document
itself, and included by using a Graphviz directive: | ai_ref_knowledge | OPEA Documentation | drawings is that the source for a drawing is a text file that can be edited and maintained in the repo along with the documentation.
These source ``.dot`` files are generally kept separate from the document
itself, and included by using a Graphviz directive: | drawings is that the source for a drawing is a text file that can be edited and maintained in the repo along with the documentation.
These source ``.dot`` files are generally kept separate from the document
itself, and included by using a Graphviz directive: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
66b77a53-a9eb-444c-b050-9642c6f60e88 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 0 | opea-semantic-v1 | d2e337d0058b2243 | Drawings Using Graphviz #######################
We support using the Sphinx `Graphviz extension`_ for creating simple
graphs and line drawings using the dot language. The advantage of using
Graphviz for drawings is that the source for a drawing is a text file that
can be edited and maintained in the repo along with the... | ai_ref_knowledge | OPEA Documentation | Drawings Using Graphviz #######################
We support using the Sphinx `Graphviz extension`_ for creating simple
graphs and line drawings using the dot language. The advantage of using
Graphviz for drawings is that the source for a drawing is a text file that
can be edited and maintained in the repo along with the... | Drawings Using Graphviz #######################
We support using the Sphinx `Graphviz extension`_ for creating simple
graphs and line drawings using the dot language. The advantage of using
Graphviz for drawings is that the source for a drawing is a text file that
can be edited and maintained in the repo along with the... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6b8da266-a37d-4073-963a-464402017e30 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 4 | opea-semantic-v1 | fabd0987a08206ee | Let's look at some more examples and then we'll get into more details about the dot language and drawing options.
Simple Directed Graph
********************* | ai_ref_knowledge | OPEA Documentation | Let's look at some more examples and then we'll get into more details about the dot language and drawing options.
Simple Directed Graph
********************* | Let's look at some more examples and then we'll get into more details about the dot language and drawing options.
Simple Directed Graph
********************* | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
75b8099e-ee3a-46d9-ad27-5681d47f2743 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 15 | opea-semantic-v1 | f41e6d7762bc2557 | the horizontal alignment of text using escape sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that are centered, left-justified, and right-justified, respectively.
Finite-State Machine
******************** | ai_ref_knowledge | OPEA Documentation | the horizontal alignment of text using escape sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that are centered, left-justified, and right-justified, respectively.
Finite-State Machine
******************** | the horizontal alignment of text using escape sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that are centered, left-justified, and right-justified, respectively.
Finite-State Machine
******************** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
77e3da40-e7c7-436d-ab19-08af012e323d | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 8 | opea-semantic-v1 | f6f23da71b9c6254 | houses, stars, etc.) * Style (filled, rounded) * Colors * Text displayed in the node * Placement of the resulting image on the page (centered)
Example: | ai_ref_knowledge | OPEA Documentation | houses, stars, etc.) * Style (filled, rounded) * Colors * Text displayed in the node * Placement of the resulting image on the page (centered)
Example: | houses, stars, etc.) * Style (filled, rounded) * Colors * Text displayed in the node * Placement of the resulting image on the page (centered)
Example: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7eacfd3d-8a4e-48e6-ba95-db95038436d6 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 6 | opea-semantic-v1 | 565ed1cd1a783d4e | in the content block for the directive. For example, for a simple directed graph (digraph) with two nodes connected by an arrow, you can write:
.. graphviz:: | ai_ref_knowledge | OPEA Documentation | in the content block for the directive. For example, for a simple directed graph (digraph) with two nodes connected by an arrow, you can write:
.. graphviz:: | in the content block for the directive. For example, for a simple directed graph (digraph) with two nodes connected by an arrow, you can write:
.. graphviz:: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
83ee9c9f-18a0-4198-99dd-e7ce88244b2f | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 9 | opea-semantic-v1 | a49a67625d37258a | You can use the `standard HTML color names`_ or use RGB values for colors, as shown.
Adding Edge Labels
****************** | ai_ref_knowledge | OPEA Documentation | You can use the `standard HTML color names`_ or use RGB values for colors, as shown.
Adding Edge Labels
****************** | You can use the `standard HTML color names`_ or use RGB values for colors, as shown.
Adding Edge Labels
****************** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
964db316-ad23-4f50-9dcd-0a35febdbeea | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 5 | opea-semantic-v1 | 09f1633aca2e8a8f | Simple Directed Graph *********************
For simple drawings with shapes and lines, you can put the Graphviz commands
in the content block for the directive. For example, for a simple directed
graph (digraph) with two nodes connected by an arrow, you can write: | ai_ref_knowledge | OPEA Documentation | Simple Directed Graph *********************
For simple drawings with shapes and lines, you can put the Graphviz commands
in the content block for the directive. For example, for a simple directed
graph (digraph) with two nodes connected by an arrow, you can write: | Simple Directed Graph *********************
For simple drawings with shapes and lines, you can put the Graphviz commands
in the content block for the directive. For example, for a simple directed
graph (digraph) with two nodes connected by an arrow, you can write: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a04349be-83f2-4a73-87af-3bb081ccc1ab | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 2 | opea-semantic-v1 | 5c05e4ffd204a8b1 | These source ``.dot`` files are generally kept separate from the document itself, and included by using a Graphviz directive:
.. graphviz:: images/boot-flow.dot | ai_ref_knowledge | OPEA Documentation | These source ``.dot`` files are generally kept separate from the document itself, and included by using a Graphviz directive:
.. graphviz:: images/boot-flow.dot | These source ``.dot`` files are generally kept separate from the document itself, and included by using a Graphviz directive:
.. graphviz:: images/boot-flow.dot | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e25bb61f-a85b-4881-af45-a2fe3145af88 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 14 | opea-semantic-v1 | 396d0e9a285ee3c8 | .. graphviz:: images/record.dot
Note that you can also specify the horizontal alignment of text using escape
sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that
are centered, left-justified, and right-justified, respectively. | ai_ref_knowledge | OPEA Documentation | .. graphviz:: images/record.dot
Note that you can also specify the horizontal alignment of text using escape
sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that
are centered, left-justified, and right-justified, respectively. | .. graphviz:: images/record.dot
Note that you can also specify the horizontal alignment of text using escape
sequences ``\n``, ``\l``, and ``\r``, which divide the label into lines that
are centered, left-justified, and right-justified, respectively. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f5d80d23-5b5c-49ac-a3e5-ce0015bd04ae | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 11 | opea-semantic-v1 | 6bf9fcbd0359cd85 | with labels on the edges (arrows) between nodes. We also show how to change the default attributes for all nodes and edges within this graph:
.. literalinclude:: images/node-shape-edges.dot | ai_ref_knowledge | OPEA Documentation | with labels on the edges (arrows) between nodes. We also show how to change the default attributes for all nodes and edges within this graph:
.. literalinclude:: images/node-shape-edges.dot | with labels on the edges (arrows) between nodes. We also show how to change the default attributes for all nodes and edges within this graph:
.. literalinclude:: images/node-shape-edges.dot | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f68c6326-5817-4638-a349-b75603f0f436 | OPEA Documentation | file://datasets/opea-docs/developer-guides/graphviz.rst | unknown | eee1be01-22fb-47b0-95d8-70fc908bc629 | 13 | opea-semantic-v1 | 91dc485626c56784 | curly braces ``{ ... }`` specify a new row (if you're in a column) or a new column (if you're in a row). For example:
.. literalinclude:: images/record.dot | ai_ref_knowledge | OPEA Documentation | curly braces ``{ ... }`` specify a new row (if you're in a column) or a new column (if you're in a row). For example:
.. literalinclude:: images/record.dot | curly braces ``{ ... }`` specify a new row (if you're in a column) or a new column (if you're in a row). For example:
.. literalinclude:: images/record.dot | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
00fdfe4e-4316-45e1-9b15-986f89f412b2 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 9 | opea-semantic-v1 | a3b65c365c27034c | blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sample on all supported hardware platforms.
For an example, open the [primary README file for the ChatQnA application] (https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/README.md). | ai_ref_knowledge | OPEA Documentation | blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sample on all supported hardware platforms.
For an example, open the [primary README file for the ChatQnA application] (https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/README.md). | blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sample on all supported hardware platforms.
For an example, open the [primary README file for the ChatQnA application] (https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/README.md). | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
099e2228-87e8-4656-8951-493925f3042f | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 7 | opea-semantic-v1 | efe6bcc174f58afc | to decide if a sample in GenAI Examples is immediately relevant to their application, so make sure to clarify the value that your sample delivers.
Structure | ai_ref_knowledge | OPEA Documentation | to decide if a sample in GenAI Examples is immediately relevant to their application, so make sure to clarify the value that your sample delivers.
Structure | to decide if a sample in GenAI Examples is immediately relevant to their application, so make sure to clarify the value that your sample delivers.
Structure | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0a522880-5f05-4e4c-bf11-de76d1460b9e | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 12 | opea-semantic-v1 | ef5a03e8f4d1e5ed | Prepare the Secondary README File #################################
The secondary README file explains how you deploy a sample or target it for specific hardware. For deployment, make sure to specify any artifacts that may be necessary. These artifacts can include:
* Compose files or setup scripts to run with Docker Co... | ai_ref_knowledge | OPEA Documentation | Prepare the Secondary README File #################################
The secondary README file explains how you deploy a sample or target it for specific hardware. For deployment, make sure to specify any artifacts that may be necessary. These artifacts can include:
* Compose files or setup scripts to run with Docker Co... | Prepare the Secondary README File #################################
The secondary README file explains how you deploy a sample or target it for specific hardware. For deployment, make sure to specify any artifacts that may be necessary. These artifacts can include:
* Compose files or setup scripts to run with Docker Co... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3ae6a7d4-8d49-4af5-80e7-55031bd5bab9 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 15 | opea-semantic-v1 | b79f817286347801 | *Profiling* - Give information on procedures to set up and monitor profiling dashboards. * *Troubleshooting* - Describe common problems with this deployment and their solutions.
For an example, open the [Docker Compose file for the ChatQnA application](https://opea-project.github.io/latest/GenAIExamples/ChatQnA/docker_... | ai_ref_knowledge | OPEA Documentation | *Profiling* - Give information on procedures to set up and monitor profiling dashboards. * *Troubleshooting* - Describe common problems with this deployment and their solutions.
For an example, open the [Docker Compose file for the ChatQnA application](https://opea-project.github.io/latest/GenAIExamples/ChatQnA/docker_... | *Profiling* - Give information on procedures to set up and monitor profiling dashboards. * *Troubleshooting* - Describe common problems with this deployment and their solutions.
For an example, open the [Docker Compose file for the ChatQnA application](https://opea-project.github.io/latest/GenAIExamples/ChatQnA/docker_... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3b1b8523-a08c-4a91-92ad-9bb690b2d18b | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 0 | opea-semantic-v1 | 9c216c8e45e5d451 | README Guidelines for GenAIExamples
When you contribute a new sample to GenAI Examples, make sure to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application. | ai_ref_knowledge | OPEA Documentation | README Guidelines for GenAIExamples
When you contribute a new sample to GenAI Examples, make sure to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application. | README Guidelines for GenAIExamples
When you contribute a new sample to GenAI Examples, make sure to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
44f20c5a-5707-4fc1-a791-7dcc8ee0509f | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 18 | opea-semantic-v1 | 8ac7fe0c3bc5cee6 | Validate a Secondary README File
When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality. | ai_ref_knowledge | OPEA Documentation | Validate a Secondary README File
When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality. | Validate a Secondary README File
When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
523d5200-7f2e-4eca-bdef-71b1a92d4cef | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 17 | opea-semantic-v1 | 2604a55e7d39a163 | Include general troubleshooting information in the primary README file. * Always validate the contents of a secondary README file when you create or update it.
Template | ai_ref_knowledge | OPEA Documentation | Include general troubleshooting information in the primary README file. * Always validate the contents of a secondary README file when you create or update it.
Template | Include general troubleshooting information in the primary README file. * Always validate the contents of a secondary README file when you create or update it.
Template | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6dbf43b7-6621-4d5b-bf61-fd16a670bedf | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 13 | opea-semantic-v1 | b1ab90f155011563 | necessary. These artifacts can include: * Compose files or setup scripts to run with Docker Compose * YAML or HELM charts to deploy with Kubernetes
Structure | ai_ref_knowledge | OPEA Documentation | necessary. These artifacts can include: * Compose files or setup scripts to run with Docker Compose * YAML or HELM charts to deploy with Kubernetes
Structure | necessary. These artifacts can include: * Compose files or setup scripts to run with Docker Compose * YAML or HELM charts to deploy with Kubernetes
Structure | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8397017a-4f70-4c03-bf6f-98381d06ecdc | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 14 | opea-semantic-v1 | a59f6517c00b28be | Your secondary README file should contain these sections:
* *Overview* – Describe the contents of the README file. Avoid repeating information that is available in the primary README. * *Deployment* – Explain how you deploy this sample on a specific hardware platform. Mention prerequisites as well as any optional metho... | ai_ref_knowledge | OPEA Documentation | Your secondary README file should contain these sections:
* *Overview* – Describe the contents of the README file. Avoid repeating information that is available in the primary README. * *Deployment* – Explain how you deploy this sample on a specific hardware platform. Mention prerequisites as well as any optional metho... | Your secondary README file should contain these sections:
* *Overview* – Describe the contents of the README file. Avoid repeating information that is available in the primary README. * *Deployment* – Explain how you deploy this sample on a specific hardware platform. Mention prerequisites as well as any optional metho... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
89ae5489-707d-4b68-834e-9740f776775c | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 6 | opea-semantic-v1 | e00b99695276bc07 | Prepare the Primary README File ###############################
The primary README file for a sample describes an overview of the sample and clarifies its usefulness in solving a practical task. Application developers use this information to decide if a sample in GenAI Examples is immediately relevant to their applicat... | ai_ref_knowledge | OPEA Documentation | Prepare the Primary README File ###############################
The primary README file for a sample describes an overview of the sample and clarifies its usefulness in solving a practical task. Application developers use this information to decide if a sample in GenAI Examples is immediately relevant to their applicat... | Prepare the Primary README File ###############################
The primary README file for a sample describes an overview of the sample and clarifies its usefulness in solving a practical task. Application developers use this information to decide if a sample in GenAI Examples is immediately relevant to their applicat... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8d650439-1711-41ce-8046-a0071e2b8ed1 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 2 | opea-semantic-v1 | 625ae1a30359ea4a | sample also supports other deployment options such as Kubernetes, or can target multiple hardware platforms, you must prepare additional (secondary) README files for those purposes.
Use these guidelines and templates to create primary and secondary README files for your sample. | ai_ref_knowledge | OPEA Documentation | sample also supports other deployment options such as Kubernetes, or can target multiple hardware platforms, you must prepare additional (secondary) README files for those purposes.
Use these guidelines and templates to create primary and secondary README files for your sample. | sample also supports other deployment options such as Kubernetes, or can target multiple hardware platforms, you must prepare additional (secondary) README files for those purposes.
Use these guidelines and templates to create primary and secondary README files for your sample. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
95fa9911-bad0-4a71-9b4c-80dfc4a7e2da | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 3 | opea-semantic-v1 | c2ba0d9a4eda23c8 | Use these guidelines and templates to create primary and secondary README files for your sample.
*Primary README File For a Sample:*
* Structure
* Guidelines
* Template | ai_ref_knowledge | OPEA Documentation | Use these guidelines and templates to create primary and secondary README files for your sample.
*Primary README File For a Sample:*
* Structure
* Guidelines
* Template | Use these guidelines and templates to create primary and secondary README files for your sample.
*Primary README File For a Sample:*
* Structure
* Guidelines
* Template | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a293b7ab-c5f5-484b-aec7-51d8ec691cd1 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 20 | opea-semantic-v1 | f816cc2015f30933 | create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation.
All tests are available in the tests folder. | ai_ref_knowledge | OPEA Documentation | create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation.
All tests are available in the tests folder. | create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation.
All tests are available in the tests folder. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b641b600-e4f6-4652-8879-a48d746b95b1 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 1 | opea-semantic-v1 | c4f913ceae4e0134 | to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application.
You should be able to deploy your sample through Docker Compose. If your sample also supports other deployment options such as Kubernetes, or can target multiple... | ai_ref_knowledge | OPEA Documentation | to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application.
You should be able to deploy your sample through Docker Compose. If your sample also supports other deployment options such as Kubernetes, or can target multiple... | to prepare a README file for the contribution. The README file explains the sample and describes how other developers can integrate it into their application.
You should be able to deploy your sample through Docker Compose. If your sample also supports other deployment options such as Kubernetes, or can target multiple... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c4393d4d-3d2c-49b9-853f-f900d6d7d9a2 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 5 | opea-semantic-v1 | 0048de039eeb419e | *Secondary README File(s) For Deployment Options/Target Hardware:* | * Structure * Guidelines * Template
Prepare the Primary README File
############################### | ai_ref_knowledge | OPEA Documentation | *Secondary README File(s) For Deployment Options/Target Hardware:* | * Structure * Guidelines * Template
Prepare the Primary README File
############################### | *Secondary README File(s) For Deployment Options/Target Hardware:* | * Structure * Guidelines * Template
Prepare the Primary README File
############################### | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ca03f218-beeb-4924-b561-ce6a24bd2418 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 11 | opea-semantic-v1 | cecc719b240d09db | insert code blocks for deployment options or targeting specific hardware. Create secondary README files for those purposes and link to them from the primary file.
Template | ai_ref_knowledge | OPEA Documentation | insert code blocks for deployment options or targeting specific hardware. Create secondary README files for those purposes and link to them from the primary file.
Template | insert code blocks for deployment options or targeting specific hardware. Create secondary README files for those purposes and link to them from the primary file.
Template | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e006f69c-102b-4b69-ad1b-9ecebbf72fcd | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 4 | opea-semantic-v1 | 640e472d40b183ca | *Primary README File For a Sample:* * Structure * Guidelines * Template
*Secondary README File(s) For Deployment Options/Target Hardware:* |
* Structure
* Guidelines
* Template | ai_ref_knowledge | OPEA Documentation | *Primary README File For a Sample:* * Structure * Guidelines * Template
*Secondary README File(s) For Deployment Options/Target Hardware:* |
* Structure
* Guidelines
* Template | *Primary README File For a Sample:* * Structure * Guidelines * Template
*Secondary README File(s) For Deployment Options/Target Hardware:* |
* Structure
* Guidelines
* Template | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e2a70064-cd05-4ca1-a9d3-2a3d0484211d | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 19 | opea-semantic-v1 | b1c03d279602c742 | When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality.
When you create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation. | ai_ref_knowledge | OPEA Documentation | When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality.
When you create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation. | When you create or update the information in a secondary README file, you must complete a validation process to ensure its quality.
When you create a new README file, create a new test for validation. When you update a README file, update the corresponding or related test(s) for validation. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e3e6026d-f402-422f-a33a-022935a60a6f | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 10 | opea-semantic-v1 | c32cf5c250f1b9c0 | Guidelines
* The primary README file is the first README file in the sample that application developers use. Keep its content clear and concise so that developers understand the purpose of the sample and know how to learn more about it. * Do not describe detailed steps in the primary README or insert code blocks for de... | ai_ref_knowledge | OPEA Documentation | Guidelines
* The primary README file is the first README file in the sample that application developers use. Keep its content clear and concise so that developers understand the purpose of the sample and know how to learn more about it. * Do not describe detailed steps in the primary README or insert code blocks for de... | Guidelines
* The primary README file is the first README file in the sample that application developers use. Keep its content clear and concise so that developers understand the purpose of the sample and know how to learn more about it. * Do not describe detailed steps in the primary README or insert code blocks for de... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e6447504-4c7c-48fb-8461-cc3443448e0a | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 16 | opea-semantic-v1 | ae62da16012f0f15 | Guidelines
* Create the secondary README file to help developers set up and run a use case in the fewest steps possible. * Each target hardware must have only one secondary README file for a specific deployment method. * To customize a microservice, use the approproate guide available in the GenAI Components folder. * ... | ai_ref_knowledge | OPEA Documentation | Guidelines
* Create the secondary README file to help developers set up and run a use case in the fewest steps possible. * Each target hardware must have only one secondary README file for a specific deployment method. * To customize a microservice, use the approproate guide available in the GenAI Components folder. * ... | Guidelines
* Create the secondary README file to help developers set up and run a use case in the fewest steps possible. * Each target hardware must have only one secondary README file for a specific deployment method. * To customize a microservice, use the approproate guide available in the GenAI Components folder. * ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fcf253c4-79a2-4f44-adfc-18d8f3c46710 | OPEA Documentation | file://datasets/opea-docs/developer-guides/readme_guidelines_genai_examples.rst | unknown | 5406787a-e51d-48b5-b60b-4e49ed73b80b | 8 | opea-semantic-v1 | 0920cc07ffe98be6 | Your primary README file should contain these sections:
* *Overview* – Describe the purpose of the sample and the task(s) it can solve. * *Architecture* – Explain how the sample works. List the building blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sa... | ai_ref_knowledge | OPEA Documentation | Your primary README file should contain these sections:
* *Overview* – Describe the purpose of the sample and the task(s) it can solve. * *Architecture* – Explain how the sample works. List the building blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sa... | Your primary README file should contain these sections:
* *Overview* – Describe the purpose of the sample and the task(s) it can solve. * *Architecture* – Explain how the sample works. List the building blocks you use from the Generative AI Components (GenAI Comps) folder. * *Deployment* – Inform how you deploy this sa... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5942f3c5-2aa9-44ff-86a4-09011c2d8fb2 | OPEA Documentation | file://datasets/opea-docs/eval/index.rst | unknown | 347a4d3f-f75b-41be-b460-e08591b09769 | 0 | opea-semantic-v1 | c0bca3ad86faf7f4 | Evaluating GenAI ################
GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination. | ai_ref_knowledge | OPEA Documentation | Evaluating GenAI ################
GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination. | Evaluating GenAI ################
GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9fd5480d-bfa0-4ed0-8136-76ac1bebe0f3 | OPEA Documentation | file://datasets/opea-docs/eval/index.rst | unknown | 347a4d3f-f75b-41be-b460-e08591b09769 | 1 | opea-semantic-v1 | 2a0effd131835519 | GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination.
We're building this documentation from content in the | ai_ref_knowledge | OPEA Documentation | GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination.
We're building this documentation from content in the | GenAIEval provides evaluation, benchmark, scorecard, and targeting for performance on throughpuut and latency, accuracy on popular evaluation harnesses, safety, and hallucination.
We're building this documentation from content in the | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b7395716-7524-497c-b980-6ac339d6e6bd | OPEA Documentation | file://datasets/opea-docs/examples/examples.rst | unknown | 495944f6-57e0-4169-91b0-b0a426c0e758 | 1 | opea-semantic-v1 | c26cce88e093497d | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIExamples top level directory
.. include:: examples.txt | ai_ref_knowledge | OPEA Documentation | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIExamples top level directory
.. include:: examples.txt | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIExamples top level directory
.. include:: examples.txt | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d173ead6-ea84-47b7-9457-286deede2fcd | OPEA Documentation | file://datasets/opea-docs/examples/examples.rst | unknown | 495944f6-57e0-4169-91b0-b0a426c0e758 | 0 | opea-semantic-v1 | a00a2aab774d370b | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIExamples top level directory | ai_ref_knowledge | OPEA Documentation | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIExamples top level directory | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIExamples top level directory | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
57e5cf25-b2a8-49a4-904c-0ca560b8edf7 | OPEA Documentation | file://datasets/opea-docs/examples/index.rst | unknown | 38c94428-0af9-4015-a561-588541e63b42 | 0 | opea-semantic-v1 | a8275d4c39c412f6 | GenAI Examples ##############
GenAIExamples are designed to give developers an easy entry into generative AI, featuring microservice-based samples that simplify the processes of deploying, testing, and scaling GenAI applications. All examples are fully compatible with Docker and Kubernetes, supporting a wide range of h... | ai_ref_knowledge | OPEA Documentation | GenAI Examples ##############
GenAIExamples are designed to give developers an easy entry into generative AI, featuring microservice-based samples that simplify the processes of deploying, testing, and scaling GenAI applications. All examples are fully compatible with Docker and Kubernetes, supporting a wide range of h... | GenAI Examples ##############
GenAIExamples are designed to give developers an easy entry into generative AI, featuring microservice-based samples that simplify the processes of deploying, testing, and scaling GenAI applications. All examples are fully compatible with Docker and Kubernetes, supporting a wide range of h... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
db10e58a-5bb3-4666-b04b-8e500facf17a | OPEA Documentation | file://datasets/opea-docs/examples/index.rst | unknown | 38c94428-0af9-4015-a561-588541e63b42 | 1 | opea-semantic-v1 | 7eeb3523b9990c57 | supporting a wide range of hardware platforms such as Gaudi, Xeon, and NVIDIA GPU, and other hardware, ensuring flexibility and efficiency for your GenAI adoption.
We're building this documentation from content in the | ai_ref_knowledge | OPEA Documentation | supporting a wide range of hardware platforms such as Gaudi, Xeon, and NVIDIA GPU, and other hardware, ensuring flexibility and efficiency for your GenAI adoption.
We're building this documentation from content in the | supporting a wide range of hardware platforms such as Gaudi, Xeon, and NVIDIA GPU, and other hardware, ensuring flexibility and efficiency for your GenAI adoption.
We're building this documentation from content in the | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
179363b7-7a6d-4fce-8bc0-cde2d445c2b6 | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 2 | opea-semantic-v1 | 9854d3637c269f7c | Source code for the OPEA Project is maintained in the `OPEA Project GitHub repository`_.
.. comment The links in this grid display can't use :ref: because we're
using raw html. There's a risk of broken links if referenced content is
moved. | ai_ref_knowledge | OPEA Documentation | Source code for the OPEA Project is maintained in the `OPEA Project GitHub repository`_.
.. comment The links in this grid display can't use :ref: because we're
using raw html. There's a risk of broken links if referenced content is
moved. | Source code for the OPEA Project is maintained in the `OPEA Project GitHub repository`_.
.. comment The links in this grid display can't use :ref: because we're
using raw html. There's a risk of broken links if referenced content is
moved. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7eafd719-45a3-4a76-97c5-7e7d1315c453 | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 1 | opea-semantic-v1 | 8ef88fe9ba6b7302 | (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently integrating secure, performant, and cost-effective Generative AI workflows into business processes.
Source code for the OPEA Project is maintained in the
`OPEA Project GitHub repository`_. | ai_ref_knowledge | OPEA Documentation | (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently integrating secure, performant, and cost-effective Generative AI workflows into business processes.
Source code for the OPEA Project is maintained in the
`OPEA Project GitHub repository`_. | (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently integrating secure, performant, and cost-effective Generative AI workflows into business processes.
Source code for the OPEA Project is maintained in the
`OPEA Project GitHub repository`_. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8b92d219-336d-4527-b491-0050a3083677 | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 5 | opea-semantic-v1 | ebbe4a283c67aa99 | needs.</p> </li> <li class="grid-item"> <a href="microservices/index.html"> <span class="grid-icon fa fa-object-group"></span> <h2>Browse GenAI Microservices</h2> </a> <p>Use modular building blocks to build robust GenAI solutions.</p> </li> </ul>
introduction/index
getting-started/README
tutorial/index
examples/ind... | ai_ref_knowledge | OPEA Documentation | needs.</p> </li> <li class="grid-item"> <a href="microservices/index.html"> <span class="grid-icon fa fa-object-group"></span> <h2>Browse GenAI Microservices</h2> </a> <p>Use modular building blocks to build robust GenAI solutions.</p> </li> </ul>
introduction/index
getting-started/README
tutorial/index
examples/ind... | needs.</p> </li> <li class="grid-item"> <a href="microservices/index.html"> <span class="grid-icon fa fa-object-group"></span> <h2>Browse GenAI Microservices</h2> </a> <p>Use modular building blocks to build robust GenAI solutions.</p> </li> </ul>
introduction/index
getting-started/README
tutorial/index
examples/ind... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d09824d8-30ab-44dc-b244-6c11818b89af | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 3 | opea-semantic-v1 | 182642a9c2b973fe | The links in this grid display can't use :ref: because we're using raw html. There's a risk of broken links if referenced content is moved.
.. raw:: html | ai_ref_knowledge | OPEA Documentation | The links in this grid display can't use :ref: because we're using raw html. There's a risk of broken links if referenced content is moved.
.. raw:: html | The links in this grid display can't use :ref: because we're using raw html. There's a risk of broken links if referenced content is moved.
.. raw:: html | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
daecb4ff-37b3-49e0-a566-2ca7e4a697ca | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 0 | opea-semantic-v1 | 5a44f065cb9555a3 | OPEA Project Documentation ##########################
Welcome to the OPEA Project (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently
integrating secure, performant, and cost-effective Generative AI workflows into business processes. | ai_ref_knowledge | OPEA Documentation | OPEA Project Documentation ##########################
Welcome to the OPEA Project (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently
integrating secure, performant, and cost-effective Generative AI workflows into business processes. | OPEA Project Documentation ##########################
Welcome to the OPEA Project (|version|) documentation published |today|. OPEA streamlines the implementation of enterprise-grade Generative AI by efficiently
integrating secure, performant, and cost-effective Generative AI workflows into business processes. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f877f85f-9757-491f-93c0-8adca566ce82 | OPEA Documentation | file://datasets/opea-docs/index.rst | unknown | 3c8b07fb-b8b9-482e-8305-01dc940173d1 | 4 | opea-semantic-v1 | 58a69da03cd94abd | .. raw:: html
<ul class="grid">
<li class="grid-item">
<a href="introduction/index.html">
<img alt="" src="_static/images/opea-icon-white.svg" width="80px"/><br/>
<h2>What is OPEA?</h2>
</a>
<p>Learn about the OPEA architecture, features, and benefits.</p>
</li>
<li class="grid-item">
<a href="getting-started/... | ai_ref_knowledge | OPEA Documentation | .. raw:: html
<ul class="grid">
<li class="grid-item">
<a href="introduction/index.html">
<img alt="" src="_static/images/opea-icon-white.svg" width="80px"/><br/>
<h2>What is OPEA?</h2>
</a>
<p>Learn about the OPEA architecture, features, and benefits.</p>
</li>
<li class="grid-item">
<a href="getting-started/... | .. raw:: html
<ul class="grid">
<li class="grid-item">
<a href="introduction/index.html">
<img alt="" src="_static/images/opea-icon-white.svg" width="80px"/><br/>
<h2>What is OPEA?</h2>
</a>
<p>Learn about the OPEA architecture, features, and benefits.</p>
</li>
<li class="grid-item">
<a href="getting-started/... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
03d43adb-ab04-4fbb-b388-0fd6ba6cda22 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 17 | opea-semantic-v1 | f34354651e4bdbc4 | * Getting Started Guide * Get Involved with the OPEA Open Source Community * Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home
../framework/framework | ai_ref_knowledge | OPEA Documentation | * Getting Started Guide * Get Involved with the OPEA Open Source Community * Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home
../framework/framework | * Getting Started Guide * Get Involved with the OPEA Open Source Community * Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home
../framework/framework | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
153a970a-dbc4-4707-a492-f1f6a938cf04 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 1 | opea-semantic-v1 | f7889516d37347d3 | of open, multi-provider, robust, and composable generative AI (GenAI) solutions. It harnesses the best innovations across the ecosystem while keeping enterprise-level needs front and center.
OPEA simplifies the implementation of enterprise-grade composite GenAI
solutions, starting with a focus on Retrieval Augmented Ge... | ai_ref_knowledge | OPEA Documentation | of open, multi-provider, robust, and composable generative AI (GenAI) solutions. It harnesses the best innovations across the ecosystem while keeping enterprise-level needs front and center.
OPEA simplifies the implementation of enterprise-grade composite GenAI
solutions, starting with a focus on Retrieval Augmented Ge... | of open, multi-provider, robust, and composable generative AI (GenAI) solutions. It harnesses the best innovations across the ecosystem while keeping enterprise-level needs front and center.
OPEA simplifies the implementation of enterprise-grade composite GenAI
solutions, starting with a focus on Retrieval Augmented Ge... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2893f68f-865f-4918-b93f-4fa4f153be6a | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 3 | opea-semantic-v1 | e1ddcfc2678b0664 | The OPEA platform includes:
* Detailed framework of composable microservices building blocks for
state-of-the-art GenAI systems including LLMs, data stores, and prompt engines | ai_ref_knowledge | OPEA Documentation | The OPEA platform includes:
* Detailed framework of composable microservices building blocks for
state-of-the-art GenAI systems including LLMs, data stores, and prompt engines | The OPEA platform includes:
* Detailed framework of composable microservices building blocks for
state-of-the-art GenAI systems including LLMs, data stores, and prompt engines | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
298f7250-fa8b-42c2-bee8-ded49d13ba76 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 13 | opea-semantic-v1 | 24b239a2eb888426 | Gateways: Customized Access to Mega- and Microservices
The Gateway serves as the interface for users to access a megaservice, providing
customized access based on user requirements. It acts as the entry point for
incoming requests, routing them to the appropriate microservices within the
megaservice architecture. | ai_ref_knowledge | OPEA Documentation | Gateways: Customized Access to Mega- and Microservices
The Gateway serves as the interface for users to access a megaservice, providing
customized access based on user requirements. It acts as the entry point for
incoming requests, routing them to the appropriate microservices within the
megaservice architecture. | Gateways: Customized Access to Mega- and Microservices
The Gateway serves as the interface for users to access a megaservice, providing
customized access based on user requirements. It acts as the entry point for
incoming requests, routing them to the appropriate microservices within the
megaservice architecture. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3d94260f-82ae-44c8-9c3d-fc79b067b1cd | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 4 | opea-semantic-v1 | 7c050d84c6a8c074 | * Detailed framework of composable microservices building blocks for state-of-the-art GenAI systems including LLMs, data stores, and prompt engines
* Architectural blueprints of retrieval-augmented GenAI component stack
structure and end-to-end workflows | ai_ref_knowledge | OPEA Documentation | * Detailed framework of composable microservices building blocks for state-of-the-art GenAI systems including LLMs, data stores, and prompt engines
* Architectural blueprints of retrieval-augmented GenAI component stack
structure and end-to-end workflows | * Detailed framework of composable microservices building blocks for state-of-the-art GenAI systems including LLMs, data stores, and prompt engines
* Architectural blueprints of retrieval-augmented GenAI component stack
structure and end-to-end workflows | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
605d60d3-24c0-4997-a653-7a58965f5d5c | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 11 | opea-semantic-v1 | e57a584c5e2f2d57 | Megaservices: A Comprehensive Solution
Megaservices are higher-level architectural constructs composed of one or more
microservices. Unlike individual microservices, which focus on specific tasks or
functions, a megaservice orchestrates multiple microservices to deliver a
comprehensive solution. Megaservices encapsulat... | ai_ref_knowledge | OPEA Documentation | Megaservices: A Comprehensive Solution
Megaservices are higher-level architectural constructs composed of one or more
microservices. Unlike individual microservices, which focus on specific tasks or
functions, a megaservice orchestrates multiple microservices to deliver a
comprehensive solution. Megaservices encapsulat... | Megaservices: A Comprehensive Solution
Megaservices are higher-level architectural constructs composed of one or more
microservices. Unlike individual microservices, which focus on specific tasks or
functions, a megaservice orchestrates multiple microservices to deliver a
comprehensive solution. Megaservices encapsulat... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
60f61966-1660-483b-8454-cee8154646a8 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 6 | opea-semantic-v1 | 495500da0b5048f5 | * Multiple micro- and megaservices to get your GenAI into production and deployed
* A four-step assessment for grading GenAI systems around performance, features,
trustworthiness and enterprise-grade readiness | ai_ref_knowledge | OPEA Documentation | * Multiple micro- and megaservices to get your GenAI into production and deployed
* A four-step assessment for grading GenAI systems around performance, features,
trustworthiness and enterprise-grade readiness | * Multiple micro- and megaservices to get your GenAI into production and deployed
* A four-step assessment for grading GenAI systems around performance, features,
trustworthiness and enterprise-grade readiness | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6e6d1c2f-af16-4579-ad54-39348c3d6b13 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 9 | opea-semantic-v1 | 9cab6d503bdf6071 | Microservices: Flexible and Scalable Architecture
The :ref:`GenAIComps` documentation describes
a suite of microservices. Each microservice is designed to perform a specific
function or task within the application architecture. By breaking down the
system into these smaller, self-contained services, microservices promo... | ai_ref_knowledge | OPEA Documentation | Microservices: Flexible and Scalable Architecture
The :ref:`GenAIComps` documentation describes
a suite of microservices. Each microservice is designed to perform a specific
function or task within the application architecture. By breaking down the
system into these smaller, self-contained services, microservices promo... | Microservices: Flexible and Scalable Architecture
The :ref:`GenAIComps` documentation describes
a suite of microservices. Each microservice is designed to perform a specific
function or task within the application architecture. By breaking down the
system into these smaller, self-contained services, microservices promo... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6f502660-2b30-4f02-a403-7b16f2ae3025 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 10 | opea-semantic-v1 | 4ab4616045d8df5e | scale individual components of the application, making it easier to maintain and evolve over time. All of the microservices are containerized, allowing cloud native deployment.
Megaservices: A Comprehensive Solution | ai_ref_knowledge | OPEA Documentation | scale individual components of the application, making it easier to maintain and evolve over time. All of the microservices are containerized, allowing cloud native deployment.
Megaservices: A Comprehensive Solution | scale individual components of the application, making it easier to maintain and evolve over time. All of the microservices are containerized, allowing cloud native deployment.
Megaservices: A Comprehensive Solution | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
78b7130e-5263-405d-8366-70c7c8cd1727 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 15 | opea-semantic-v1 | ef4572cdf79b3530 | interact with the underlying Microservices. By abstracting the complexity of the underlying infrastructure, Gateways provide a seamless and user-friendly experience for interacting with the Megaservice.
Next Step
********* | ai_ref_knowledge | OPEA Documentation | interact with the underlying Microservices. By abstracting the complexity of the underlying infrastructure, Gateways provide a seamless and user-friendly experience for interacting with the Megaservice.
Next Step
********* | interact with the underlying Microservices. By abstracting the complexity of the underlying infrastructure, Gateways provide a seamless and user-friendly experience for interacting with the Megaservice.
Next Step
********* | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8517be96-bd0e-47f5-9f26-16bd9263becb | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 12 | opea-semantic-v1 | ed4f1cba4d32af9d | application requirements. This approach enables the creation of modular yet integrated applications. You can find a collection of use case-based applications in the :ref:`GenAIExamples` documentation
Gateways: Customized Access to Mega- and Microservices | ai_ref_knowledge | OPEA Documentation | application requirements. This approach enables the creation of modular yet integrated applications. You can find a collection of use case-based applications in the :ref:`GenAIExamples` documentation
Gateways: Customized Access to Mega- and Microservices | application requirements. This approach enables the creation of modular yet integrated applications. You can find a collection of use case-based applications in the :ref:`GenAIExamples` documentation
Gateways: Customized Access to Mega- and Microservices | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8ff1cd52-2bb0-4cda-858f-e69f7e4f62cc | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 14 | opea-semantic-v1 | 7367c24d0ff3a0f7 | customized access based on user requirements. It acts as the entry point for incoming requests, routing them to the appropriate microservices within the megaservice architecture.
Gateways support API definition, API versioning, rate limiting, and request
transformation, allowing for fine-grained control over how users ... | ai_ref_knowledge | OPEA Documentation | customized access based on user requirements. It acts as the entry point for incoming requests, routing them to the appropriate microservices within the megaservice architecture.
Gateways support API definition, API versioning, rate limiting, and request
transformation, allowing for fine-grained control over how users ... | customized access based on user requirements. It acts as the entry point for incoming requests, routing them to the appropriate microservices within the megaservice architecture.
Gateways support API definition, API versioning, rate limiting, and request
transformation, allowing for fine-grained control over how users ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ad13f699-1e05-4a80-81c5-d7d451232b1b | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 2 | opea-semantic-v1 | 82d344792a732f81 | facilitate efficient integration of secure, performant, and cost-effective GenAI workflows into business systems and manage its deployments, leading to quicker GenAI adoption and business value.
The OPEA platform includes: | ai_ref_knowledge | OPEA Documentation | facilitate efficient integration of secure, performant, and cost-effective GenAI workflows into business systems and manage its deployments, leading to quicker GenAI adoption and business value.
The OPEA platform includes: | facilitate efficient integration of secure, performant, and cost-effective GenAI workflows into business systems and manage its deployments, leading to quicker GenAI adoption and business value.
The OPEA platform includes: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c331f267-2548-483c-988b-e6ef7e7c0c72 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 16 | opea-semantic-v1 | bc5f2d34fe97c9cb | Links to:
* Getting Started Guide
* Get Involved with the OPEA Open Source Community
* Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home | ai_ref_knowledge | OPEA Documentation | Links to:
* Getting Started Guide
* Get Involved with the OPEA Open Source Community
* Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home | Links to:
* Getting Started Guide
* Get Involved with the OPEA Open Source Community
* Browse the OPEA wiki, mailing lists, and working groups: https://wiki.lfaidata.foundation/display/DL/OPEA+Home | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d07cfeec-d77f-4d94-b88c-cefd40ed6969 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 8 | opea-semantic-v1 | 4beb1b96af96b125 | the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a megaservice thereby creating real-world Enterprise AI applications.
Microservices: Flexible and Scalable Architecture | ai_ref_knowledge | OPEA Documentation | the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a megaservice thereby creating real-world Enterprise AI applications.
Microservices: Flexible and Scalable Architecture | the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a megaservice thereby creating real-world Enterprise AI applications.
Microservices: Flexible and Scalable Architecture | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d9db91b6-b510-4a34-af45-bb7e5ada1e13 | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 5 | opea-semantic-v1 | 0a3276688a30fd8a | * Architectural blueprints of retrieval-augmented GenAI component stack structure and end-to-end workflows
* Multiple micro- and megaservices to get your GenAI into production and
deployed | ai_ref_knowledge | OPEA Documentation | * Architectural blueprints of retrieval-augmented GenAI component stack structure and end-to-end workflows
* Multiple micro- and megaservices to get your GenAI into production and
deployed | * Architectural blueprints of retrieval-augmented GenAI component stack structure and end-to-end workflows
* Multiple micro- and megaservices to get your GenAI into production and
deployed | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
de493713-f3b3-4473-b8de-1cd98c07593f | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 0 | opea-semantic-v1 | 92c78fd337e32d5b | OPEA Overview #############
OPEA (Open Platform for Enterprise AI) is a framework that enables the creation
and evaluation of open, multi-provider, robust, and composable generative AI
(GenAI) solutions. It harnesses the best innovations across the ecosystem while
keeping enterprise-level needs front and center. | ai_ref_knowledge | OPEA Documentation | OPEA Overview #############
OPEA (Open Platform for Enterprise AI) is a framework that enables the creation
and evaluation of open, multi-provider, robust, and composable generative AI
(GenAI) solutions. It harnesses the best innovations across the ecosystem while
keeping enterprise-level needs front and center. | OPEA Overview #############
OPEA (Open Platform for Enterprise AI) is a framework that enables the creation
and evaluation of open, multi-provider, robust, and composable generative AI
(GenAI) solutions. It harnesses the best innovations across the ecosystem while
keeping enterprise-level needs front and center. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f59bcef4-3727-48e3-aa44-5854f99a55ca | OPEA Documentation | file://datasets/opea-docs/introduction/index.rst | unknown | 725a9b96-ab8a-4acd-ade9-33c2ba8fd3c2 | 7 | opea-semantic-v1 | f35d42a343bb3fdf | OPEA Project Architecture *************************
OPEA uses microservices to create high-quality GenAI applications for
enterprises, simplifying the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a
megaservice thereby creating real-world Enterpr... | ai_ref_knowledge | OPEA Documentation | OPEA Project Architecture *************************
OPEA uses microservices to create high-quality GenAI applications for
enterprises, simplifying the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a
megaservice thereby creating real-world Enterpr... | OPEA Project Architecture *************************
OPEA uses microservices to create high-quality GenAI applications for
enterprises, simplifying the scaling and deployment process for production. These microservices leverage a service composer that assembles them into a
megaservice thereby creating real-world Enterpr... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0f5c00bf-bad0-448e-81a8-bee71d8af322 | OPEA Documentation | file://datasets/opea-docs/microservices/index.rst | unknown | 1a18531c-df74-45b6-890f-51c4f4b2183c | 3 | opea-semantic-v1 | 71fde899aeed399b | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIComps/comps directory
.. include:: microservices.txt | ai_ref_knowledge | OPEA Documentation | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIComps/comps directory
.. include:: microservices.txt | .. comment This include file is generated in the Makefile during doc build time from all the directories found in the GenAIComps/comps directory
.. include:: microservices.txt | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
31245a78-902b-40e4-bf92-19020f307172 | OPEA Documentation | file://datasets/opea-docs/microservices/index.rst | unknown | 1a18531c-df74-45b6-890f-51c4f4b2183c | 1 | opea-semantic-v1 | 414383a757f0afb8 | a mega-service tailored for real-world Enterprise AI applications. All the microservices are containerized, allowing cloud native deployment. Checkout how the microservices are used in :ref:`GenAIExamples`.
We're building this microservices documentation from content in the | ai_ref_knowledge | OPEA Documentation | a mega-service tailored for real-world Enterprise AI applications. All the microservices are containerized, allowing cloud native deployment. Checkout how the microservices are used in :ref:`GenAIExamples`.
We're building this microservices documentation from content in the | a mega-service tailored for real-world Enterprise AI applications. All the microservices are containerized, allowing cloud native deployment. Checkout how the microservices are used in :ref:`GenAIExamples`.
We're building this microservices documentation from content in the | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f0ff2726-8225-4d4c-a1b0-b15b060249ec | OPEA Documentation | file://datasets/opea-docs/microservices/index.rst | unknown | 1a18531c-df74-45b6-890f-51c4f4b2183c | 0 | opea-semantic-v1 | 24bb15f3f5c6798c | GenAI Microservices ###################
GenAI microservices leverage a service composer to
assemble a mega-service tailored for real-world Enterprise AI applications. All
the microservices are containerized, allowing cloud native deployment. Checkout
how the microservices are used in :ref:`GenAIExamples`. | ai_ref_knowledge | OPEA Documentation | GenAI Microservices ###################
GenAI microservices leverage a service composer to
assemble a mega-service tailored for real-world Enterprise AI applications. All
the microservices are containerized, allowing cloud native deployment. Checkout
how the microservices are used in :ref:`GenAIExamples`. | GenAI Microservices ###################
GenAI microservices leverage a service composer to
assemble a mega-service tailored for real-world Enterprise AI applications. All
the microservices are containerized, allowing cloud native deployment. Checkout
how the microservices are used in :ref:`GenAIExamples`. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f1f5324b-c658-4fbb-8d89-8e54c7bdba6f | OPEA Documentation | file://datasets/opea-docs/microservices/index.rst | unknown | 1a18531c-df74-45b6-890f-51c4f4b2183c | 2 | opea-semantic-v1 | a0e36d267fb9bf13 | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIComps/comps directory | ai_ref_knowledge | OPEA Documentation | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIComps/comps directory | .. contents::
.. comment This include file is generated in the Makefile during doc build
time from all the directories found in the GenAIComps/comps directory | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1b1af5cd-c8c3-4eb1-8e92-f04d6231096d | OPEA Documentation | file://datasets/opea-docs/publish/blog.rst | unknown | 3703ca80-7446-4e34-b0c6-398841f41c01 | 2 | opea-semantic-v1 | 7b6503ff805d0981 | AI <https://mp.weixin.qq.com/s/nqGiQFaqDyNsGcBUmQSI8w>`_ - Ruoyu Ying * - 03/14/2025 - `Document Summarization: A Step-by-Step Guide with OPEA™ 1.2 and Intel® Gaudi® 2 <https://www.intel.com/content/www/us/en/developer/articles/technical/document-summarization-step-by-step-guide.html>`_ - Mustafa S.
Cetin, Sihan Chen, ... | ai_ref_knowledge | OPEA Documentation | AI <https://mp.weixin.qq.com/s/nqGiQFaqDyNsGcBUmQSI8w>`_ - Ruoyu Ying * - 03/14/2025 - `Document Summarization: A Step-by-Step Guide with OPEA™ 1.2 and Intel® Gaudi® 2 <https://www.intel.com/content/www/us/en/developer/articles/technical/document-summarization-step-by-step-guide.html>`_ - Mustafa S.
Cetin, Sihan Chen, ... | AI <https://mp.weixin.qq.com/s/nqGiQFaqDyNsGcBUmQSI8w>`_ - Ruoyu Ying * - 03/14/2025 - `Document Summarization: A Step-by-Step Guide with OPEA™ 1.2 and Intel® Gaudi® 2 <https://www.intel.com/content/www/us/en/developer/articles/technical/document-summarization-step-by-step-guide.html>`_ - Mustafa S.
Cetin, Sihan Chen, ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
db73ebf6-aad6-4fb1-99c5-59b7ef5fe2ec | OPEA Documentation | file://datasets/opea-docs/publish/blog.rst | unknown | 3703ca80-7446-4e34-b0c6-398841f41c01 | 0 | opea-semantic-v1 | acda96111e47e8e4 | Come learn, try, develop, and share your stories! Please submit PRs, organizing content in reverse chronological order.
.. list-table:: Trending Blogs | ai_ref_knowledge | OPEA Documentation | Come learn, try, develop, and share your stories! Please submit PRs, organizing content in reverse chronological order.
.. list-table:: Trending Blogs | Come learn, try, develop, and share your stories! Please submit PRs, organizing content in reverse chronological order.
.. list-table:: Trending Blogs | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f52136a1-941f-435a-8cbb-9b2531a7adfe | OPEA Documentation | file://datasets/opea-docs/publish/blog.rst | unknown | 3703ca80-7446-4e34-b0c6-398841f41c01 | 1 | opea-semantic-v1 | 03ee3e972b872d55 | .. list-table:: Trending Blogs
* - Date
- URL
- Authors
* - 06/09/2025
- `Deploy a RAG-Based Chatbot in Minutes on Intel Tiber AI Cloud <https://www.intel.com/content/www/us/en/developer/articles/technical/deploy-a-rag-based-chatbot-on-tiber-ai-cloud.html>`_
- Alex Sin, Edward Lee, Kelli Belcher
* - 04/18/2025
-... | ai_ref_knowledge | OPEA Documentation | .. list-table:: Trending Blogs
* - Date
- URL
- Authors
* - 06/09/2025
- `Deploy a RAG-Based Chatbot in Minutes on Intel Tiber AI Cloud <https://www.intel.com/content/www/us/en/developer/articles/technical/deploy-a-rag-based-chatbot-on-tiber-ai-cloud.html>`_
- Alex Sin, Edward Lee, Kelli Belcher
* - 04/18/2025
-... | .. list-table:: Trending Blogs
* - Date
- URL
- Authors
* - 06/09/2025
- `Deploy a RAG-Based Chatbot in Minutes on Intel Tiber AI Cloud <https://www.intel.com/content/www/us/en/developer/articles/technical/deploy-a-rag-based-chatbot-on-tiber-ai-cloud.html>`_
- Alex Sin, Edward Lee, Kelli Belcher
* - 04/18/2025
-... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0b097cc2-31c4-4d4a-b0ad-24b2178dd95e | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 5 | opea-semantic-v1 | 8d7a6bcffdf19422 | .. mermaid::
graph LR;
U[User]-->SA[Supervisor Agent];
SA-->WA[Worker Agent];
WA-->RT[Retrieval Tool];
SA-->T1[Tool 1];
SA-->T2[Tool 2];
SA-->TN[Tool N];
SA-->U;
WA-->SA;
RT-->WA;
T1-->SA;
T2-->SA;
TN-->SA; | ai_ref_knowledge | OPEA Documentation | .. mermaid::
graph LR;
U[User]-->SA[Supervisor Agent];
SA-->WA[Worker Agent];
WA-->RT[Retrieval Tool];
SA-->T1[Tool 1];
SA-->T2[Tool 2];
SA-->TN[Tool N];
SA-->U;
WA-->SA;
RT-->WA;
T1-->SA;
T2-->SA;
TN-->SA; | .. mermaid::
graph LR;
U[User]-->SA[Supervisor Agent];
SA-->WA[Worker Agent];
WA-->RT[Retrieval Tool];
SA-->T1[Tool 1];
SA-->T2[Tool 2];
SA-->TN[Tool N];
SA-->U;
WA-->SA;
RT-->WA;
T1-->SA;
T2-->SA;
TN-->SA; | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
166e7159-e296-4dcd-a3dd-e80f38625133 | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 2 | opea-semantic-v1 | 0eb69eb115b9a2b8 | can provide high-quality output for different aspects of a complex query, and the supervisor agent can aggregate the information together to provide a comprehensive answer.
How It Works
************ | ai_ref_knowledge | OPEA Documentation | can provide high-quality output for different aspects of a complex query, and the supervisor agent can aggregate the information together to provide a comprehensive answer.
How It Works
************ | can provide high-quality output for different aspects of a complex query, and the supervisor agent can aggregate the information together to provide a comprehensive answer.
How It Works
************ | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
37c9fb25-fa38-43ca-9b44-f7574a44e719 | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 4 | opea-semantic-v1 | d250adaa1782dcad | gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent.
.. mermaid:: | ai_ref_knowledge | OPEA Documentation | gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent.
.. mermaid:: | gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent.
.. mermaid:: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
38207c82-00f4-4d8a-8f4a-7f46bc291413 | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 0 | opea-semantic-v1 | 01c9bf6472b1109f | This example showcases a hierarchical multi-agent system for question-answering applications.
Purpose
*******
* Improve relevancy of retrieved context. Agent can rephrase user queries, decompose user queries, and iterate to get the most relevant context for answering user’s questions. Compared to conventional RAG, RAG ... | ai_ref_knowledge | OPEA Documentation | This example showcases a hierarchical multi-agent system for question-answering applications.
Purpose
*******
* Improve relevancy of retrieved context. Agent can rephrase user queries, decompose user queries, and iterate to get the most relevant context for answering user’s questions. Compared to conventional RAG, RAG ... | This example showcases a hierarchical multi-agent system for question-answering applications.
Purpose
*******
* Improve relevancy of retrieved context. Agent can rephrase user queries, decompose user queries, and iterate to get the most relevant context for answering user’s questions. Compared to conventional RAG, RAG ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
90d8128f-7da7-486c-b043-d745ef886968 | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 3 | opea-semantic-v1 | 3c44137202d18648 | How It Works ************
The supervisor agent interfaces with the user and dispatch tasks to the worker agent and other tools to gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent. | ai_ref_knowledge | OPEA Documentation | How It Works ************
The supervisor agent interfaces with the user and dispatch tasks to the worker agent and other tools to gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent. | How It Works ************
The supervisor agent interfaces with the user and dispatch tasks to the worker agent and other tools to gather information and come up with answers. The worker agent uses the retrieval tool to generate answers to the queries posted by the supervisor agent. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c4113a7e-3bda-4393-86f6-7d9325eacd2f | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 1 | opea-semantic-v1 | 028391dad2b63fec | be exposed as APIs for Agents to gather knowledge that may be missing in the retrieval vector database. * Hierarchical agent can further improve performance.
Expert worker agents, such as retrieval agent, knowledge graph agent, SQL agent, etc., can provide high-quality output for different aspects of a complex query, a... | ai_ref_knowledge | OPEA Documentation | be exposed as APIs for Agents to gather knowledge that may be missing in the retrieval vector database. * Hierarchical agent can further improve performance.
Expert worker agents, such as retrieval agent, knowledge graph agent, SQL agent, etc., can provide high-quality output for different aspects of a complex query, a... | be exposed as APIs for Agents to gather knowledge that may be missing in the retrieval vector database. * Hierarchical agent can further improve performance.
Expert worker agents, such as retrieval agent, knowledge graph agent, SQL agent, etc., can provide high-quality output for different aspects of a complex query, a... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c8001dfe-b23f-4500-8488-b9194df68845 | OPEA Documentation | file://datasets/opea-docs/tutorial/AgentQnA/AgentQnA_Guide.rst | unknown | 0486e1a5-3cc6-4348-a329-b5e5dddb5734 | 6 | opea-semantic-v1 | 350510f3a237ad39 | graph LR; U[User]-->SA[Supervisor Agent]; SA-->WA[Worker Agent]; WA-->RT[Retrieval Tool]; SA-->T1[Tool 1]; SA-->T2[Tool 2]; SA-->TN[Tool N]; SA-->U; WA-->SA; RT-->WA; T1-->SA; T2-->SA; TN-->SA;
Deployment
**********
Here are some deployment options, depending on your hardware and environment: | ai_ref_knowledge | OPEA Documentation | graph LR; U[User]-->SA[Supervisor Agent]; SA-->WA[Worker Agent]; WA-->RT[Retrieval Tool]; SA-->T1[Tool 1]; SA-->T2[Tool 2]; SA-->TN[Tool N]; SA-->U; WA-->SA; RT-->WA; T1-->SA; T2-->SA; TN-->SA;
Deployment
**********
Here are some deployment options, depending on your hardware and environment: | graph LR; U[User]-->SA[Supervisor Agent]; SA-->WA[Worker Agent]; WA-->RT[Retrieval Tool]; SA-->T1[Tool 1]; SA-->T2[Tool 2]; SA-->TN[Tool N]; SA-->U; WA-->SA; RT-->WA; T1-->SA; T2-->SA; TN-->SA;
Deployment
**********
Here are some deployment options, depending on your hardware and environment: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
066daa3e-207f-4d84-ac65-8e95338b936a | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 14 | opea-semantic-v1 | 0e33afe79f2db893 | the voice chatbot system, starting from the user input and going through the Audio2Text, response generations, and Text2Audio components, ultimately resulting in the bot's output.
The architecture follows a series of steps to process user queries and generate
responses: | ai_ref_knowledge | OPEA Documentation | the voice chatbot system, starting from the user input and going through the Audio2Text, response generations, and Text2Audio components, ultimately resulting in the bot's output.
The architecture follows a series of steps to process user queries and generate
responses: | the voice chatbot system, starting from the user input and going through the Audio2Text, response generations, and Text2Audio components, ultimately resulting in the bot's output.
The architecture follows a series of steps to process user queries and generate
responses: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0898594a-8804-4f14-b3f3-d6941db561bb | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 15 | opea-semantic-v1 | aae420af9acab30a | The architecture follows a series of steps to process user queries and generate responses:
1. **Automatic Speech Recognition (ASR)**: ASR is used to accurately recognize and
transcribe human speech, which is crucial for LLMs. The ASR system receives audio
input, extracts features, maps features to sequences of phon... | ai_ref_knowledge | OPEA Documentation | The architecture follows a series of steps to process user queries and generate responses:
1. **Automatic Speech Recognition (ASR)**: ASR is used to accurately recognize and
transcribe human speech, which is crucial for LLMs. The ASR system receives audio
input, extracts features, maps features to sequences of phon... | The architecture follows a series of steps to process user queries and generate responses:
1. **Automatic Speech Recognition (ASR)**: ASR is used to accurately recognize and
transcribe human speech, which is crucial for LLMs. The ASR system receives audio
input, extracts features, maps features to sequences of phon... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3dffe5e5-f80e-4ab6-bb75-f427bdd4f21c | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 9 | opea-semantic-v1 | 2a2c5571da538ccb | flowchart LR %% Colors %% classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orchid fill:#C26DBC,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef invisible fill:transparent,stroke:transparent; style ... | ai_ref_knowledge | OPEA Documentation | flowchart LR %% Colors %% classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orchid fill:#C26DBC,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef invisible fill:transparent,stroke:transparent; style ... | flowchart LR %% Colors %% classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef orchid fill:#C26DBC,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5 classDef invisible fill:transparent,stroke:transparent; style ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
42733824-d9a6-40be-8105-118a0943b3c1 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 0 | opea-semantic-v1 | 3fc8a8f2bfef0bb9 | Overview ********
AudioQnA is an example that demonstrates the integration of Generative AI
(GenAI) models for performing question-answering (QnA) on audio files, with
the added functionality of Text-to-Speech (TTS) for generating spoken
responses.The example showcases how to convert audio input to text using
Autom... | ai_ref_knowledge | OPEA Documentation | Overview ********
AudioQnA is an example that demonstrates the integration of Generative AI
(GenAI) models for performing question-answering (QnA) on audio files, with
the added functionality of Text-to-Speech (TTS) for generating spoken
responses.The example showcases how to convert audio input to text using
Autom... | Overview ********
AudioQnA is an example that demonstrates the integration of Generative AI
(GenAI) models for performing question-answering (QnA) on audio files, with
the added functionality of Text-to-Speech (TTS) for generating spoken
responses.The example showcases how to convert audio input to text using
Autom... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5a51cda8-3e6b-4629-8510-3f614e5bfa95 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 10 | opea-semantic-v1 | ef416cd8725e5c10 | AudioQnA-MegaService["AudioQnA MegaService "] direction LR ASR([ASR MicroService]):::blue LLM([LLM MicroService]):::blue TTS([TTS MicroService]):::blue end subgraph UserInterface[" User Interface "] direction LR a([User Input Query]):::orchid UI([UI server<br>]):::orchid end
WSP_SRV{{whisper service<br>}}
SPC_SRV{{spe... | ai_ref_knowledge | OPEA Documentation | AudioQnA-MegaService["AudioQnA MegaService "] direction LR ASR([ASR MicroService]):::blue LLM([LLM MicroService]):::blue TTS([TTS MicroService]):::blue end subgraph UserInterface[" User Interface "] direction LR a([User Input Query]):::orchid UI([UI server<br>]):::orchid end
WSP_SRV{{whisper service<br>}}
SPC_SRV{{spe... | AudioQnA-MegaService["AudioQnA MegaService "] direction LR ASR([ASR MicroService]):::blue LLM([LLM MicroService]):::blue TTS([TTS MicroService]):::blue end subgraph UserInterface[" User Interface "] direction LR a([User Input Query]):::orchid UI([UI server<br>]):::orchid end
WSP_SRV{{whisper service<br>}}
SPC_SRV{{spe... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5a85fb86-68ea-4166-85ef-52e284cfb96f | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 4 | opea-semantic-v1 | 1bb95a85a4165fdd | Key Implementation Details **************************
User Interface:
The interface that interactivates with users, gets inputs from users and
serves responses to users. AudioQnA GateWay:
The agent that maintains the connections between user-end and service-end,
forwards requests and responses to apropriate nodes... | ai_ref_knowledge | OPEA Documentation | Key Implementation Details **************************
User Interface:
The interface that interactivates with users, gets inputs from users and
serves responses to users. AudioQnA GateWay:
The agent that maintains the connections between user-end and service-end,
forwards requests and responses to apropriate nodes... | Key Implementation Details **************************
User Interface:
The interface that interactivates with users, gets inputs from users and
serves responses to users. AudioQnA GateWay:
The agent that maintains the connections between user-end and service-end,
forwards requests and responses to apropriate nodes... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
62fc2d24-1cb6-4f28-8b8c-9ddb9197692d | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 2 | opea-semantic-v1 | 780950d8342d052a | Purpose *******
* **Enable audio conversation with LLMs**: AudioAnA is to develop an innovative voice-to-text-to-LLM-to-text-to-voice conversational system that leverages advanced language models to facilitate seamless and natural communication between humans and machines. | ai_ref_knowledge | OPEA Documentation | Purpose *******
* **Enable audio conversation with LLMs**: AudioAnA is to develop an innovative voice-to-text-to-LLM-to-text-to-voice conversational system that leverages advanced language models to facilitate seamless and natural communication between humans and machines. | Purpose *******
* **Enable audio conversation with LLMs**: AudioAnA is to develop an innovative voice-to-text-to-LLM-to-text-to-voice conversational system that leverages advanced language models to facilitate seamless and natural communication between humans and machines. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7562e307-c38f-428a-ae75-95f1c8a8cf50 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 13 | opea-semantic-v1 | a991caae14d1018f | %% Embedding service flow direction LR ASR <-.-> WSP_SRV LLM <-.-> LLM_gen TTS <-.-> SPC_SRV
This diagram illustrates the flow of information in the voice chatbot system,
starting from the user input and going through the Audio2Text, response
generations, and Text2Audio components, ultimately resulting in the bot's o... | ai_ref_knowledge | OPEA Documentation | %% Embedding service flow direction LR ASR <-.-> WSP_SRV LLM <-.-> LLM_gen TTS <-.-> SPC_SRV
This diagram illustrates the flow of information in the voice chatbot system,
starting from the user input and going through the Audio2Text, response
generations, and Text2Audio components, ultimately resulting in the bot's o... | %% Embedding service flow direction LR ASR <-.-> WSP_SRV LLM <-.-> LLM_gen TTS <-.-> SPC_SRV
This diagram illustrates the flow of information in the voice chatbot system,
starting from the user input and going through the Audio2Text, response
generations, and Text2Audio components, ultimately resulting in the bot's o... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
901b34c9-ca4c-4e75-ad0e-324a4834e014 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 5 | opea-semantic-v1 | f9536277c7574653 | using Automatic Speech Recognition (ASR), generates answers to user queries using a language model, and then converts those answers back to speech using Text-to-Speech (TTS).
How It Works
************ | ai_ref_knowledge | OPEA Documentation | using Automatic Speech Recognition (ASR), generates answers to user queries using a language model, and then converts those answers back to speech using Text-to-Speech (TTS).
How It Works
************ | using Automatic Speech Recognition (ASR), generates answers to user queries using a language model, and then converts those answers back to speech using Text-to-Speech (TTS).
How It Works
************ | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9d1f4326-f2c3-4620-87ca-0a2ba013ae6a | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 16 | opea-semantic-v1 | d901b126cb54ae55 | similar to human speech. The TTS system analyzes the input text, converts the text into a standard form and converts normalized text into final speech.
Deployment
********** | ai_ref_knowledge | OPEA Documentation | similar to human speech. The TTS system analyzes the input text, converts the text into a standard form and converts normalized text into final speech.
Deployment
********** | similar to human speech. The TTS system analyzes the input text, converts the text into a standard form and converts normalized text into final speech.
Deployment
********** | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9f8951c5-07b7-4f7a-9d51-18b07d133b46 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 6 | opea-semantic-v1 | 0d303c4886d7e0b0 | How It Works ************
The AudioQnA example is implemented using the component-level microservices defined
in `GenAI Components <https://github.com/opea-project/GenAIComps>`. The flow chart below
shows the information flow between different microservices for this example. | ai_ref_knowledge | OPEA Documentation | How It Works ************
The AudioQnA example is implemented using the component-level microservices defined
in `GenAI Components <https://github.com/opea-project/GenAIComps>`. The flow chart below
shows the information flow between different microservices for this example. | How It Works ************
The AudioQnA example is implemented using the component-level microservices defined
in `GenAI Components <https://github.com/opea-project/GenAIComps>`. The flow chart below
shows the information flow between different microservices for this example. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
aab04793-0288-496b-a9cb-1ad27f36c8cd | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 1 | opea-semantic-v1 | 9aa1cef92a51be60 | using Automatic Speech Recognition (ASR), generate answers to user queries using a language model, and then convert those answers back to speech using Text-to-Speech (TTS).
Purpose
******* | ai_ref_knowledge | OPEA Documentation | using Automatic Speech Recognition (ASR), generate answers to user queries using a language model, and then convert those answers back to speech using Text-to-Speech (TTS).
Purpose
******* | using Automatic Speech Recognition (ASR), generate answers to user queries using a language model, and then convert those answers back to speech using Text-to-Speech (TTS).
Purpose
******* | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b2fedc59-aae5-45ef-bebc-5f7f9787fad5 | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 8 | opea-semantic-v1 | 54a9fc75b43780de | config: flowchart: nodeSpacing: 400 rankSpacing: 100 curve: linear themeVariables: fontSize: 50px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26DBC,stroke:#A... | ai_ref_knowledge | OPEA Documentation | config: flowchart: nodeSpacing: 400 rankSpacing: 100 curve: linear themeVariables: fontSize: 50px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26DBC,stroke:#A... | config: flowchart: nodeSpacing: 400 rankSpacing: 100 curve: linear themeVariables: fontSize: 50px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26DBC,stroke:#A... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c529164e-1cd2-4fd4-b7ac-14cf07a9854f | OPEA Documentation | file://datasets/opea-docs/tutorial/AudioQnA/AudioQnA_Guide.rst | unknown | bc21d3d3-6dda-44c6-a2fc-8ca0a8d4ee31 | 11 | opea-semantic-v1 | ca4d44b93ae2ba9e | WSP_SRV{{whisper service<br>}} SPC_SRV{{speecht5 service <br>}} LLM_gen{{LLM Service <br>}} GW([AudioQnA GateWay<br>]):::orange
%% Questions interaction
direction LR
a[User Audio Query] --> UI
UI --> GW
GW <==> AudioQnA-MegaService
ASR ==> LLM
LLM ==> TTS | ai_ref_knowledge | OPEA Documentation | WSP_SRV{{whisper service<br>}} SPC_SRV{{speecht5 service <br>}} LLM_gen{{LLM Service <br>}} GW([AudioQnA GateWay<br>]):::orange
%% Questions interaction
direction LR
a[User Audio Query] --> UI
UI --> GW
GW <==> AudioQnA-MegaService
ASR ==> LLM
LLM ==> TTS | WSP_SRV{{whisper service<br>}} SPC_SRV{{speecht5 service <br>}} LLM_gen{{LLM Service <br>}} GW([AudioQnA GateWay<br>]):::orange
%% Questions interaction
direction LR
a[User Audio Query] --> UI
UI --> GW
GW <==> AudioQnA-MegaService
ASR ==> LLM
LLM ==> TTS | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.