Radiation-damage caution no longer claims a decay correction that did not happen

The anisotropy caution for a run with more than 10 A^2 of relative B said the scale model removes the
average monotone damage and advised --relative-b. The decay is applied only where it cross-validates,
and on the rotation battery it never did (every damaged set skipped it), so the sentence was false
wherever it was printed; --relative-b on such a run (a 360 deg trigonal sweep, +11 A^2) is itself
refused by its cross-validation, and forced it lowers ISa 20.4 -> 18.6 and CC_anom 0.45 -> 0.33.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HVeDQsU5a8AJUdJPgWevAK
This commit is contained in:
leonarski_fandClaude Opus 5.5 committed 2026-11-14 01:51:14 +01:00
1 parent c1bbf02a7c
commit 8c023fd826
1 file changed
+2 -2
@@ -1470,8 +1470,8 @@ AnisotropyResult AnalyzeAnisotropy(const std::vector<MergedReflection> &merged,
"reachable by a lab-fixed systematic and reduces the power of the test");
if (std::isfinite(run.radiation_damage_relative_b) && std::fabs(run.radiation_damage_relative_b) > 10.0)
result.cautions.emplace_back(
"the run carries substantial radiation damage; the scale model removes its average "
"monotone part, but a non-monotone dose ramp needs --relative-b to be taken out too");
"the run carries substantial radiation damage; the scale model takes out a decay only "
"where it cross-validates, so part of the damage can remain in the fall-off");
// R2's Laue-class caution, fired on its measured signature rather than on the Laue class alone.
// Too high a symmetry assignment pushes real anisotropy into the directions the systematic error is
// measured in, so sigma_sys is inflated by the signal itself and the gate collapses (measured: a