Custom view modes with MDEventWorkspaceInputs

[Owen Arnold]

There is an option on the rebinning filter, checked by default, called something like 'Output Histogram Workspace', which switches between rebinning using SliceMD and BinMD. The visualised output workspaces look the same, but the user can take the output workspace forward for quantification if it's a full MDEventWorkspace. The ThreeSlice and MultiSlice tools do not work well with outputs of this type. I'm getting empty output windows in the VSI when switching to these modes in three slice, and empty output windows when applying slices in multislice mode.

[Nick Draper]

Moved to milestone 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Michael Reuter]

This now seems to work in the SliceMD case as it always worked in the BinMD case. With large datasets, the SliceMD route is quite slow, but it does work.

[Owen Arnold]

CreateMDWorkspace(Dimensions='3',EventType='MDEvent',Extents='-1,1,-1,1,-1,1',Names='a,b,c',Units='a,b,c',OutputWorkspace='w')
FakeMDEventData(InputWorkspace='w',UniformParams='1000')
SliceMD(InputWorkspace='w',AlignedDim0='a,-1,1,10',AlignedDim1='b,-1,1,10',AlignedDim2='c,-1,1,10',OutputWorkspace='w')

• Open 'w' in VSI
• Click Rebin Button
• Uncheck 'Output Histo Workspace' on Rebin properties
• Click Apply -> Shows good output in Standard View, note that 'w_visual_md' is created in the workspace list, which is of type MDEventWorkspace, not MDHistoWorkspace.
• Now open the 3 slice view -> Nothing shows
• Now try the multi slice view -> Nothing shows

These tests were performed on version 2.5 on Mantid.

[Michael Reuter]

Even following the new procedure, this still works for me on both development and 2.5.0 Mantid. I can see things in both the multislice and threeslice views. I tested on both Windows and Ubuntu. I cannot reproduce the error. If this problem persists, you'll have to fix it.

[Michael Reuter]

OK. I noticed something odder about this. The first view of the data was fine, but if I switched back to standard view and then back to either MS or TS, the view was messed up. However, switching to SplatterPlot and back "fixed" the view again. I've got another discussion about an issue with generated data that needs to resolved before I decide what to do next.

[Alex Buts]

There is some strange thing happening when min-max for the test workspace are not set correctly but switching from BinMD to SliceMD and back occurs seamlessly.

And I would comment on those oddities when used to the interface better.

[Nick Draper]

Reopened, and resolved again for owen to test

[Owen Arnold]

Following the exact procedure that I reported (comment 7) on the release candidate, I have not been able to trigger this problem again.

[Stuart Campbell]

This ticket has been transferred to github issue ​6579