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] 2604d6: somo/grpy: break the shell viscosity tooltip onto ...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: 2604d632f4f228744bec8377554f0b68dffd8328 https://github.com/ehb54/ultrascan3/commit/2604d632f4f228744bec8377554f0b68… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_hydro.cpp Log Message: ----------- somo/grpy: break the shell viscosity tooltip onto sense-lines The tags make Qt treat the tip as rich text, so the lines fall where the sense does rather than at whatever width a single long line happens to take. The point that answers the question which prompted the rename -- that intrinsic viscosity is always computed, and always reported when shell reduction is off -- now stands on its own line instead of trailing a paragraph. 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] e89096: somo/grpy: name the shell viscosity checkbox for w...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-984 Home: https://github.com/ehb54/ultrascan3 Commit: e890967d575f7a8f9f5d487ac5ad6352207a0e4d https://github.com/ehb54/ultrascan3/commit/e890967d575f7a8f9f5d487ac5ad6352… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn_hydro.cpp M us_somo/somo/doc/manual/somo/somo_hydro.html M us_somo/somo/doc/manual/somo/somo_hydro_shell_reduction.html Log Message: ----------- somo/grpy: name the shell viscosity checkbox for what it gates " Require intrinsic viscosity " read as an on/off switch for the quantity itself. Because a disabled checkbox keeps its setting, unchecking it with shell reduction on and then switching the reduction off left an unchecked, greyed-out box that looked as though viscosity had been turned off for ordinary GRPY runs too -- and could not be turned back on without re-enabling the reduction. It never was off, and no behaviour changes here. With shell reduction off, ShellSolver::run() returns on the unreduced path having set viscosity_unreliable false; that flag is additionally cleared at the start of every run, there is exactly one solver construction site so nothing bypasses it, and it is the only thing that withholds [eta] or the viscosity-derived Einstein radius from the reported results. The setting reaches nothing else: the result-file name suffix and the non-default-settings report are both gated on grpy_shell. So this is a naming fix. "to converge" says that the box governs when the series of calculations may stop, not whether the quantity is computed -- intrinsic viscosity comes from the same matrix as every other quantity, at no additional cost, and is therefore always computed. A tooltip states the same in the window itself, the first in this one, following the newer MALS/DAD screens. The manual had it right but under the old name. Both pages are renamed to match, and somo_hydro.html now says explicitly that the checkbox bears only on the stopping decision, that the quantity is always computed, and that the retained setting has no effect at all while the option is off. 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] a8bd96: Add perceive validate: predict the coded residues ...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: a8bd967b8319fd9605340a9b23db8126f1820abf https://github.com/ehb54/ultrascan3/commit/a8bd967b8319fd9605340a9b23db8126… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive_somo.h M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/src/us_hydrodyn_perceive_somo.cpp M us_somo/develop/src/us_hydrodyn_script.cpp Log Message: ----------- Add perceive validate: predict the coded residues as if unknown Rebuilds every residue somo.residue does code, pretending it is unknown, and reports computed vbar, molvol and hydration against the stored values with a summary. The same idea as perceive compare, which does this for atom typing, but for the computed properties, and it exercises the whole pipeline including perception. That makes it the only end-to-end measure of accuracy. Chain termini and residues with unmodelled atoms are counted and skipped rather than quietly averaged in. Over seven structures and 1157 rebuilt residue instances, ordinary amino acids give mean absolute errors of about 2.7% on vbar and 2.1% on molvol, matching what the standalone harness claimed. The ligand rows are the interesting ones. Heme's computed volume is 32.6% above the stored value and NAD's is 28.1% above. Earlier work in this branch reached the same conclusion by a completely different route, using 3V both on the isolated molecule and by difference in context, and arrived at comparable numbers. Two independent methods agree the stored ligand volumes are around 30% low. NAD's computed vbar of 0.619 is also closer to the measured 0.620 than the stored 0.599 is. Heme's vbar comes out 24% low, which is the expected failure: it is a metalloporphyrin, Durchschlag and Zipper publish no increment for iron, and the engine reports the atom for review rather than inventing a value. Hydration is much the weakest of the three, around half the residues within half a water and systematically low, the misses being the polar and charged side chains. A per-type majority cannot express residue-specific hydration. This also confirms the pH coupling from the runtime side: residue_list carries pH-adjusted hydration, so aspartate reads 6.0 and glutamate 7.0, exactly the charged-carboxylate values, where the raw file fields give 1.0. The lookup counts one vote per residue name, since residue_list holds several entries for residues with ionization variants and counting each weights them more heavily purely for being pH-aware, which was enough to flip a borderline type and cost serine and threonine a water each. Refs ehb54/ultrascan-tickets#980 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] 94b65c: Wire the computed properties into SOMO and add a h...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 94b65c74df263037724748131118d4736d9c7b4a https://github.com/ehb54/ultrascan3/commit/94b65c74df263037724748131118d473… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive_somo.h M us_somo/develop/libus_somo.pro M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/src/us_hydrodyn_perceive_somo.cpp M us_somo/develop/src/us_hydrodyn_script.cpp Log Message: ----------- Wire the computed properties into SOMO and add a headless perceive libus_somo.pro did not list the four sources added since the perceiver work resumed, so the grid volume, psv engine, hydration lookup and residue builder were never compiled into the library at all. Registered, and the symbols are confirmed present in the built dylib. The Qt adapter now takes the bond graph from the new perceive overload and goes through somo_residue_builder, so a proposal made inside SOMO carries vbar, molvol and hydration rather than zeros. Tentative gained those three fields for callers that want the numbers instead of the text block. The hydration lookup is built from SOMO's own loaded residue_list, so a proposal is always consistent with the user's tables rather than a snapshot compiled into the binary. "perceive auto <pdb>" is the headless sub-command: every default accepted, nothing prompted, nothing written back to somo.residue. It also prints how many atoms were flagged, since in a pipeline nobody is watching the REVIEW block go past. Defaults are pinnable through gparams in the same way as covolume: perceive_psv, perceive_volume, perceive_hydration, perceive_volume_probe, perceive_volume_grid and perceive_bead_color. A reserved bead colour is a hard error rather than a silent substitution, because two of the reserved values exclude a bead from the hydrodynamic computation and accepting one would quietly produce a model missing beads. Verified end to end through us3_somo -g on 2CMD, whose citrate is genuinely not coded: vbar 0.542, molvol 186.56, and seven review flags. On the residue basis SOMO stores, that vbar corresponds to 0.607 for the free molecule against a literature value near 0.59 to 0.62. The proposed hydration of zero for a triacid is plainly too low, and all four hydroxyl oxygens come back flagged at 49% agreement, which is the intended behaviour: propose, then say what cannot be supported. Refs ehb54/ultrascan-tickets#980 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] 2468de: Fill in psv, anhydrous volume and hydration for ge...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 2468dee50e5528732bbd4bc222537c494a74dccc https://github.com/ehb54/ultrascan3/commit/2468dee50e5528732bbd4bc222537c49… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: A us_somo/develop/include/us_hydrodyn_hydration.h M us_somo/develop/include/us_hydrodyn_perceive.h A us_somo/develop/include/us_hydrodyn_residue_builder.h M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/perceiver/Makefile A us_somo/develop/perceiver/tests/builder.cpp M us_somo/develop/perceiver/tests/emit_residue.cpp A us_somo/develop/perceiver/tests/hydration.cpp A us_somo/develop/src/us_hydrodyn_hydration.cpp M us_somo/develop/src/us_hydrodyn_perceive.cpp A us_somo/develop/src/us_hydrodyn_residue_builder.cpp Log Message: ----------- Fill in psv, anhydrous volume and hydration for generated entries A generated somo.residue entry left vbar, molvol and hydration at zero. This computes all three and emits a complete entry, with anything still unset stated as "NOT SET" in the header so a partly filled entry always looks partly filled. Hydration lookup (us_hydrodyn_hydration.h/.cpp) Derived at run time from whatever somo.residue is loaded rather than embedded, so it cannot drift from the user's own tables. 1581 observations give 48 hybrid types, 41 of them confident and 7 flagged; flagged types are surfaced for review rather than silently defaulted, and ties break toward the lower water count, since under-hydrating a proposal the user will edit is safer than over-hydrating one they may accept unchanged. The per-atom values in somo.residue are a hand distribution of a per-residue Kuntz total rather than a per-atom rule, so this is a starting point for editing and says so. The residue total is the quantity with literature backing; tests confirm the totals reproduce Kuntz for 14 of 14 applicable residues, with Asp and Glu deliberately low because SOMO stores them protonated. One test records a gap Mattia suspected: every nucleotide entry carries zero hydration. It is asserted as the current state, so it turns red the day someone fills those in, which is when models built on the old values need revisiting. Orchestration (us_hydrodyn_residue_builder.h/.cpp) perceive, then psv, volume and hydration, then emit. emit_residue takes an optional Properties argument rather than including the new headers, which include it in turn. A generated tryptophan entry now gives vbar 0.753 against a stored 0.738, molvol 224.29 against 228.2, and hydration 2.0 against 2.0. Over twelve residues treated as unknown, computed molvol is within 2.32% of the stored values on average and never worse than 4.6%. The volume convention factor is specific to the radius set. The 1.204/1.131 measured previously came from 3V's default radii; this pipeline uses SOMO's own, which are smaller, so the right factors are 1.248 and 1.179. The factor tracks polarity as much as size, hydrophobics sitting near 1.26 to 1.29 and polar residues near 1.16 to 1.21, so the band split is placed below the hydrophobic cluster rather than at the midpoint, where it separated leucine from isoleucine and cost both 8%. Also corrects a comment that described the residue header's ASA field as a molecular weight column. Refs ehb54/ultrascan-tickets#980 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] eb2fff: Add the Durchschlag & Zipper psv engine
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: eb2fffb9b195733f5c397d8502e880d37c8be907 https://github.com/ehb54/ultrascan3/commit/eb2fffb9b195733f5c397d8502e880d3… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: A us_somo/develop/include/us_hydrodyn_psv.h M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/perceiver/Makefile A us_somo/develop/perceiver/tests/psv.cpp A us_somo/develop/src/us_hydrodyn_psv.cpp Log Message: ----------- Add the Durchschlag & Zipper psv engine Computes partial specific volume from published atomic volume increments, consuming the perceived atoms and the bond/ring graph added in the previous commit. Returns molar volume, vbar and a labelled decomposition -- atomic sum, covolume, ring decrement, electrostriction, ring and charge counts -- so a value can be audited rather than taken on trust. Atoms whose environment cannot be classified are reported for review rather than guessed. The covolume defaults off, since a residue is a monomeric unit and SOMO already adds one structure-level covolume in calc_vbar_updated; a flag turns it on for a standalone molecule. Only rings lying entirely inside the residue are charged, which is both correct chemistry and immunity to the spurious cross-residue rings that clashing coordinates produce. Two rules a naive implementation gets wrong, both verified against the published tables: The hydroxyl increment is topological, not a running count. A second NEIGHBOURING hydroxyl takes 0.4 but an isolated one is a fresh 2.3, so hydroxyls are clustered by whether their carrier atoms are bonded. 1,2-ethanediol comes out at 53.5 and 1,8-octanediol at 152.0, exactly the published calculated volumes; a running count reproduces neither. Guanidinium charges only the terminal nitrogens. Table 1's footnote limits the 8.0 increment "in Arg only to the two terminal N", so arginine's NE takes the amine value. Tests reproduce urea 44.2, glycerol 70.0 and all seven published group increments exactly, and give mean absolute error of 1.64% against the stored somo.residue vbar over the fifteen charge-neutral amino acids, none worse than 6%. Arginine and histidine sit outside that: the perceiver assigns them no formal charge while somo.residue stores them protonated, so they lose an electrostriction term. Arginine is essentially always protonated at physiological pH, so that is a perception gap for the deferred pH layer rather than ambiguous chemistry. Refs ehb54/ultrascan-tickets#980 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] aca818: Add SSSR ring perception and expose the perceived ...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: aca818535d29d2f0f1742799a0abe5ba3a9a4457 https://github.com/ehb54/ultrascan3/commit/aca818535d29d2f0f1742799a0abe5ba… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive.h M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/perceiver/Makefile A us_somo/develop/perceiver/tests/sssr.cpp A us_somo/develop/perceiver/tests/sssr_real.cpp M us_somo/develop/src/us_hydrodyn_perceive.cpp Log Message: ----------- Add SSSR ring perception and expose the perceived bond graph Prerequisite for the Durchschlag & Zipper volume increments, which charge a ring-formation decrement once per ring (3-ring 2.1 through >=9-ring 14.1). The perceiver exposed only an "aromatic" flag and never returned Bonds at all, so ring sizes and the topology needed to classify a nitrogen or oxygen environment were unavailable to any caller. Bonds gains "rings", the smallest set of smallest rings. find_sssr() is declared in the header so it can be unit-tested on hand-built adjacency with no geometry involved. A new perceive(atoms, bonds_out, explicit_bonds) overload hands the graph back; the existing signature delegates to it, so current callers are unaffected. SSSR is kept separate from find_rings(), which enumerates every simple 5- or 6-cycle and feeds aromaticity. That is the right input for "is this atom in a flat conjugated ring" but the wrong one for anything charged per ring: a fused bicyclic has three simple cycles and circuit rank two. Keeping them apart also leaves the validated perception untouched, confirmed by the regression figure holding at 99.833%. Method is the standard one for molecule-sized graphs: smallest cycle through each bond, then greedy smallest-first acceptance while a candidate covers a bond no accepted ring covers, until the circuit rank is reached. Rings beyond max_ring (12) are not sought, since the consumer charges a single large-ring term for everything from nine up. Tests sssr.cpp 35 checks on hand-built graphs: acyclic shapes, every ring size 3 to 9, ring with substituent, fused bicyclics (naphthalene, indole, purine) giving two rings rather than three cycles, spiro, bridged, three-fused, disconnected components, macrocycle beyond max_ring, idempotency, and that every reported ring is a genuine cycle. Also checks the arithmetic the counts drive: one 6-ring decrement reproduces the published phenylalanine volume, one 5-ring the proline one. sssr_real.cpp 18 checks on real coordinates through the whole perception path, over all eight demo structures. Phe {6}, Tyr {6}, Trp {5,6}, His {5}, Pro {5}, DA/DG {5,5,6}, DC/DT {5,6}, and Ala/Gly/Leu/Ser/Arg ring-free, with every instance of a type giving an identical signature. Some demo structures carry physically impossible geometry, which produces spurious small rings: 1AO6 models LYS536/NZ 0.73 A from LEU583/CG, shorter than any covalent bond, and 6LYZ has two oxygens 1.22 A apart. This yields 13 cross-residue and 12 three-membered rings across the demo set, none of them inside a residue, so no residue's own ring count is affected. The tests assert this as such: a cross-residue ring must be closed by an inter-residue bond that is neither a backbone link nor a disulfide, and no three-membered ring may lie within a single residue. Refs ehb54/ultrascan-tickets#980 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] 5a7d47: Remove local filesystem paths from perceiver files
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 5a7d47edafebb9346b8cf92280f645c67be9a70f https://github.com/ehb54/ultrascan3/commit/5a7d47edafebb9346b8cf92280f645c6… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/perceiver/.gitignore M us_somo/develop/perceiver/DECISIONS.md M us_somo/develop/perceiver/tools/calibrate_3v_context.py M us_somo/develop/perceiver/tools/psv_durchschlag.py M us_somo/develop/perceiver/tools/recalc_ligand_volumes.py Log Message: ----------- Remove local filesystem paths from perceiver files The repository is public, so absolute paths from a personal workspace should not appear in it. Five places carried them, all written by me: .gitignore a home-directory path naming where the demo PDBs were copied from DECISIONS.md the local clone location psv_durchschlag.py where the source PDFs happened to sit calibrate_3v_context.py a hardcoded default path to Volume.exe recalc_ligand_volumes.py the same The two tools now resolve Volume.exe from $VOLUME_EXE, else PATH, which is also what makes them runnable by anyone rather than only where that binary was built. Behaviour is otherwise unchanged; self-tests still pass. Refs ehb54/ultrascan-tickets#980 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] 53cb46: Native grid volume + analysis tools for vbar/molvo...
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 53cb46050ae922ae69b7ca5afe8018652c1d2f2e https://github.com/ehb54/ultrascan3/commit/53cb46050ae922ae69b7ca5afe801865… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: A us_somo/develop/include/us_hydrodyn_grid_volume.h M us_somo/develop/perceiver/DECISIONS.md A us_somo/develop/perceiver/Makefile M us_somo/develop/perceiver/README.md A us_somo/develop/perceiver/tests/grid_volume.cpp A us_somo/develop/perceiver/tools/calibrate_3v_context.py A us_somo/develop/perceiver/tools/hydration_table.py A us_somo/develop/perceiver/tools/psv_durchschlag.py A us_somo/develop/perceiver/tools/recalc_ligand_volumes.py A us_somo/develop/src/us_hydrodyn_grid_volume.cpp Log Message: ----------- Native grid volume + analysis tools for vbar/molvol/hydration Groundwork for filling the three fields a generated residue entry currently leaves at zero: psv (vbar), anhydrous molar volume, and hydration. Native grid volume (us_hydrodyn_grid_volume.h/.cpp, Qt-free) accessible A = { v : |v - c_i| > r_i + probe for every atom i } excluded E = { v : v not in A, and dist(v, A) > probe } volume = |E| * grid^3 probe 0 gives the bare van der Waals union, probe 1.4 the solvent-excluded volume. Interior cavities are deliberately not counted, which is what lets V(complex) - V(complex minus ligand) measure a bound ligand in context. Only the accessible/blocked boundary is dilated -- the nearest accessible voxel to any blocked voxel is always a boundary one -- so the cost is a surface rather than a volume, and a 0.25 A grid runs in about a second for a 1300-atom protein. This removes what would otherwise be a new external dependency on 3V (vossvolvox). 3V is retained only as the validation oracle: tests/grid_volume.cpp reproduces Volume.exe to within 0.8% on an isolated residue, a whole protein, and a bound-ligand difference, and adds analytic checks (single sphere, coincident spheres, and a sealed hollow shell whose cavity must not be counted). 10 checks, 0 failures. Analysis tools (prototypes, not built into libus_somo) psv_durchschlag.py Durchschlag & Zipper atomic volume increments, no fitting. Self-tests against the papers' own worked values before reporting anything. hydration_table.py derives a hybrid-type -> waters lookup from somo.residue; 36 of 48 types unanimous, 7 weak and flagged for review rather than silently defaulted. calibrate_3v_context.py calibrates the in-context difference method against residues whose volume we already know. recalc_ligand_volumes.py recomputes prosthetic-group volumes, guarded on elemental formula and on reproducing the stored value. DECISIONS.md records the findings behind these, including why the anhydrous volume field wants a 1.4 A probe rather than 0, and the measured-versus- calculated trap in the Durchschlag 1986 tables. The perceiver's hand-written test Makefile is force-added: the repository root ignores "Makefile" for the qmake-generated ones, which left the documented "make unit" impossible from a fresh clone. Refs ehb54/ultrascan-tickets#980 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] 334282: Fix bead colour field in generated residue entries
by emre brookes Aug. 8, 2026

Aug. 8, 2026
Branch: refs/heads/ehb54-issue-978 Home: https://github.com/ehb54/ultrascan3 Commit: 334282a13e665610a461cf04cad6af0cd9f17454 https://github.com/ehb54/ultrascan3/commit/334282a13e665610a461cf04cad6af0c… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-08 (Sat, 08 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive.h M us_somo/develop/src/us_hydrodyn_perceive.cpp Log Message: ----------- Fix bead colour field in generated residue entries emit_residue() wrote the residue's atom count into the bead line's COLOUR field. The bead line is hydration, colour, placing_method, chain, volume (US_Hydrodyn::read_residue_file, us_hydrodyn_load.cpp:509), so a generated entry's colour was whatever the atom count happened to be: - 6 atoms -> colour 6, RESERVED brown, which marks a bead as buried and EXCLUDES it from the hydrodynamic computation - 7 atoms -> colour 7, reserved for fused beads - 8 atoms -> colour 8, reserved for beads found exposed on re-check - >15 -> out of range entirely Six- to eight-atom ligands are common (glycerol has 6, phosphate 5), so this silently dropped beads from models built with a generated entry. Emit DEFAULT_BEAD_COLOR instead, defined once in us_hydrodyn_perceive.h with the documented colour list from the SOMO manual (somo_residue.html, Panel 3) and helpers bead_color_is_reserved() / bead_color_is_selectable() for the residue-definition UI. Default is 10 (light green), which the manual records as the Automatic Bead Builder's colour for non-coded residues; it is a single named constant so the policy can be changed in one place. Also spell out the remaining bead-line fields rather than emitting bare zeros. Refs ehb54/ultrascan-tickets#978 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
  • ← Newer
  • 1
  • ...
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • ...
  • 667
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.