Problem
The SQM screen shows a !CAL marker whenever no per-device calibration file
exists (python/PiFinder/ui/sqm.py, _is_calibrated() / the units-line badge).
Uncalibrated is the normal, validated state. The zero-touch path is the one
the factory profiles are built for, and the headline archive accuracy in
docs/ax/sqm.md (bias −0.008 mag, MAE 0.061 mag across nine sweeps) was
measured with no calibration file present.
So the badge flags the expected case as a deficiency. docs/ax/sqm/CONTEXT.md
explicitly lists "Needs calibration" under Avoid these ambiguous phrases,
because factory profiles are the normal path. The screen's own badge says the
thing the glossary tells us not to say.
Since #544, the wizard's headline output matters even less than it used to: the
tracked black level supersedes the wizard-measured bias offset once its fit is
leased, leaving the dark-current rate as the wizard's only lasting contribution.
Options
- Show
CAL only when a calibration file exists, and show nothing otherwise.
- Relabel the uncalibrated state to something neutral (e.g.
FACT for factory
profile) so both states read as valid.
- Leave it and rely on documentation.
Docs dependency
docs/source/sqm.rst currently explains the marker to users under
Calibration → When you need it:
The SQM screen shows a small !CAL marker when you have not run the
calibration wizard on your PiFinder. This is the normal state and it does not
mean anything is wrong. Once you run the wizard the marker changes to CAL.
If this badge is removed or relabelled, update that passage in
docs/source/sqm.rst in the same change. The screenshots on that page do not
show the badge, so no image re-capture is needed.
Problem
The SQM screen shows a
!CALmarker whenever no per-device calibration fileexists (
python/PiFinder/ui/sqm.py,_is_calibrated()/ the units-line badge).Uncalibrated is the normal, validated state. The zero-touch path is the one
the factory profiles are built for, and the headline archive accuracy in
docs/ax/sqm.md(bias −0.008 mag, MAE 0.061 mag across nine sweeps) wasmeasured with no calibration file present.
So the badge flags the expected case as a deficiency.
docs/ax/sqm/CONTEXT.mdexplicitly lists "Needs calibration" under Avoid these ambiguous phrases,
because factory profiles are the normal path. The screen's own badge says the
thing the glossary tells us not to say.
Since #544, the wizard's headline output matters even less than it used to: the
tracked black level supersedes the wizard-measured bias offset once its fit is
leased, leaving the dark-current rate as the wizard's only lasting contribution.
Options
CALonly when a calibration file exists, and show nothing otherwise.FACTfor factoryprofile) so both states read as valid.
Docs dependency
docs/source/sqm.rstcurrently explains the marker to users underCalibration → When you need it:
If this badge is removed or relabelled, update that passage in
docs/source/sqm.rstin the same change. The screenshots on that page do notshow the badge, so no image re-capture is needed.