[us-commits] [ehb54/ultrascan3] 777461: Fix peak-averaging falling back to stale curves fo...

emre brookes noreply at github.com
Mon Jun 22 14:08:06 MDT 2026


  Branch: refs/heads/somo-dev-claude
  Home:   https://github.com/ehb54/ultrascan3
  Commit: 777461f53eafdbeb70fa7512e042f5f43b4e19df
      https://github.com/ehb54/ultrascan3/commit/777461f53eafdbeb70fa7512e042f5f43b4e19df
  Author: ehb54 <brookes at uthscsa.edu>
  Date:   2026-06-22 (Mon, 22 Jun 2026)

  Changed paths:
    M us_somo/develop/src/us_hydrodyn_saxs_hplc_makeiq.cpp

  Log Message:
  -----------
  Fix peak-averaging falling back to stale curves for single-curve peaks

avg() silently refuses to average fewer than 2 selected curves (by
design, for the interactive "average selected" button), but a
Gaussian peak's "top %" intensity window can easily select just one
curve. When that happened, both avg() calls in the peak-averaging
loop were silently no-ops, and the code went on to read whatever
curve happened to be last in the list -- a leftover from a previous
peak's iteration -- instead of a real result for this peak. That
explained curves with no _n/_c suffix and curves from different
peaks ending up identical/overlapping with mismatched concentrations.

Single-curve peaks are now detected and handled directly (the lone
normalized curve, or lone raw curve when no concentration data is
available, is used as the result without attempting to average it
with itself), so every peak always gets its own correctly named and
correctly scaled curve.

Co-Authored-By: Claude Sonnet 4.6 <noreply at anthropic.com>



To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications


More information about the us-commits mailing list