← Sensing 2026 hub
Sensing 2026 · the logbook

The logbook

One short entry per spaced session — not a report, a thinking trace. The tutorial is built around these, so write them as you go, not the night before.

Five fields, ninety seconds

Each interactive ends by asking for one logbook entry. They all use the same five prompts. The one that matters most is the fourth — it is where the critical thinking shows.

What a good entry looks like

A strong entry names a specific wrong turn and the evidence that corrected it — not “I learned about magnetometers.” Example, from Anchor 1 (the trade-off triangle):

Session 1 · Anchor 1 — choose a magnetometer for 10 nT @ 1 kHz
Tried
Dragged P into the 1 kHz target zone; read the four magnetometer rows against it.
Stuck
~10 min — I assumed I needed the most sensitive sensor (SQUID), but the target-zone readout kept insisting sensitivity wasn't the binding constraint.
Hub resource used
Anchor 1 reference card — the boundary line “more sensitivity is not strictly better” — and the magnetometer table.
Changed my mind because…
10 nT is a large field; every row resolves it, so bandwidth, not sensitivity, decides. I'd been optimising the wrong corner.
Still unclear
Whether NV-diamond's room-T, µm-scale advantage outweighs its modest sensitivity for a real 1 kHz job, or whether SERF-OPM's fading bandwidth rules it out first.

Your template — print it or copy it

Three blank cards, one per spaced session.

The rhythm — three sittings, not one

Spread the three entries across the week (the workshop tracks your ticks). Each 30-min session is ~2 anchors and one entry; the tutorial discusses all three.

SessionAnchorsOne entry about…
1 · early week1 triangle · 2 noise/Allanthe design task + the noise-trace task
2 · mid week3 SQL · 4 laddercoin-flip / photon-counting + pick-the-rung
3 · late week5 back-action · 6 transductionsqueezing-band task + a broken transduction chain
Tutorialbring all three entries — we discuss them (90 min)