biophysics.uleth.ca lists
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

us-commits

Download
Threads by month
  • ----- 2026 -----
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2025 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
us-commits@biophysics.uleth.ca

  • 6666 discussions
[ehb54/ultrascan3] a11dc0: somo/doc: bump manual last-updated/last-modified d...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: a11dc0be21767815c933c548a3f40de397ea5fe4 https://github.com/ehb54/ultrascan3/commit/a11dc0be21767815c933c548a3f40de3… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html M us_somo/somo/doc/manual/somo/somo_misc.html Log Message: ----------- somo/doc: bump manual last-updated/last-modified dates Update both date fields (top "Last updated" and bottom "Last modified on") on somo_misc.html and somo_hydro.html to reflect the GRPY doc edits. Refs ehb54/ultrascan-tickets#987 To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] e34ae2: somo/doc: update manual for in-process GRPY, preci...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: e34ae2102472da996832c77372c968ca5a6d4e72 https://github.com/ehb54/ultrascan3/commit/e34ae2102472da996832c77372c968ca… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html M us_somo/somo/doc/manual/somo/somo_misc.html Log Message: ----------- somo/doc: update manual for in-process GRPY, precision, memory guard The GRPY overhaul (#972) and the memory guard (#987) left the SOMO manual stale/incomplete: - somo_misc.html documented the removed "Enable Parallel GRPY" checkbox and the Docker-based parallel path. Rewritten: GRPY now runs in-process, multi-threaded by default (no checkbox); notes the memory-lean/single-precision solver and the pre-flight memory guard, and points oversized models to single precision, a smaller model, or ZENO (size-independent, no rotational diffusion). Also softened the "GRPY can crash" note to the guarded behavior. - somo_hydro.html: document the new "GRPY Numerical Precision" (Double/Float) control; drop the stale "parallel GRPY ... July 2024 release" clause from the buried-beads paragraph. Release date in somo_misc.html marked with an HTML comment to confirm at release. Refs ehb54/ultrascan-tickets#987 Co-Authored-By: Claude Opus 4.8 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] de70ea: somo/grpy: clear grpy_used_beads at run start (fix...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: de70ea2fcf18a94984a1f865fb30dee38f26b8db https://github.com/ehb54/ultrascan3/commit/de70ea2fcf18a94984a1f865fb30dee3… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: clear grpy_used_beads at run start (fix stale count) grpy_used_beads was populated with push_back each run but, unlike its sibling lists (grpy_to_process, grpy_model_numbers), was never cleared at the top of calc_grpy_hydro -- it only drained via pop_front as models processed. So any run that aborts before processing (now including the pre-flight memory guard, but also the stop-flag and filename-length aborts) left a stale count behind, and the next run's max()/processing saw it. Observed as: a vdW model triggers the memory guard, then a subsequent smaller SoMo model in the same session is wrongly reported with the vdW bead count. Clear grpy_used_beads at run start, consistent with the other lists. Refs ehb54/ultrascan-tickets#987 Co-Authored-By: Claude Opus 4.8 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] a23a53: somo/grpy: memory guard - point oversized models t...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: a23a53982b33f7f85c4b33b422037f8355c0656a https://github.com/ehb54/ultrascan3/commit/a23a53982b33f7f85c4b33b422037f83… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: memory guard - point oversized models to ZENO Single precision only ~halves the footprint, so a genuinely huge structure (e.g. 20k beads ~90 GB single) still will not fit on a modest machine. Add ZENO to the guard's remedy message as the size-independent alternative, noting its limitation (it does not compute rotational diffusion). Refs ehb54/ultrascan-tickets#987 Co-Authored-By: Claude Opus 4.8 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 9107bb: somo/grpy: memory guard - add Windows physical-RAM...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: 9107bb46c07f34ea32ea5afe4a775af018020f3d https://github.com/ehb54/ultrascan3/commit/9107bb46c07f34ea32ea5afe4a775af0… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: memory guard - add Windows physical-RAM detection Windows is a shipped SOMO target (GRPY_win64) but was falling through to the "unknown -> no guard" path. Add GlobalMemoryStatusEx (ullTotalPhys) so the pre-flight memory guard applies there too. Mac/Linux paths unchanged; the Windows branch is #if'd out off-Windows and needs verifying on the win build. Refs ehb54/ultrascan-tickets#987 Co-Authored-By: Claude Opus 4.8 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] cf4ff5: somo/grpy: pre-flight memory guard for oversized m...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-987 Home: https://github.com/ehb54/ultrascan3 Commit: cf4ff58c731891c97b578dafc5b53166931a183e https://github.com/ehb54/ultrascan3/commit/cf4ff58c731891c97b578dafc5b53166… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: pre-flight memory guard for oversized models The in-process GRPY solver holds the tiled upper triangle of the 11N x 11N mobility matrix in RAM (peak ~ (11N)^2/2 * scalar bytes), so a model larger than physical RAM cannot fit in-core -- e.g. 20k beads needs ~180 GB double / ~90 GB single. Because the solve runs synchronously on the GUI thread, such a model previously sent the machine into heavy swapping with a frozen interface. Add a pre-flight guard in calc_grpy_hydro() before the batch starts: estimate peak memory for the largest selected model from its used-bead count and the chosen precision, read physical RAM (macOS hw.memsize / Linux sysconf; unknown -> no guard), and if the estimate exceeds ~70% of RAM: - interactive: a Cancel / Run-anyway dialog naming the estimate, the machine RAM, and the remedies (single precision, or a smaller model); - script mode (gui_script): never block on a dialog -- report the error to the editor and stderr and fail with a non-zero exit. Verified: a headless run of a 20,000-bead model on a 32 GB machine reports "~198.3 GB needed, 32.0 GB available" and exits non-zero pre-flight, instead of thrashing. Fixes ehb54/ultrascan-tickets#987 Co-Authored-By: Claude Opus 4.8 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] c9ac11: somo/doc: document the GRPY Numerical Precision co...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: c9ac1177ffb801eaf2ec54bf734b72f5329a554c https://github.com/ehb54/ultrascan3/commit/c9ac1177ffb801eaf2ec54bf734b72f5… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html Log Message: ----------- somo/doc: document the GRPY Numerical Precision control The Double/Float control shipped with the in-process GRPY work but was never documented -- a grep across the whole manual returned nothing for it, despite the box sitting directly above the shell-reduction one just added. Same file, same window, so it is described here in window order: buried-bead exclusion, precision, shell reduction. Explains what the setting actually governs (the precision in which the large internal matrix is stored and factored), why it matters (that matrix holds eleven quantities per bead and grows as the square of the bead count, so it is what limits the treatable model size), and that the tensor arithmetic and all subsequent processing stay in double precision regardless. States the accuracy cost from validation rather than in the abstract: every labelled observable is identical to the four significant figures displayed, with only the near-zero reoriented coupling terms differing. Recommends Double as the default nonetheless, since the benefit appears only when memory is the binding constraint. Fixes ehb54/ultrascan-tickets#984 Co-Authored-By: Claude Opus 5 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 95fec1: somo/doc: document GRPY shell reduction in the Hyd...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 95fec1cc63cc817cc419d9e1eeb4027a9793e0ad https://github.com/ehb54/ultrascan3/commit/95fec1cc63cc817cc419d9e1eeb4027a… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html Log Message: ----------- somo/doc: document GRPY shell reduction in the Hydrodynamics Options manual Adds a section to somo_hydro.html covering the new "GRPY Shell Reduction" box, placed after the GRPY buried-bead exclusion it generalizes, and bumps the page's Last updated stamp. Covers what the procedure does (repeated exact GRPY on progressively larger subsets of the most solvent-exposed beads, stopping when successive results agree, with the remaining error estimated by Richardson extrapolation), the three controls and their defaults, and why the check is nearly free. Gives particular attention to the "Require intrinsic viscosity" checkbox, since the hydrodynamic quantities do not tolerate reduction equally: at equal reduction the rotational diffusion error is ~1.8x the translational, and the intrinsic viscosity ~3.3x and systematically one-sided. It is the viscosity that determines when the procedure can stop, so requiring it costs much of the speed gain; when not required, the viscosity and the Einstein radius derived from it are withheld from the results rather than reported with a caveat, while being retained and annotated in the results file. Also answers, quantitatively, the question the preceding buried-bead paragraph explicitly left open ("would need an in depth investigation", supported only by preliminary 2021 tests on lysozyme): retaining >50% of beads changes the translational diffusion coefficient by ~0.02%, 30-50% by ~0.12%, 20-30% by ~0.5%, degrading rapidly below ~10%. Buried-bead exclusion typically retains ~40%, so that paragraph's regime is now measured. Notes the reported error bounded the true deviation in all 344 validation tests. Ends with the honest practical caveat: the gain grows with model size, is negligible for small models, and on top of the default buried-bead exclusion is typically 2-3x rather than the larger factors available from a completely unreduced model -- the lasting benefit being the error estimate, not the speed. All markup uses named entities, so the page remains pure ASCII under its declared ISO-8859-1 charset. Fixes ehb54/ultrascan-tickets#984 Co-Authored-By: Claude Opus 5 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 68384f: somo/grpy: wire shell reduction into SOMO with a H...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 68384f0bed49388d107ce8e4ae046097a44a8fba https://github.com/ehb54/ultrascan3/commit/68384f0bed49388d107ce8e4ae046097… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/grpy/grpy_shell.hpp M us_somo/develop/grpy/tests/test_shell.cpp M us_somo/develop/include/us_hydrodyn.h M us_somo/develop/include/us_hydrodyn_hydro.h M us_somo/develop/src/us_hydrodyn_grpy.cpp M us_somo/develop/src/us_hydrodyn_hydro.cpp M us_somo/develop/src/us_hydrodyn_settings.cpp Log Message: ----------- somo/grpy: wire shell reduction into SOMO with a Hydrodynamics Options control Adds the GUI control, settings persistence, and the call-site integration for the shell-reduction layer, plus two fixes that only an end-to-end run exposed. GUI: a "GRPY Shell Reduction" groupbox in the SOMO Hydrodynamic Calculation Options window, below GRPY Numerical Precision and alongside the buried-bead exclusion it generalizes. Off / On, a target-accuracy field, and a "require intrinsic viscosity" checkbox. Backed by hydro.grpy_shell{,_tol,_require_eta}, persisted in settings save/load/default and display_default_differences, mirroring grpy_single. gui_script `global grpy_shell` / `grpy_shell_tol` / `grpy_shell_require_eta` and GRPY_SHELL still override, for headless work. Intrinsic viscosity: when it was not required to converge (or was and did not), it is WITHHELD from the reported results rather than propagated with a caveat -- a value carrying a warning is still a value that gets used downstream. Withheld together with it is the GRPY Einstein radius: both are parsed from the same report line ("Zero frequency intrinsic viscosity eta 0", fields 1 and 2) and the radius is viscosity-derived, so it inherits the identical unreliability. Guarded at all three sites -- the per-model assignments and the cross-model accumulator. The values remain in the results file, annotated, for the record. Note the cross-model mean divides by the TOTAL model count, not a per-observable count, so a run mixing contributing and non-contributing models would silently corrupt it. That is safe only because this is a run-level setting: every model in a run either requires viscosity convergence or none does. Commented at the site. Two fixes found by running it, not by the unit tests: 1. When the ladder cannot meet the tolerance it runs out onto its final rung, which is the unreduced model -- so the result is exact. It was still reporting the last inter-rung gap as the error bar (1.68% on a 246-bead test), which describes the coarser rung just discarded, not the answer returned. Honest, since it bounds a true error of zero, but plainly misleading. A ShellReport ::unreduced flag now zeroes the bars and the annotation states that the result is exact. 2. The same path wrongly marked viscosity unreliable. An unreduced solve has nothing to converge, so viscosity is exact regardless of what was requested; withholding it would have discarded a perfectly good value. viscosity_ok() now short-circuits on unreduced. Six assertions cover both in tests/test_shell.cpp. Verified end to end on a bead model via gui_script: the annotation reports "98 of 98" beads (SOMO's ASA buried-bead exclusion having already reduced 246 -> 98, which is exactly why a model this size has nothing left to give), zero estimated error, no viscosity warning, and every observable bit-identical to the unreduced baseline. Clean libus_somo + app builds, no new warnings. Fixes ehb54/ultrascan-tickets#984 Co-Authored-By: Claude Opus 5 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 12fa3e: somo/grpy: self-validating shell reduction with re...
by emre brookes Aug. 6, 2026

Aug. 6, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 12fa3ee4567ed094364a5348644cc3fc2fb58b44 https://github.com/ehb54/ultrascan3/commit/12fa3ee4567ed094364a5348644cc3fc… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M us_somo/develop/grpy/README.md A us_somo/develop/grpy/grpy_exposure.hpp A us_somo/develop/grpy/grpy_shell.hpp M us_somo/develop/grpy/tests/run.sh A us_somo/develop/grpy/tests/test_shell.cpp M us_somo/develop/libus_somo.pro Log Message: ----------- somo/grpy: self-validating shell reduction with reported error bars GRPY costs O((11N)^3), so the bead count dominates. A dense bead packing is hydrodynamically screened -- interior beads sit in near-stagnant fluid and carry almost no force -- so the exact calculation can run on a surface-enriched subset. This generalizes the existing binary ASA buried-bead exclusion into a convergence test that reports the error it introduced. Method: Shrake-Rupley exposure per bead (1.4 A probe), keep the most-exposed ceil(f*N), solve on a doubling ladder of bead fractions, stop when the reported bar drops below tolerance. Three rungs give the convergence order from the ratio of successive gaps, so the remaining error is Richardson-extrapolated per observable. The ladder is geometric against O(N^3) and costs ~1.14x its final rung, so the check is nearly free; its final rung is the unreduced model, so an unreducible structure degrades to exactly today's behaviour. The bar bounds the true error: verified 92/92 (translational, 23 models, N=204-4068) and 252/252 (7 observables x 12 models x 3 tolerances) against unreduced exact GRPY. The observed convergence order (median 1.83) matches a value predicted independently by a raw reduction sweep, so the error model is derived rather than fitted. Selection is by target bead FRACTION, not a fixed exposure threshold: the buried fraction ranges ~1%-50% across model types, so one threshold gives wildly different cost per model while a fraction controls O(N^3) directly. Observables do not share a reduction frontier. Median error relative to D_t at equal reduction is 1.77x for D_r but 3.34x for intrinsic viscosity, which drove the stopping decision in 36/36 test cases. ShellOptions::require therefore lets the caller choose what must converge, and ShellReport::viscosity_unreliable tells the caller to withhold viscosity and the viscosity-derived Einstein radius when it was not converged; the values stay in the report for the record, with a warning appended. Known failure mode, guarded: on a degenerate exposure distribution (a perfect cubic lattice realizes ~9 distinct values over 216 beads) rungs swallow whole symmetry shells instead of refining, the estimated order comes out spuriously high, and the bar understated by ~1.4x. A floor caps extrapolation tightening at 2x the raw gap. That restores honesty on the lattice and is slack on every real model tested -- identical honesty, no speedup cost. The lattice is kept as a regression in tests/test_shell.cpp. MW and Rg are pinned to full-model values. Re-derived from a reduced bead list, MW would fall with the dropped beads (corrupting sedimentation and both viscosities, which are mass-normalized) and Rg would rise (a hollow shell has a larger radius of gyration than the solid body). Both are regression-tested. Disabled by default: with enabled=false the result is byte-identical to Solver::run, so results never move silently. On speed, honestly: against an unreduced model the gain reaches ~120x, but SOMO defaults to ASA buried-bead exclusion, which already removes most dead beads. Measured on that production baseline the incremental gain is ~2-3x, rising with model size. The durable contribution is the error bar -- the existing exclusion reports no uncertainty at all. Module only; the SOMO call site and GUI control follow separately. Co-Authored-By: Claude Opus 5 <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
  • ← Newer
  • 1
  • ...
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • ...
  • 667
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.