Skip to content

Commit ef31f9f

Browse files
committed
Merge branch 'release/0.6.2' into 0.6.x
2 parents 94e1ce9 + 2a7d806 commit ef31f9f

File tree

29 files changed

+4093
-1413
lines changed

29 files changed

+4093
-1413
lines changed

README.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ The mlrun/demos repository provides demos that implement full end-to-end ML use-
1313
- [Churn Demo: Real-Time Customer-Churn Prediction](#demo-churn)
1414
- [NetOps Demo: Predictive Network Operations/Telemetry](#demo-netops)
1515
- [Stock-Analysis Demo](#demo-stocks)
16+
- [Model deployment Pipeline: Real-time operational Pipeline](#demo-model-deployment)
1617
- [How-To: Converting Existing ML Code to an MLRun Project](#howto-convert-to-mlrun)
1718

1819
<a id="overview"></a>
@@ -188,6 +189,32 @@ The demo include the following steps:
188189

189190
<p><img src="./stock-analysis/assets/images/stocks-demo-pipeline.png" alt="Stock-analysis pipeline output" width="500"/></p>
190191

192+
<a id="demo-model-deployment"></a>
193+
194+
## Model deployment Pipeline: Real-time operational Pipeline
195+
196+
This demo shows how to deploy a model with streaming information.
197+
198+
This demo is comprised of several steps:
199+
200+
<p><img src="./model-deployment-pipeline/assets/model-deployment-pipeline.png" alt="Model deployment Pipeline Real-time operational Pipeline" width="500"/></p>
201+
202+
203+
While this demo covers the use case of 1<sup>st</sup>-day churn, it is easy to replace the data, related features and training model and reuse the same workflow for different business cases.
204+
205+
These steps are covered by the following pipeline:
206+
207+
- **1. Data generator** — Generates events for the training and serving and Create an enrichment table (lookup values).
208+
- **2. Event handler** - Receive data from the input. This is a common input stream for all the data. This way, one can easily replace the event source data (in this case we have a data generator) without affecting the rest of this flow. It also store all incoming data to parquet files.
209+
- **3. Stream to features** - Enrich the stream using the enrichment table and Update aggregation features using the incoming event handler.
210+
- **4. Optional model training steps -**
211+
- **4.1 Get Data Snapshot** - Takes a snapshot of the feature table for training.
212+
- **4.2 Describe the Dataset** - Runs common analysis on the datasets and produces plots suche as histogram, feature importance, corollation and more.
213+
- **4.3 Training** - Runing training with multiple classification models.
214+
- **4.4 Testing** - Testing the best performing model.
215+
- **5. Serving** - Serve the model and process the data from the enriched stream and aggregation features.
216+
- **6. Inference logger** - We use the same event handler function from above but only its capability to store incoming data to parquet files.
217+
191218
<a id="howto-convert-to-mlrun"></a>
192219
## How-To: Converting Existing ML Code to an MLRun Project
193220

customer-churn-prediction/.test

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
churn-project.ipynb

getting-started-tutorial/tutorial-1-MLRun-basics.ipynb renamed to getting-started-tutorial/01-mlrun-basics.ipynb

Lines changed: 328 additions & 295 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)