Pipeline: Add pipeline subsystem
#60
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaancayli
changed the title
Pipeline: Initial pipeline setup
kaancayli
changed the title
Pipeline: Initial pipeline setupPipeline: Add pipeline subsystem
Hialus
requested changes
Feb 15, 2024
There was a problem hiding this comment.
Sorry for leaving so many small comments 😅. But I think they should make the code quality better.
Also please ensure that in the future not all pipelines are in the same file, but are properly split up into multiple files according to their area. Having it all in one file eventually results in an unreadable mess.
MichaelOwenDyer
previously approved these changes
Feb 19, 2024
Not all pipelines will return an IrisMessage
…yris into feature/pipeline-subsystem-v1
Hialus
requested changes
Feb 21, 2024
Hialus
approved these changes
Feb 21, 2024
isabellagessl
pushed a commit
that referenced
this pull request
Nov 11, 2024
Co-authored-by: Michael Dyer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
For Pyris V2 we need modular and reusable pipelines. This system will support different Pipeline selections in the future, which are all accessible through the same Interface. We also want to send status updates during pipeline processing.
Description
The primary objective of the pipeline subsystem is to abstract the prompting and reasoning logic associated with various LLM use cases, such as exercise creation and tutor chat, from the overall system infrastructure.
The
FeaturePipelinescomponent is the initial receiver of user queries from the Endpoint subsystem. It directs these queries to the appropriate functional units specifically designed to handle distinct use cases. These units transform user queries into structured prompts, which are subsequently directed to the LLM subsystem through the corresponding completion and chat interfaces, contingent upon the context of the query. Responses from the LLM subsystem are then conveyed back to the Endpoint subsystem for user delivery.During query processing, the FeaturePipelines component leverages the retrieval interface from the Retrieval subsystem to obtain contextual data pertinent to the user queries. Further details about the Retrieval subsystem can be found in the later chapters of the documentation.
Simultaneously, the FeaturePipelines component communicates operational progress to the Notification Service. This service processes the progress data and interfaces with the Artemis Connector to disseminate progress notifications. In its role, the Artemis Connector forwards these notifications to the designated Artemis system. The specifics of the Artemis Connector's role and its interaction with the Artemis system are detailed in later chapters of the documentation.