3109: Bumps FitProblem fix

[krzywon]

Description

This uses the new interface for bumps where every fit problem is multi-fit. Iterating through the models now directly returns the fitness object instead of the individual fit problem. This change brings SasView in line with this new behavior.

This only fixes the majority of the issues related to this major change. Fits will continue to fail, but this PR allows the app to build and launch. See the issue for more info.

Refs #3109

Review Checklist:

Licencing (untick if necessary)

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

[rozyczko]

The code looks good but I still get this message when trying to fit.

File "sas\qtgui\Perspectives\Fitting\FittingWidget.py", line 2115, in fitComplete
AttributeError: 'str' object has no attribute 'fitness'

[rozyczko]

Do you want to actually remove example_data from the sasdata source directory during the build step?
Should you not just cp -r the thing?

[rozyczko]

Using this build:

https://github.com/SasView/sasview/actions/runs/10814069439

[krzywon]

@rozyczko - The fitting error is expected. This work, as noted in the pull request, only gets SasView to build and launch with the latest version of bumps. There is an outstanding issue how fitting packages parameters and what bumps expects.

[rozyczko]

Alternatively, we can use the last release of bumps?
git clone --depth=1 --branch v0.9.3 https://github.com/bumps/bumps.git ../bumps

[rozyczko]

this does look good as the first step in solving the interoperability issue.

[wpotrzebowski]

I am getting the same error #3109, while testing #3100. Should we also make the same fix 6.0.0?

[krzywon]

I am getting the same error #3109, while testing #3100. Should we also make the same fix 6.0.0?

If you are running from source, the local repo takes precedence over any installed version. If you have pulled from bumps master recently, this is likely why you are seeing this. 6.0.0 builds should be using bumps v0.9.2.