Feature #4390
closedMake one instrument idle timeout button for all workflow
0%
Description
queue timeout toggle button only works on queuing, not depth-first traversal. This new timeout trigger monitors usage of instrument instead.
Updated by Anchi Cheng over 7 years ago
- Status changed from Assigned to In Test
This uses setData and getData as indicator of instrument usage. Two event bindings may be needed to bind Conditioner (and its subclass) to PresetsManager since these may have just one call to setData and wait a long time for it to return.
It is best to default idle timeout time in PresetsManager settings to a few minutes so a long camera exposure or readout does not time out.
Updated by Anchi Cheng over 6 years ago
de0af4f0 disable instrument usage tracking for now. It stops too fast.
Use the timeout toggle button for Issue #5420 only for now.
Updated by Anchi Cheng over 6 years ago
Change to use event sent to manager to monitor. The problem before as well as the first version in manager has leaks that too many threads want to check and restart the timer. Got 6 in 30 minutes of running for example.
Created NodeBusyNotificationEvent for a sparse trigger.
Updated by Anchi Cheng about 5 years ago
- Status changed from In Test to Closed
This works very well.
Activate this timer at Presets Manager.