What is our primary use case?
My main use case for Weights & Biases is as a platform to understand machine learning experiments, including tuning model evolutions and managing data. I use it heavily when I need to write ML scripts for my data processing and data analyst responsibilities. It primarily functions as a research tool for tracking and visualizing, serving as a framework to support my data work.
To provide a specific example of how I have used Weights & Biases in my work, I have a script in my current process that involves code I want to write in Python and PyTorch. I install Weights & Biases, log in to the website, and run queries by configuring it. I have used it to create graphs of the accuracy for the process I'm working on, specifically for a customer prediction model that uses Python scripting.
When I used Weights & Biases for my customer prediction model in Python, it helped me not only with the visualization aspect but also in managing datasets and collaborating with my team members during model development and deployment. It compares the model and visualizes the metrics we want to derive from it by running ML scripts, helping us understand the project in a deeper way through image classifications and NLP models, monitoring accuracy and utilization, and managing hyperparameters while sharing experiments and comparing results.
I have used Weights & Biases mainly for predictions, as it generates automated predictions based on the LLMs we create and stores those predictions, providing data with accuracy and creating charts to help us compare the data and run against future experiments.
What is most valuable?
Weights & Biases offers several best features including tracking, visualization, the registry part, datasets, dataset versioning, and monitoring framework integrations.
Out of tracking, visualization, registry, dataset versioning, and monitoring, I find myself relying on data versioning the most because it stores changes in datasets for reproducibility, and the model registry keeps track of which prediction model is currently deployed, along with real-time monitoring during training. It also provides accuracy scores, functioning as an experimental tracking tool.
These features help in ML engineering, comparing models, and collaborating with the team while maintaining reproducibility throughout the ML lifecycle.
Weights & Biases has positively impacted my organization by improving the processes we build for the client, particularly in prediction projects. It has improved our datasets and metrics, resulting in faster model comparisons. It provides tracking and model management that helps maintain reproducibility throughout the ML lifecycle.
What needs improvement?
Weights & Biases can be improved in areas such as user experience, user interface, cost, and features.
Regarding needed improvements, I believe the storage cost should be addressed because we want to store larger datasets and more items, so it can be enhanced in that aspect.
For how long have I used the solution?
I have been using Weights & Biases for a year.
What do I think about the stability of the solution?
Weights & Biases is a stable platform.
What do I think about the scalability of the solution?
In terms of scalability, it can support individuals and small teams effectively.
Which solution did I use previously and why did I switch?
Previously, we used MLflow, ClearML, and TensorBoard, but they lacked the experimental tracking and model management features that Weights & Biases offers, so we switched to it for its end-to-end ML platforms and storage capacity. It stands out from others due to its open-source nature and stronger model registry with good deployment support.
What was our ROI?
In terms of return on investment, it has helped reduce manual efforts, especially in areas such as fraud detection. It provides accuracy and validation by giving us precision metrics, regression models, and more.
Which other solutions did I evaluate?
I evaluated various options including MLflow, Neptune.ai, and TensorBoard before settling on Weights & Biases.
What other advice do I have?
My advice to others considering Weights & Biases is to leverage its storage registry and track all important metrics while using the model registry and production monitoring accurately. It maintains proper experiment tracking and is very useful for versioning and comparing features to make data-driven model decisions.
Regarding Weights & Biases' AI capabilities, I believe it has solid governance and security measures.
I find that audit logging is stronger than in other tools, but we still need to examine perspectives regarding unauthorized access and similar concerns.
As for accuracy and reliability of outputs from Weights & Biases, it does not directly help with model accuracy but improves model development through experiments and comparisons, making it easier to identify which models deliver the highest accuracy indirectly, as it optimizes the data in a better way.
I have given Weights & Biases an overall rating of 7 out of 10.