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
<<attachment: within-gui.png>>
<<attachment: image_216.png>>
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview