hipequivariance-ops-torch
Zero-code-change drop-in for NVIDIA's cuequivariance_ops_torch kernels, backed
by Triton, with first-class support for AMD ROCm GPUs.
This is an optional convenience package. The real compute — and the
recommended integration path — lives in the
geometric-nn-ops-torch
package. We recommend a direct dependency on that API instead where possible.
What it does
hipequivariance-ops-torch installs a Python package that implements the
cuequivariance_ops_torch API under the same module name and provides the
symbols cuequivariance_torch imports:
triangle_attention— routed togeometric-nn-opstriangle_multiplicative_update— routed togeometric-nn-opsattention_pair_bias— routed togeometric-nn-opsTriMulPrecisionCUEQ_TRIATTN_FALLBACK_THRESHOLD(deep import fromcuequivariance_ops_torch.triangle_attention)CUEQ_TRIMUL_FALLBACK_THRESHOLD(deep import fromcuequivariance_ops_torch.triangle_multiplicative_update)CUEQ_ATTENTION_PAIR_BIAS_FALLBACK_THRESHOLD(deep import fromcuequivariance_ops_torch.attention_pair_bias_torch)
Unmodified code calling e.g.
from cuequivariance_torch.primitives.triangle import triangle_attention then
runs on AMD GPUs with no source changes. The shim attempts to be zero-cost but
may incur a performance penalty.
Precision
The underlying ops take their fp32 matmul precision from
torch.backends.cuda.matmul.fp32_precision and have no per-call override. The
ops sometimes make use of torch operations which can only use the unscoped torch
global. This conflicts with the cuequivariance
triangle_multiplicative_update's precision argument, which presents an API
indicating that the user can select their desired precision. cuequivariance does
not consistently honor this API, however. Rather than inconsistent behavior, the
shim checks the precision setting for compatibility with the torch global:
- requesting more precision than the torch setting (e.g.
precision="ieee"when the torch global is "tf32") raises, as the required precision cannot be satisfied, creating a correctness issue. - requesting less (e.g.
precision="tf32"when the torch global is "ieee") warns, as falling back to full precision is a performance issue but not a correctness one.
Install
Installing the shim is an optional step separate from the main package, which
does not depend on it. The shim raises at import if a
cuequivariance-ops-torch-* wheel is detected as installed, and warns if the
installed cuequivariance-torch differs from the version it was designed for.
Install PyTorch for your platform first, following the PyTorch instructions. Otherwise pip installs the default PyTorch build from PyPI, which on Linux targets NVIDIA CUDA rather than AMD ROCm.
pip install hipequivariance-ops-torch # this shim, pulls in the kernels package as a dep
pip install "cuequivariance==0.9.1" "cuequivariance-torch==0.9.1" # NVIDIA's frontend Python
# do NOT install cuequivariance-ops-torch-cu12 / -cu13
For an editable install from source instead:
git clone https://github.com/AMDResearch/geometric-nn-ops.git
cd geometric-nn-ops/
pip install -e . # the kernels
pip install -e hipequivariance_ops_torch # this shim
Status
| Op | Forward | Backward |
|---|---|---|
triangle_attention |
yes | yes |
triangle_multiplicative_update |
yes | yes (torch fallback; native Triton bwd pending) |
attention_pair_bias |
yes (pure torch; no Triton kernel yet) | yes (pure torch; no Triton kernel yet) |
License
Apache-2.0. Copyright Advanced Micro Devices, Inc. See LICENSE.
Metadata
Release files for hipequivariance-ops-torch 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 | Actions |
|---|---|---|---|---|
| hipequivariance_ops_torch-0.1.0.tar.gz | 13.7 kB | With provenance | Details for hipequivariance_ops_torch-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hipequivariance_ops_torch-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for hipequivariance_ops_torch-0.1.0-py3-none-any.whl |
Total release size: 27.3 kB
Release files / hipequivariance_ops_torch-0.1.0.tar.gz
| Download URL | hipequivariance_ops_torch-0.1.0.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0d9cef40e21228af826f8d0729e55d16073327d3dd44006eadedf16eddadc9f
|
|
BLAKE2b-256 checksum How to use checksums |
a135ab5995e6940934741c62c3d5d5ae1e1a1a167988e794335ae7db5d25048d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 6, 2026.
Transparency logRelease files / hipequivariance_ops_torch-0.1.0-py3-none-any.whl
| Download URL | hipequivariance_ops_torch-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e6bf21c63e5786bec959670c11d6e2f89f6f4d62c9c78969233d2d7c8038401
|
|
BLAKE2b-256 checksum How to use checksums |
cdbe6f0d81e99597d2260affa1c4766e78a27e48d090938c9a79aa3aabe3b0be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 6, 2026.
Transparency logSecurity for hipequivariance-ops-torch 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
Both files in this release have been uploaded with provenance metadata.
Attestation for hipequivariance_ops_torch-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 Nov 6, 2026.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.