Skip to content

Reproducible thread error in bumps on Mac OS (Trac #1084) #1135

@smk78

Description

@smk78

Reported by user Judith Witte (using Mac OS 10.13.3).

Was fitting happily in an (unspecified) earlier version of !SasView which then just ''"stopped working"'' (wouldn't open anymore). So upgraded to 4.1.2. Data loads in 4.1.2 but on attempting a fit this is returned:

Error(s) Occurred:
> Traceback (most recent call last):
>   File "sas/sasgui/perspectives/fitting/fit_thread.pyc", line 82, in compute
>   File "sas/sasgui/perspectives/fitting/fit_thread.pyc", line 14, in map_apply
>   File "sas/sasgui/perspectives/fitting/fit_thread.pyc", line 11, in map_getattr
>   File "sas/sascalc/fit/BumpsFitting.pyc", line 275, in fit
>   File "sas/sascalc/fit/BumpsFitting.pyc", line 375, in run_bumps
> AttributeError: 'FitDriver' object has no attribute 'fitter'

This looks remarkably similar to #1117 which is only classified as minor, however Judith says this is stopping her from doing any fitting. She also comments that ''"The first error occurs after I choose the model (not clicked on Fit yet)"''. If you look carefully at the screenshots you will note two slightly different errors. So am initially marking this as a blocker pending further investigation as it appears a more serious and widespread problem than in 1061.

@pkienzle has commented:

''"There is an error in bumps, but it isn't being properly reported because of an error in the bumps wrapper. I can arrange it so that the next bumps release fixes the wrapper error but I can't address the bumps error without being able to reproduce it."''

Data and screenshots from Judith to assist diagnosis are attached.

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

{
    "status": "assigned",
    "changetime": "2019-03-29T23:45:19",
    "_ts": "2019-03-29 23:45:19.408689+00:00",
    "description": "Reported by user Judith Witte (using Mac OS 10.13.3).\n\nWas fitting happily in an (unspecified) earlier version of !SasView which then just ''\"stopped working\"'' (wouldn't open anymore). So upgraded to 4.1.2. Data loads in 4.1.2 but on attempting a fit this is returned:\n\n{{{\nError(s) Occurred:\n> Traceback (most recent call last):\n>   File \"sas/sasgui/perspectives/fitting/fit_thread.pyc\", line 82, in compute\n>   File \"sas/sasgui/perspectives/fitting/fit_thread.pyc\", line 14, in map_apply\n>   File \"sas/sasgui/perspectives/fitting/fit_thread.pyc\", line 11, in map_getattr\n>   File \"sas/sascalc/fit/BumpsFitting.pyc\", line 275, in fit\n>   File \"sas/sascalc/fit/BumpsFitting.pyc\", line 375, in run_bumps\n> AttributeError: 'FitDriver' object has no attribute 'fitter'\n}}}\n\nThis looks remarkably similar to #1061 which is only classified as minor, however Judith says this is stopping her from doing any fitting. She also comments that ''\"The first error occurs after I choose the model (not clicked on Fit yet)\"''. If you look carefully at the screenshots you will note two slightly different errors. So am initially marking this as a blocker pending further investigation as it appears a more serious and widespread problem than in 1061.\n\n@pkienzle has commented:\n\n''\"There is an error in bumps, but it isn't being properly reported because of an error in the bumps wrapper. I can arrange it so that the next bumps release fixes the wrapper error but I can't address the bumps error without being able to reproduce it.\"''\n\nData and screenshots from Judith to assist diagnosis are attached.",
    "reporter": "smk78",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView Bug Fixing",
    "time": "2018-04-03T09:48:17",
    "component": "SasView",
    "summary": "Reproducible thread error in bumps on Mac OS",
    "priority": "blocker",
    "keywords": "",
    "milestone": "SasView 4.3.0",
    "owner": "wojciech",
    "type": "defect"
}

Metadata

Metadata

Assignees

Labels

BlockerPrevents a different issue from being resolvedDefectBug or undesirable behaviour

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions