cuequivariance
Skill3.9k starsChanged 44 days agoApache-2.0View on GitHub
Use when defining cuEquivariance groups and irreps, building equivariant tensor products, or validating segmented polynomials with NumPy.
2 other projects use a version of this.
Trending
Steady talk.about the whole repository
Most recently taken up by
- NVIDIA/cuEquivarianceword for word, first seen Nov 8, 2026
- patoangolano/bio-stacktheir own version, first seen Oct 15, 2026
Who's talking about NVIDIA/skills
- hillstreet-ph/open-connect“feat: add open-nvidia-kit to the marketplace”GitHub · Oct 31, 2026 · 2 reactions
- NVIDIA-AI-Blueprints/video-search-and-summarization“docs(skills): deprecate vss-deploy-profile in favour of vss-build-vis…”GitHub · Sep 9, 2026 · 1 reactions
- isaac-sim/IsaacLab“Onboard IsaacLab skills for NVCARPS compatibility”GitHub · Aug 14, 2026 · 1 reactions
- NVIDIA/cudf-spark“Fix NVSkills workflow permissions [skip ci]”GitHub · Aug 14, 2026 · 1 reactions
- NVIDIA/cudf-spark“NVSkills Request CI Workflow [skip ci]”GitHub · Jul 2, 2026 · 1 reactions
The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 17
Talked about on GitHub (17 times).
On GitHub · 17
- Oct 31, 2026feat: add open-nvidia-kit to the marketplace — hillstreet-ph/open-connect2 reactions · 5 comments
- Sep 9, 2026docs(skills): deprecate vss-deploy-profile in favour of vss-build-vis… — NVIDIA-AI-Blueprints/video-search-and-summarization1 reaction · 3 comments
- Aug 14, 2026Onboard IsaacLab skills for NVCARPS compatibility — isaac-sim/IsaacLab1 reaction · 4 comments
- Aug 14, 2026Fix NVSkills workflow permissions [skip ci] — NVIDIA/cudf-spark1 reaction · 2 comments
- Jul 2, 2026NVSkills Request CI Workflow [skip ci] — NVIDIA/cudf-spark1 reaction · 2 comments
12 more on GitHub
- May 22, 2026Publish Skill Card Generator as an installable Agent Skill — NVIDIA/Trustworthy-AI1 reaction · 3 comments
- May 22, 2026Provide official CCCL SKILLs — NVIDIA/cccl1 reaction · 2 comments
- May 20, 2026Document that the dali-dynamic-mode skill exists — NVIDIA/DALI1 reaction · 15 comments
- Oct 31, 2026[challenge:AMD-AI-League] Delphi-select the project and prepare AMD/NVIDIA evidence-backed submission — timerloggedout-spec/termux-monorepo0 reactions · 3 comments
- Oct 27, 2026[intake] GPU DataFrame acceleration — NVIDIA accelerated-computing-cudf — gaia-research/gaia-skill-tree0 reactions · 1 comment
- Oct 23, 2026Y26-306 - AI: Investigate NVidia skills and SkillsEvaluation for Skill security checks — sanger/General-Backlog-Items0 reactions
- Oct 16, 2026[Candidate] nvidia/skills - large collection (412 SKILL.md files) — ProSkillsMD/proskills0 reactions · 1 comment
- Sep 25, 2026cualign-prototype: 진단·처방 금지 정책을 NVIDIA 스킬 nemotron-policy-generator 로 만들어 content-safety 레일에 적용 — dalsoop/nvidia-hackaton-2026-one0 reactions
- Aug 27, 2026All 155 NVIDIA/skills links are 404 — repo was restructured — VoltAgent/awesome-agent-skills0 reactions · 4 comments
- Jun 10, 2026Follow the process to sign the skills and sync to the [nvidia/skills](https://github.com/nvidia/skills) repo — NVIDIA/cudf-spark0 reactions
- Jun 7, 2026documentation for LLMs — buckaroo-data/buckaroo0 reactions
- Jun 4, 2026RB.006: It breaks when the nested rigid bodies are replaced — NVIDIA/simready-foundation0 reactions · 3 comments
Other versions2 projects use a version of this.
Word for word · 1
- NVIDIA/cuEquivariance★ 447100% same
Edited · 0
None found.
Wrote their own version · 1
- patoangolano/bio-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository438 other files it gives its agents.
- skills/dicom-metadata-extract/AGENTS.mdAGENTS.md
- nvidia-skill-finderSkill
- accelerated-computing-cudfSkill
- ambient-healthcare-agent-with-nemotron-voice-agentSkill
- amc-run-rtsp-calibrationSkill
- amc-run-sample-calibrationSkill
- amc-run-video-calibrationSkill
- amc-setup-calibration-stackSkill
- boltz2-nimSkill
- codonfm-embedSkill
- codonfm-finetuneSkill
- codonfm-scoreSkill
- codonfm-setupSkill
- complexa-evaluate-pdbsSkill
- complexa-sweepSkill
- complexa-targetSkill
- cuequivariance-jaxSkill
- cuequivariance-torchSkill
- diffdock-nimSkill
- drug-discovery-pipelineSkill
- evo2-nimSkill
- genmol-nimSkill
- genomics-workflow-accelerationSkill
- kermt-add-cmim-pretrainSkill
- kermt-continue-pretrainSkill
- kermt-embedSkill
- kermt-finetuneSkill
- kermt-inferSkill
- kermt-monitorSkill
- kermt-pretrain-scratchSkill
- kermt-setupSkill
- molmim-nimSkill
- msa-search-nimSkill
- msa-structure-prediction-pipelineSkill
- nvmolkit-usageSkill
- openfold2-nimSkill
- openfold3-nimSkill
- parabricksSkill
- proteinmpnn-nimSkill
- rfd4-proteina-nimSkill
- rfdiffusion-nimSkill
- cdf-anomalygenSkill
- cdf-augmentationSkill
- cdf-auto-labelingSkill
- cdf-autonomous-vehicle-dataset-generationSkill
- cdf-curation-and-retrievalSkill
- cdf-defect-image-generationSkill
- cdf-event-video-generationSkill
- cdf-image-attribute-augmentationSkill
- cdf-orchestration-preflightSkill
- cdf-orchestration-setupSkill
- cdf-orchestration-write-dagSkill
- cdf-simulationSkill
- cdf-video-data-augmentationSkill
- compute-sanitizer-diagnose-cuda-bugsSkill
- cudaq-guideSkill
- cudaq-importingSkill
- cudf-query-engine-builderSkill
- cumlSkill
- cuopt-developerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Check the installed version and requested backend.
- Distinctive: line 33
Prefer a built-in descriptor.
- Distinctive: line 231
All descriptors come in two variants:
- Very specific: line 330
Use this helper to split an existing SegmentedPolynomial operand at irrep boundaries.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
cuequivariance: Groups, Irreps, and Segmented Polynomials
Purpose
cuequivariance (imported as cue) provides two core abstractions:
- Group theory:
Irrepsubclasses define irreducible representations of Lie groups (SO3, O3, SU2, or custom).Irrepsmanages collections with multiplicities. - Segmented polynomials:
SegmentedTensorProductdescribes tensor contractions over segments of varying shape, linked byPathobjects carrying Clebsch-Gordan coefficients.SegmentedPolynomialwraps multiple STPs into a polynomial with named inputs/outputs. Two higher-level wrappers attach group representations:EquivariantPolynomial— dense operands withIrrepsAndLayoutmetadataIrDictPolynomial— operands already split by irrep, with per-groupIrrepsmetadata for thedict[Irrep, Array]workflow
Inputs
Required inputs: requested operation, group, input irreps and multiplicities, output irrep types, layout, batch shapes, dtype, and weight ownership. Take explicit user requirements first, then existing project definitions; state defaults for unspecified values. Derive operand sizes and output block order from the descriptor. For custom groups, also establish the selection rules, generators, and Clebsch-Gordan coefficients. Optional inputs include test rotations and a framework backend.
Prerequisites
Use Python 3.10+ with cuequivariance and its NumPy, SciPy, opt_einsum, SymPy, and NetworkX dependencies. Reuse the project's interpreter and lockfile. If setup is needed outside an existing project, the bundled CPU requirements pin the source revision used by these examples; install them with that interpreter's pip. Core NumPy execution requires no GPU stack or API credentials. Check the installed version and API availability before using IrDictPolynomial with an older package.
Instructions
- Check the installed version and requested backend. Install
cuequivariancefor CPU NumPy work; JAX and PyTorch execution use the separatecuequivariance-jaxandcuequivariance-torchskills. Inspect available APIs before using newer features such asIrDictPolynomialin an older environment. - Establish the group, input irreps, multiplicities, layout, and batch shapes before building a descriptor. Preserve the descriptor's actual output block order; a regrouped irrep summary does not reorder its output array.
- Prefer a built-in descriptor. For a custom group, validate parsing, group relations, selection rules, and Clebsch-Gordan covariance on CPU first. Complex mathematical representations do not imply complex CUDA support.
- Execute a small deterministic NumPy example and check shapes and equivariance.
IrDictPolynomialcarries metadata; execute its.polynomialwith operands split according to.input_irrepsand.output_irreps, including weights first when present. - Convert
mul_irandir_mulby transposing the multiplicity and representation axes within each irrep block. A flat reshape alone changes the represented features.
Source paths below are relative to the cuequivariance/ project inside a source checkout. When using this skill separately, inspect the installed package with cue.__file__ or consult https://github.com/NVIDIA/cuEquivariance. The repository is not required for the examples.
Limitations
- Core descriptors and NumPy evaluation do not provide JAX or PyTorch execution kernels; use the corresponding frontend for framework execution and gradients.
- Custom-group mathematics must be checked independently. A valid complex representation does not establish support in a particular CUDA kernel.
IrDictPolynomialdescribes split operands; it does not convert high-level dictionaries into the ordered arrays accepted by its underlying polynomial. Preserve the descriptor's metadata and layout when assembling those arrays.
Troubleshooting
| Symptom | Check and correction |
| Import fails or an API is absent | Check the interpreter, installed version, and module location. Use the project's compatible dependencies or the bundled requirements when setting up a standalone environment. |
| Operand size or output shape is wrong | Compare each array with the descriptor's input/output dimensions; include the weights operand first when present. |
| Values disagree after a layout conversion | Transpose multiplicity and representation axes within each irrep block before flattening; keep output data in the descriptor's block order. |
| Custom-group equivariance fails | Check selection rules, generator relations, and CG covariance on a small NumPy example before changing execution backends. |
Examples
The examples below cover custom groups, descriptors, layouts, and NumPy execution. Some snippets extend variables from the preceding snippet; the final complete example can be run independently.
Defining a custom group
Subclass cue.Irrep (a frozen dataclass) and implement:
from __future__ import annotations
import dataclasses
import re
from typing import Iterator
import numpy as np
import cuequivariance as cue
@dataclasses.dataclass(frozen=True)
class Z2(cue.Irrep):
odd: bool # dataclass field -- required for correct __eq__ and __hash__
# No __init__ needed -- @dataclass(frozen=True) generates it: Z2(odd=True)
@classmethod
def regexp_pattern(cls) -> re.Pattern:
# Pattern whose first group is passed to from_string
return re.compile(r"(odd|even)")
@classmethod
def from_string(cls, string: str) -> Z2:
if string not in ("odd", "even"):
raise ValueError(f"Invalid Z2 irrep: {string!r}")
return cls(odd=string == "odd")
def __repr__(rep: Z2) -> str:
return "odd" if rep.odd else "even"
def __mul__(rep1: Z2, rep2: Z2) -> Iterator[Z2]:
# Selection rule: which irreps appear in the tensor product rep1 x rep2
return [Z2(odd=rep1.odd ^ rep2.odd)]
@classmethod
def clebsch_gordan(cls, rep1: Z2, rep2: Z2, rep3: Z2) -> np.ndarray:
# Shape: (num_paths, rep1.dim, rep2.dim, rep3.dim)
if rep3 in rep1 * rep2:
return np.array([[[[1]]]])
else:
return np.zeros((0, 1, 1, 1))
@property
def dim(rep: Z2) -> int:
return 1
def __lt__(rep1: Z2, rep2: Z2) -> bool:
# Ordering for sorting; dimension is compared first by the base class
return rep1.odd < rep2.odd
@classmethod
def iterator(cls) -> Iterator[Z2]:
# Must yield trivial irrep first
for odd in [False, True]:
yield Z2(odd=odd)
def discrete_generators(rep: Z2) -> np.ndarray:
# Shape: (num_generators, dim, dim)
if rep.odd:
return -np.ones((1, 1, 1))
else:
return np.ones((1, 1, 1))
def continuous_generators(rep: Z2) -> np.ndarray:
# Shape: (lie_dim, dim, dim) -- Z2 is discrete, so lie_dim=0
return np.zeros((0, rep.dim, rep.dim))
def algebra(self) -> np.ndarray:
# Shape: (lie_dim, lie_dim, lie_dim) -- structure constants [X_i, X_j] = A_ijk X_k
return np.zeros((0, 0, 0))
# Usage:
irreps = cue.Irreps(Z2, "3x odd + 2x even") # dim=5Required methods summary
| Method | Returns | Purpose |
regexp_pattern() | re.Pattern | Parse string like "1", "0e", "odd" |
from_string(s) | Irrep | Construct from matched string |
__repr__ | str | Canonical string form |
__mul__(a, b) | Iterator[Irrep] | Selection rule for tensor product |
clebsch_gordan(a, b, c) | ndarray (n, d1, d2, d3) | CG coefficients |
dim (property) | int | Dimension of representation |
__lt__(a, b) | bool | Ordering (dimension first, then custom) |
iterator() | Iterator[Irrep] | All irreps, trivial first |
continuous_generators() | ndarray (lie_dim, dim, dim) | Lie algebra generators |
discrete_generators() | ndarray (n, dim, dim) | Finite symmetry generators |
algebra() | ndarray (lie_dim, lie_dim, lie_dim) | Structure constants |
Built-in groups
cue.SO3(l): 3D rotations.lis a non-negative integer.dim = 2l+1. String:"0","1","2".cue.O3(l, p): 3D rotations + parity.p=+1(even) orp=-1(odd). String:"0e","1o","2e".cue.SU2(j): Spin group.jis a non-negative half-integer. String:"0","1/2","1".
Irreps and layout
irreps = cue.Irreps("SO3", "16x0 + 4x1 + 2x2") # 16 scalars, 4 vectors, 2 rank-2
irreps.dim # 16*1 + 4*3 + 2*5 = 38
for mul, ir in irreps:
print(mul, ir, ir.dim) # 16 0 1, then 4 1 3, then 2 2 5IrrepsLayout controls memory order within each (mul, ir) block:
cue.ir_mul: data ordered as(ir.dim, mul)— used by all descriptors and ir_dict internallycue.mul_ir: data ordered as(mul, ir.dim)— used by nnxdict[Irrep, Array]and PyTorch
IrrepsAndLayout combines irreps with a layout into a Rep:
rep = cue.IrrepsAndLayout(cue.Irreps("SO3", "4x0 + 2x1"), cue.ir_mul)
rep.dim # 10Building a SegmentedTensorProduct from scratch
The subscripts string uses Einstein notation. Operands are comma-separated, coefficient modes follow +.
# Matrix-vector multiply: y_i = sum_j M_ij * x_j
d = cue.SegmentedTensorProduct.from_subscripts("ij,j,i")
d.add_segment(0, (3, 4)) # operand 0: matrix segment of shape (3, 4)
d.add_segment(1, (4,)) # operand 1: vector of size 4
d.add_segment(2, (3,)) # operand 2: output vector of size 3
d.add_path(0, 0, 0, c=1.0) # link segments 0,0,0 with coefficient=1.0
poly = cue.SegmentedPolynomial.eval_last_operand(d) # last operand becomes output
[y] = poly(M_flat, x) # numpy evaluationMulti-segment STP (how descriptors work internally)
Descriptors build STPs with multiple segments per operand. Each segment corresponds to an irrep block:
# Linear equivariant map: output[iv] = sum_u weight[uv] * input[iu]
d = cue.SegmentedTensorProduct.from_subscripts("uv,iu,iv")
# Segment for l=1: ir_dim=3, mul_in=2, mul_out=5
s_in_0 = d.add_segment(1, (3, 2)) # input block
s_out_0 = d.add_segment(2, (3, 5)) # output block
d.add_path((2, 5), s_in_0, s_out_0, c=1.0)
# Segment for l=0: ir_dim=1, mul_in=4, mul_out=3
s_in_1 = d.add_segment(1, (1, 4))
s_out_1 = d.add_segment(2, (1, 3))
d.add_path((4, 3), s_in_1, s_out_1, c=1.0)Weights operand
For weighted tensor products (subscript starting with uvw or uv), the first operand is always weights. The weight segment shape is (mul_1, mul_2, ...) matching the multiplicity modes. The weights operand gets new_scalars() irreps since weights are invariant.
CG coefficients as path coefficients
d = cue.SegmentedTensorProduct.from_subscripts("uvw,iu,jv,kw+ijk")
# For each pair of input irreps and each output irrep in the selection rule:
for cg in cue.clebsch_gordan(ir1, ir2, ir3):
# cg has shape (ir1.dim, ir2.dim, ir3.dim)
d.add_path((mul1, mul2, mul3), seg_in1, seg_in2, seg_out, c=cg)Descriptors
All descriptors come in two variants:
- Original — returns
EquivariantPolynomialwith dense operands _ir_dict— returnsIrDictPolynomialwith operands already split by irrep
EquivariantPolynomial descriptors
# Fully connected tensor product (all input-output irrep combinations)
e = cue.descriptors.fully_connected_tensor_product(
16 * cue.Irreps("SO3", "0 + 1 + 2"),
16 * cue.Irreps("SO3", "0 + 1 + 2"),
16 * cue.Irreps("SO3", "0 + 1 + 2"),
)
# Channelwise tensor product (same-channel only, sparse)
e = cue.descriptors.channelwise_tensor_product(
64 * cue.Irreps("SO3", "0 + 1"), cue.Irreps("SO3", "0 + 1"),
cue.Irreps("SO3", "0 + 1"), simplify_irreps3=True,
)
# Full (weightless) tensor product
e = cue.descriptors.full_tensor_product(
cue.Irreps("SO3", "2x0 + 1x1"), cue.Irreps("SO3", "0 + 1"),
)
# Elementwise tensor product (paired channels)
e = cue.descriptors.elementwise_tensor_product(
cue.Irreps("SO3", "4x0 + 4x1"), cue.Irreps("SO3", "4x0 + 4x1"),
)
# Linear equivariant map (weight x input)
e = cue.descriptors.linear(
cue.Irreps("SO3", "4x0 + 2x1"),
cue.Irreps("SO3", "3x0 + 5x1"),
)
# Spherical harmonics
e = cue.descriptors.spherical_harmonics(cue.SO3(1), [0, 1, 2, 3])
# Symmetric contraction (MACE-style)
e = cue.descriptors.symmetric_contraction(
64 * cue.Irreps("SO3", "0 + 1 + 2"),
64 * cue.Irreps("SO3", "0 + 1"),
(1, 2, 3),
)IrDictPolynomial descriptors
Each _ir_dict constructor returns an IrDictPolynomial: .polynomial is a SegmentedPolynomial already split by irrep, and .input_irreps / .output_irreps describe the operand groups. Each (mul, ir) block in those groups corresponds to one polynomial operand of size mul * ir.dim.
channelwise_tensor_product_ir_dict always simplifies output irreps. To compare
with its dense counterpart, pass simplify_irreps3=True to
channelwise_tensor_product, or explicitly regroup the output data as well
as its irrep metadata. The third argument filters irrep types; it does not set
output multiplicities.
# Channelwise tensor product
desc = cue.descriptors.channelwise_tensor_product_ir_dict(
64 * cue.Irreps("SO3", "0 + 1"),
cue.Irreps("SO3", "0 + 1"),
cue.Irreps("SO3", "0 + 1"),
)
desc.polynomial # SegmentedPolynomial
desc.input_irreps # (weight_irreps, irreps1, irreps2)
desc.output_irreps # (irreps_out,)
# Scale coefficients and inspect individual input operands
scaled_poly = desc.polynomial * 0.5
for i, op in enumerate(desc.polynomial.inputs):
print(f"Input {i}: size={op.size}, num_segments={op.num_segments}")Other constructors use the same operand metadata contract:
# Fully connected tensor product
desc = cue.descriptors.fully_connected_tensor_product_ir_dict(irreps1, irreps2, irreps3)
# Full (weightless) tensor product
desc = cue.descriptors.full_tensor_product_ir_dict(irreps1, irreps2)
# Elementwise tensor product
desc = cue.descriptors.elementwise_tensor_product_ir_dict(irreps1, irreps2)
# Linear
desc = cue.descriptors.linear_ir_dict(irreps_in, irreps_out)
# Spherical harmonics
desc = cue.descriptors.spherical_harmonics_ir_dict(cue.O3(1, -1), [0, 1, 2, 3])
# Symmetric contraction
desc = cue.descriptors.symmetric_contraction_ir_dict(irreps_in, irreps_out, (1, 2, 3))split_polynomial_by_irreps
Use this helper to split an existing SegmentedPolynomial operand at irrep boundaries. Supply the operand's irreps explicitly because the bare polynomial has no representation metadata:
poly = e.polynomial # from an EquivariantPolynomial
poly = cue.split_polynomial_by_irreps(poly, 2, irreps_sh) # split input 2
poly = cue.split_polynomial_by_irreps(poly, 1, irreps_in) # split input 1
poly = cue.split_polynomial_by_irreps(poly, -1, irreps_out) # split outputEquivariantPolynomial key methods
e.inputs # tuple of Rep (group representations for each input)
e.outputs # tuple of Rep
e.polynomial # the underlying SegmentedPolynomial
# Numpy evaluation
[out] = e(weights, input1, input2)
# Preparing for uniform_1d execution (see cuequivariance_jax SKILL.md)
e_ready = e.squeeze_modes().flatten_coefficient_modes()
# Split dense operands using the representation metadata already attached to e
e_split = e.split_operand_by_irrep(1).split_operand_by_irrep(-1)
# Scale all coefficients
e_scaled = e * 0.5
# Fuse compatible STPs
e_fused = e.fuse_stps()normalize_paths_for_operand
Called internally by descriptors. Normalizes path coefficients so that a random input produces unit-variance output for the specified operand. Critical for numerical stability.
SegmentedPolynomial structure
poly = e.polynomial
poly.num_inputs # number of input operands
poly.num_outputs # number of output operands
poly.inputs # tuple of SegmentedOperand
poly.outputs # tuple of SegmentedOperand
poly.operations # tuple of (Operation, SegmentedTensorProduct)
# Each operation maps buffers to STP operands
for op, stp in poly.operations:
print(op.buffers) # e.g., (0, 1, 2) means inputs[0], inputs[1] -> outputs[0]
print(stp.subscripts)SegmentedOperand
operand = poly.inputs[0]
operand.num_segments # how many segments
operand.segments # tuple of shape tuples, e.g., ((3, 4), (1, 2))
operand.size # total flattened size (sum of products of segment shapes)
operand.ndim # number of dimensions per segment
operand.all_same_segment_shape() # True if all segments have identical shape
operand.segment_shape # the common shape (only if all_same_segment_shape)Custom equivariant polynomial from scratch
import numpy as np
import cuequivariance as cue
# Build a fully-connected SO3(1)xSO3(1)->SO3(0) tensor product manually
cg = cue.clebsch_gordan(cue.SO3(1), cue.SO3(1), cue.SO3(0)) # shape (1, 3, 3, 1)
d = cue.SegmentedTensorProduct.from_subscripts("uvw,iu,jv,kw+ijk")
d.add_segment(1, (3, 4)) # input1: 4x SO3(1), shape=(ir_dim, mul)
d.add_segment(2, (3, 4)) # input2: 4x SO3(1)
d.add_segment(3, (1, 16)) # output: 16x SO3(0) (4*4 fully connected)
for c in cg:
d.add_path((4, 4, 16), 0, 0, 0, c=c)
d = d.normalize_paths_for_operand(-1)
poly = cue.SegmentedPolynomial.eval_last_operand(d)
ep = cue.EquivariantPolynomial(
[
cue.IrrepsAndLayout(cue.Irreps("SO3", "4x1").new_scalars(d.operands[0].size), cue.ir_mul),
cue.IrrepsAndLayout(cue.Irreps("SO3", "4x1"), cue.ir_mul),
cue.IrrepsAndLayout(cue.Irreps("SO3", "4x1"), cue.ir_mul),
],
[cue.IrrepsAndLayout(cue.Irreps("SO3", "16x0"), cue.ir_mul)],
poly,
)
# Numpy evaluation
w = np.random.randn(ep.inputs[0].dim)
x = np.random.randn(ep.inputs[1].dim)
y = np.random.randn(ep.inputs[2].dim)
[out] = ep(w, x, y)Key file locations
| Component | Path |
Irrep base class | cuequivariance/group_theory/representations/irrep.py |
Rep base class | cuequivariance/group_theory/representations/rep.py |
SO3 | cuequivariance/group_theory/representations/irrep_so3.py |
O3 | cuequivariance/group_theory/representations/irrep_o3.py |
SU2 | cuequivariance/group_theory/representations/irrep_su2.py |
Irreps | cuequivariance/group_theory/irreps_array/irreps.py |
IrrepsLayout | cuequivariance/group_theory/irreps_array/irreps_layout.py |
IrrepsAndLayout | cuequivariance/group_theory/irreps_array/irreps_and_layout.py |
SegmentedTensorProduct | cuequivariance/segmented_polynomials/segmented_tensor_product.py |
SegmentedPolynomial | cuequivariance/segmented_polynomials/segmented_polynomial.py |
EquivariantPolynomial | cuequivariance/group_theory/equivariant_polynomial.py |
IrDictPolynomial | cuequivariance/group_theory/ir_dict_polynomial.py |
| Descriptors | cuequivariance/group_theory/descriptors/ |
| Tensor product descriptors | cuequivariance/group_theory/descriptors/irreps_tp.py |
spherical_harmonics | cuequivariance/group_theory/descriptors/spherical_harmonics_.py |
symmetric_contraction | cuequivariance/group_theory/descriptors/symmetric_contractions.py |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

