leonarski_fandClaude Opus 5
154f4f8895
Build Packages / Unit tests (push) Successful in 1h37m59s
Build Packages / build:windows:nocuda (push) Successful in 16m1s
Build Packages / build:windows:cuda (push) Successful in 18m38s
Build Packages / build:viewer-tgz:cpu (push) Successful in 7m16s
Build Packages / build:viewer-tgz:cuda (push) Successful in 8m11s
Build Packages / build:rugnux-tgz (x86_64) (push) Successful in 6m46s
Build Packages / build:rugnux:aarch64 (cross) (push) Successful in 6m12s
Build Packages / build:rpm (rocky8_nocuda) (push) Successful in 14m15s
Build Packages / build:rpm (rocky9_nocuda) (push) Successful in 15m18s
Build Packages / build:rpm (ubuntu2204_nocuda) (push) Successful in 16m19s
Build Packages / build:rpm (ubuntu2404_nocuda) (push) Successful in 15m42s
Build Packages / build:rpm (rocky8_sls9) (push) Successful in 17m11s
Build Packages / build:rpm (rocky9_sls9) (push) Successful in 17m50s
Build Packages / build:rpm (rocky8) (push) Successful in 15m11s
Build Packages / build:rpm (rocky9) (push) Successful in 16m7s
Build Packages / build:rpm (ubuntu2204) (push) Successful in 13m18s
Build Packages / build:rpm (ubuntu2404) (push) Successful in 13m0s
Build Packages / HDF5 consumer tests (DIALS, XDS) (push) Successful in 23m19s
Build Packages / Generate python client (push) Successful in 38s
Build Packages / Build documentation (push) Successful in 1m5s
Build Packages / Create release (push) Successful in 26s
Build Packages / build:rugnux:windows (push) Successful in 16m1s
The measurement landed report-only because the code could not say which frames it was talking about. It can now. A candidate is scanned at the batch width and at that width doubled and doubled again, so a defect far longer than one batch is judged against a reference that does not still contain it - on one sweep a 137 degree stretch measured minus 0.0352 at 59 sigma while its worst single batch read minus 0.008 and was refused. Its edges are then found by moving them a frame at a time with the WHOLE stretch re-measured at each position, rather than by halving it: the reflection count the verdict rests on never shrinks as the edge sharpens, which is what used to drive the harm onto one frame. Nothing narrower than one rocking event is ever removed, that width taken from the run's own combine, because a single frame is below what the statistic can resolve. And delta-CC1/2 may confirm a removal, never propose one. The frames must also disagree with the merge on their own per-image correlation, computed on the partials and independent of the statistic being confirmed - otherwise the test selects on the very quantity it then reports as improved, which flatters any removal whatsoever. Measured: on a sweep where dropping 450 frames takes R_meas from 0.28 to 0.21, dropping 450 frames of the same sizes chosen by position makes every number worse. Over a hundred and forty-eight datasets: no space group and no cell changes, no single-frame removals anywhere, and the ledger no longer calls a frame inconsistent with a merge it agrees with better than average. Eighty-eight are byte-identical. Where it acts it is worth R_meas 0.82 to 0.23, ISa 9.5 to 14.1, a resolution shell. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011GxZqDiFP3KqriBhNdcR56
