<div dir="ltr"><div><div>Hi Kalin,<br><br></div>I'm thinking that maybe there is ghost level information that is wrong, or maybe extent information. I'm assuming that you're running the server in serial so in that case you shouldn't have any ghost levels. If your grid has 16 points in each direction than than the extent for that should be [i, i+15, j, j+15, k, k+15] for a single process (note that extents don't need to start from 0 but usually do). If your grid is 16 cells in each direction than the extent would be [i, i+16, j, j+16, k, k+16]. <br>
<br>If that isn't the problem, dan you share your code and your vti file from your test harness? <br><br></div>Regards,<br>Andy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 1:11 PM, Kalin Kanov <span dir="ltr"><<a href="mailto:kalin@cs.jhu.edu" target="_blank">kalin@cs.jhu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear All,<br>
<br>
I am developing a custom ParaView reader for my data. I have a working plugin for ParaView that reads and displays the data. However, what I am getting in the 3D view is not as expected. My reader subclasses vtkImageAlgorithm and produces a 3D structured grid. When I load the data in ParaView I only see 3 of the surfaces of the cube (attached is a screenshot). Any idea why this would be happening?<br>
<br>
When I view the data in spreadsheet form all 4096 point (the testing cube is 16x16x16) have associated scalar data and the coordinates look good, but the 3D view displays only the left, right and bottom walls of the cube. Additionally, I also have a small test harness that uses my custom reader as input for a vtkXMLImageDataWriter and the resulting .vti file when loaded into ParaView and visualized looks good.<br>
<br>
Thank you,<br>
Kalin Kanov<br>
</blockquote></div><br></div>