Skip to content

Revert the polydisp table to the original state on model change#3768

Merged
wpotrzebowski merged 1 commit intomainfrom
3536-polydispersity-confused
Nov 17, 2025
Merged

Revert the polydisp table to the original state on model change#3768
wpotrzebowski merged 1 commit intomainfrom
3536-polydispersity-confused

Conversation

@rozyczko
Copy link
Copy Markdown
Member

Description

Running a fit with polydisperse parameters checked adds an error column to the polydisp table.
This is OK when just running the fit - the min/max/npts/nsigs/function combobox columns get shifted and display ok.
But when a model is changed AFTER the fitting, the table is not properly reindexed.
THis PR fixes the issue.

Fixes # 3536

How Has This Been Tested?

Local win 10 testing

Review Checklist:

[if using the editor, use [x] in place of [ ] to check a box]

Documentation (check at least one)

  • [ X] There is nothing that needs documenting
  • Documentation changes are in this PR
  • There is an issue open for the documentation (link?)

Installers

  • There is a chance this will affect the installers, if so
    • Windows installer (GH artifact) has been tested (installed and worked)
    • MacOSX installer (GH artifact) has been tested (installed and worked)
    • Wheels installer (GH artifact) has been tested (installed and worked)

Licensing (untick if necessary)

  • The introduced changes comply with SasView license (BSD 3-Clause)

@gonzalezma
Copy link
Copy Markdown
Contributor

Tested functionality (for polydispersity) in Windows 11 and works as expected.

Copy link
Copy Markdown
Contributor

@gonzalezma gonzalezma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks ok to me and fixes bug (at least for polydispersity, but I don't see why it would be different for the magnetic part)

@wpotrzebowski wpotrzebowski merged commit 07e332b into main Nov 17, 2025
30 checks passed
@wpotrzebowski wpotrzebowski deleted the 3536-polydispersity-confused branch November 17, 2025 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants