2 Commits

Include renames

Author	SHA1	Message	Date
leonarski_fandClaude Opus 5	6b738713e8	model validation: place the model, then weight the maps by sigma_A ... --model re-fractionalized the model into the data cell and then left it there. On a non-isomorphous pair that is a placement error, not a cell error: the box is squeezed, the body inside it is not moved. Six parameters now recover it - an angle-axis rotation about the model's centroid and a translation, refined over a 6 / 4.5 / 3.5 A ladder, the scale (k_overall, anisotropic B, k_sol, b_sol) re-fitted at every evaluation so the target measures the placement and not the scale. The refinement sees only the working reflections and the step is committed only if R-free, on the free set it never saw, drops; otherwise the model goes back where it was read. Measured on merged lysozyme data against a deposited lysozyme model whose cell differs by 3.4% in c: R-work 0.559 -> 0.400, R-free 0.591 -> 0.383. Over the same 3.5 A range the external arbiter (REFMAC rigid body through dimple) works in, 0.524 -> 0.330 against REFMAC's 0.522 -> 0.355, and the recovered movement agrees with REFMAC's to 0.25 deg and 0.03 A (3.05 deg / 1.04 A vs 2.76 / 0.98). 2.4 s of added wall clock, 234 structure-factor evaluations. The map coefficients become 2mFo-DFc and mFo-DFc. sigma_A is estimated by maximum likelihood per resolution shell on the free reflections only, with the number of shells taken from the size of the free set so no shell is thin; centric and acentric reflections carry their own likelihoods, and a centric reflection's bias-free coefficient is mFo. Cross-checked against CCP4 SIGMAA on the same reflections: mean FOM 0.404 against its 0.396, with the same per-shell structure. The figure of merit is written to _maps.mtz so the weighting can be undone. The per-shell scaling refusal in fit_model stands - Fobs is never rescaled and the R-factors are untouched - but m and D are per-dataset, so maps from one campaign are no longer scaled identically. That is argued at the code and in docs/CPU_DATA_ANALYSIS_DECISIONS.md 14.4. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EFEJG6WBQv8th4UJFNe53N	2026-09-02 13:06:05 +02:00
leonarski_f	511be0c366	v1.0.0-rc.165 (#75) ... * `rugnux --model` adopts the model's space group as a label where the data were merged in its enantiomorph, instead of reindexing the reflections - which swapped I(+) with I(-). * `rugnux --model` warns, naming the atom, when the anomalous density at the model's atoms comes out inverted, which means the data and the model are in opposite hands. * `rugnux --model` writes an anomalous difference map (`<prefix>_anom.ccp4`) when the merge kept the Bijvoet split, and names the ten model atoms it peaks highest on as `ANOMALOUS_SITE_01`..`_10`. * `MEAN_ATOM_DENSITY_SIGMA` is read from the map by cubic rather than linear interpolation and comes out around a tenth higher; it is no longer comparable with the figure earlier versions printed. * `rugnux --model` reads an mmCIF coordinate file as well as a PDB one, gzipped or not, taking the format from the file's content rather than its name. * A model `rugnux --model` cannot use is reported as a `WARNING:` line in the results report instead of only in the log. * The rugnux results report has a `10. MODEL VALIDATION` section when `--model` was given; `REPORT_VERSION` is 4, `WARNINGS` moves to section 11 and no existing key changed. * The rugnux results report records how the run was invoked, what it cost and what it ran on: `COMMAND_LINE=`, `WALL_TIME=` and `GPU_COUNT=` / `GPU=`. * rugnux says which GPUs it can see before it starts processing. * `rugnux --export-unmerged` also writes `<prefix>_unmerged.mtz` on a `--no-merge` run, and is ignored on a run with no output prefix instead of writing a file called `_unmerged.mtz`. * `/start` asks the writer whether the run can be written before the detector is armed, so a run whose master file already exists, or whose output directory cannot be created, is refused up front with the writer's own message. This needs the TCP image stream or the built-in HDF5 writer; the ZeroMQ stream is unchanged. * A calibration that fails goes to `Error` carrying the reason instead of `Inactive`, so `/wait_till_done` and `/wait_until_running` report it; a cancelled calibration still goes to `Inactive`. * `/wait_till_done` answers 500 with the message when a collection ended in an error. A cancelled collection and a collection that only triggered a warning still answer 200. * A pending start failure is discarded by `/cancel` and `/deactivate`, as it already was by `/start` and `/initialize`. * `/scan_result` no longer reports the previous run's images after a collection that failed to start, or after `/deactivate`. * The TCP image stream protocol version is 4. `jfjoch_writer` and `jfjoch_broker` have to be of the same release, as before. Reviewed-on: #75	2026-08-27 22:16:54 +02:00