Open krzywon opened 2 months ago
Talking with @pkienzle, the hope was for bumps to be backward compatible. That isn't true at this point.
Issues found so far:
[None, None]
as the parameter bounds throws the error shown above. (https://github.com/bumps/bumps/pull/155)FitProblems
in a MultiFitProblem
returns the SasFitness
object. Previously, the return was a BaseFitProblem
object. (#3110)uncertainties.ufloat
objects. When bumps attempts to coerce param values to a float, the uncertainties package throws an error.The bumps build process has changed. setup.py
no longer exists, so our build system will have to be modernized.
Bumps no longer includes the gui
package as part of its distribution. Based on discussions with @bmaranville, this was likely an oversight and will be fixed in bumps. I thought of just moving those views into SasView, but the back-end bumps API is likely to change, as related to the dream output, so might have to keep chasing their changes everytime bumps is updated if we go that route.
bumps.gui
is included in the bumps
package as of 88b1fa65e5d235565fc99df2613c3fe34cfea210
Describe the bug A recent, major, update has overhauled bumps. This has broken fitting on our end. I am still investigating the underlying issue. @pkienzle would like to keep backwards compatibility, and said he is planning to run old bumps tests against the latest bumps to see what has changed.
Error when running a SasView fit using
sasview
main
branch andbumps
master
branch:Expected behavior The fit should run without errors.
SasView version (please complete the following information):
Additional context This does not affect the release branch due to the version pin we have there.