MantisBT - ParaView
View Issue Details
0015443ParaView(No Category)public2015-05-01 15:242016-08-12 09:59
Alan Scott 
Kitware Robot 
normalminorhave not tried
closedmoved 
git-master 
 
Sandia
incorrect functionality
0015443: Volume rendering non first block fails
You can only volume render the first block of a multi-block dataset. This is a bug, and desperately needs to be fixed.

* Linux, master, local server.
* Open can.exo. All variables on. Turn off the first block (leaving the second block, the plate, turned on). Apply.
* Volume render.

<<Bug>> You will see lots of warnings, and nothing gets volume rendered. Without tricks, this makes volume rendering non first blocks impossible.



This is version 4.4.0-junk of ParaView.
PV_INSTALL_DIR is /projects/viz/paraview/ParaView/4.4.0-junk/Linux-eng-sci-rhel6-x86_64
[1] 28584
ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 318
vtkMultiBlockDataSet (0x6305920): Invalid iterator location.


ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/ParaViewCore/VTKExtensions/Rendering/vtkVolumeRepresentationPreprocessor.cxx, line 75
vtkVolumeRepresentationPreprocessor (0x6271a00): Could not extract a dataset from multiblock input.


ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkCompositeDataPipeline (0x62805c0): Algorithm vtkVolumeRepresentationPreprocessor(0x6271a00) returned failure for request: vtkInformation (0x5937030)
  Debug: Off
  Modified Time: 386168
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  FORWARD_DIRECTION: 0
  FROM_OUTPUT_PORT: 0
  ALGORITHM_AFTER_FORWARD: 1


No tags attached.
Issue History
2015-05-01 15:24Alan ScottNew Issue
2016-08-12 09:59Kitware RobotNote Added: 0038810
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0038810)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.