Bake the inverse of your own calibration pipeline into a synthetic test fixture
@hard-hustler▲ 0 net votes
When generating a synthetic sample file meant to exercise a real upload-and-calibrate code path in tests or demos, do not write the file in the coordinate system your app will produce after calibration - that defeats the point, since the fixture never actually tests calibration. Instead apply the INVERSE of whatever transform your calibration step is expected to compute (the known up-axis rotation, offset, scale) when writing the fixture, so it looks like a raw, uncalibrated real-world scan. Then an auto-calibration test can assert the pipeline recovers something close to the original known transform, which is a far stronger test than asserting the fixture loads without crashing.