Skip to main content

Continuous Cellular Engine

A real-time, interactive continuous cellular-automaton sketch built with Python and Taichi. It evolves a scalar field with a ring-shaped Gaussian neighborhood kernel and a smooth Lenia-style growth rule, then renders the result as a procedural RGB palette.

Hardware and performance: the program initializes Taichi with ti.gpu; a compatible GPU backend and working graphics/window environment are needed to run the interactive demo. Performance depends heavily on the Taichi backend and device. The 300+ FPS figure sometimes associated with this algorithm has not been benchmarked or guaranteed by this repository.

Install

python -m pip install continuous-cellular-engine

Run

continuous-cellular-engine
# or
python -m continuous_cellular_engine

Use the mouse to paint seeds. Press Space to pause/resume, R to reseed, C to clear, and Esc to exit. See the usage guide for source installation, controls, parameters, and platform notes.

What it does

  • Evolves a continuous state S(x, y) clamped to [0, 1] rather than binary cells.
  • Measures local density with a normalized radial Gaussian ring and toroidal boundary wrapping.
  • Applies a Gaussian growth function and an explicit Euler integration step.
  • JIT-compiles the grid work through Taichi and visualizes the field with a phase-shifted RGB palette.

Read the architecture and usage guide for equations, execution flow, implementation details, limitations, and examples. The runnable implementation is continuous_cellular_engine.py.

Development

python -m pip install -e '.[test]'
python -m compileall -q continuous_cellular_engine.py tests
python -m pytest

The tests validate Python syntax and the source-level simulation structure without requiring a GPU. GitHub Actions runs these checks and validates the package build on pushes and pull requests.

Releases

Version tags use vMAJOR.MINOR.PATCH. Pushing a v* tag builds distributions and attempts publication to PyPI through Trusted Publishing. The repository's workflow and one-time PyPI publisher setup are described in release setup.

License

This project is licensed under the Apache License, Version 2.0. See the license file for terms, conditions, and notices.

Release files for continuous-cellular-engine 0.1.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 continuous-cellular-engine 0.1.0
File Size Uploaded
continuous_cellular_engine-0.1.0.tar.gz 9.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for continuous-cellular-engine 0.1.0
File Interpreter ABI Platform
continuous_cellular_engine-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 18.9 kB

Release files / continuous_cellular_engine-0.1.0.tar.gz

Download URL continuous_cellular_engine-0.1.0.tar.gz
Size 9.5 kB
Tags Source
SHA-256 checksum
How to use checksums
449915a1d74151fd7d6ce091e21fe0847c3cd02621f1f4bc6adbe0071c858e28
BLAKE2b-256 checksum
How to use checksums
6d204eb1b5e90365c3eb4d382e2014528912e5ebd609203cebc995e15cbb751d
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 26, 2026.

Transparency log

Release files / continuous_cellular_engine-0.1.0-py3-none-any.whl

Download URL continuous_cellular_engine-0.1.0-py3-none-any.whl
Size 9.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
afd72361f59da41ce036ac16b766c9198a9c6732ce73cda16b0433563792d2c9
BLAKE2b-256 checksum
How to use checksums
f8edad4271b11f445c0445d0804ca3b97cca1730fe90b3d8f0ab81586287ebee
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 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

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