Ticket #4920 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

AlgorithmManager: fixes to handle StartLiveData

Reported by: Janik Zikovsky Owned by: Janik Zikovsky
Priority: major Milestone: Release 2.1
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: #4808 Tester: Stuart Campbell

Description (last modified by Janik Zikovsky) (diff)

  • Send a signal when a new managed algorithm is added
    • Connect the AlgorithmMonitor GUI to it.
    • This will allow algorithms to launch other algos (notably, StartLiveData launching MonitorLiveData) and have them show up.
  • Correct the logic in the managed list to keep the list length constant even if one algo is running a long time.

Change History

comment:1 Changed 9 years ago by Janik Zikovsky

  • Status changed from new to accepted
  • Description modified (diff)

comment:2 Changed 9 years ago by Janik Zikovsky

  • Blocking 4808 added

comment:3 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmManager sends out a notification when algorithm...

starts asynchronously

Changeset: 24cc3696e789302c79b38aad6aa52377a28cc700

comment:4 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmMonitor monitors new algorithms starting

using the observer, no matter what the source. No more needed to directly add algorithms to it. Also refs #4808, the MonitorLiveData algorithm from StartLiveData shows up in the algo list

Changeset: 9a661bd11ae7e6907fd0d66f21cb3144f6382669

comment:5 Changed 9 years ago by Janik Zikovsky

Refs #4920 indentation and comments only

Changeset: fc7b1361d362028c892bd835833cec5f39257ceb

comment:6 Changed 9 years ago by Janik Zikovsky

Refs #4920: on some platforms, tests segfault if algos arent finished

Also starting test to check on managed algo queue

Changeset: 2013e6458f10e5db7e75e9ef89eca113306b46c2

comment:7 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmManager pop out oldest non-running algo

if you have one long running algo, e.g. MonitorLiveData

Changeset: 065b2eef82bbf0e77634358d480a93f683154279

comment:8 Changed 9 years ago by Janik Zikovsky

  • Status changed from accepted to verify
  • Resolution set to fixed

comment:9 Changed 9 years ago by Janik Zikovsky

Testers: code review, and check that StartLiveData's spawned MonitorLiveData thread shows up in the GUI.

comment:10 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmManager sends out a notification when algorithm...

starts asynchronously

Changeset: 24cc3696e789302c79b38aad6aa52377a28cc700

comment:11 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmMonitor monitors new algorithms starting

using the observer, no matter what the source. No more needed to directly add algorithms to it. Also refs #4808, the MonitorLiveData algorithm from StartLiveData shows up in the algo list

Changeset: 9a661bd11ae7e6907fd0d66f21cb3144f6382669

comment:12 Changed 9 years ago by Janik Zikovsky

Refs #4920 indentation and comments only

Changeset: fc7b1361d362028c892bd835833cec5f39257ceb

comment:13 Changed 9 years ago by Janik Zikovsky

Refs #4920: on some platforms, tests segfault if algos arent finished

Also starting test to check on managed algo queue

Changeset: 2013e6458f10e5db7e75e9ef89eca113306b46c2

comment:14 Changed 9 years ago by Janik Zikovsky

Refs #4920 AlgorithmManager pop out oldest non-running algo

if you have one long running algo, e.g. MonitorLiveData

Changeset: 065b2eef82bbf0e77634358d480a93f683154279

comment:15 Changed 8 years ago by Stuart Campbell

  • Status changed from verify to verifying
  • Tester set to Stuart Campbell

comment:16 Changed 8 years ago by Stuart Campbell

  • Status changed from verifying to closed

comment:17 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 5766

Note: See TracTickets for help on using tickets.