Three things the CPU analysis page either did not describe or described in the
wrong place.
The beam-stop finder had no entry at all, though it runs by default and puts
pixels into the mask. It gets a short 1.5, next to the other measurement made
from raw frames before anything is indexed: what it masks and why, the per-ring
comparison the detection rests on, and the shaping that follows.
The resolution estimate was two paragraphs on the end of "Resolution and
ice-ring handling", which is neither where a reader looks for it nor what that
section is about. It moves to its own 3.6 at the end of spot finding, where it
belongs - it is read off the finished spot list - and loses the recapitulation
of what the old estimator did wrong, which is commit-message material.
The ice-ring positions are measured values taken from a paper, so they owe an
acknowledgement, and had only an in-source comment. DOI verified against
Crossref; the title is not the one the ring positions are usually attributed to.
Also: the per-image loop's default worker cap is 16 per GPU, not the 8 the
options table still gave, and it applies to --mode mx only.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y5XisyYxmF8mUEQjzpMRe2
leonarski_fandClaude Opus 5
ebf2064c26
