Ticket #2968 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Disable sliders for dimensions < 4 in simple GUI

Reported by: Owen Arnold Owned by: Michael Reuter
Priority: minor Milestone: Iteration 30
Component: VATES Keywords:
Cc: Blocked By:
Blocking: Tester: Owen Arnold

Description (last modified by Nick Draper) (diff)

Suggestion by Alex Buts is that for the Slicomatic/multi-slice views, we disable sliders according to the dimensionality of the workspace. Either disable, or just don't show.

Change History

comment:1 Changed 9 years ago by Nick Draper

  • Status changed from new to assigned
  • Owner set to Michael Reuter
  • Description modified (diff)

comment:2 Changed 9 years ago by Michael Reuter

This is a strange request. The multislice view only works for N=3. If you do N<=2, 2D cut planes don't make any sense and neither does the view. We don't know how to handle N>=4 other than doing "time" for N=4. I guess I don't see the point. Some pictures might be nice to get a handle on this request.

comment:3 Changed 9 years ago by Michael Reuter

  • Milestone changed from Iteration 29 to Iteration 30

comment:4 Changed 9 years ago by Michael Reuter

  • Status changed from assigned to accepted

This will actually cover enabling/disabling the time controls based on the dataset dimensionality.

comment:5 Changed 9 years ago by Michael Reuter

  • Status changed from accepted to verify
  • Resolution set to fixed

In [14669]:

Disable the time controls for datasets with no timesteps. This fixes #2968.

comment:6 Changed 9 years ago by Janik Zikovsky

  • Status changed from verify to verifying
  • Tester set to Janik Zikovsky

comment:7 Changed 9 years ago by Janik Zikovsky

  • Status changed from verifying to reopened
  • Resolution fixed deleted

I've had some odd behavior looking at 2D MDWorkspaces... I created a 2D workspace with this code:

CreateMDWorkspace(Dimensions='4',Extents='-5,5,-5,5,-5,5,-5,5',Names='Q_sample_x,Q_sample_y,Q__sample_z,t',Units='A,A,A,sec',SplitInto='5',SplitThreshold='2000',MaxRecursionDepth='3',
		MinRecursionDepth='1',	OutputWorkspace='MD_4D')
CreateMDWorkspace(Dimensions='3',Extents='-5,5,-5,5,-5,5,',Names='x,y,z',Units='A,A,A',SplitInto='5',SplitThreshold='2000',MaxRecursionDepth='3',
		MinRecursionDepth='1',	OutputWorkspace='MD_3D')
CreateMDWorkspace(Dimensions='2',Extents='-5,5,-5,5',Names='x,y',Units='A, m',SplitInto='5',SplitThreshold='2000',MaxRecursionDepth='3',
		MinRecursionDepth='1',	OutputWorkspace='MD_2D')

... and opened it into Vates simple view (within MantidPlot). I have some situations where when I would go to Multislice, or when I would close the view and then reopen it would freeze my desktop and I had to switch to a console to kill MantidPlot.

I also got a couple of segfaults when trying e.g. the ThreeSlice button with these workspaces. Maybe because they have no data??

comment:8 Changed 9 years ago by Michael Reuter

  • Status changed from reopened to accepted

comment:9 Changed 9 years ago by Michael Reuter

  • Status changed from accepted to verify
  • Resolution set to fixed

The simple interface is meant for 3D and 4D data. 2D data won't work since the tools used are inherently 3+1 D. Please evaluate the ticket in that light and open another one to address the 2D or less issue. For that, we'll just have to warn that none of the displays will function.

comment:10 Changed 9 years ago by Janik Zikovsky

Made new ticket #3756 for my issues.

comment:11 Changed 9 years ago by Owen Arnold

  • Status changed from verify to verifying
  • Tester changed from Janik Zikovsky to Owen Arnold

comment:12 Changed 9 years ago by Owen Arnold

  • Status changed from verifying to closed

New ticket generated to capture this request as Multislice is inherently 3D+.

comment:13 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 3815

Note: See TracTickets for help on using tickets.