Match Peak and MDWorkspaces

[Owen Arnold]

Similar to #6521

The peaks workspace should 'know' what coordinate system it was created in. It should warn about usage in the PeaksViewer in any other coordinate system.

[Owen Arnold]

refs #6521 #6542. Evaluate and inform on compatible workspaces.

Handle the case that the mdworkspace does not appear self-consistent. Also handle the case where an integrated peaks workspace is being viewed in a coordinate system that is not the same as the one it was integrated in.

Changeset: 2eb6418b5be1594f74824c81ca32c56805646b57

[Owen Arnold]

refs #6521 #6542 small modification to warning.

Changeset: 7335416bbd076ee904661a62cc39a6b7f2a61e23

[Owen Arnold]

refs #6521 #6542 quality enum for vc++.

Changeset: 65b1e2ec63a1412d990fe683a1e3c2dd23a7b483

[Owen Arnold]

Tester:

Follow the first set of instructions (including the first set of bullet points) given with the test instructions for #6521. You should now have an MDWorkspace and PeaksWorkspace loaded in the PeaksViewer/SliceViewer, with no notifications relating to the current set of actions.

• Close the SliceViewer
• Run SetSpecialCoordinates on the PeaksWorkspace generated via FindPeaksMD setting the coordinates to HKL
• Reopen the MDWorkspace and PeaksWorkspace in the SliceViewer/PeaksViewer.
• You should get NO notification errors or warnings.

• Now integrate the PeaksWorkspace using IntegratePeaksMD and then repeat the bullet points above.
• You should now get a notification error explaining that the peaks will look distorted because they are being viewed in a different coordinate system to the one they were integrated in.

[Gesner Passos]

Following the test procedure, you get the exactly result described.

[Stuart Campbell]

This ticket has been transferred to github issue ​7388