Opened 4 years ago

Closed 4 years ago

#739 closed defect (duplicate)

Load project issues

Reported by: richardh Owned by: krzywon
Priority: critical Milestone: SasView 4.1.0
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing


Loading a project gives "access violations" on at least some models.

Loading a project with constraints between two fit pages looks like it loads OK (apart from 5 or 6 access violations) but hitting "fit" in the constraints tab goes into an infinite calculation, with

2016-10-08 14:40:11 : Fitting is in progress…

or "fit" on an individual fit page gives errors below and then removes the fit button

2016-10-08 14:40:11 : Traceback (most recent call last):

File "C:\stfc\sasview4\sasview\src\sas\sasgui\perspectives\fitting\", line 82, in compute

result = map(map_apply, inputs)

File "C:\stfc\sasview4\sasview\src\sas\sasgui\perspectives\fitting\", line 14, in map_apply

return apply(arguments[0], arguments[1:])

File "C:\stfc\sasview4\sasview\src\sas\sasgui\perspectives\fitting\", line 11, in map_getattr

return getattr(classInstance, classFunc)(*args)

File "C:\stfc\sasview4\sasview\src\sas\sascalc\fit\BumpsFitting?.py", line 274, in fit

result = run_bumps(problem, handler, curr_thread)

File "C:\stfc\sasview4\sasview\src\sas\sascalc\fit\BumpsFitting?.py", line 345, in run_bumps

best, fbest =

File "C:\Anaconda\lib\site-packages\bumps-\bumps\", line 830, in fit


File "C:\Anaconda\lib\site-packages\bumps-\bumps\", line 526, in solve


File "C:\Anaconda\lib\site-packages\scipy\optimize\", line 371, in leastsq

shape, dtype = _check_func('leastsq', 'func', func, x0, args, n)

File "C:\Anaconda\lib\site-packages\scipy\optimize\", line 20, in _check_func

res = atleast_1d(thefunc(*((x0[:numinputs],) + args)))

File "C:\Anaconda\lib\site-packages\bumps-\bumps\", line 554, in _bounded_residuals

self.problem.setp(p + stray)

File "C:\Anaconda\lib\site-packages\bumps-\bumps\", line 270, in setp


File "C:\stfc\sasview4\sasview\src\sas\sascalc\fit\BumpsFitting?.py", line 230, in call


File "<string>", line 6, in eval_expressions

NameError?: global name 'M1' is not defined


Change History (1)

comment:1 Changed 4 years ago by krzywon

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.