Replace the usage of sub algorithm with child algorithm

[Nick Draper]

Let us just have one term for this purpose.

Both in code and documentation

[Nick Draper]

I'm giving this a go with a simple search and replace

[Nick Draper]

• updated wiki based on simple search
• Updated code with searches on subAlg, sub-Alg and sub alg
• Renamed a couple of sub alg filenames
• Updated design document

[Nick Draper]

re#6194 minor change

Changeset: 255646497364f353a4f05a380a56e39768a205de

[Nick Draper]

refs #6194 sub-alg to child alg name change

Changeset: beffd5056926e4decd421954f3b4598be8b4c7ac

[Nick Draper]

To test search the code for sub algorithm, or more important take a specific look at the algorithm class

[Nick Draper]

refs #6194 sub-alg to child alg name change

Changeset: 5efbeea5470612b2bb74106254179a0efa7c6456

[Gesner Passos]

There is still mention of sub algorithm in two files. The first one must be removed:

Mantid/Framework/PythonInterface/PythonAlgorithms/LoadVesuvio.py:557

# More verbose until the sub algorithm stuff is sorted

The seccond one may stay, because it does not directly mentions that it is dealing with a child algorithm. But, I would remove as well:

Mantid/Framework/PythonAPI/test/PythonAlgorithmTest.py: sub_alg

# Get the algorithm property
sub_alg = self._getAlgorithmProperty("Algo")
sub_alg.execute()
self.setPropertyValue("OutputWorkspace", sub_alg.getPropertyValue("OutputWorkspace"))

[Nick Draper]

re #6194 caught a couple of straggler sub algorithm references

Changeset: aeaddad080a89f7f4a290c9e14f6d1d513c1e512

[Nick Draper]

Both instances above dealt with

[Martyn Gigg]

Confirmed that sub-alg, subAlg etc references seem to be gone.

[Nick Draper]

re #6194 caught a couple of straggler sub algorithm references

Changeset: aeaddad080a89f7f4a290c9e14f6d1d513c1e512

[Stuart Campbell]

This ticket has been transferred to github issue ​7040