How Debrief v4 fits together
Debrief v4 starts with foundations rather than features. Here is the shape everything else will hang from.
Blog¶
Short, frequent posts on what is new in Debrief v4, written in the same pull request as the work they describe.
Fast enough to drag
When you drag the time slider or a target solution, the numbers must keep up with your hand. We measured whether they will.
Measuring on the real Earth
Debrief v4 measures ranges and bearings along the true shape of the Earth. Legacy Debrief did not, so some figures will change slightly.
Load and look: the whole path, end to end
Phase 1's job is to prove the architecture by walking one path all the way through. You open a catalogue, see a plot on a map, select tracks, run a Python tool, and see its result on the map. That now works in VS Code.
Nothing lost: undo, crashes, and a plot shared with others
Phase 2 is about trust. An analyst should be able to try something, take it back, have Debrief die mid-save, or share a plot with a colleague who changes it at the same time, and never lose work or have it overwritten without being told.
One schema, two languages
Debrief's analysis runs in Python and its interface in TypeScript. Every piece of data that passes between them is defined once, so the two sides cannot quietly disagree.
Debrief's Python, in your browser
The public demonstration of Debrief will run its Python analysis tools inside your web browser. We checked that it works before building on it.
Try it in your browser
You no longer need to install anything to try Debrief v4. The blog now has demos you can play with: the real map, tool forms and Python tools, running in your browser.