aimstack/aim repository overview

⁠Quick reference

• Maintained by: aimstack⁠
• Where to get help: Aim slack community⁠

⁠Supported tags and respective Dockerfile links

• latest⁠

⁠Quick reference (Cont.)

• Aim website⁠
• Aim on GitHub⁠
• Aim docs⁠

⁠An easy-to-use & supercharged open-source experiment tracker

Aim logs your training runs, enables a beautiful UI to compare them and an API to query them programmatically.

⁠About Aim

Aim is an open-source, self-hosted ML experiment tracking tool. It's good at tracking lots (1000s) of training runs and it allows you to compare them with a performant and beautiful UI.

You can use not only the great Aim UI but also its SDK to query your runs' metadata programmatically. That's especially useful for automations and additional analysis on a Jupyter Notebook.

Aim's mission is to democratize AI dev tools.

⁠Why use Aim?

An easy-to-use & supercharged open-source experiment tracker. Aim logs your training runs, enables a beautiful UI to compare them and an API to query them programmatically.Why use Aim?

• Compare runs easily to build models faster. Group and aggregate 100s of metrics. Analyze and learn correlations. Query with easy pythonic search.
• Deep dive into details of each run for easy debugging. Explore hparams, metrics, images, distributions, audio, text, etc. Track plotly and matplotlib plots. Analyze system resource usage.
• Have all relevant information centralized for easy governance. Centralized dashboard to view all your runs. Use SDK to query/access tracked runs. You own your data - Aim is open source and self hosted.

⁠How to use this image

⁠Running Aim UI in a Docker container

In order to spin a Docker container with Aim UI run:

docker run -d -p 43800:43800 -v <AIM_REPO_PATH>:/opt/aim aimstack/aim

Access Aim UI from http://localhost:43800/⁠

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.