ℹ️ About

Drop a star to support Aim ⭐	Join Aim discord community
🔮 Aim 4.0 - COMING SOON!!

An easy-to-use & supercharged open-source AI metadata tracker.

Aim logs all your AI metadata, enables a UI to observe/compare them, and an SDK to query them programmatically.

Learn more:
Experiment tracking with Aim
AI agents tracing with Aim

_{SEAMLESSLY INTEGRATES WITH:}

_{TRUSTED BY ML TEAMS FROM:}

AimStack offers enterprise support that's beyond core Aim. Contact via [email protected] e-mail.

About • Demos • Ecosystem • Quick Start • Examples • Documentation • Community • Blog • COMING SOON!!

ℹ️ About

Aim is an open-source, self-hosted AI Metadata tracking tool designed to handle 100,000s of tracked metadata sequences.

Aim provides a performant and beautiful UI for exploring and comparing metadata such as training runs or agents executions. Additionally, its SDK enables programmatic access to tracked metadata — perfect for automations and Jupyter Notebook analysis.

Aim's mission is to democratize AI dev tools 🎯

AI systems and agents tracing with Aim

Log Inputs, Outputs and Actions of Executions 🤖	Visualize & Compare Executions Steps via UI 🔍
Track all the inputs, outputs of LLMs and tools Capture terminal output of executions Get notified on executions progress and finish	Deep dive into single execution steps Compare executions side-by-side View previous exectutions terminal outputs

Experiment tracking with Aim

Log Metadata Across Your ML Pipeline 💾	Visualize & Compare Metadata via UI 📊
ML experiments and any metadata tracking Integration with popular ML frameworks Easy migration from other experiment trackers	Metadata visualization via Aim Explorers Grouping and aggregation Querying using Python expressions
Run ML Trainings Effectively ⚡	Organize Your Experiments 🗂️
System info and resource usage tracking Real-time alerting on training progress Logging and configurable notifications	Detailed run information for easy debugging Centralized dashboard for holistic view Runs grouping with tags and experiments

🔮 Aim 4.0

Aim 4.0 is coming soon!!

A major iteration of Aim as the ultimate metadata library to track all your interactions with your models - including experiments, prompts etc.

Remote first
Scalable
Capable of storing and querying 100,000s of metadata sequences
Custom UI dashboards and reports

The Aim experiment tracker is not just one-off experiment tracker. It's built on top of the metadata library that Aim is. Now you can also do prompt engineering on Aim. Stay tuned for more...

🎬 Demos

Check out live Aim demos NOW to see it in action.

Machine translation experiments	lightweight-GAN experiments

Training logs of a neural translation model(from WMT'19 competition).	Training logs of 'lightweight' GAN, proposed in ICLR 2021.

FastSpeech 2 experiments	Simple MNIST

Training logs of Microsoft's "FastSpeech 2: Fast and High-Quality End-to-End Text to Speech".	Simple MNIST training logs.

🌍 Ecosystem

Aim is not just an experiment tracker. It's a groundwork for an ecosystem. Check out the two most famous Aim-based tools.

aimlflow	Aim-spaCy

Exploring MLflow experiments with a powerful UI	an Aim-based spaCy experiment tracker

🏁 Quick start

Follow the steps below to get started with Aim.

1. Install Aim on your training environment

pip3 install aim

2. Integrate Aim with your code

from aim import Run

# Initialize a new run
run = Run()

# Log run parameters
run["hparams"] = {
    "learning_rate": 0.001,
    "batch_size": 32,
}

# Log metrics
for i in range(10):
    run.track(i, name='loss', step=i, context={ "subset":"train" })
    run.track(i, name='acc', step=i, context={ "subset":"train" })

See the full list of supported trackable objects(e.g. images, text, etc) here.

3. Run the training as usual and start Aim UI

aim up

Learn more

Migrate from other tools

Aim has built-in converters to easily migrate logs from other tools. These migrations cover the most common usage scenarios. In case of custom and complex scenarios you can use Aim SDK to implement your own conversion script.

Integrate Aim into an existing project

Aim easily integrates with a wide range of ML frameworks, providing built-in callbacks for most of them.

Query runs programmatically via SDK

Aim Python SDK empowers you to query and access any piece of tracked metadata with ease.

from aim import Repo

my_repo = Repo('/path/to/aim/repo')

query = "metric.name == 'loss'" # Example query

# Get collection of metrics
for run_metrics_collection in my_repo.query_metrics(query).iter_runs():
    for metric in run_metrics_collection:
        # Get run params
        params = metric.run[...]
        # Get metric values
        steps, metric_values = metric.values.sparse_numpy()

Set up a centralized tracking server

Aim remote tracking server allows running experiments in a multi-host environment and collect tracked data in a centralized location.

See the docs on how to set up the remote server.

Deploy Aim on kubernetes

The official Aim docker image: https://hub.docker.com/r/aimstack/aim
A guide on how to deploy Aim on kubernetes: https://aimstack.readthedocs.io/en/latest/using/k8s_deployment.html

Read the full documentation on aimstack.readthedocs.io 📖

🆚 Comparisons to familiar tools

TensorBoard vs Aim

Training run comparison

Order of magnitude faster training run comparison with Aim

The tracked params are first class citizens at Aim. You can search, group, aggregate via params - deeply explore all the tracked data (metrics, params, images) on the UI.
With tensorboard the users are forced to record those parameters in the training run name to be able to search and compare. This causes a super-tedius comparison experience and usability issues on the UI when there are many experiments and params. TensorBoard doesn't have features to group, aggregate the metrics.

Scalability

Aim is built to handle 1000s of training runs - both on the backend and on the UI.
TensorBoard becomes really slow and hard to use when a few hundred training runs are queried / compared.

Beloved TB visualizations to be added on Aim

Embedding projector.
Neural network visualization.

MLflow vs Aim

MLFlow is an end-to-end ML Lifecycle tool. Aim is focused on training tracking. The main differences of Aim and MLflow are around the UI scalability and run comparison features.

Aim and MLflow are a perfect match - check out the aimlflow - the tool that enables Aim superpowers on MLflow.

Run comparison

Aim treats tracked parameters as first-class citizens. Users can query runs, metrics, images, and filter using the params.
MLFlow does have a search by tracked config, but there are no grouping, aggregation, subplotting by hyperparams and other comparison features available.

UI Scalability

Aim UI can handle several thousands of metrics at the same time smoothly with 1000s of steps. It may get shaky when you explore 1000s of metrics with 10000s of steps each. But we are constantly optimizing!
MLflow UI becomes slow to use when there are a few hundreds of runs.

Weights and Biases vs Aim

Hosted vs self-hosted

Weights and Biases is a hosted closed-source MLOps platform.
Aim is self-hosted, free, and open-source experiment tracking tool.

🛣️ Roadmap

Detailed milestones

The Aim product roadmap ❇️

The Backlog contains the issues we are going to choose from and prioritize weekly
The issues are mainly prioritized by the highly-requested features

High-level roadmap

The high-level features we are going to work on the next few months:

In progress

Aim SDK low-level interface
Dashboards – customizable layouts with embedded explorers
Ergonomic UI kit
Text Explorer

Next-up

Aim UI

Runs management
- Runs explorer – query and visualize runs data(images, audio, distributions, ...) in a central dashboard
Explorers
- Distributions Explorer

SDK and Storage

Scalability
- Smooth UI and SDK experience with over 10.000 runs
Runs management
- CLI commands
  - Reporting - runs summary and run details in a CLI compatible format
  - Manipulations – copy, move, delete runs, params and sequences
Cloud storage support – store runs blob(e.g. images) data on the cloud
Artifact storage – store files, model checkpoints, and beyond

Integrations

ML Frameworks:
- Shortlist: scikit-learn
Resource management tools
- Shortlist: Kubeflow, Slurm
Workflow orchestration tools

Done

👥 Community

Aim README badge

Add Aim badge to your README, if you've enjoyed using Aim in your work:

[![Aim](https://img.shields.io/badge/powered%20by-Aim-%231473E6)](https://github.com/aimhubio/aim)

Cite Aim in your papers

In case you've found Aim helpful in your research journey, we'd be thrilled if you could acknowledge Aim's contribution:

@software{Arakelyan_Aim_2020,
  author = {Arakelyan, Gor and Soghomonyan, Gevorg and {The Aim team}},
  doi = {10.5281/zenodo.6536395},
  license = {Apache-2.0},
  month = {6},
  title = {{Aim}},
  url = {https://github.com/aimhubio/aim},
  version = {3.9.3},
  year = {2020}
}

Contributing to Aim

Considering contibuting to Aim? To get started, please take a moment to read the CONTRIBUTING.md guide.

Join Aim contributors by submitting your first pull request. Happy coding! 😊

Made with contrib.rocks.

Name		Name	Last commit message	Last commit date
Latest commit History 2,301 Commits
.github		.github
docs		docs
pkgs/aimstack		pkgs/aimstack
src		src
tests		tests
.gitattributes		.gitattributes
.gitignore		.gitignore
.readthedocs.yaml		.readthedocs.yaml
CHANGELOG.md		CHANGELOG.md
CITATION.cff		CITATION.cff
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
MANIFEST.in		MANIFEST.in
README.md		README.md
pyproject.toml		pyproject.toml
setup.py		setup.py

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

An easy-to-use & supercharged open-source AI metadata tracker.

About • Demos • Ecosystem • Quick Start • Examples • Documentation • Community • Blog • COMING SOON!!

ℹ️ About

AI systems and agents tracing with Aim

Experiment tracking with Aim

🔮 Aim 4.0

🎬 Demos

🌍 Ecosystem

🏁 Quick start

1. Install Aim on your training environment

2. Integrate Aim with your code

3. Run the training as usual and start Aim UI

Learn more

🆚 Comparisons to familiar tools

🛣️ Roadmap

Detailed milestones

High-level roadmap

👥 Community

Aim README badge

Cite Aim in your papers

Contributing to Aim

More questions?

About

Releases

Packages

Languages

License

YodaEmbedding/aim

Folders and files

Latest commit

History

Repository files navigation

An easy-to-use & supercharged open-source AI metadata tracker.

About • Demos • Ecosystem • Quick Start • Examples • Documentation • Community • Blog • COMING SOON!!

ℹ️ About

AI systems and agents tracing with Aim

Experiment tracking with Aim

🔮 Aim 4.0

🎬 Demos

🌍 Ecosystem

🏁 Quick start

1. Install Aim on your training environment

2. Integrate Aim with your code

3. Run the training as usual and start Aim UI

Learn more

🆚 Comparisons to familiar tools

🛣️ Roadmap

Detailed milestones

High-level roadmap

👥 Community

Aim README badge

Cite Aim in your papers

Contributing to Aim

More questions?

About

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages