As part of this issue, I found that calculating the inverse of a 1x1
matrix results in a segmentation fault

The main change here is to what CutMD can do. It Clears BOTH the transforms and the original workspaces off the output workspace.

1) This fixes the issue with the labeling when plotMD is run, because there is no original workspace to try to take dimension information from.

2) However, the plots generated from CutMD from the SliceViewer are now garbage. This could because the line cuts (BinMD) are operating over a Histogram workspace already (CutMD created with NoPix=True), but is something I will need to get to the root of.

Refs #11209

https://scan6.coverity.com:8443/reports.htm#v29240/p10083/fileInstanceId=11027297&defectInstanceId=3877465&mergedDefectId=529167
clear noise -- it is initialized in the algorithm itself.

This is MD algorithms after all.

If you modify a MDHisto with +, -, * etc. you cannot run BinMD afterwards
because it would work quietly but give incorrect results.

so changed all algorithms that used it.

Also make doxygen more explicit.

Because that is more readable

Because that is more readable

To reduce warnings when coord_t = float. Also, fix a warning #4473.

Reduce warnings and avoid errors

which should fix CloneMDWorkspace. Also, fix to BinMD to strip spaces from dimension names.

The wrong coordinate transformation was being calculated. Tests happened to pass because the transformation in the previous tests were too simple

and the coordinate transformations to it when binning a MDHistoWorkspace

Like BinMD and SliceMD.

involving 0-length lines being drawn

when the original workspace is removed from AnalysisDataService. This should allow the destructor to be called properly, freeing memory and closing the file. Should let windows system test pass.