Please see below a list of issues and how to reproduce them.
Likely Source of Issue | Key |
---|---|
ParaView | 1 |
ParaView already fixed | 2 |
Mantid | 3 |
Unknown | 4 |
- Colour Editor Panel Issue : Resolved by going back to single instance
- Quad View : Resolved by not applying grid axis (in PV4.3.1 property is not available)
- Cut Filter : Resolved by hooking up the active view with the propertiesPanel
- Blanking Arrays: Resolved by loading MDHisto workspaces the old way
- BinMD : Resolved by making the pipeline browser available again
- Restart : Resolved by going back to single instance
- Drag and Drop : Resolved by updating the proxies when properties are changed. Also we needed to hedge for active ParaView servers which can be NULL (new in PV4.3.1)
- Cube Axis Visibility : Resolved by hooking up the active view with the propertiesPanel
- Colour Bar : Resolved by hooking up the active view with the propertiesPanel
- Scale then Cut : Resolved by making the pipeline browser available again
- Multiple Instances : Resolved by going back to single instance
- Rotation Splatterplot : Resolved by setting interaction mode in splatterplot explicitly
- Non-movable Slices : Resolved. The way the user moves the slices in the QuadView has changed, but the functionality is still there.
- View settings 2 : This is not an integration issue. The settings subwindow opens in front of the Mantidplot Window. This causes the Mantiplot menu bar to be shown. This is something which already existed earlier on.
- Slice Viewer : This was resolved by a patch from Utkarsh
- Remove cut filter : Resolved by using a new way of deleting sources in ParaView
- View settings : This seems to be intended. See the following links ViewSettings and ColorPallettes. In summary: The view settings have been migrated to the properties panel and the what we see in the view settings menu are color palettes.
When loading starting the VSI a second time, we get a message pop up 1 :
> Replacing existing manager for function :
> "COLOR_EDITOR_PANEL"
When switch to QuadView, default grid axis is not on any longer displayed (error message) 3
The cut filter does not seem to have the positioning tool any longer with which the user can manually select a plane 4
First cut then scale does not work 3
Structured data (MDHisto) requires blanking arrays. The Histo data appears as a big box. Blanking arrays seem to be missing. 3 longer term 1
Remove BinMD is not available any longer for rebinned data (probably an issue with active source) 3
Once output warning report from PV is started, it propagates when VSI is restarted. 1
Cannot add PeakWS through drag and drop; it thinks it is an MDEventWS and crashes(More tests needed in Splatterplot, when we can load PeakWS) 1, 3
Cube axis visibility does not work any longer. 2
Color bar appears only in SplatterPlot mode. There is no checkbox to enable or disable it. 1
Apply scale/cut filter, then go to view settings( or anything that can change the focus). We cannot remove the filter any longer. 3
When loading MDEventWS into the VSI and PeakWS into another instance of the VSI, the color scale of the MDEventWS seems to get messed up. It seems that the instances are NOT independent. 1
Probable issue with BasisVectors in newer ParaView. API change. 3
When loading data into splatterplot, it appears that only translation of the data set is possible no rotation. 1
When loading data into the ThreeSliceView (QuadView), we cannot move the slice planes any longer. Trying to move the slice planes just translates the data set. 1
When making a change in the view settings panel, it seems that this does not have an effect on the VSI 1
Found my Andrei "Selected a splatter plot for a histo workspace. Defaulted to standard view." 3
Found by Andrei: "In VSI, when I go to View->Settings, the settings dialog has the same menus as MantidPlot. I can start my planning tool from there". This issue seems to only exist on Ubuntu and OSX. [1] (#ParaView)
When trying to open the Slice Viewer from the MultiSlice window, Mantid crashes. [1] (#ParaView)
When applying a cut filter in standard view and switching to splatterplot view, Mantid crashes [1] (#ParaView)
Drag and Drop: Anton Non Orthongonal : Owen
General thoughts:
- Issues BinMD and Scale then Cut probably exist because we cannot select the correct element of the pipeline. Having the pipeline browser back might solve this.
- Issues Quad View, Blanking Arrays and Cube Axis Visibility seem to be addressed in later versions of PV.
- Issue Drag and Drop is something Anton can try to find out more about.
- Issues Colour Editor Panel and Restart seem to be related and seem to be a fundamental issue with PV. So this is probably something that Utkarsh will be able to understand quickly.
- Issue Cut then Slice might be a change of the cut filter design. It is worth that Utkarsh verifies this.
- Issue Colour Bar is something that is probably only related to PV, so it is usfull for Utkarsh to have a look at it.
- Issue Multiple Instances would require some input from Utkarsh, since it seems that the instances of PV seem to communicate.
- Issue Non Orthongonal relates to a ParaView non-orthngonal-source API change around the vtkFieldData. We can probably fix this ourselves.
In terms of rating the issues for Utkarsh:
- Issues Colour Editor Panel and Restart
- Issue Multiple Instances
- Issue Colour Bar
- Issue Cut Filter
- Issue Rotation Splatterplot
- Issue Non-movable Slices
- Issue View settings
- The other issues in no order
-
- Load a sample data set into the VSI
- Close the VSI
- Load the sample data set again into the VSI
- Confirm that a pop opens with warnings
-
- Will be dealt with when we remove ShowCubeAxes and set CubeAxesVisibility of the representation as Utkarsh suggested.
-
- Load a MDEvent sample data set into the VSI
- Swith to Standard View
- Apply the Cut filter
- Confirm that there is no visual slice tool available. There used to be a plane that the user could drag around to define the slice. It is not there any longer.
-
- Load a MDEvent sample data set into the VSI
- Switch to Standard View
- Apply the Cut filter, press OK
- Apply the Scale filter
- Confirm that a PV error message appears
-
- Load a MDHisto sample data set into the VSI
- Switch to Standard View
- Confirm that it is one big box (it should be a more complex shape). Signals of 0 are replaced by blue boxes
-
- Load a MDEvent sample data set into the VSI
- Switch to Standard View
- Press the Rebin button, select BinMD and press Ok
- Confirm that a big box is created (same issue as in Issue5)
- Confirm that when pressing Rebin button, there is no option to Remove rebinning. This should be available, if the active source was a rebinned source.
-
- Load a sample data set into the VSI
- Close the VSI
- Load the sample data set again into the VSI
- Confirm that a pop opens with warnings
- Switch to the Standard view
- Press Scale button
- Confirm that the pop up with warnings appears and you cannot set the scale filter.
-
- Load a MDEvent sample data set into the VSI
- Switch to SplatterPlot View
- Drag and Drop a PeaksWorkspace into the VSI
- Confirm that a pop up appears claiming that we try to add an MDEventWorkspace.
- Confirm that Mantid crashes
-
- Load a MDEvent sample data set into the VSI
- Switch to Standard View
- Try to set the cub axes visibility
- Confirm that nothing happens
-
- Load a MDEvent sample data set into the VSI
- Switch between Standard View and SplatterPlot View
- Confirm that the Color bar appears in standard view and not in splatterplot view
- Confirm that there doesn’t seem to be an option to set the color bar
-
- Load a MDEvent sample data set into the VSI
- Switch to Standard View
- Apply a scale filter ( you should still have the option to delete it)
- Press the ViewSettings button in the menu bar
- Confirm that you cannot delete the filter any longer
-
- Load a MDEvent sample data set into the VSI
- Look at the color scaling of the rendered image
- Load a PeakWorkspace into a separate instance of the VSI, i.e. don’t use the drag and drop feature to load the VSI
- Confirm that the displayed colors of the rendered MDEvent sample have changed. The two VSI instances seem to communicate.
-
- Load a MDEvent sample data set into the VSI
- Switch to the splatter plot view.
- Perform usual rotation with the mouse
- Confirm that response is not a rotation, but rather a translation
-
- Load a MDEvent sample data set into the VSI
- Switch to the three slice view
- Try to shift the slice plane
- Confirm that this only results in a translation of the data set
-
- Load a MDEvent sample data set into the VSI
- Open the view settings
- Change the background color and press apply
- Confirm that the background color does not change
- Load a MDEvent sample data set into the VSI (in OSX or Ubuntu)
- Open the view settings
- Confirm that you can see the Mantid task bar
- Load a MDEvent sample data set into the VSI
- Switch to Multislice
- Try to open the Slice Viewer by pressing shift and click on the black slice triangle at the same time.
- Confirm that Mantid breaks
- Load a MDEvent sample data set into the VSI
- Switch to Standard view and add a cut filter
- Switch to splatter plot view
- Confirm that Mantid breaks