Zebrafish
Neural

Initial records come from the local preview; new trials run on the replacement server. Recovery record ↗

ZEBRAFISH NEURAL / BROWSER LAB

Change the scene.
Measure the response.

A browser, a visual target, and the fish’s controller. We move the target, remove the cue, or add a distraction. Every trial leaves a record you can replay.

CONNECTIONConnectingWaiting for the experiment server.Inspect the evidence ↓
01

Switchback

The target changes position.

02

Blackout

The visual cue disappears.

03

Decoy

A competing cue appears.

LIVE BROWSER

Waiting for a trial

—
Controlled visual environmentNO FRAME

The actual browser view will appear here.

No sample footage or substitute simulation.
AWAITING SERVER FRAME
BaselineInterventionRecovery
0 s8 s11 s—
Model time—
Target contacts—
First contact—
Distance to target—
Time on target visible target · before / after intervention— → —
No trial received

Encoded visual cue

32 × 16

Screenshot luminance mapped to a bearing cue.

Motor response

LeftRight

Waiting for samples.

FROM OBSERVATION TO EVIDENCE

Replay the response.

Pick a saved trial. Recompute its recorded inputs, then test what changes when one signal is removed. Interrupted attempts are labeled separately.

NO SAVED TRIALS YET

One trial, inspectable from start to finish.

Recorded screenshot inputs, neural states, and cursor positions stay aligned in model time.

WHAT IS BEING TESTED

A visual response, with a paper trail.

Methods & scope ↗
01 / INPUT

A real browser screenshot.

The adapter finds the brightness-weighted center of the screenshot’s bright regions and maps its bearing into visual input. The controller does not receive target coordinates or text instructions.

02 / RESPONSE

Same controller, different conditions.

A defined protocol changes the scene. We record the controller’s activity and movement before, during, and after the intervention. Target contacts are measurements, not scripted outcomes.

03 / REPRODUCIBILITY

Recompute what was recorded.

Replay checks the saved inputs against the published controller. It verifies computational consistency, not where the original computation ran. This experiment does not update learned weights.