Book Image

Comet for Data Science

By : Angelica Lo Duca
Book Image

Comet for Data Science

By: Angelica Lo Duca

Overview of this book

This book provides concepts and practical use cases which can be used to quickly build, monitor, and optimize data science projects. Using Comet, you will learn how to manage almost every step of the data science process from data collection through to creating, deploying, and monitoring a machine learning model. The book starts by explaining the features of Comet, along with exploratory data analysis and model evaluation in Comet. You’ll see how Comet gives you the freedom to choose from a selection of programming languages, depending on which is best suited to your needs. Next, you will focus on workspaces, projects, experiments, and models. You will also learn how to build a narrative from your data, using the features provided by Comet. Later, you will review the basic concepts behind DevOps and how to extend the GitLab DevOps platform with Comet, further enhancing your ability to deploy your data science projects. Finally, you will cover various use cases of Comet in machine learning, NLP, deep learning, and time series analysis, gaining hands-on experience with some of the most interesting and valuable data science techniques available. By the end of this book, you will be able to confidently build data science pipelines according to bespoke specifications and manage them through Comet.
Table of Contents (16 chapters)
1
Section 1 – Getting Started with Comet
5
Section 2 – A Deep Dive into Comet
10
Section 3 – Examples and Use Cases

Exploring DevOps and MLOps principles and best practices

A traditional approach to moving software from testing to production includes two separate steps:

  1. Development – Developers implement their code and test it in their local environment and under their local conditions.
  2. Operations – When the code is ready, developers send the code to the operations teams, who are responsible for installing and maintaining the code in the production machine.

This approach requires a great effort from both teams – developers and operations teams – because, on the one hand, a little change in the code requires a new installation and configuration in the production machine. On the other hand, when the operations team discovers an anomaly in the code, they should communicate with the development team to run new tests, and then the process may become very slow.

If the number of tasks is small, a manual process could be acceptable, but if you have millions...