Move the Muon workflow out of the MuonAnalysis interface code

[mantid-builder]

Original Reporter: Arturs Bekasovs

This ticket is blocked by :

• TRAC8506
• TRAC8534
• TRAC8550
• TRAC8597
• TRAC8702

Muon Interface has quite a long sequence of things it does to the loaded workspace before it actually gets plotted on the screen. Currently, all these steps are buried in the depths of the interface code. This is bad.

Firstly, because it makes them difficult to test. Currently, only the individual algorithms are tested, but not how they are working together.

Secondly, this makes it impossible to use the workflow outside the interface, which is currently required for http://trac.mantidproject.org/mantid/ticket/6473.

To solve similar kinds of problems, a notion of ''Workflow algorithm'' was introduced. Those are not doing much work themselves, but are instead setting parameters for child algorithms. This seems like a right thing to use inside Muon Analysis.

So, the initial plan is:

1. Find out how many and what kind of algorithms are needed.

2. Write rigorous tests for them.

3. Implement algorithms so that tests are passing.

4. Refactor MuonAnalysis interface code to use these algorithms instead.

   Keywords: Maintenance

[mantid-builder]

This issue was originally trac ticket 8494

[mantid-builder]

http://trac.mantidproject.org/mantid/raw-attachment/ticket/8494/muon_workflow.png

(uploaded by Arturs Bekasovs on 2014-02-25T14:52:54)

---