ISIS SANS reductions are being affect by passed reductions

[Steve Williams]

From Richard Heenan:
If a value in the gui box for transmission spectrum is entered manually, it seems to be ignored! – another bug! Eg try entering 1, then the transmissions should come out at 1.0, they don’t, but give the normal values.

The solution needs to check that these things are always true:

• After running the SANS GUI once and changing settings: all settings that were changed must be reflected in the workspace history of the new output workspace
• Everywhere the method workspaceExists(workspace) is used in the Python code under Code/Mantid/Scripts/SANS the settings in workspace must be checked too
• All execute() methods in the Reduction class must be "const" in that they don't change the class's data
• as the execute() methods cann't be exception proof all exceptions with in them must raise to a handler that removes the reducer object and all workspaces touched by that instance of the reducer object
• All workspaces produced by a SANS run (e.g. trans_can_2.0_14.0) should but documented somewhere accessible from the links under http://www.mantidproject.org/SANS#ISIS . At least the use and the names of the algroithms used to create them must be included. Some detail on the settings used in their creation would be helpful

[Steve Williams]

Created ticket #2757 to correct the spelling mistake that would look silly to a user

[Stuart Campbell]

This ticket has been transferred to github issue ​3603