leonarski_fandClaude Opus 5.5
e8584423c6
The rotation merge's resident device engine (RotationScaleMerge's GPU half) lived to the end of the scale-merge step, so model validation reserved its own engines on a card the merge still held: on the F432 1.30 A set 8.8 GB of the 16.6 GB card was taken when the validation started. Nothing after the validation reads the engine except the opt-in finalist ledger's P1 merge, which runs on it beside the validation; so, unless that merge is running, the engine is released just before the validation call. Device memory in use when the validation starts: 8.8 GB -> 2.2 GB; the validation window's device-wide peak is now 6.5 GB (structure factors 2.2 GB, ten rigid-body engines 2.5 GB). p.mtz md5-identical. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SVmAWnzCmRKAXVUCdc4iNi
Jungfraujoch
Application to receive and analyse data from the PSI JUNGFRAU and EIGER detectors, together with
rugnux, its program for processing stored diffraction data - rotation and serial, macromolecular
and small-molecule - from images to merged reflections.
All documentation is now placed in docs/ subdirectory and for the current version hosted on Jungfraujoch Read The Docs page.