Paving the way between black-box and white-box modeling.
Project description
About WeightsLab
WeightsLab is a powerful tool for editing and inspecting data & AI models.
What Problems Does It Solve?
WeightsLab addresses critical AI research challenges:
- Dataset insights & optimization
- Overfitting and training plateau
- Over/Under parameterization
Key Capabilities
The granular statistics and interactive paradigm enable powerful workflows:
- Monitor granular insights on data samples, signals, and weight parameters
- Use the AI agent to:
- Create slices of data and discard them for the next training iteration
- Discard low-quality samples from training data
- Iterative pruning or growing of the architectures (INCOMING feature)
Find our demos:
The password is graybx. More demo to come in the future!
DEMOS
Getting Started
Installation
Define a Python environment (Python >=3.10, <3.15)
python -m venv weightslab_venv
./weightslab_venv/Scripts/activate
Or install directly on your machine.
Install our framework:
pip install weightslab
Deploy our interface with Docker:
weightslab ui launch
[!IMPORTANT] For a detailed installation guide and more advanced features, please see the Installation Documentation.
Quick Training Example
Here's a complete example showing how to integrate WeightsLab into a basic PyTorch training script:
#!/usr/bin/env python3
"""
Basic PyTorch training script with WeightsLab integration
"""
import torch
import torch.nn as nn
import torch.optim as optim
from torch.utils.data import DataLoader, TensorDataset
import weightslab as wl # ← Import WeightsLab (auto-creates secure certs!)
# Define a simple model
class SimpleModel(nn.Module):
def __init__(self):
super().__init__(input_shape=12, output_shape=2)
self.linear = nn.Linear(input_shape, 1)
def forward(self, x):
return self.linear(x)
# Create synthetic data
def create_data(n_samples=1000):
X = torch.randn(n_samples, 10)
y = X.sum(dim=1, keepdim=True) + 0.1 * torch.randn(n_samples, 1)
return TensorDataset(X, y)
# Main training function
def main():
# Initialize WeightsLab - this creates certificates automatically!
print("🚀 Initializing WeightsLab...")
# Load hyperparameters (from YAML if present)
parameters = {}
config_path = os.path.join(os.path.dirname(__file__), "config.yaml")
if os.path.exists(config_path):
with open(config_path, "r") as fh:
parameters = yaml.safe_load(fh) or {}
parameters = wl.watch_or_edit(
parameters,
flag="hyperparameters",
defaults=parameters,
poll_interval=1.0,
) or {} # Wrap the hyperparameters
# Wrap your model and optimizer with WeightsLab
model = wl.watch_or_edit(
SimpleModel(
input_shape=parameters.get('model', {}).get('input_shape', 10),
output_shape=parameters.get('model', {}).get('output_shape', 1)
)
) # ← WeightsLab tracks your model
optimizer = wl.watch_or_edit(
optim.Adam(model.parameters(), lr=parameters.get('model', {}).get('optimizer', {}).get('lr', 0.01)),
flag='optimizer'
) # ← WeightsLab tracks optimizer
# Create and wrap criterion
criterion = wl.watch_or_edit(
nn.CrossEntropyLoss(reduction="none"),
flag="loss",
signal_name="train-loss-CE",
log=True # If log is False, only save per sample value, not plot criterion
)
# Create data and dataloader
dataset = create_data()
train_loader = wl.watch_or_edit(
dataset,
flag="data",
loader_name="loader",
batch_size=parameters.get('data', {}).get('train_loader', {}).get('batch_size', 8),
shuffle=parameters.get('data', {}).get('train_loader', {}).get('shuffle', False),
is_training=True, # Is it the training dataloader ?
compute_hash=parameters.get('data', {}).get('train_loader', {}).get('compute_hash', True), # Compute hash for train loader to allow dynamic augmentations and dataset sanity check
preload_labels=parameters.get('data', {}).get('train_loader', {}).get('preload_labels', True),
preload_metadata=parameters.get('data', {}).get('train_loader', {}).get('preload_metadata', True),
enable_h5_persistence=parameters.get('data', {}).get('train_loader', {}).get('enable_h5_persistence', True),
num_workers=parameters.get('data', {}).get('train_loader', {}).get('num_workers', 4)
)
# Training loop
print("🏃 Starting training...")
print("💡 Launch the UI with: weightslab ui docker launch")
print("🌐 Open browser to: https://localhost:5173")
n_epochs = parameters.get('n_epochs')
pbar = tqdm.tqdm(range(n_epochs), desc='Training..') if parameters.get('tqdm_display', False) else range(n_epochs)
for epoch in pbar: # Train for 5 epochs
total_loss = 0
for batch_X, batch_y in dataloader:
# Forward pass
predictions = model(batch_X)
loss = criterion(predictions, batch_y)
# Backward pass
optimizer.zero_grad()
loss.backward()
optimizer.step()
total_loss += loss.item()
avg_loss = total_loss / len(dataloader)
print(f"Epoch {epoch+1}/5 - Loss: {avg_loss:.4f}")
print("✅ Training complete!")
if __name__ == "__main__":
main()
Migrating from wandb? See the diff:
--- train_baseline.py
+++ train_wl.py
@@ -1,11 +1,12 @@
import argparse
import torch
import torch.nn as nn
-from torch.utils.data import DataLoader
from torchvision import datasets, transforms, models
from torchmetrics.classification import MulticlassAccuracy
-import wandb
+import weightslab as wl
+from weightslab.components.global_monitoring import (
+ guard_training_context, guard_testing_context)
+@wl.signal(name="image_bytes")
+def image_bytes(ctx): return ctx.image.nbytes # static per-sample signal
+
+@wl.signal(name="byte_adjusted_loss", subscribe_to="loss/CE")
+def byte_adjusted_loss(ctx): return ctx.subscribed_value / ctx.image_bytes # chains on image_bytes
+
def main():
@@ -15,29 +16,38 @@
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
parameters = {"batch_size": 128, "lr": 1e-3}
- wandb.init(project="cifar10")
-
transform = transforms.Compose([
transforms.ToTensor(),
transforms.Normalize((0.4914, 0.4822, 0.4465), (0.2470, 0.2435, 0.2616)),
])
train_set = datasets.CIFAR10("./data", train=True, download=True, transform=transform)
test_set = datasets.CIFAR10("./data", train=False, download=True, transform=transform)
- train_loader = DataLoader(train_set, batch_size=parameters["batch_size"], shuffle=True, num_workers=2)
- test_loader = DataLoader(test_set, batch_size=256, num_workers=2)
+ wl.watch_or_edit(parameters, flag="hyperparameters") # live-editable in UI
+
+ train_loader = wl.watch_or_edit(
+ train_set, flag="data", loader_name="train_loader",
+ batch_size=parameters["batch_size"], shuffle=True, is_training=True)
+ test_loader = wl.watch_or_edit(
+ test_set, flag="data", loader_name="test_loader",
+ batch_size=256, shuffle=False, is_training=False)
model = models.resnet18(weights=None)
model.fc = nn.Linear(model.fc.in_features, 10)
model = model.to(device)
optimizer = torch.optim.Adam(model.parameters(), lr=parameters["lr"])
- criterion = nn.CrossEntropyLoss()
- accuracy = MulticlassAccuracy(num_classes=10).to(device)
+ criterion = wl.watch_or_edit(
+ nn.CrossEntropyLoss(), flag="loss", signal_name="loss/CE")
+ accuracy = wl.watch_or_edit(
+ MulticlassAccuracy(num_classes=10).to(device),
+ flag="metric", signal_name="acc")
+
+ wl.serve(serving_grpc=True)
for epoch in range(1, args.epochs + 1):
model.train()
accuracy.reset()
for x, y in train_loader:
+ with guard_training_context:
x, y = x.to(device), y.to(device)
logits = model(x)
loss = criterion(logits, y)
optimizer.zero_grad()
loss.backward()
optimizer.step()
accuracy.update(logits, y)
- wandb.log({"train/loss": loss.item()})
- wandb.log({"train/acc": accuracy.compute().item(), "epoch": epoch})
+ wl.save_signals(preds_raw=logits, targets=y,
+ signals={"metric/accuracy": accuracy.compute().item()})
model.eval()
accuracy.reset()
with torch.no_grad():
for x, y in test_loader:
+ with guard_testing_context:
x, y = x.to(device), y.to(device)
accuracy.update(model(x), y)
- wandb.log({"test/acc": accuracy.compute().item(), "epoch": epoch})
+ wl.save_signals(preds_raw=logits, targets=y,
+ signals={"metric/accuracy": accuracy.compute().item()})
- wandb.finish()
+ wl.keep_serving()
Step-by-Step Integration
-
Add the import at the top of your script:
import weightslab as wl # ← Include our SDK into your experiment
-
Wrap your parameters with WeightsLab tracking:
model = wl.watch_or_edit(parameters, ...) # ← Now WeightsLab monitors your parameters and allow you to update them from your UI
-
Wrap your model with WeightsLab tracking:
model = wl.watch_or_edit(SimpleModel(...), ...) # ← Now WeightsLab monitors your model state
-
Wrap your optimizer with WeightsLab tracking:
optimizer = wl.watch_or_edit(optim.Adam(...), ...) # ← Tracks optimizer state and update optimizer learning rate from your UI
-
Wrap your signal with WeightsLab tracking:
criterion = wl.watch_or_edit(nn.CrossEntropyLoss(reduction="none"), ...) # ← Tracks this signal and others (metrics, ..etc) from your UI
-
Wrap your dataset with WeightsLab tracking:
train_loader = wl.watch_or_edit(dataset, ...) # ← Tracks this dataset and others (validation, test) from your UI
-
Run your training script as usual:
python train.py -
Launch the UI in another terminal:
weightslab ui docker launch
-
Open your browser to
https://localhost:5173to track experiment evoluation and results!
What WeightsLab Does Automatically
- 🔐 Creates TLS certificates in
~/.weightslab-certs/ - 🎫 Generates secure auth tokens for gRPC communication
- 📊 Tracks model parameters and optimizer state in real-time
- 📈 Provides live metrics and visualization in the web UI
- 🔄 Enables model editing (incoming feature) and hyperparameter tuning through the UI
Security
By default, WeightsLab runs in unsecured mode (NO TLS, HTTP, no gRPC authentification). To enable TLS encryption and gRPC authentication:
Quick Setup + Launch
Setup secure environment AND launch Docker in one command:
weightslab ui docker se
export WEIGHTSLAB_CERTS_DIR='~/.weightslab-certs/' # Windows commands is
This will:
- Generate TLS certificates and gRPC auth token in
~/.weightslab-certs/ - Launch the Docker stack with security enabled
- If setup fails, Docker still launches (unsecured fallback)
Separate Steps (If Needed)
Setup secure environment only:
weightslab se
# Ubuntu command
echo 'export WEIGHTSLAB_CERTS_DIR="~/.weightslab-certs/"' >> ~/.bashrc
source ~/.bashrc
# Windows command
# setx WEIGHTSLAB_CERTS_DIR '~/.weightslab-certs/' /M
Then launch Docker later:
weightslab ui docker launch
Custom Certificates Directory
Store certificates in a custom location using the WEIGHTSLAB_CERTS_DIR environment variable:
# Generate the certs
weightslab se "/path/to/my/certs"
# Export path to env.
# Ubuntu command
echo 'export WEIGHTSLAB_CERTS_DIR=/path/to/my/certs' >> ~/.bashrc
source ~/.bashrc
# Windows command
# setx WEIGHTSLAB_CERTS_DIR /path/to/my/certs /M
# Start UI
weightslab ui docker launch
Options for Secure Environment Setup
For weightslab se or weightslab ui docker se:
| Flag | Effect |
|---|---|
--force-certs |
Regenerate certificates even if they already exist |
--no-auth |
Skip gRPC auth token generation (TLS only) |
Examples:
weightslab se --force-certs # Regenerate certs only
weightslab se --no-auth # TLS only, no gRPC token
weightslab ui docker se # Setup + launch in one
weightslab ui docker se --force-certs # Setup (regenerate) + launch
What Gets Created?
After running weightslab se or weightslab ui docker se, your ~/.weightslab-certs/ directory contains:
backend-server.crt— Backend TLS certificatebackend-server.key— Backend TLS private keyca.crt— CA certificate.grpc_auth_token— gRPC authentication token (if not using--no-auth)
Running Without Security
To explicitly run in unsecured mode, delete the certificates directory:
rm -r ~/.weightslab-certs
weightslab ui docker launch # Falls back to unsecured HTTP
Testing the Setup
Secured environment:
weightslab se # Setup certs and token
weightslab ui docker launch # Launch Docker
python main.py # Backend finds certs, runs secured
Unsecured environment:
weightslab ui docker launch # Launch Docker (no certs)
python main.py # Backend runs unsecured
Cookbook
Check out our materials, which include examples ranging from toys to more complex models and experiments.
Quickstart examples:
- WeightsLab - Classification toy (PyTorch)
- WeightsLab - Segmentation toy (PyTorch)
- WeightsLab - Detection toy (PyTorch)
- WeightsLab - Classification toy (PyTorch Lightning)
Configuration
WeightsLab and Weightslab UI are configured through environment variables. A fully commented .env template is included at the repository root — copy it and adjust for your setup:
cp .env .env.local # or edit .env directly
| Category | Key variables |
|---|---|
| Logging | WEIGHTSLAB_LOG_LEVEL, WEIGHTSLAB_LOG_TO_FILE, WEIGHTSLAB_ROOT_LOG_DIR |
| gRPC server | GRPC_BACKEND_HOST, GRPC_BACKEND_PORT, GRPC_MAX_MESSAGE_BYTES, GRPC_TLS_ENABLED, GRPC_TLS_CERT_DIR, GRPC_TLS_CERT_FILE, GRPC_TLS_KEY_FILE, GRPC_TLS_CA_FILE, GRPC_TLS_REQUIRE_CLIENT_AUTH, GRPC_AUTH_TOKEN, GRPC_AUTH_TOKENS |
| Watchdog | GRPC_WATCHDOG_STUCK_SECONDS, GRPC_WATCHDOG_INTERVAL_SECONDS, GRPC_WATCHDOG_RESTART_THRESHOLD, GRPC_WATCHDOG_EXIT_ON_STUCK |
| Data / cache | WL_MAX_PREVIEW_CACHE_SIZE, WL_PREVIEW_CACHE_WARMUP_WAIT_MS, WL_DEFAULT_THUMBNAIL_SIZE, WEIGHTSLAB_SAVE_PREDICTIONS_IN_H5 |
| AI keys | OPENROUTER_API_KEY |
| Agent config | AGENT_CONFIG_PATH |
| Weightslab UI | VITE_SERVER_HOST, VITE_SERVER_PORT, VITE_HISTOGRAM_MAX_BINS, ENVOY_HOST, ENVOY_PORT |
AGENT_CONFIG_PATH lets you point the data agent to a custom directory that contains agent_config.yaml.
If set, WeightsLab looks for <AGENT_CONFIG_PATH>/agent_config.yaml before fallback locations.
WeightsLab also reads TLS settings from registered runtime config (hyperparameters), using config-first precedence over environment variables.
If TLS is enabled (grpc_tls_enabled in config or GRPC_TLS_ENABLED in env),
certificate path resolution is:
- config file paths (
grpc_tls_cert_file,grpc_tls_key_file,grpc_tls_ca_file) - env file paths (
GRPC_TLS_CERT_FILE,GRPC_TLS_KEY_FILE,GRPC_TLS_CA_FILE) - config directory (
grpc_tls_cert_dir) - env directory (
GRPC_TLS_CERT_DIR) - default
~/certs(backend-server.crt,backend-server.key,ca.crt)
TLS flags also follow config-first precedence:
grpc_tls_enabled then GRPC_TLS_ENABLED, and
grpc_tls_require_client_auth then GRPC_TLS_REQUIRE_CLIENT_AUTH.
Full documentation with all variables and their descriptions: docs/configuration.rst
AI Agent
WeightsLab can run its data agent in two modes:
- Local provider with Ollama
- Cloud provider with OpenRouter
Use local Ollama when you want a fully local setup and do not need cloud-hosted models (see more details installation from the documentation). Use OpenRouter when you want larger hosted models and model selection directly from Weightslab UI.
Cloud OpenRouter
SDK Configuration
You can either preconfigure OpenRouter in agent_config.yaml / .env, or initialize it interactively from Weightslab UI.
Example static configuration:
agent:
provider: openrouter
openrouter_model: meta-llama/llama-3.3-70b-instruct
fallback_to_local: false
# openrouter_api_key: ${OPENROUTER_API_KEY}
Environment variable:
export OPENROUTER_API_KEY=your_key_here
Interactive setup from Weightslab UI
OpenRouter models can be initialized and set directly from the UI:
- Click in the agent bar or double-click to expand the agent window.
- Type
/init. - Choose either:
AEnter your OpenRouter API key manuallyBUse the OpenRouter OAuth flow
- Select a model from the fetched list, then confirm.
The default OpenRouter model, as recommended by Graybx, is meta-llama/llama-3.3-70b-instruct.
Agent Commands in Weightslab UI
The agent input supports these commands:
/initinitializes the cloud provider flow for OpenRouter/modelopens the model chooser and switches the active OpenRouter model/resetclears the current runtime agent connection and status
The agent history also records setup and model-change events as log-style entries, separate from normal agent responses.
Typical Usage Flow
- Start your WeightsLab backend (e.g., "main.py").
- Start Weightslab UI.
- If you use Ollama, query the agent directly.
- If you use OpenRouter and the agent is not configured yet, type
/init. - Ask natural-language data operations such as sorting, filtering, slicing, and inspection requests. You can also ask questions about the data.
- Use
/modelto try another cloud model without re-entering the key. - Use
/resetif you want to clear the current connection and start over.
Documentation (API + SDK)
Community
Graybx is building a wonderful community of AI researchers and engineers. Are you interested in joining our project? Contact us at hello [at] graybx [dot] com
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file weightslab-1.1.8.tar.gz.
File metadata
- Download URL: weightslab-1.1.8.tar.gz
- Upload date:
- Size: 79.9 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.15
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
644dad2e12d2d262c73f0a859e05936f14c783f6789b1545f55f134ca1519fed
|
|
| MD5 |
dd570aa902ef5a66797226e33a1576d3
|
|
| BLAKE2b-256 |
5163dca47ec097783db32708f5506e99a19e21ceb92fe00ce10855feb31bf913
|
File details
Details for the file weightslab-1.1.8-py3-none-any.whl.
File metadata
- Download URL: weightslab-1.1.8-py3-none-any.whl
- Upload date:
- Size: 79.8 MB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.11.15
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3d4d0abdbcaca81e21516526be422133b9f80062299b27174cd56e1b70f12880
|
|
| MD5 |
de99f9cf9b952f7c1efe312b8cdab464
|
|
| BLAKE2b-256 |
c8545d8b7bf155982ba723bdbcb24dd6582aace08480daa2a545a16f5e9e5d02
|