Skip to main content

rainbow-tensor

See how tensor operations move, reuse and combine elements.

PyPI Python Tests Backend contracts License: MIT

Documentation · Notebook examples · LLM visualization guide · Releases

rainbow-tensor turns tensor shapes and operations into SVG figures for Jupyter notebooks, lessons and technical explanations. Choose an output element to see its source coordinates and the calculation behind it. Record several operations to follow that element all the way back to the original inputs.

Four tensor panels showing repeated reverse indexing, transpose and sum, with the sources of the first output highlighted

One result, three contributions, two original positions. The first output is 6 + 3 + 6 = 15, because the same source element was sampled twice.

Installation

Python 3.10 or newer is required.

python -m pip install rainbow-tensor

For clickable result cells and notebook controls:

python -m pip install "rainbow-tensor[interactive]"

Install into the Python environment used by your notebook kernel. NumPy and IPython are included as dependencies. PyTorch, JAX and TensorFlow are optional and installed separately. Static SVG rendering does not require widget packages.

Your first visualization

Paste this into a notebook cell:

import numpy as np
import rainbow_tensor as rt
from IPython.display import display

x = np.arange(1, 7).reshape(2, 3)
# [[1, 2, 3],
#  [4, 5, 6]]

visual = rt.sum(x, axis=1, focus=(1,))
display(visual)

The result has shape (2,). Focusing output (1,) highlights the second row and explains 4 + 5 + 6 = 15. Change the focus to (0,) to follow the first row. The explanation appears below the figure and is also available as visual.text.

To inspect an indexing expression instead:

selection = ([1, 0, 1], slice(None, None, -1))
display(rt.index(x, selection, focus=(2, 0)))

The result is [[6, 5, 4], [3, 2, 1], [6, 5, 4]]. Its position (2, 0) reads source (1, 2). Repeated picks keep their separate positions in the result.

Follow a complete operation chain

Flow records the steps that produced a result. Each step retains its shape and coordinate mapping without allocating a complete intermediate tensor.

flow = rt.Flow()
source = flow.input(x, name="X")
selected = flow.index(source, selection, name="S")
transposed = flow.transpose(selected, name="T")
y = flow.sum(transposed, axis=1, name="Y")

assert y.shape == (3,)
assert [y.value((i,)) for i in range(3)] == [15, 12, 9]
display(y.visualize(focus=(0,)))

For Y[0], the trace follows T[0, 0], T[0, 1] and T[0, 2] through the transpose and index back to X[1, 2], X[0, 2] and X[1, 2]. The duplicate contribution remains visible.

trace = y.trace((0,))
assert trace.complete
counts = {item.reference.coordinate: item.count for item in trace.roots}
assert counts == {(1, 2): 2, (0, 2): 1}

A structural trace reads no array values. Input occurrence counts describe paths through the recorded expression, not coefficients or derivatives. Record operations explicitly through flow to retain their history. Input values are read afresh on each value query or visualization.

Read the provenance guide or run the worked notebook.

Explore by clicking

With the interactive extra installed, pass a tracked result or an operation and its arguments to explore:

explorer = rt.explore(y)
display(explorer)

# A single operation can be explored without recording a Flow.
index_explorer = rt.explore(rt.index, x, selection)
display(index_explorer)

Click a visible result cell to update the source highlights and explanation. Enter and Space activate a focused cell. Coordinate fields also reach positions hidden by a large preview.

explorer.set_focus((2,))
explorer.visual.save("focused-result.svg")

# Run these when you have finished with the controls.
explorer.close()
index_explorer.close()

Live controls need a running notebook kernel and a host with widget support. y.visualize(focus=(2,)) produces the equivalent static figure.

Supported operations

What you want to understand Public views
Tensor structure shape
Slices, masks and repeated gathers index, take, repeat
Reshaping and axis movement reshape, transpose, swapaxes, moveaxis, squeeze, expand_dims
Joining and broadcasting concatenate, stack, broadcast
Reductions and contractions sum, mean, matmul, einsum
Storage metadata memory

Operation views support focus= to explain one result element. The same operations are available as Flow methods. shape and memory are standalone inspection views. flow.broadcast returns one tracked output per input, each with its own values and output port.

Indexing supports integers, slices, ellipsis, new axes, boolean masks and advanced integer arrays. Reductions support multiple axes, negative axes, axis=None, axis=() and keepdims=True. Scalars use shape and coordinate (). Empty tensors retain their zero-length dimensions and have no selectable output element.

NumPy arrays and CPU tensors from PyTorch, JAX and TensorFlow are covered by the backend contract suite. Other array-like inputs need a shape and scalar coordinate access. Shape tuples such as rt.shape((2, 3, 4)) use generated row-major placeholder values.

Figures, explanations and limits

Every view returns a TensorVisual with an SVG, a plain-text explanation and operation metadata. Its trace describes a focused output. Visuals from a recorded Flow also expose a bounded provenance tree.

visual.save("row-sum.svg")
print(visual.text)

save writes the figure only. Keep visual.text alongside it when sharing the explanation outside a notebook. SVG figures remain usable without a running Python process.

Large tensors use bounded previews. Repeat mappings and basic slice selections remain compact instead of enumerating every output position. Math views default to 10,000 terms per output and 100,000 across the preview. Flow evaluation also counts recursive factor references and input reads. Work that exceeds a budget is shown as ?, and incomplete structural traces identify the limit reached.

Numerical previews use Python scalar arithmetic. Backend accumulation dtype, rounding and overflow may differ. The figures explain logical operations and coordinate origins, while memory reports available storage metadata.

Theme and language

The default auto theme follows the viewer's light or dark preference, including in saved SVG files. Language follows the Python environment and system locale. English and Simplified Chinese are included.

rt.set_default_theme("auto")
rt.set_language("en")
display(rt.shape(x, theme="dark"))  # Override the theme for one figure.

Add a language by supplying a JSON translation catalog. Missing entries fall back to English, and rt.load_translations("translations") loads extra catalogs without changing application code. See themes and translations.

Learn and teach

Start here What you will find
Learning path Small exercises that connect shapes, output coordinates and source values
Notebook collection Runnable examples from basic shapes through cross-operation tracing
API reference Function signatures, parameters and result objects
LLM visualization guide A reusable prompt and verified patterns for generating beginner explanations
Architecture Coordinate mappings, rendering boundaries and performance decisions

Contributing

Bug reports, clearer teaching examples and translation catalogs are welcome. For a bug report, include a small reproducing input, the operation, the expected result and your package, Python and backend versions. Use GitHub Issues to report a problem or discuss a new operation.

To work on the package:

git clone https://github.com/Niox1337/rainbow-tensor.git
cd rainbow-tensor
python -m pip install -e ".[dev,interactive]"
python -m pytest
python -m ruff check .

Optional backend tests skip when their framework is absent from that Python environment. CI separately requires PyTorch, JAX and TensorFlow, as well as running the main suite on Python 3.10 and 3.12. SVG golden tests protect existing figures, and distribution checks exercise installed wheels and source packages.

python -m build
python scripts/check_distribution.py --interactive
python -m pip install -r docs/requirements.txt
python -m sphinx -b html -W --keep-going docs docs/_build/html

The distribution check expects one wheel and one source archive in dist. Use --dist-dir PATH for a different build directory. Keep changes focused and add a regression example when correcting an operation's behavior.

License

MIT, Copyright 2026 Zhixiang Feng.

Metadata

Release files for rainbow-tensor 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rainbow-tensor 1.3.0
File Size Uploaded
rainbow_tensor-1.3.0.tar.gz 217.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rainbow-tensor 1.3.0
File Interpreter ABI Platform
rainbow_tensor-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 331.0 kB

Release files / rainbow_tensor-1.3.0.tar.gz

Download URL rainbow_tensor-1.3.0.tar.gz
Size 217.3 kB
Tags Source
SHA-256 checksum
How to use checksums
1aaea763e27a6cad31a1f0f33999618787c0930734a68d6adf521784490b690b
BLAKE2b-256 checksum
How to use checksums
c5dbed56f5a86b2643565b50ae8f896883372e5056208698f6d56d8fc5567ab8
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 Sep 22, 2026.

Transparency log

Release files / rainbow_tensor-1.3.0-py3-none-any.whl

Download URL rainbow_tensor-1.3.0-py3-none-any.whl
Size 113.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
446e7a6d061070eb03779b0ba3ebb5db4f0f4fa2cb286fa1a8dd971fba1fd07d
BLAKE2b-256 checksum
How to use checksums
661485121f209ac9c0cb024e74c9ff8fc6fa3f96ab1f265a04e4557c9bf8734b
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 Sep 22, 2026.

Transparency log

Release history Release notifications | RSS feed

1.8.0

2 release files

1.3.1

2 release files

This release

1.3.0 This release

2 release files

1.2.0

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.15.0

2 release files

0.14.0

2 release files

0.13.0

2 release files

0.12.0

2 release files

0.11.0

2 release files

0.10.8

2 release files

0.10.7

2 release files

0.10.6

2 release files

0.10.5

2 release files

0.10.4

2 release files

0.10.3

2 release files

0.10.2

2 release files

0.10.1

2 release files

0.10.0

2 release files

0.9.0

2 release files

0.8.0

2 release files

0.7.0

2 release files

0.2.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page