Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added pipeline graph to deployment usage #11

Merged
merged 1 commit into from
Jun 11, 2023
Merged

Added pipeline graph to deployment usage #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion manuscript/09.2-Deployment-Usage_Pipeline-Workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ To execute the pipeline steps, the Airflow Docker Operator is employed, which en

Once the model is in the serving phase, a Streamlit app is deployed for applying inference on new data.

![DAG pipeline](images/09-Deployment-Usage/DAG-pipeline.png)
![](images/09-Deployment-Usage/use-case-pipeline-graph.png)

The code below defines the `ml_pipeline_dag` function as an Airflow DAG using the `dag` decorator. Each step of the pipeline, including data preprocessing, model training, model comparison, and serving the best model, is represented as a separate task with the `@task` decorator. Dependencies between these tasks are established by passing the output of one task as an argument to the next task. The `ml_pipeline` object serves as a representation of the entire DAG.

Expand Down
Binary file added manuscript/images/09-Deployment-Usage/use-case-pipeline-graph.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.