Navigate

Quick find

Find what you need

Esc

Fly Lab / a simulated nervous system

Watch the fly move.

Connecting

Follow a simulated fly's movement, then explore its brain activity and visual inputs. Choose a published source to see what it is doing.

Pause viewing stops updates here; the simulation keeps running. Some experiments run slower than real time.

More to explore: Doom AI or recorded speech comparisons.

Connecting to the live body view…

Live poses from the physics simulation, shown with simplified body shapes and joints. The full body mesh is not published in this feed.
Live measurements & source identity
Source
Not bound
Stream identity
—
Graph identity
—
Mode
—
Execution
—
Sequence
—
Measured RTF
—
Sample rate
—
Sample age
—
Active neurons
—
Spikes / interval
—
Neural compute
—
Site build
490bd51ff8ad
How to read this view

The simulation uses a complete retained fly nervous system to drive a simulated body. The source selector distinguishes the female BANC and male MaleCNS networks; a source stays unavailable until it is published.

The body panel shows real articulated poses from the live FlyGym physics simulation, drawn as bounded part proxies and the measured joint skeleton. The brain panel samples soma anchors from the viewer's public presentation layout and colours them with the real per-neuron counts reported for that interval; it is not a spike-timestamp recording and no activity is generated in the browser. The vision panel shows the fly's rendered-eye or consumed-input images when the running viewer build serves them, with a source-produced reconstruction when available.

Real-time factor (RTF) is simulation time divided by wall time, reported by the live viewer. Full nervous-system intervals take substantial computation; “best-effort live” means a low measured RTF. Check the Execution row for the viewer’s declared cadence: “fast approximate” indicates a decimated physics/controller run. The last verified sample remains visible until its freshness window expires.

Read-only by construction: the public site worker stores bounded snapshots published outbound by the lab. There is no inbound route, no command channel and no operator data in the public payload.