They need to state it was entirely autonomous.

The phyphox app recorded acceleration and angular velocity at a sampling rate of 100 Hz.

I wonder if they considered using the fact that a roller coaster trajectory is closed loop? That tends to help with calibration, but maybe the devices are nicely factory calibrated to begin with. They get close, but stop short of mentioning it:

The measurements were stopped after the attraction returned to its resting state. This provides reference points at the beginning and the end of the ride where the velocity is zero.

And this gets you real close to building visual inertial oximetry:

Smartphone video recordings were used to correlate specific ride manoeuvres with the recorded data for the roller coaster.

A list of tasks I'm already behind on is the last thing I want to be reminded of constantly.

:)

Both offer direct, mechanical engagement that avoids the continuous friction slip of a wet clutch.

Which was the point.

Also platforms like Wasm still do Mx1 scheduling without async preemption, where Gosched is required at places.

E.g.: my "transpiled" SQLite driver takes special care to make sure long running SQL queries (and the busy handler) can be canceled with contexts even on platforms without async preemption.

It doesn't need to say if you do any business with Anthropic (for other customers, internal tools or processes), you lose all your contracts with us.

My dev branch got broken when I rebased to main after a week of drift.

I had to bisect over around a million commits to the monorepo to find the culprit.