You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are all fine until it comes to communicating with them, e.g. stopping them.
The standard mechanism is to set a control variable, pollable by the thread.
This is done here but the polling doesn't seem to happen or to be acted on.
{
"status": "closed",
"changetime": "2016-03-17T23:08:27",
"_ts": "2016-03-17 23:08:27.113281+00:00",
"description": "They are all fine until it comes to communicating with them, e.g. stopping them.\nThe standard mechanism is to set a control variable, pollable by the thread.\nThis is done here but the polling doesn't seem to happen or to be acted on.\n\nI would like some time to investigate this.",
"reporter": "piotr",
"cc": "",
"resolution": "invalid",
"workpackage": "SasView Bug Fixing",
"time": "2016-03-17T17:48:11",
"component": "SasView",
"summary": "What's going on with fit threads?",
"priority": "major",
"keywords": "",
"milestone": "SasView 4.0.0",
"owner": "",
"type": "defect"
}
The text was updated successfully, but these errors were encountered:
Trac update at 2016/03/17 23:06:52: piotr commented:
Paul K to the rescue. This is working as expected - choose the right optimizer and you see things work properly.
The "proper" behaviour of threads being actively killed will happen when we switch to Qt.
They are all fine until it comes to communicating with them, e.g. stopping them.
The standard mechanism is to set a control variable, pollable by the thread.
This is done here but the polling doesn't seem to happen or to be acted on.
I would like some time to investigate this.
Migrated from http://trac.sasview.org/ticket/531
The text was updated successfully, but these errors were encountered: