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
Testing actions/runs/10638002500 build for @krzywon in reviewing #3100 I'm seeing some odd behaviour with P@S models. But it looks like the behaviour is there in the 6.0.0b2 release and even the 5.0.6 release, so is likely not introduced by the PR and has (worryingly) been hanging around for a while.
This is with the L-M optimizer (I've not tested other optimizers).
When it happens you will have clicked Fit and then not seen anything happen! You wait a while and then click Stop Fit. This returns focus to you but one or more of the following may be observed:
a nonsensical radius_effective parameter; eg, nan
the Log Explorer reports something like ERROR: Fitting failed: Traceback (most recent call last): File "sas\qtgui\Perspectives\Fitting\FitThread.py", line 79, in compute File "sas\qtgui\Perspectives\Fitting\FitThread.py", line 19, in map_apply File "sas\qtgui\Perspectives\Fitting\FitThread.py", line 16, in map_getattr File "sas\sascalc\fit\BumpsFitting.py", line 284, in fit AssertionError
the Log Explorer reports other parameters as nan
But thereafter, although you can change parameter values, tick/untick boxes, clicking Fit has no effect; in essence, that Fit Page is 'dead'.
I think the structure_factor_mode setting may be implicated?
To Reproduce
Steps to reproduce the behavior:
Load some data (eg, the 2% SDS)
Create an ellipsoid@hayter_msa model
Try fitting it
Expected behavior
Fitting should proceed and the Fit Page should not go 'dead' no matter the parameter/combo box settings.
Screenshots
Clearly, in this example, that combination of polar & equitorial radii should not generate that equivalent_spherical_radius.
SasView version (please complete the following information):
Likely most v5.x and all v6.x
Operating system (please complete the following information):
W10/x64
The text was updated successfully, but these errors were encountered:
Thanks for the reminder about that issue from 5 years ago, @krzywon ! It might explain what I'm seeing but I want to play some more.
Certainly, I am now less convinced that there is an issue with structure_factor_mode, but on the flip side, I have definitely found an issue with radius_effective_mode (see #3108 ).
As noted at the start of this issue the behaviour was irreproducible and so it is difficult to pass an opionion with 100% certainty. However, retested using https://github.com/SasView/sasview/actions/runs/10638002500 on W10/x64. Despite using the same data, model, and S(Q) parameter values (incl the tiny concentration_salt), and playing around with checking/unchecking parameters and clicking the Fit button in-between, I have not seen any of the bulleted behaviour above. So hopefully it has also been fixed as a consequence of #3100 too.
Describe the bug
Testing actions/runs/10638002500 build for @krzywon in reviewing #3100 I'm seeing some odd behaviour with P@S models. But it looks like the behaviour is there in the 6.0.0b2 release and even the 5.0.6 release, so is likely not introduced by the PR and has (worryingly) been hanging around for a while.
This is with the L-M optimizer (I've not tested other optimizers).
When it happens you will have clicked Fit and then not seen anything happen! You wait a while and then click Stop Fit. This returns focus to you but one or more of the following may be observed:
But thereafter, although you can change parameter values, tick/untick boxes, clicking Fit has no effect; in essence, that Fit Page is 'dead'.
I think the structure_factor_mode setting may be implicated?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Fitting should proceed and the Fit Page should not go 'dead' no matter the parameter/combo box settings.
Screenshots
Clearly, in this example, that combination of polar & equitorial radii should not generate that equivalent_spherical_radius.
SasView version (please complete the following information):
Likely most v5.x and all v6.x
Operating system (please complete the following information):
W10/x64
The text was updated successfully, but these errors were encountered: