Hi Andy, yes that was clear. I'd been conveniently ignoring the bounding dimensions. Mark
From: Andy Bauer [mailto:andy.ba...@kitware.com] Sent: Friday, August 16, 2013 1:09 PM To: Vanmoer, Mark W Cc: paraview@paraview.org Subject: Re: [Paraview] catalyst/copro ignoring camera position in exported python pipeline? Hi Mark, The adaptor is meant to convert a simulation code's data structures into something that derives from vtkDataObject. So the adaptor could have a RAW binary file passed in and produce a vtkImageData for your case. As far as the Catalyst Python script is concerned, all it is expecting at for the source is a vtkImageData in your example. It may be that the bounding box of the data coming in from the RAW file is different than the vtkImageData you load in the second time. I'd suggest checking that. Something else you could try is the "fit to screen" option when outputting screenshots from Catalyst. That should behave similarly to the fit to screen option in the GUI. Let me know if this isn't clear since I'm not sure I answered your question. Andy On Fri, Aug 16, 2013 at 1:37 PM, Vanmoer, Mark W <mvanm...@illinois.edu<mailto:mvanm...@illinois.edu>> wrote: 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 _______________________________________________ Powered by www.kitware.com<http://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
_______________________________________________ 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
