As noted by smk78 none of the structure factor functions have their mathematical functions described in the documentation.

Sabrina Gaertner here is trying to finish off some analysis she started a couple of years ago using SasView 4.1.0. Project file attached.

4.2.0 (release or Jenkins builds) does load the project, but with some caveats.

The project requires a lamellar+gaussian_peak plugin. If you create this in 4.2.0 (ie, new architecture) then load the project, all of the FitPage parameters remain at their defaults.

If, instead, you use the same plugin created in 4.1.0 (previous architecture), then all of the FitPage parameters are updated with the values in the project file: the desired behaviour!

On intermittent occasions (it is difficult to pin down the exact circumstances because of all the things we were trying), we got this error:

2018-09-27 13:59:35,467 : ERROR : sas.sasgui.guiframe.gui_statusbar (gui_statusbar.pyc:80) :: 2018-09-27 13:59:35 : Error: This model state has missing or outdated information.
Traceback (most recent call last):
  File "sas\sasgui\perspectives\fitting\fitpage.pyc", line 2036, in reset_page
  File "sas\sasgui\perspectives\fitting\basepage.pyc", line 1257, in reset_page_helper
  File "sas\sasgui\perspectives\fitting\basepage.pyc", line 2343, in _set_dipers_Param
  File "sas\sasgui\perspectives\fitting\basepage.pyc", line 2430, in _on_select_Disp
  File "sas\sasgui\perspectives\fitting\fitpage.pyc", line 603, in _set_sizer_dispersion
  File "sas\sasgui\perspectives\fitting\basepage.pyc", line 2421, in _reset_dispersity
  File "sas\sasgui\perspectives\fitting\basepage.pyc", line 843, in save_current_state
  File "sasmodels\sasview_model.pyc", line 520, in clone
  File "copy.pyc", line 190, in deepcopy
  File "copy.pyc", line 334, in _reconstruct
  File "copy.pyc", line 163, in deepcopy
  File "copy.pyc", line 256, in _deepcopy_dict
RuntimeError: dictionary changed size during iteration

Is this indicating that there is a problem with the lookup table of old parameters to new ones?

This bug seems to have some parallels with #1183, and since that is presently a blocker I'm making this a blocker also.

While testing fix for ticket #1173 a new bug became clear which explained one user's extreme frustration in a recent email stating among other things:

I also wanted to change a little the model, as in some contrast my sponge phase S(q) has 2 bumps instead of 1. When I did it, it showed me an error (same as happened with other models and we talked about it in previous e-mails) and it set all the fitting windows I had opened to the default values. So basically I lost most of the fittings I did that day, except the ones I had in pdf.

The only exception seems to be that FitPage1 behaves somewhat differently than the others though I have not pinned down the exact nature of that. It seems that in that case the parameters are usually also reset to defaults but the graph is not updated (all graphs associated with the other tabs are immediately updated) and in fact may generate a new window?.

NOTE: I checked this was the case not only with plugins but a mixture of standard built in models as well.