Refs #8176 Add algorithm to Mantid.
Refs #8176 Fixed algorithm output
Refs #8176 Change algorithm parameter names to remove space.
Refs #8346 Change workspace averaging to only use unique names.
Refs #8349. Made floating window placement a bit smarter.

We are still cascading, but is previous place is free - we use it again.
Refs #8249. Don't delete existing workspace and close it's plot.

The workspace will get overwritten and it will cause existing plot to be
updated automatically.

Plus refactored a function, as with mentioned functionality removed it
looked too big for what it was doing.
Refs #8346 Implement better way of filtering of runs.
Refs #8349. Don't plot ws again if plot already exists.

Just make sure the plot is visible in that case. It should've been updated
automatically.
Refs #8349. Use plotSpectrum for setting plot style.

As we can now plot to the same window, no need to set style parameters
manually.
Refs #8349. Removed big function which wasn't actually needed.
Refs #8349. Use plotSpectrum instead of checking/plotting manually.
Refs #8349. Made plotSpectrum get plot style params itself.
Refs #8349. Removed unused closePlotWindow.
Refs #8349. Quick fix for the problem I've found.

Don't show fitting results in the workspace selector on DA tab. When
fitting is done, they do get deleted before creating a new ones. Property
browser is subscribed to deletion events but not to addition events, which
causes problems in that case.
Refs #8349. Don't show all graphs when uncheking "Hide prev. graphs"

As now they all share the same place, when all shown they are hidden behind
a single graph.

That's a simple solution, need to discuss whether scientists want something
different to happen.
Add non-functioning workspace property re #8398

Signed-off-by: Karl Palmen <karl.palmen@stfc.ac.uk>
refs #8488 This should fix it

Par file has the azimuthal angle sign convention opposite to the one, used by nxspe. To avoid any confusion, nxspe should always use one (right hand side) convention for azimuthal angle.
refs #8488 should fix unit test
Begin to write code to put params into workspace re #8398

My original plan of putting the table into a POCO XML document
then putting that into the workspace like LoadParameters does
is not on, because LoadParameters does something dodgy, that
will sometime need fixing and should not be replicated.
So I'm forced to put the parameters in directly. This would lead
to better code, but I presently have no idea how to do it.

Signed-off-by: Karl Palmen <karl.palmen@stfc.ac.uk>
refs #8488 should fix it.