View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010557ParaViewBugpublic2010-04-15 14:312016-08-12 09:58
ReporterKen Moreland 
Assigned ToRobert Maynard 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0010557: Structured volume rendering broken on tiled displays
Description(From Liu Ning on the ParaView mailing list.)

There seems to be a problem with the volume rendering of image data on tiled displays. When rendering on two nodes and two tiles, each tile has half the data (presumably the local half).
TagsNo tags attached.
Project
Topic Name
Type
Attached Filesjpg file icon Wavelet-FixedPointMapper.jpg [^] (17,669 bytes) 2010-04-15 14:31


jpg file icon Wavelet-GPUMapper.jpg [^] (18,496 bytes) 2010-04-15 14:31


jpg file icon box_ex2.jpg [^] (17,066 bytes) 2010-04-15 14:31

 Relationships

  Notes
(0020194)
Ken Moreland (manager)
2010-04-15 14:33

My guess is that the problem is with the representation proxy responsible for volume rendering image data. The problem appears to be independent of the image data volume renderer (see the attached images of the Wavelet rendering with two different mappers, both of which are broken). When you render, for example, an unstructured grid (such as in the attached image of box.ex2), it renders fine.
(0020482)
Utkarsh Ayachit (administrator)
2010-04-29 15:45

The problem is because the by default paraview does not use compositing on tile-displays for small data. We support movement of polydata/unstructured grid, so they are happily cloned on all tile machines and hence volume rendering works. But with image data, we don't move the data around and hence the volume rendering looks broken.

Setting "Compositing Threshold" to 0 under the Tile Display Parameters does the trick.

However this is a nuisance. As a fix, the tile display view should automatically detect if volume rendering is being used and force a compositing mode.
(0037810)
Kitware Robot (administrator)
2016-08-12 09:58

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.

 Issue History
Date Modified Username Field Change
2010-04-15 14:31 Ken Moreland New Issue
2010-04-15 14:31 Ken Moreland File Added: Wavelet-FixedPointMapper.jpg
2010-04-15 14:31 Ken Moreland File Added: Wavelet-GPUMapper.jpg
2010-04-15 14:31 Ken Moreland File Added: box_ex2.jpg
2010-04-15 14:33 Ken Moreland Note Added: 0020194
2010-04-29 15:45 Utkarsh Ayachit Note Added: 0020482
2010-04-30 14:30 Utkarsh Ayachit Status backlog => tabled
2010-04-30 14:30 Utkarsh Ayachit Assigned To => Robert Maynard
2010-04-30 14:30 Utkarsh Ayachit Target Version => 3.10
2016-08-12 09:58 Kitware Robot Note Added: 0037810
2016-08-12 09:58 Kitware Robot Status expired => closed
2016-08-12 09:58 Kitware Robot Resolution open => moved


Copyright © 2000 - 2018 MantisBT Team