Ticket #71 (closed: fixed)

Opened 13 years ago

Last modified 5 years ago

Handle the differences between parent and child algorithms

Reported by: Nick Draper Owned by: Russell Taylor
Priority: major Milestone: Iteration 4
Component: Keywords:
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Nick Draper) (diff)

Ensure that child algorithms are created, run, results are available to the parent, and are destroyed correctly.

Change History

comment:1 Changed 13 years ago by Nick Draper

(In [561]) re #71 added isChild() to algorithm

comment:2 Changed 13 years ago by Nick Draper

(In [562]) re #71 fixed !problem

comment:3 Changed 13 years ago by Nick Draper

(In [579]) re #71 removed internal uses of IAlgorithm (this is still used in FrameworkManager - as it should be). completed the createSubAlgorithm method

comment:4 Changed 13 years ago by Nick Draper

(In [583]) re #71 revert path change

comment:5 Changed 13 years ago by Nick Draper

  • Owner changed from Nick Draper to Russell Taylor
  • Description modified (diff)

comment:6 Changed 13 years ago by Russell Taylor

(In [598]) LoadInstrument & LoadLog are now child algorithms of LoadRaw. Child algorithms are now initialised in createSubAlgorithm. Note that the vector store of child algorithms is not used and should perhaps be removed. Re #71.

comment:7 Changed 13 years ago by Russell Taylor

(In [600]) Mean old Visual Studio enforces protected access more correctly (although still not fully correctly according to the access rules given in the C++ FAQ). Re #71.

comment:8 Changed 13 years ago by Nick Draper

  • Status changed from new to closed
  • Resolution set to fixed

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​919

Note: See TracTickets for help on using tickets.