Presentation 1
Presentation 1
MLOps: A Reality!!!!
Data science and ML have become essential
capabilities to solve dynamic real-world issues, shift Many organisations are also engaging in their data
industries and generate value in all fields. At science teams and ML resources to guide decisions
present, you have access to components for that can provide their customers with value
successful application of ML:. creation.
FEATURES OF MLOps
1. Data extraction: You pick and integrate the appropriate data from different data sources for the ML
process.
2. Data Analysis: You perform the EDA to learn the available data for ML model development.
Exploratory data analysis.
3. Data Preparation: the data for the ML task is planned. This method includes data purification, which
separates the data into preparation, testing and validation sets.
4. Model training: the data scientist uses various techniques for training various ML models using the
prepared data.
5. Model assessment: The model is tested on a holdout test set for model quality assessment. The
results of this step are a series of measurements for evaluating the model consistency.
6. Model Validation: The model is verified appropriate for implementation – it is greater than a certain
baseline in its predictive efficiency.
7. Model Servicing: The validated model is used to serve predictions in a target setting. The following
deployment may be:
• An integrated model on a mobile device or side.
• Part of a scheme of lots prediction.
• The model monitoring: a new iteration in the ML phase is monitored for the model's
predictive efficiency.
CONTINUOUS INTEGRATION: • Trial of the expected artefacts • Test the forecasting service by
In this configuration, as new code is generated by each portion in the calling the service API and
committed to or pushed into the pipeline. verifying that the answer you are
repository source code, the pipeline • Integration testing among the expecting is available. Typically,
and its components are designed, components of the pipeline. this test catches problems that
checked and packed. The CI method can happen when the model
can involve the following checks, in CONTINUOUS DELIVERY: version is modified and expects a
addition to the building of packages, Your framework provides constantly different input.
container images and executables: new pipeline implementations to the • Automated use in a testing area,
• Evaluate your engineering logic target environment at this stage, for instance, by moving code to
for your feature. providing the newly trained model the dev environment.
• Test unit the various methods with prediction services. To deliver • Half-automatic deployment in a
that your model implements. You pipelines and models quickly and pre-production environment for
have a function that takes a effectively continuously, take the instance, when reviews approve
categorical column and encodes following into account: improvements, is triggered by
the function as a single-hot • Until deploying your model, fusion of code in the main
function, for instance. verify consistency of your model branch.
• Testing to converge your concept with the mentioned challenges. • The manual deployment of the
training (that is, the loss of your You need to confirm, for example pipeline in the pre-production
model goes down by iterations that the packages that the design environment after many
and overfits a few sample needs are enabled in the successful runs.
records). servicing environment and that
• To verify that the NaN values are the usable memory, calculation
not generated by your model and accelerator resources.
training because of division by
zero or the manipulation of large
or small values.