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] 908b2f: somo/doc: link the shell-reduction theory page fro...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 908b2ffbbc38781d8e1125ca14ee1184630ed3e2 https://github.com/ehb54/ultrascan3/commit/908b2ffbbc38781d8e1125ca14ee1184… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html Log Message: ----------- somo/doc: link the shell-reduction theory page from the section head and the accuracy text The theory page had a single inbound link, buried in the second of eight paragraphs. A reader arriving at the box heading, or skimming to the accuracy figures, would not have seen it. Now linked from three places, each where a reader would want it: the opening paragraph, which poses the question the page answers; the Richardson sentence, which names the method; and the accuracy paragraph, from which the natural next question is how far the estimate has been tested. Dates: both stamps on both pages already read the current date, so nothing to bump. somo_misc.html carries an earlier date but is upstream's edit, correctly stamped for itself. 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] f9bdfd: somo/doc: theory page for GRPY shell reduction, wi...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: f9bdfd141549a30df1cab9c799cc167486a11659 https://github.com/ehb54/ultrascan3/commit/f9bdfd141549a30df1cab9c799cc1674… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html A us_somo/somo/doc/manual/somo/somo_hydro_shell_reduction.html Log Message: ----------- somo/doc: theory page for GRPY shell reduction, with the mathematics and references The user-facing documentation named Richardson extrapolation in a single sentence and stopped there. The mathematics existed only in the module README and the header comments, neither of which a SOMO user reads. New page somo_hydro_shell_reduction.html, following the existing theory-page pattern (cormap.html, IntegralBaselineTheory.html), linked from the sentence that previously stood alone. It covers why bead count dominates the cost, how the subsets are chosen and why by fraction rather than by exposure threshold, the extrapolation itself, the safeguards, per-quantity convergence, the extent of the testing, and what the option is and is not for. Every formula and constant on the page was checked against the implementation rather than written from memory: the order equation, the remaining-error and extrapolated-value expressions, the clamp range, the 1.5 safety factor, the half-the-raw-gap floor, the default ladder, and the 8/7 geometric cost. Two things it makes explicit that the documentation did not say anywhere: - The extrapolation needs THREE subsets. A run that stops after two -- because it converged at once, or because memory allowed no more -- reports the raw inter-rung difference instead. Still conservative, but cruder, and decided by how the ladder happens to stop rather than by anything the user set. - "Shell reduction" is NOT the classical shell model. That method replaces the particle with surface beads and extrapolates to zero bead radius; this one retains existing beads and extrapolates to the complete model. Same physical motivation, both extrapolations to a limit, different procedures -- and an easy confusion for exactly this audience. References: Richardson 1911 and Richardson & Gaunt 1927 for the method; Roache 1994/1998 for the three-level observed-order practice this follows (the Grid Convergence Index, with bead count in place of grid spacing); Shrake & Rupley 1973 for the exposure calculation; Garcia de la Torre & Bloomfield 1981 and Carrasco & Garcia de la Torre 1999 for the shell-model context distinguished above; Zuk et al 2018 and Brookes & Rocco 2018 for GRPY and SOMO. 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] 7d2452: somo: untrack revision.sh and moc artifacts commit...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 7d245291648635d6ac78b2781985c39d165d406a https://github.com/ehb54/ultrascan3/commit/7d245291648635d6ac78b2781985c39d… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: R us_somo/develop/revision.sh R us_somo/develop/us_saxs_cmds_t/moc_predefs.h R us_somo/develop/us_saxs_cmds_t/moc_us_cmdline_app.cpp Log Message: ----------- somo: untrack revision.sh and moc artifacts committed by mistake The previous commit staged with `git add -A us_somo`, which swept in three files that were untracked for good reason: - us_somo/develop/revision.sh -- somo-dev deliberately removed this from the tree; each clone supplies its own untracked copy, and qmake runs it as a FORCE target on every build. Tracking it both reverses that decision and makes every build dirty the working tree. - us_saxs_cmds_t/moc_predefs.h, moc_us_cmdline_app.cpp -- moc output, i.e. build artifacts. Tracking them also broke `git pull` for anyone holding their own copies: "untracked working tree files would be overwritten by merge". Removed from the index only; the local files are untouched. Anyone whose pull was blocked can now pull cleanly -- the net change across the two commits does not touch these paths, so their local copies are left alone. 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] 104ed9: somo/grpy: optionally write and display a bead mod...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 104ed92bc56aef41aaa36f39ccb10212f3422f74 https://github.com/ehb54/ultrascan3/commit/104ed92bc56aef41aaa36f39ccb10212… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/grpy/grpy_exposure.hpp 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 A us_somo/develop/revision.sh 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 M us_somo/develop/src/us_hydrodyn_write.cpp A us_somo/develop/us_saxs_cmds_t/moc_predefs.h A us_somo/develop/us_saxs_cmds_t/moc_us_cmdline_app.cpp M us_somo/somo/doc/manual/somo/somo_hydro.html Log Message: ----------- somo/grpy: optionally write and display a bead model of each shell rung A "Save shell bead models" checkbox in the GRPY Shell Reduction box. When set, the reduced model used at each ladder rung is written and opened in the viewer, so the shell can be seen thickening as the ladder converges and the retained beads inspected directly. For validating the reduction by eye; off by default. Files go to <somo>/tmp as <model>-shell-rung-<n>, overwritten without prompting -- they are regenerated every run, and prompting per rung would add a modal dialog per rung to a diagnostic. The mapping from the shell report back to beads was the part worth care. ShellReport now records the indices its ranking selected (ShellOptions:: record_subsets, off by default, so nothing is paid when unused), and those index the bead list handed to GRPY -- i.e. the .grpy file, which holds the beads that are active and, unless buried beads are included, not buried, in `use_model` order. That order is NOT bead_model order: bead_output.sequence == 1 reorders into exposed-sidechain / exposed-main-chain / buried. Taking bead_model order would therefore have written models of the wrong beads, silently and plausibly. To make that impossible rather than merely correct today, the ordering is extracted from write_bead_model() into US_Hydrodyn::bead_model_output_order() and both callers use it. The writer also refuses and says so if an index falls outside the rebuilt list, rather than emitting a wrong picture. Selection now returns indices (reduce_top_frac_idx), which also removes the old coordinate-matching rebuild -- O(keep*N), some 32M comparisons on an 11328-bead model -- with reduce_top_frac kept as a wrapper so existing callers and tests are unaffected. Tests: recorded subsets are sized to their rung, in range, unique, nested (each rung contains the previous), complete on the full rung, absent unless requested, and identical to the ranking's own selection. 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] 8dcc49: somo/grpy: exclude the overwrite prompt from the G...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 8dcc49382cade039accd9f266f8b37ac37448176 https://github.com/ehb54/ultrascan3/commit/8dcc49382cade039accd9f266f8b37ac… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: exclude the overwrite prompt from the GRPY timer "Time to process" spans the whole run, and the results-writing path prompts for a filename whenever an output file exists and overwrite_hydro is false. That prompt is modal, so the operator's response time was counted as compute. Measured directly: the same binary, model and settings gave 5m 00s answering slowly and 3m 49s answering quickly -- 71 s of pure click latency, varying per run, which makes interactive GRPY timings incomparable with each other. It also cost real analysis time here: a 21% gap between two runs was attributed to machine contention on the strength of a microbenchmark that bounded the alternative explanation at ~3%. The bound was right; the conclusion was wrong. The missing time was the operator. US_Timer already supports this exactly: stop_timer banks the interval so far WITHOUT counting a completion, and start_timer restarts from zero, so stop/start is pause/resume and the paused span is never accumulated. No change to US_Timer. An RAII guard applies it at the four prompt sites that fall inside the timed region; the fifth call runs before the timer starts and is untouched. The prompt itself is deliberately unchanged -- this only stops it being counted as compute. 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] 8599c8: somo/doc: say that the quoted shell-reduction erro...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 8599c88d5ecbfe77c3688ccf953369d0afd7017f https://github.com/ehb54/ultrascan3/commit/8599c88d5ecbfe77c3688ccf953369d0… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/somo/doc/manual/somo/somo_hydro.html Log Message: ----------- somo/doc: say that the quoted shell-reduction error is the largest over quantities The page said the achieved error is written to the results file, but not that the single figure shown in the progress window is the MAXIMUM over the requested quantities. Since intrinsic viscosity converges far more slowly than the rest, that figure is usually its, and reading it as the accuracy of the translational diffusion coefficient understates the latter severalfold -- a misreading a real run produced. 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] ede8e9: Report time and wavelength units in UV-Vis file he...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-991 Home: https://github.com/ehb54/ultrascan3 Commit: ede8e9a28ff5ed7db03f418db4677eef0f860e60 https://github.com/ehb54/ultrascan3/commit/ede8e9a28ff5ed7db03f418db4677eef… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_dad.h M us_somo/develop/src/us_hydrodyn_dad.cpp Log Message: ----------- Report time and wavelength units in UV-Vis file headers The UV-Vis module wrote its saved and viewed .dat headers with a hardcoded SAXS abscissa: both save_file() and view() started from a fixed " q units:1/A" and emitted q / I(q) column names for anything with f_is_time false. A(t) curves at a fixed wavelength are in time and A(lambda) curves at a fixed time are in nm, so neither was q, and the headers contradicted the plot axes, which already labelled the same curves Time [s] and lambda [nm]. Factor the duplicated blocks into header_units() and header_column_names(), keyed on the same _UV-Vis_ plus f_is_time pair update_enables() uses for its axis titles. Genuinely q-based curves in this module (_Rt_q, _Ihasht_q, _UV_Vis_Istarq_t) keep the q header. The same conflation of "not time" with "is q" corrupted data on load: use_units carries the 1/nm to 1/Angstrom q conversion from the global SAS option, and was applied to every non-time file, so reloading a saved A(lambda) curve with that option enabled multiplied every wavelength by 0.1. Force use_units to 1.0 for UV-Vis wavelength files, alongside the two existing special cases, testing both the new header token and the file name so files saved by earlier versions are covered. Also omit zero-valued PSV, I0se and I0st on UV-Vis curves; they are set unconditionally when A(lambda) curves are made and carry no meaning on absorbance data. Refs ehb54/ultrascan-tickets#991 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] 0c57fb: somo/grpy: rate-limit progress calls; they cost mo...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 0c57fbfc96e735c40ff26c82c9a1b31bfeeb0916 https://github.com/ehb54/ultrascan3/commit/0c57fbfc96e735c40ff26c82c9a1b31b… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/grpy/grpy_core.hpp M us_somo/develop/grpy/linalg.hpp Log Message: ----------- somo/grpy: rate-limit progress calls; they cost more than the work they report A run whose ladder stopped at the same rungs as an earlier one took 8m20s against 4m09s. Requiring intrinsic viscosity adds no computation -- it only changes when the ladder stops -- so the doubling was the progress reporting added in 4e14d5f3. Progress has two independent problems and one knob cannot solve both: FREEZE LENGTH -- the calling thread is a compute worker, so the event loop cannot turn until the current slice ends. Fixed by sizing the slice. CALL RATE -- the callback itself costs something, paid per call however short the slices are. In SOMO it is qApp->processEvents() against an editor buffer that grows all session, which is why this hurt a long run and not a short one. Nothing controlled this at all: solve() ticked once per tile, up to 2*nt calls -- hundreds on a large model -- against an operation that is cheap next to the factor. tune_chunk now times only the work, never the callback. Timing them together made an expensive callback SHRINK the chunk, which raises the call rate and makes the overhead worse -- the opposite correction. That defect was real but was not the main cost: fixing it alone moved 80 calls to 73. ProgressGate is the actual fix. It rate-limits emissions against what the callback measurably costs: emit after ~10x the last callback's duration, and never more often than every ~80 ms. A cheap callback is essentially unthrottled; an expensive one throttles itself to ~10% overhead instead of dominating. Applied to assembly, factor and solve. Measured, 512-bead model with a 20 ms callback: 80 calls and 2.79x the whole solve before, 11 calls and 1.03x after. A trivial callback is 0.98x, i.e. the chunking machinery itself costs nothing. The tradeoff is deliberate: frequent repaints and low overhead are not both achievable when a repaint is expensive. This favours throughput, so the bar updates less often exactly where updating is costly. 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] faf147: somo: silence the per-atom debug dump at the end o...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: faf147fa301e7485b3f1f68bb4c54fceee7f4c70 https://github.com/ehb54/ultrascan3/commit/faf147fa301e7485b3f1f68bb4c54fce… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_load.cpp Log Message: ----------- somo: silence the per-atom debug dump at the end of calc_mw() It printed "end of calc_mw()" and then one CSV row per atom on every PDB load -- thousands of lines for a large structure -- which slows a debug cycle when stdout is a terminal or an editor shell. Commented rather than deleted: it is diagnostic, not dead, and is the thing to re-enable when ionization or net-charge numbers look wrong. Left with a note of the caveat that made it misleading anyway -- its pH is hardwired to 7 rather than read from the form, so it does not describe the pH actually in use; the already-commented call immediately above is the variant that does. Matches the several other commented-out info_* diagnostics around it. 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] f3e555: somo/grpy: name the worst observable, and stop ann...
by emre brookes Aug. 7, 2026

Aug. 7, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: f3e555a32854d3ee39df4d5df0901640384580c2 https://github.com/ehb54/ultrascan3/commit/f3e555a32854d3ee39df4d5df0901640… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-07 (Fri, 07 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_grpy.cpp Log Message: ----------- somo/grpy: name the worst observable, and stop announcing an inert cap Both found by a real capped run (3GUT vdW, GRPY_SHELL_MAX_BEADS=2000). The result line quoted err_max alone: "estimated error 3.85%". That is the MAX over the requested observables, and intrinsic viscosity runs ~3.3x the error of D_t at equal reduction, so on an unconverged run the single number quoted is essentially always the viscosity's. Reading it as the accuracy of the whole calculation makes D_t look several times worse than it is -- in that run, 1416 of 11328 beads kept implies a D_t bar near 1.15%, not 3.85%. ShellReport::worst was already computed for exactly this and had never been shown; it is now named, with a following line pointing at the per-observable estimates in the results file. Suppressed on an exact (unreduced) result, where every bar is zero and "worst" means nothing. The cap override also announced itself when shell reduction was OFF, where it bounds nothing: the same run printed "bead cap OVERRIDDEN to 2000" and then refused the model on memory, implying the 2000 had caused the refusal when it was irrelevant. It now says so when inert, rather than going silent -- a stale environment variable should still be visible. 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
  • ← Newer
  • 1
  • ...
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • ...
  • 667
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.