You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Parameters npts and nsigma do not seem to be used correctly. Only the default values (npts=35, nsigma=3) produce the expected results. Overriding those values currently creates wrong distributions and in turn results in wrong fittings on data.
See examples in the screenshots below. It seems like if the last parameter changed is PD[ratio] instead of npts or nsigma, the distribution will just be plotted with default values (like in Figure 5), but if the last parameter changed is npts or nsigma, a completely wrong distribution with a seemingly random number of points will be generated.
To Reproduce
Steps to reproduce the behavior:
Go to any shape-dependent model with polydispersity option checked
Changing npts and nsigma will produce errors in the shape of the distribution and the number of points used to plot the distribution.
Click 'Compute/plot'
Expected behavior
The distribution should appear correctly based on nsigma with the number of points specified by npts.
SasView version (please complete the following information):
Version:6.0.0a1
Operating system (please complete the following information):
OS: Windows 11
Additional context @murphyryanp discovered this issue initially. We think the problem could be in the sasview repo or the sasmodels repo. In sasview, the most recent updates that can affect this are in FittingWidget.py. In sasmodels, it seems like there's an update to the direct_model.py that changes how npts is calculated, but unclear if it's really any different from the older version.
The text was updated successfully, but these errors were encountered:
@butlerpd@krzywon I just ran across this bug myself in version 6.0.0b2 (Windows 10) during summer school. I was in the process of making a new issue then realized there was an existing one from Anita on the alpha version. I confirmed that this issue did not appear in 5.0.6.
I think I finally found the issue. Any change to any polydispersity parameter (ratio, min, max, npts, nsigs) modifies the width/PD[ratio] value of the underlying model. The other values remain as the default values, regardless of what is shown in the table.
Describe the bug
Parameters npts and nsigma do not seem to be used correctly. Only the default values (npts=35, nsigma=3) produce the expected results. Overriding those values currently creates wrong distributions and in turn results in wrong fittings on data.
See examples in the screenshots below. It seems like if the last parameter changed is PD[ratio] instead of npts or nsigma, the distribution will just be plotted with default values (like in Figure 5), but if the last parameter changed is npts or nsigma, a completely wrong distribution with a seemingly random number of points will be generated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The distribution should appear correctly based on nsigma with the number of points specified by npts.
Screenshots





Figure 1:
Figure 2:
Figure 3:
Figure 4:
Figure 5:
SasView version (please complete the following information):
Operating system (please complete the following information):
Additional context
@murphyryanp discovered this issue initially. We think the problem could be in the sasview repo or the sasmodels repo. In sasview, the most recent updates that can affect this are in FittingWidget.py. In sasmodels, it seems like there's an update to the direct_model.py that changes how npts is calculated, but unclear if it's really any different from the older version.
The text was updated successfully, but these errors were encountered: