A problem on loading a saved project (Trac #458)

[butlerpd]

Adrian Rennie has reported the following problem. This seems to have something todo with how save state works. in that it saves information necessary to recreate the state. Suspect that in this case the path to getting to the state originally works but the path being taken by the load state gets into a problem due to order of how things get generated?

---

On opening a saved project I received the following message:

Error(s) Occurred:
Plotting Error: data has no positive values, and therefore can not be log- scaled
File "sas\perspectives\fitting\fit_thread.pyc", line 82, in compute
File "sas\perspectives\fitting\fit_thread.pyc", line 14, in map_apply
File "sas\perspectives\fitting\fit_thread.pyc", line 11, in map_getattr
File "sas\fit\BumpsFitting.pyc", line 262, in fit
File "sas\fit\BumpsFitting.pyc", line 345, in run_bumps
File "bumps\fitters.pyc", line 859, in stderr
File "bumps\lsqerror.pyc", line 79, in hessian
File "bumps\numdifftools.pyc", line 1159, in call
File "bumps\numdifftools.pyc", line 1170, in hessian
File "bumps\numdifftools.pyc", line 1084, in hessdiag
File "bumps\numdifftools.pyc", line 720, in _partial_der
File "bumps\numdifftools.pyc", line 424, in _derivative
File "bumps\numdifftools.pyc", line 686, in _romb_extrap
!ValueError: operands could not be broadcast together with shapes (24,) (2,)

None "

The program then seemed to hang and I had to kill it. This seems a bit strange as after the save I had exited the program normally. Restarting a saved project seems to do something that was not happening previously.

Migrated from http://trac.sasview.org/ticket/458

{
    "status": "closed",
    "changetime": "2017-10-27T10:29:13",
    "_ts": "2017-10-27 10:29:13.405567+00:00",
    "description": "Adrian Rennie has reported the following problem.  This seems to have something todo with how save state works. in that it saves information necessary to recreate the state.  Suspect that in this case the path to getting to the state originally works but the path being taken by the load state gets into a problem due to order of how things get generated?\n\n-----------------\n\n  On opening a saved project I received the following message:\n\n  Error(s) Occurred:\n  Plotting Error: data has no positive values, and therefore can not be log-   scaled\n   File \"sas\\perspectives\\fitting\\fit_thread.pyc\", line 82, in compute\n    File \"sas\\perspectives\\fitting\\fit_thread.pyc\", line 14, in map_apply\n    File \"sas\\perspectives\\fitting\\fit_thread.pyc\", line 11, in map_getattr\n    File \"sas\\fit\\BumpsFitting.pyc\", line 262, in fit\n    File \"sas\\fit\\BumpsFitting.pyc\", line 345, in run_bumps\n    File \"bumps\\fitters.pyc\", line 859, in stderr\n    File \"bumps\\lsqerror.pyc\", line 79, in hessian\n    File \"bumps\\numdifftools.pyc\", line 1159, in __call__\n    File \"bumps\\numdifftools.pyc\", line 1170, in hessian\n    File \"bumps\\numdifftools.pyc\", line 1084, in hessdiag\n    File \"bumps\\numdifftools.pyc\", line 720, in _partial_der\n    File \"bumps\\numdifftools.pyc\", line 424, in _derivative\n    File \"bumps\\numdifftools.pyc\", line 686, in _romb_extrap\n  !ValueError: operands could not be broadcast together with shapes (24,) (2,)\n\n   None \"\n\n  The program then seemed to hang and I had to kill it.  This seems a bit   strange as after the save I had exited the program normally.  Restarting a saved project seems to do something that was not happening previously.\n",
    "reporter": "butler",
    "cc": "",
    "resolution": "obsolete",
    "workpackage": "SasView Bug Fixing",
    "time": "2015-07-21T22:17:18",
    "component": "SasView",
    "summary": "A problem on loading a saved project",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView Next Release +1",
    "owner": "",
    "type": "defect"
}

[butlerpd]

Trac update at 2017/10/27 10:29:13:

• butler commented:

This looks like a bumps problem that we had several times and I think may have been fixed by now (should be on several version of bumps further down the road). At any rate lots of work has also happened on the save/load front and this does not seem to be a recurrent problem since the ticket has not been updated in 2 years. Thus going to assume this has been fixed when something else got fixed? At any rate going to close this ticket.

• butler changed resolution from "" to "obsolete"
• butler changed status from "new" to "closed"