mlem VS fiftyone

Mlem for Lemmy has a similar look and feel to Apollo. Still missing a lot of features though. https://github.com/iterative/mlem

Here are a few things to consider: 1. You're using both DVC and MLflow to store the model artifact, why? 2. How I envision MLflow, DVC and git to work together is like this. DVC to manage the training dataset, git to manage the code, and MLflow will do the rest. About the part about "versioning" the model, MLflow has a model registry feature to "tag" a well-performing experiment. 3. Or just to do everything in DVC. DVC also has a way to do experiment tracking. Then if you need a model registry there's MLEM by the same company.

No, it's a completely separate open source tool, not directly related to DVC - https://github.com/iterative/mlem

This functionality can be used from open source tool mlem.ai and our released UI - https://studio.iterative.ai/

MLEM is a new MLOps tool to bridge the gap between ML engineers and DevOps teams by using the git-based approach that developers are already familiar with. Using MLEM, developers can store and track their ML models throughout their lifecycle: GitHub - iterative/mlem: 🐶 Version and deploy your ML models following GitOps principles

In this brief walkthrough, I will illustrate how to leverage open-source FiftyOne and Anomalib to build deployment-ready anomaly detection models. First, we will load and visualize the MVTec AD dataset in the FiftyOne App. Next, we will use Albumentations to test out augmentation techniques. We will then train an anomaly detection model with Anomalib and evaluate the model with FiftyOne.

My experience has been much like this. For twenty years, I’ve emphasized scientific and engineering discovery in my work as an academic researcher, publishing these findings at the top conferences in computer vision, AI, and related fields. Yet, at my company, we focus on infrastructure that enables others to unlock scientific discovery. We have built a software framework that enables its users to do better work when training models and curating datasets with large unstructured, visual data — it’s kind of like a PyTorch++ or a Snowflake for unstructured data. This software stack, called FiftyOne in its single-user open source incarnation and FiftyOne Teams in its collaborative enterprise version, has garnered millions of installations and a vibrant user community.

We will use the Hugging Face transformers and diffusers libraries for inference, FiftyOne for data management and visualization, and scikit-image for evaluation metrics.

With all that background out of the way, let’s turn theory into practice and learn how to use clustering to structure our unstructured data. We’ll be leveraging two open-source machine learning libraries: scikit-learn, which comes pre-packaged with implementations of most common clustering algorithms, and fiftyone, which streamlines the management and visualization of unstructured data:

FiftyOne is the leading open-source toolkit for the curation and visualization of unstructured data, built on top of MongoDB. It leverages the non-relational nature of MongoDB to provide an intuitive interface for working with datasets consisting of images, videos, point clouds, PDFs, and more.

Welcome to our weekly FiftyOne tips and tricks blog where we recap interesting questions and answers that have recently popped up on Slack, GitHub, Stack Overflow, and Reddit.

If you want to perform emoji searches locally with the same visual interface, you can do so with the Emoji Search plugin for FiftyOne.