Ticket #10518 (new)

Opened 6 years ago

Last modified 5 years ago

Is it possible/sensible to remove the AlgorithmProxy class

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Release 3.6
Component: Framework Keywords: Maintenance
Cc: Blocked By:
Blocking: Tester:

Description

Several recent issues, #10438 & #10377, have uncovered problems with the AlgorithmProxy not correctly mirroring Algorithm. Obviously these can be fixed but do we need to class at all these days given that we no longer return algorithm objects in Python (its original use case).

This ticket is to investigate whether it is feasible and sensible to do the removal.

Change History

comment:1 Changed 6 years ago by Roman Tolchenov

AlgorithmManager keeps a few pointers. Do we need it when we use notifications?

comment:2 Changed 6 years ago by Martyn Gigg

For MantidPlot we will need to store the pointer somewhere for the asynchronous runs but I don't really see why the manager needs to keep anything past it having finished.

It's a good thing to bear in mind though when we look in to it.

comment:3 Changed 6 years ago by Martyn Gigg

  • Milestone changed from Release 3.4 to Release 3.5

comment:4 Changed 5 years ago by Martyn Gigg

  • Milestone changed from Release 3.5 to Release 3.6

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​11360

Note: See TracTickets for help on using tickets.