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

August 2026

  • 1 participants
  • 404 discussions
[ehb54/ultrascan3] fbd259: somo: ask about open RasMol windows on exit, and s...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/somo-dev Home: https://github.com/ehb54/ultrascan3 Commit: fbd25903bcbb082bfa6ecbdb0ab776e277329c8a https://github.com/ehb54/ultrascan3/commit/fbd25903bcbb082bfa6ecbdb0ab776e2… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-09 (Sun, 09 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn.h M us_somo/develop/include/us_hydrodyn_pdb_parsing.h M us_somo/develop/src/us_hydrodyn_load.cpp M us_somo/develop/src/us_hydrodyn_other.cpp M us_somo/develop/src/us_hydrodyn_pdb_parsing.cpp M us_somo/develop/src/us_hydrodyn_pdb_tool.cpp M us_somo/develop/src/us_hydrodyn_saxs_1d.cpp M us_somo/develop/src/us_saxs_util_best.cpp M us_somo/develop/src/us_saxs_util_dmd.cpp M us_somo/develop/src/us_saxs_util_hydro.cpp M us_somo/develop/src/us_saxs_util_loads.cpp M us_somo/somo/doc/manual/somo/somo_pdb_parsing.html M us_somo/somo/doc/manual/somo/somo_pdb_parsing_expert_mode.html Log Message: ----------- somo: ask about open RasMol windows on exit, and skip heavy water Two housekeeping fixes for ehb54/ultrascan-tickets#1000. RasMol viewers are started by model_viewer() with startDetached(), so nothing held on to them. closeEvent() only ever looked at the legacy `rasmol` QProcess member, which is allocated but never started - its one launch() call sits inside #if defined( TODO_FIX_MOVIE_FRAME ) and uses a Qt3 API - so the check never fired and every viewer SOMO opened was left behind. Track the detached pids and ask on exit whether to close them or leave them open. Liveness and termination go through small portable helpers rather than QProcess, since a detached child has no QProcess to ask. "Skip solvent water molecules" now means light and heavy water everywhere. The main GUI reader already listed DOD, but the headless reader, the hydro reader, 1D SAXS, the PDB editor and the BEST/DMD exclusion lists each tested for HOH alone, so the same structure parsed differently depending on the route - 5PTI, 63 D2O residues, keeps 728 atoms instead of 539 through those paths. All of them now share one definition in us_hydrodyn_pdb_parsing.h. WAT stays out of it: that is SOMO's own explicit hydration water, not solvent to discard. Commit: 10d48cec080b53d282c4412ccfa6b46a44349c9f https://github.com/ehb54/ultrascan3/commit/10d48cec080b53d282c4412ccfa6b46a… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_pdb_parsing.h M us_somo/develop/src/us_hydrodyn_load.cpp M us_somo/develop/src/us_hydrodyn_pdb_parsing.cpp M us_somo/develop/src/us_hydrodyn_settings.cpp M us_somo/develop/src/us_saxs_util_hydro.cpp M us_somo/develop/src/us_saxs_util_loads.cpp M us_somo/etc/somo.config.new M us_somo/etc/somo.defaults.new M us_somo/somo/doc/manual/somo/somo_pdb_parsing.html M us_somo/somo/doc/manual/somo/somo_pdb_parsing_expert_mode.html Log Message: ----------- somo: add a "Skip deuterium atoms" PDB parsing option Neutron structures carry deuterium where an X-ray structure carries hydrogen - 5PTI has 103 of them in the protein, on top of its D2O. The hydrogen test the readers apply matches names beginning with H only, so those deuteriums survived parsing and arrived as unknown atoms; somo.residue codes them no better than it codes hydrogens. New option below "Skip hydrogen atoms", default on, applied in the same four readers. Unlike the hydrogen option it is live rather than greyed out, so the old behaviour is still reachable, with the deuteriums then falling to the missing atoms setting. Deuterium is recognized from the wwPDB element field (columns 77-78) where the file supplies it and from the atom name otherwise - a name test alone cannot tell a deuterium from the second letter of a two-letter element, "CD " being cadmium. Persisted through the JSON config alongside the other parsing options, and added to the somo.config/somo.defaults templates. Configs written before this option existed simply take the default, since load_config_json() lays down the hard-coded defaults before reading. Commit: f6627f7cd8c199bd5ffafc5c584bc570f9969003 https://github.com/ehb54/ultrascan3/commit/f6627f7cd8c199bd5ffafc5c584bc570… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn.h M us_somo/develop/src/us_hydrodyn.cpp M us_somo/develop/src/us_hydrodyn_script.cpp Log Message: ----------- somo: close RasMol viewers a gui_script opened, rather than orphaning them A gui_script never reaches closeEvent() - "exit" calls exit(0) directly, and gui_script_error() calls exit(-1) - so the exit prompt was not a hang risk (guiFlag is false for the duration of a script in any case). But it also meant nothing cleaned up: auto_view_pdb is on by default, so any script that loads a PDB without saying "norasmol" left a RasMol process behind on every run. Route all three script exits through gui_script_exit(), which closes the tracked viewers and says so on stdout. A script that wants them kept says rasmol leaveopen and "rasmol close" spells out the default. A script that runs off the end without "exit" hands back to the GUI, where the interactive prompt still applies - the viewers belong to whoever is now at the keyboard. Commit: 8423eafd59f9a43fec0aa39e679c25d4b852bb53 https://github.com/ehb54/ultrascan3/commit/8423eafd59f9a43fec0aa39e679c25d4… Author: emre brookes <ehb54(a)users.noreply.github.com> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn.h M us_somo/develop/include/us_hydrodyn_pdb_parsing.h M us_somo/develop/src/us_hydrodyn.cpp M us_somo/develop/src/us_hydrodyn_load.cpp M us_somo/develop/src/us_hydrodyn_other.cpp M us_somo/develop/src/us_hydrodyn_pdb_parsing.cpp M us_somo/develop/src/us_hydrodyn_pdb_tool.cpp M us_somo/develop/src/us_hydrodyn_saxs_1d.cpp M us_somo/develop/src/us_hydrodyn_script.cpp M us_somo/develop/src/us_hydrodyn_settings.cpp M us_somo/develop/src/us_saxs_util_best.cpp M us_somo/develop/src/us_saxs_util_dmd.cpp M us_somo/develop/src/us_saxs_util_hydro.cpp M us_somo/develop/src/us_saxs_util_loads.cpp M us_somo/etc/somo.config.new M us_somo/etc/somo.defaults.new M us_somo/somo/doc/manual/somo/somo_pdb_parsing.html M us_somo/somo/doc/manual/somo/somo_pdb_parsing_expert_mode.html Log Message: ----------- Merge pull request #506 from ehb54/ehb54-issue-1000 somo: ask about open RasMol windows on exit; skip heavy water and deuterium Compare: https://github.com/ehb54/ultrascan3/compare/8590afabf8d5...8423eafd59f9 To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 3bad99: perceiver: protein atom names win over two-letter ...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 3bad992100c7ec2c1c17f27ca04051e89f8f3417 https://github.com/ehb54/ultrascan3/commit/3bad992100c7ec2c1c17f27ca04051e8… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive_elements.h M us_somo/develop/perceiver/tests/tests_unit.cpp Log Message: ----------- perceiver: protein atom names win over two-letter elements Keying element inference on the residue name alone broke modified residues -- the very population this feature exists for. MSE, PTR, CGU and any renamed residue carry protein atom names (CA, CB, CD, NE) under a NON-standard residue name, so they took the ligand branch and every backbone CA became CALCIUM. That changed the hybrid, the radius, the grid volume and the hydration as well as the psv: alanine came back as vbar 0.171, molvol 83.9, hydration 4.0 instead of 0.739 / 87.4 / 1.0. Caught by re-running the 20-residue comparison rather than trusting the unit tests, which used real residue names and so never entered that branch. Resolution order is now explicit: 1. lone ion atom name == residue name ("CA" in residue "CA") 2. standard residue leading letter 3. protein atom name leading letter, whatever the residue is called 4. two-letter element FE, CL, SE, BR, CU, ZN, MG 5. leading letter Step 3 is the one that makes modified and renamed residues work, and it is why "SE in MSE" still resolves to selenium while "CA in MSE" resolves to carbon: the collision set is atom NAMES, not residues. 86 checks, 0 failures, with MSE/PTR/CGU/renamed cases in the suite. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 0af114: perceiver: emit psv at the table temperature, not ...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 0af114235e228655fac50e08d209d20d2e66c116 https://github.com/ehb54/ultrascan3/commit/0af114235e228655fac50e08d209d20d… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_residue_builder.h M us_somo/develop/perceiver/tests/builder.cpp M us_somo/develop/src/us_hydrodyn_residue_builder.cpp Log Message: ----------- perceiver: emit psv at the table temperature, not the increments' The Durchschlag & Zipper increments describe 25 C. somo.residue is a 20 C table -- SOMO itself converts with tc_vbar() using 4.25e-4 cm^3 g^-1 K^-1. The perceiver applied no conversion at all, so every generated entry was 5 K x 4.25e-4 = 0.0021 cm^3/g high: about +0.3%, small enough to read as method noise and not noise at all. Found by comparing against Mattia Rocco's independent recalculation. Matching the temperature reference collapses the disagreement: residue vs his 25 C vs his 20 C GLY ALA VAL -0.07 .. +0.02% +0.20 .. +0.33% LEU ILE THR CYS MET PHE TRP ASN GLN SER +0.07% +0.41% ASP +0.16% +0.52% 14 of 20 residues agree to within +-0.07% once the reference matches. His conversion itself is exact, which was the other possibility Mattia raised: the dv/dT implied by his 25 C and 20 C columns is 4.2500e-04 for all 20 residues with ZERO spread, and equals SOMO's tc_vbar coefficient. No rounding error there -- the discrepancy was entirely on this side. The temperatures and the coefficient are Options fields rather than literals, so a table at another reference temperature is a parameter change. builder.cpp gains the check: ALA psv 0.7413 at 25 C -> 0.7392 at 20 C, which is Rocco's tabulated 20 C value exactly. 57 checks, 0 failures. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 2ee2c6: perceiver: element inference must key on the resid...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 2ee2c6af7d1ce944ea384d34deff28ac864df569 https://github.com/ehb54/ultrascan3/commit/2ee2c6af7d1ce944ea384d34deff28ac… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive_elements.h M us_somo/develop/perceiver/tests/tests_unit.cpp Log Message: ----------- perceiver: element inference must key on the residue, not the atom name The previous rule took the leading letter unless the atom name equalled the residue name. That is right for proteins and wrong for ligands -- exactly the population this code exists for. Six of fifteen test cases failed: FE in HEM -> F (fluorine) CU in CUA -> C CL in CIT -> C SE in MSE -> S NA in XYZ -> N BR in LIG -> B so a heme iron contributed a fluorine volume, silently. The discriminator is the RESIDUE. In a standard residue the naming convention is fixed and the element is always the leading letter: CA is the alpha carbon, NE2 a nitrogen, SD a sulfur. In a ligand it is not, and a two-letter atom name that matches a known element is that element. Residual ambiguity, stated in the header: a ligand carbon named bare "CA" reads as calcium. Ligand carbons are normally C1/CAA/CB1, and the psv now refuses to compute rather than guessing when an element cannot be resolved, so the failure is visible either way. Answers the question directly: with this, a PDB with no element column is handled correctly for proteins AND for ligands with two-letter elements. Without it, only proteins were safe. 79 checks, 0 failures. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 34d7c5: perceiver: never compute a psv from unidentified e...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 34d7c5b303f2d8b0ee75f4c88c13badba270c3f3 https://github.com/ehb54/ultrascan3/commit/34d7c5b303f2d8b0ee75f4c88c13badb… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_perceive_elements.h M us_somo/develop/perceiver/tests/tests_unit.cpp M us_somo/develop/src/us_hydrodyn_perceive_somo.cpp M us_somo/develop/src/us_hydrodyn_psv.cpp Log Message: ----------- perceiver: never compute a psv from unidentified elements A PDB with an empty element column (77-78) produced psv values of 0.001, -0.068, -0.087 -- meaningless numbers that still look like numbers. 1AO6-compl_monA.pdb in the demo set is such a file, which is how it surfaced. Two independent defects, either alone enough: 1. The atom-name fallback used norm_element(), which only strips non-alphabetics. So the alpha carbon "CA" became CALCIUM, "NE2" became NEON, and "CB", "CG", "OD1" matched no element at all. Every atomic volume increment then evaluated to zero and the sum collapsed to roughly the electrostriction terms. element_from_atom_name() takes the leading letter, accepting a two-letter element only when the atom name equals the residue name -- HETATM "CA" in residue "CA" is calcium, "CA" in "ALA" is carbon. 2. somo_psv::compute() reported ok on a residue containing atoms it had no increment for. It now counts them, records why in the review block, and returns ok == false, so the caller emits no psv rather than a plausible figure. An unidentified element is not a small error; it is not a volume. The grid volume was unaffected and still looked sensible (Ala 77.45 A^3), which is precisely why this was not obvious from the output. tests_unit.cpp gains the case that catches it: CA/CB/CG1/OD1/NE2/NZ/SD/OXT must resolve by leading letter, while CA-in-CA, FE-in-FE, ZN-in-ZN, MG-in-MG resolve as the two-letter element. 69 checks, 0 failures. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] f6627f: somo: close RasMol viewers a gui_script opened, ra...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-1000 Home: https://github.com/ehb54/ultrascan3 Commit: f6627f7cd8c199bd5ffafc5c584bc570f9969003 https://github.com/ehb54/ultrascan3/commit/f6627f7cd8c199bd5ffafc5c584bc570… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn.h M us_somo/develop/src/us_hydrodyn.cpp M us_somo/develop/src/us_hydrodyn_script.cpp Log Message: ----------- somo: close RasMol viewers a gui_script opened, rather than orphaning them A gui_script never reaches closeEvent() - "exit" calls exit(0) directly, and gui_script_error() calls exit(-1) - so the exit prompt was not a hang risk (guiFlag is false for the duration of a script in any case). But it also meant nothing cleaned up: auto_view_pdb is on by default, so any script that loads a PDB without saying "norasmol" left a RasMol process behind on every run. Route all three script exits through gui_script_exit(), which closes the tracked viewers and says so on stdout. A script that wants them kept says rasmol leaveopen and "rasmol close" spells out the default. A script that runs off the end without "exit" hands back to the GUI, where the interactive prompt still applies - the viewers belong to whoever is now at the keyboard. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 10d48c: somo: add a "Skip deuterium atoms" PDB parsing option
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-1000 Home: https://github.com/ehb54/ultrascan3 Commit: 10d48cec080b53d282c4412ccfa6b46a44349c9f https://github.com/ehb54/ultrascan3/commit/10d48cec080b53d282c4412ccfa6b46a… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn_pdb_parsing.h M us_somo/develop/src/us_hydrodyn_load.cpp M us_somo/develop/src/us_hydrodyn_pdb_parsing.cpp M us_somo/develop/src/us_hydrodyn_settings.cpp M us_somo/develop/src/us_saxs_util_hydro.cpp M us_somo/develop/src/us_saxs_util_loads.cpp M us_somo/etc/somo.config.new M us_somo/etc/somo.defaults.new M us_somo/somo/doc/manual/somo/somo_pdb_parsing.html M us_somo/somo/doc/manual/somo/somo_pdb_parsing_expert_mode.html Log Message: ----------- somo: add a "Skip deuterium atoms" PDB parsing option Neutron structures carry deuterium where an X-ray structure carries hydrogen - 5PTI has 103 of them in the protein, on top of its D2O. The hydrogen test the readers apply matches names beginning with H only, so those deuteriums survived parsing and arrived as unknown atoms; somo.residue codes them no better than it codes hydrogens. New option below "Skip hydrogen atoms", default on, applied in the same four readers. Unlike the hydrogen option it is live rather than greyed out, so the old behaviour is still reachable, with the deuteriums then falling to the missing atoms setting. Deuterium is recognized from the wwPDB element field (columns 77-78) where the file supplies it and from the atom name otherwise - a name test alone cannot tell a deuterium from the second letter of a two-letter element, "CD " being cadmium. Persisted through the JSON config alongside the other parsing options, and added to the somo.config/somo.defaults templates. Configs written before this option existed simply take the default, since load_config_json() lays down the hard-coded defaults before reading. To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 893ca3: fix: raw newline inside a string literal from a sc...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 893ca35e20958e29ab777e19c6ece7969242cf35 https://github.com/ehb54/ultrascan3/commit/893ca35e20958e29ab777e19c6ece796… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/src/us_hydrodyn.cpp Log Message: ----------- fix: raw newline inside a string literal from a scripted edit To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 88a248: fix: perceived_entries member must not live in a s...
by emre brookes Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/ehb54-issue-980 Home: https://github.com/ehb54/ultrascan3 Commit: 88a24853e7729bacff2f5b2100e852f36e34e3bd https://github.com/ehb54/ultrascan3/commit/88a24853e7729bacff2f5b2100e852f3… Author: ehb54 <brookes(a)uthscsa.edu> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M us_somo/develop/include/us_hydrodyn.h Log Message: ----------- fix: perceived_entries member must not live in a slots block (moc) To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
[ehb54/ultrascan3] 05443d: [3c]GMP-VELOCITY-MWL: 5.ANALYSIS -- after MPI anal...
by alexsav815 Aug. 10, 2026

Aug. 10, 2026
Branch: refs/heads/alexey-dev-issue983 Home: https://github.com/ehb54/ultrascan3 Commit: 05443d3866e8bfadf228afd9dd5ce028d97860c6 https://github.com/ehb54/ultrascan3/commit/05443d3866e8bfadf228afd9dd5ce028… Author: alexsav815 <alexsav.science(a)gmail.com> Date: 2026-08-10 (Mon, 10 Aug 2026) Changed paths: M programs/us_autoflow_analysis/us_autoflow_analysis.cpp M programs/us_mwl_species_sim/us_mwl_species_sim.cpp Log Message: ----------- [3c]GMP-VELOCITY-MWL: 5.ANALYSIS -- after MPI analysis ends, proceed with MWL pre-fit simulations; .pro & respective CMake file edited accordingly ... To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications
1 0
0 0
  • ← Newer
  • 1
  • ...
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • ...
  • 41
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.