TIREx Tracker
The TIREx tracker is a command line tool and API to automatically track resource usage, hardware specifications, and other metadata when running information retrieval experiments. It can be used easily in Python applications. For more information, refer to the project's readme.
Python API
The Python API can be installed via Pip from PyPI. After installing the package, you can use the TIREx tracker in your Python.
Pip Dependency
First, install the TIREx tracker Python package from PyPI:
pip install tirex-tracker
Python Usage
Now, you can track the hardware metrics and metadata of your Python code by using the context manager:
from tirex_tracker import tracking
with tracking() as results:
# Do something...
print(results)
Alternatively, you can track the hardware metrics and metadata of a Python function by using the function decorator:
from tirex_tracker import tracked
@tracked
def do_something():
# Do something...
do_something()
print(do_something.results)
If you cannot use either the context manager or the function decorator from above, you can manually start and stop the tracking:
from tirex_tracker import start_tracking, stop_tracking
handle = start_tracking()
try:
# Do something...
finally:
results = stop_tracking(handle)
print(results)
Citation
If you find our work useful and reference or use it in a paper, please cite us.
@inproceedings{tirextracker2025,
author = {Hagen, Tim and Fr{\"o}be, Maik and Merker, Jan Heinrich and Scells, Harrisen and Hagen, Matthias and Potthast, Martin},
booktitle = {48th International ACM SIGIR Conference on Research and Development in Information Retrieval (SIGIR 2025)},
month = jul,
publisher = {ACM},
title = {{TIREx Tracker: The Information Retrieval Experiment Tracker}},
year = {2025}
}
You can also use the CITATION.cff to generate a citation in other formats.
License
The TIREx tracker code is licensed under the MIT License. If you use the TIREx tracker in your experiments, we would appreciate you citing our paper.
Abstract
The reproducibility and transparency of retrieval experiments heavily depends on properly provided information on the experimental setup and conditions. But as manually curating such experiment metadata can be tedious, error-prone, and inconsistent, metadata should be systematically collected in an automatic way—similar to the collection of Python and git-specific settings in the
ir_metadatareference implementation. To enable a platform-independent automatic metadata collection following their_metadataspecification, we introduce the TIREx tracker: a tool realized via a lightweight C binary, pre-compiled with all dependencies for all major platforms to track hardware configurations, usage of power/CPUs/RAM/GPUs, and experiment/system versions. The TIREx tracker seamlessly integrates into Python, Java, or C/C++ workflows and can be easily incorporated in run submissions of shared tasks, which we showcase for the TIRA/TIREx platform.
Metadata
Release files for tirex-tracker 0.2.24
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tirex_tracker-0.2.24.tar.gz | 5.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tirex_tracker-0.2.24-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.2 MB
Release files / tirex_tracker-0.2.24.tar.gz
| Download URL | tirex_tracker-0.2.24.tar.gz |
|---|---|
| Size | 5.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ea1c013e50f86fb91711857e93b8847b389f3300b8788c522580a3047188ca5
|
|
BLAKE2b-256 checksum How to use checksums |
f5851024c0631e74fb411ba9cd765071994ea40479fefb72fb5a51580ddde907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / tirex_tracker-0.2.24-py3-none-any.whl
| Download URL | tirex_tracker-0.2.24-py3-none-any.whl |
|---|---|
| Size | 5.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb72cf4d71093e8797f9d2f5da740665bf3d2ebfcd175caf67f0ca8861f2bc1b
|
|
BLAKE2b-256 checksum How to use checksums |
e56d803dc173e5a8a0efbd70b830bee62cd17526dfb0a2f866b3e72b5a43b991
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency log