Emanuele Strazzullo · research notebook

The lab

Small, reproducible experiments in machine learning, planning and control. The networks and planners are written from scratch and run in your browser, except on the applied side, which uses established tools and says so. Every result comes with the protocol that produced it, and the negative results are published too.

Experiments

01 5 environments · ongoing

System One / System Two

Can a tiny network, trained by a slow planner, make most decisions at a fraction of the planner's cost, and know when to hand control back?

A fast network (System One) proposes every move with a confidence. When it is unsure, or when a cheap safety check rejects its move, a slow planner (System Two) decides instead, and that decision becomes a new training example. The same pipeline runs on five very different problems.

Open the experiment →
02 complete

Handwriting pad

Can a network with 22,298 parameters read handwritten letters as well as a classic recogniser that compares your letter with every stored example?

Write one uppercase letter at a time with your finger, like on a car's touchpad. Both recognisers read it in your browser, and the page shows how much arithmetic each one spent.

Open the experiment →
03 applied · in progress

Go1 in your browser

Can a model of a real robot, trained on a GPU, walk in a browser tab, and can a planner teach it where it struggles?

The lab's applied side: established tools (MuJoCo, MuJoCo Playground, a free Colab GPU) instead of code written from scratch, under the same method. The Unitree Go1 runs in your browser, and you steer it.

Open the experiment →

How experiments are run

  1. Targets first. What would count as success is written down before measuring, and never changed afterwards.
  2. Separate data. Design decisions use development seeds or writers; final numbers use held-out test ones, used only for the final studies.
  3. Repeated runs. Every final result that depends on training is the mean of 5 independent training runs, with 95% intervals.
  4. Feasibility first. Before a long study, a short test with go/no-go criteria decides whether it is worth running; when a study goes ahead anyway, that is stated.
  5. Everything logged. Every design decision is recorded with its evidence, and negative results are reported like positive ones.
  6. From scratch. On the from-scratch side, no machine-learning libraries: networks, backpropagation, planners and environments are written in TypeScript (the quadruped's 3D physics uses the Rapier engine). The applied side uses established tools, and says which.