A Python library orchestrating data during the full life cycle of Machine Learning pipelines.
Overview | Principles | Features | Installation | Contribute
Goldener is an open-source Python library (Apache 2 licence) designed to manage the orchestration of data during the full life cycle of Machine Learning (ML) pipelines.
In the artificial intelligence (AI) era, the data is the new gold. Being able to collect it is already something but creating value from it is the real challenge. Goldener is designed to help to make the most of the available data. It provides tools to orchestrate data during the full life cycle of Machine Learning pipelines, from the training phase to the monitoring phase.
Goldener makes the right data available at the right time, allowing to optimize the performance of any ML pipelines while minimizing the costs (time, performance, computing resources).
When it's time to annotate data, Goldener finds the most representative subset to annotate. During annotation, it can help to define annotation guidelines by spotting specific cases or as well run annotation quality checks. Once enough data is annotated, Goldener can split it in multiple sets (train, validation, test) ensuring the reproduction of the task variability. During the training phase, Goldener can efficiently balance the data to optimize the training time and the model performance. Finally, when the model is deployed, Goldener can find the most informative data to monitor the model performance and detect any drift in the data distribution.
Goldener is designed to process large datasets efficiently. It is built on the assumption that every AI lifecycle is most of the time iterative and incremental. Its design principles are:
- Progressive batch processing: Each task can be stopped and restarted on demand (or failure). Already computed results are not recomputed.
- Multipurposes embeddings: The same embeddings are used for the different for different tasks (selection, splitting, monitoring, etc.).
- Modality-agnostic: The same tool is actionable for any data modalities (text, image, video, tabular, etc.) and even for multimodality data.
This is not yet applied, but for the next iterations, the following principles will be as well followed:
- Distributed first: Any task can be distributed across multiple machines.
- On demand access to pipelines: All processing pipelines are serializable. They are stored and available whenever a new request is made.
Goldener can find the most representative data subset to annotate. It can extract and store semantic knowledge of the data from embeddings extracted with pre-trained models. Then, it leverages this knowledge to find the most representative subset of data to annotate. This subset of data can be annotated in order to train or monitor a model.
from goldener import (
GoldSelector,
GoldDescriptor,
GoldTorchEmbeddingTool,
GoldTorchEmbeddingToolConfig,
GoldTensorVectorizationTool,
)
gd = GoldDescriptor(
table_path="my_table_for_description",
embedder=GoldTorchEmbeddingTool(
GoldTorchEmbeddingToolConfig(
model=my_model,
layers=my_layers,
)
),
vectorizer=GoldTensorVectorizationTool()
)
gs = GoldSelector(
table_path="my_table_for_selection", selection_key="selection"
)
description = gd.describe_in_table(dataset)
selection_table = gs.select_in_table(description, 100, "to_annotate")
selected = GoldSelector.get_selection_indices(selection_table, "to_annotate", "selection")Goldener can split data between the train and validation sets ensuring that the training set is containing most of the different situations for the tasks. From a description of the samples (embeddings), the most different/unique elements are kept for the training set while the least informative ones are kept for the validation set.
from goldener import (
GoldSet,
GoldSplitter,
GoldDescriptor,
GoldSelector,
)
gd = GoldDescriptor(...) # reuse the descriptor used for smart sampling
gselector = GoldSelector(...)
gs = GoldSplitter(
sets=[GoldSet("train", 0.7), GoldSet("val", 0.3)],
descriptor=gd,
selector=gselector,
)
split_table = gs.split_in_table(dataset)
splits = gs.get_split_indices(
split_table, selection_key="selected", idx_key="idx"
)
train_indices = splits["train"]
val_indices = splits["val"]Among the data, there are often multiple "modes" (e.g. different types of images, different types of text, etc.). Goldener can clusterize the data to find these different modes. Then, the different clusters can be leveraged to define annotation guidelines for each cluster.
from goldener import (
GoldClusterizer,
GoldSKLearnClusteringTool,
GoldDescriptor,
GoldTorchEmbeddingTool,
GoldTorchEmbeddingToolConfig,
GoldTensorVectorizationTool,
)
from sklearn.cluster import KMeans
gd = GoldDescriptor(...) # reuse the descriptor used for smart sampling
gcluster = GoldClusterizer(
table_path="my_table_for_clusterization",
clustering_tool=GoldSKLearnClusteringTool(KMeans(n_clusters=10)),
cluster_key="cluster",
)
description = gd.describe_in_table(dataset)
clustered_table = gcluster.clusterize_in_table(description)
for cluster_id in range(10):
cluster_indices = get_cluster_indices(clustered_table, "cluster", cluster_id)
# sample few samples and use them to define annotation guidelines for this clusterDepending on the dataset (size, data type, task), the computation tackled by Goldener can be quite resource intensive and time consuming. The dimensionality reduction aims to reduce the memory footprint and increase the speed for the downstream task. It can be quite useful to adapt the computation to the hardware constraints or access results in time constrained situation.
import torch
from sklearn.decomposition import PCA
from goldener import GoldSKLearnReductionTool
# 50 embeddings of dimension 16
x = torch.randn(50, 16)
reducer = GoldSKLearnReductionTool(PCA(n_components=2))
x_reduced = reducer.fit_transform(x) # shape: (50, 2)When training with randomly sampled batches, the content distribution within each batch can vary a lot — some batches may end up overrepresenting certain types of data while barely including others. This imbalance can hurt how well a model learns to recognize the underrepresented cases.
Goldener proposes a batch sampler grouping data into groups of similar content, and then drawing samples so each batch is spread across clusters as evenly as possible.
from goldener.organize import GoldClusterizedBatchSampler
from goldener import GoldClusterizer, GoldDescriptor, GoldSKLearnClusteringTool
from sklearn.cluster import KMeans
gd = GoldDescriptor(...) # reuse the descriptor used for smart sampling
gc = GoldClusterizer(...) # reuse the clusterizer used for annotation guidelines
batch_sampler = GoldClusterizedBatchSampler(
dataset=my_dataset,
batch_size=32,
clusterizer=gc,
descriptor=gd,
n_clusters=10,
)Installing Goldener is as simple as running the following command:
pip install goldenerWe welcome contributions to Goldener! Here's how you can help:
- Fork the repository
- Clone your fork
- Install the dependencies
- Create your branch and make your proposals
- Push to your fork and create a pull request
- The PR will be automatically tested by GitHub Actions
- A maintainer will review your PR and may request changes
- Once approved, your PR will be merged
To set up the development environment:
- Install
uvif you haven't already:
curl -LsSf https://astral.sh/uv/install.sh | sh- Create and activate a virtual environment (optional but recommended):
uv venv
source .venv/bin/activate # On Unix/macOS- Install development dependencies:
uv sync --all-extras # Install all dependencies including development dependencies- Run tests:
uv run pytest .- Run type checking with mypy:
uv run mypy .- Run linting with ruff:
# Run all checks
uv run ruff check .
# Format code
uv run ruff format .- Set up pre-commit hooks:
# Install git hooks
uv run pre-commit install
# Run pre-commit on all files
uv run pre-commit run --all-filesThe pre-commit hooks will automatically run:
- mypy for type checking
- ruff for linting and formatting
- pytest for tests
whenever you make a commit.
To release a new version of the goldener package:
- Create a new branch for the release:
git checkout -b release-vX.Y.Z - Update the version
vX.Y.Zinpyproject.toml - Run
uv syncto update the lock file with the new version - Commit the changes with a message like
release vX.Y.Z - Merge the branch into
main - Trigger a new release on GitHub with the tag
vX.Y.Z