Accelrod
Installation
pip install -U accelrod
[all] includes nbformat to visualize the result in notebook
pip install -U accelrod[all]
Example
import torch
from accelrod.benchmark import benchrun, plot_result
# without max_dimension, the matrix size will be determined based on available VRAM
result = benchrun(
algorithm="GEMM",
device="auto",
as_dataframe="pandas",
params={
# "max_dimension": 2048,
"dtype": [torch.float32, torch.float16, torch.bfloat16],
},
)
# plot in notebook
import plotly.offline as pyo
pyo.init_notebook_mode()
plot_result(result)
Developer guide
Setup working env / dependencies
Sync the project's dependencies with the environment.
uv sync
lock dependencies declared in a pyproject.toml
uv pip compile pyproject.toml -o requirements.txt
Add dev dependencies
uv add --dev ruff pytest
Editable Installs
uv pip install -e .[all,dev]
Test package with local build
uv pip install dist/accelrod-0.1.0-py3-none-any.whl uv run --with accelrod --no-project --refresh-package accelrod -- python -c "import accelrod"
Metadata
Release files for accelrod 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| accelrod-0.1.0.tar.gz | 9.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| accelrod-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / accelrod-0.1.0.tar.gz
| Download URL | accelrod-0.1.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a76f5904b300ab52518c51ae50c7e5a49221be2c6e9c7ace5a504f0f0bdbd63
|
|
BLAKE2b-256 checksum How to use checksums |
6c0da9fcb678978eacad94791c0368c04e7a6c7c2fa72350458a5d2b6e1627c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 12, 2025.
Transparency logRelease files / accelrod-0.1.0-py3-none-any.whl
| Download URL | accelrod-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33b1615db65a8b8ec349b8a86a92de448b81c9d5e5fbd9873023c74d9b3022fb
|
|
BLAKE2b-256 checksum How to use checksums |
47b4bc9ecdd55459cf8d597f50611ff7275984ead488147536d6c531cc8befef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 12, 2025.
Transparency logSecurity for accelrod 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for accelrod-0.1.0.tar.gz
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 Feb 12, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.