Support for SAXS fitting (v2)

[klytje]

Description

After long discussions on how to support SAXS fitting in SasView in the short term, it was decided to extend the generic scattering calculator with a 'SAXS fitting' option.

When this option is selected, the Compute button text is replaced with Generate plugin model. Loading a Nuclear data file with this option enabled circumvents the usual loading logic, and instead forwards the selected file path to AUSAXS. This serves two purposes:

1. AUSAXS also supports mmCIF files, which is the new standard in biological scattering, and
2. we avoid having to extend/modify the PDB loading logic with the additional information required for SAXS calculations.

Clicking the Generate plugin model will then create a new SAXS fit (<filename>) model, which is automatically selected & opened for the user in the fit panel. The SAXS data may then be loaded in & fitted.

Though a little awkward, I found this implementation to work decently well, at least for a short-term solution. In the long run, I'd like to have the following:

1. The ability to load both the SAXS data & structure file directly into the fitting panel (see my discussion here).
2. An optional initialization function for plugin models, which is invoked once before the actual Iq calculations start. I need this to avoid attaching the loaded structure file as a property to the Iq function. Having it float in the module namespace would make it load on SasView startup, which is also not ideal.
3. Custom plugin model interfaces in the fit panel. There's a lot of additional options available in AUSAXS which are currently difficult/impossible to expose to the user. Though this could also be implemented through a dedicated SAXS fitting window, for (1) to work, this is required.
4. We could potentially extend the SasView file loaders to support mmCIF & full PDB data loading, if we want to avoid relying on AUSAXS for this. Alternatively, we could continue to rely on AUSAXS to parse the files, but store the data on the SasView side. Or just keep it as is. I'm indifferent on this issue.

This PR replaces #3194.

Review Checklist:

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

Documentation
Do we need documentation for this? There's links to the AUSAXS paper in the generated plugin model file itself, if people are interested.

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)

[krzywon]

I haven't tested, but see my code comments.

[krzywon]

Do not merge: This PR needs to make a minor change to what is introduced by #3544 (due to an API-breaking pyAUSAXS version update).

Is this comment in your PR description still valid, @klytje?

[klytje]

@krzywon No, it is ready for merging. The shape2sas calculations were different from what I remembered and will not need manual updating (I just checked).

[krzywon]

One final code review. I'll do a functionality test later.

[krzywon]

How could a user arrive here and what should they do to correct it, if they do?

[klytje]

What about something like this? It's not critical that this part succeeds, which is why I wrapped it in a try/catch clause.
logger.warning("Could not bring the newly generated plugin model into focus in the Fitting window. Please report this issue.")

[krzywon]

I tested today and am getting a warning when trying to create the plugin model. I think this is a Win-specific issue. The path saved in the plugin model uses backslashes causing a unicode error.

When I open the file generated in the model editor, I get the following error:

2026-01-13 14:56:52,113 : WARNING : sas.sascalc.fit.models (models.py:166) :: Failed to load plugin '\sasview\SasView\plugin_models\ausaxs_saxs_plugin.py'. See \sasview\SasView\plugin_models\plugins.log for details
2026-01-13 14:57:07,276 : ERROR : sas.qtgui.Utilities.ModelEditors.TabbedEditor.TabbedModelEditor (TabbedModelEditor.py:448) :: Error building model: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated \UXXXXXXXX escape (, line 21)
2026-01-13 14:57:07,278 : ERROR : sas.qtgui.Utilities.ModelEditors.TabbedEditor.TabbedModelEditor (TabbedModelEditor.py:454) :: structure_path = "\sasview\src\sas\example_data\coordinate_data\diamond.pdb"

[klytje]

@krzywon Windows issue should be fixed now. I changed the structure path to always be stored as a posix path instead. Verified it works on my own Windows system.

Can you can take a look at the open review conversations?

[klytje]

pyausaxs is no longer pinned as it was causing issues with the debian sasview packaging.

[krzywon]

This is getting closer! The code looks fine at this point, but running locally, I am seeing an error. Also, closing the GSC and immediately switching to the fitting perspective is a bit jarring and seems like the GSC crashed. Auto-loading the model is useful, but I don't think closing the tool is ideal.

Steps to repeat the error below:

1. Open the GSC
2. Load sas.example_data.coordinate_data.diamond.pdb
3. Generate a SAXS fit
4. In the fitting window, click the Calculate button.
5. Error

ERROR: Traceback (most recent call last): File "sasview\src\sas\sascalc\data_util\calcthread.py", line 269, in _run self.compute(*args, **kwargs) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "sasview\src\sas\qtgui\Perspectives\Fitting\ModelThread.py", line 216, in compute return_data = self.model.calculate_Iq(self.data.x[index]) File "sasmodels\sasmodels\sasview_model.py", line 710, in calculate_Iq return self._calculate_Iq(qx, qy) ~~~~~~~~~~~~~~~~~~^^^^^^^^ File "sasmodels\sasmodels\sasview_model.py", line 736, in _calculate_Iq result = calculator(call_details, values, cutoff=self.cutoff, magnetic=is_magnetic) File "sasmodels\sasmodels\kernel.py", line 94, in Iq _, F2, _, shell_volume, _ = self.Fq(call_details, values, cutoff, ~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ magnetic, radius_effective_mode=0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "sasmodels\sasmodels\kernel.py", line 169, in Fq self._call_kernel(call_details, values, cutoff, magnetic, ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ radius_effective_mode) ^^^^^^^^^^^^^^^^^^^^^^ File "sasmodels\sasmodels\kernelpy.py", line 190, in _call_kernel self.result = _loops( ~~~~~~^ self._parameter_vector, self._form, self._volume, radius, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ self.q_input.nq, call_details, values, cutoff) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "sasmodels\sasmodels\kernelpy.py", line 226, in _loops total = form() File "sasmodels\sasmodels\kernelpy.py", line 168, in self._form = lambda: form(q, *kernel_args) ~~~~^^^^^^^^^^^^^^^^^ File "~\AppData\Local\sasview\SasView\plugin_models\ausaxs_saxs_plugin.py", line 26, in Iq Iq._mol = ausaxs.create_molecule(structure_path) ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ File "sasview\venv\Lib\site-packages\pyausaxs\wrapper\Molecule.py", line 336, in create_molecule return Molecule(*args) File "sasview\venv\Lib\site-packages\pyausaxs\wrapper\Molecule.py", line 17, in init self._create_molecule(*args) ~~~~~~~~~~~~~~~~~~~~~^^^^^^^ File "sasview\venv\Lib\site-packages\pyausaxs\wrapper\Molecule.py", line 63, in _create_molecule self._create_molecule_from_file(args[0]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "sasview\venv\Lib\site-packages\pyausaxs\wrapper\Molecule.py", line 27, in _create_molecule_from_file _check_error_code(status, "_create_molecule_from_file") ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "sasview\venv\Lib\site-packages\pyausaxs\wrapper\AUSAXS.py", line 46, in _check_error_code raise RuntimeError(f"AUSAXS: "{function_name}" failed with error code {status.value}: \n"{error_message}"") RuntimeError: AUSAXS: "_create_molecule_from_file" failed with error code 1: "PDBAtom::add_implicit_hydrogens: Could not identify group of atom 1. Unknown element, residual or atom: (O, ???, O)"

[klytje]

@krzywon what is the expected outcome when trying to calculate the solution scattering by a crystal? My library is complaining that the PDB file is invalid (and indeed it is: there's no element or residue information, only an atom name which can be misinterpreted).

[klytje]

I have now added support for processing files with unknown residues, but I really do not think we should enable this by default. It needs an explicit toggle so users are aware of what is actually being done with their data, which is currently not possible.

Regarding automatically closing the GSC: I tried disabling this, and I found that to be an even worse experience, as there is no feedback that something actually happened. I think that, though it may not be ideal, closing the GSC & opening the fitting panel with the model already selected gives much clearer feedback. And it would be the next natural step to take for the user anyway.