[Paraview] catalyst/copro ignoring camera position in exported python pipeline?

[Vanmoer, Mark W]

Hello, is there a way to set up a coprocessing adaptor to work with RAW binary files? What I've done in the past is to first load a RAW binary in the GUI and export a coprocessing script to save a vti, run the simulation a single timestep writing the vti, then load that and save another script to create images from the full simulation.

I tried skipping the write to vti step and instead have the render-to-image script based on the RAW binary source. Attached is what I get, the image_216.png, where it appears to have moved the camera position quite a bit. I looked at the Python, and it appears to have the correct camera positions, etc.

In the C++ adaptor, I have the  data set as a vtkImageData and I figure this is where the problem is, since the adaptor is expecting that and not RAW binary. Would I have to load the data into some intermediary vtkDoubleArrays, say, and then supply those to the vtkImageData? Or is there more to it than that?

This is more out of curiosity since the other approach works fine.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130816/0f89333c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: within-gui.png
Type: image/png
Size: 21205 bytes
Desc: within-gui.png
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130816/0f89333c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image_216.png
Type: image/png
Size: 4226 bytes
Desc: image_216.png
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130816/0f89333c/attachment-0003.png>