Looks like ParaView doesn't know that it can treat these guys as images and give you the option of the Slice Representation. As such it has to do surface extraction (convert to unstructured) in order to show you the values.
To demonstrate rid of all but one grid in your spatial collection and load that then look at memory inspector when you change to surface mode. Then take the spatial collection out to get the slice representation as an option. Not sure how to fix it without coding a bit. What you need to do is make sure it stays in structured format (as Felipe hinted at). I thought merge blocks would work, but that makes unstructured grids too. Sample to image data might work. You can probably use the python source hdf5 import path to do it directly. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Sun, Feb 1, 2015 at 4:32 AM, Felipe Bordeu Weldt < [email protected]> wrote: > hi, > > I think the best way is to write only one cell (with the correct position > in the espace) for each picture and then apply each picture as a texture in > each cell. > For me this is the way to go. But technically I don’t know how to do it. > > Felipe > > Le 30 janv. 2015 à 17:51, Michael Jackson <[email protected]> a > écrit : > > I have written an Xdmf file that uses the 3D CoRectMesh to display a > montage of 54 gray scale images. They are laid out in a 9x6 fashion. Each > Image is about 1292x968 pixels. We have run stitching algorithms on the > images to find their correct coordinates in XYZ space so that they will > form the montage correctly. > > The raw amount of memory is 67,535,424 bytes. If that has to be as RGBA > for rendering then it is 270,141,696 bytes. > > Then ParaView has to create a "cell" for each pixel and then some other > stuff. At one point ParaView spiked to 120GB of RAM and then fell back to > about 36GB of RAM. This seems a bit excessive to me. This is with ParaView > 4.3.1 on a Windows 8.1 workstation. Am I doing something wrong? Just seems > like a lot of memory. > > Are their alternate ways of writing the Xdmf file so that each image is a > single cell perhaps? > > Thanks for any insights. > > I can make the data set available to anyone who needs it. > _________________________________________________________ > Mike Jackson [email protected] > BlueQuartz Software www.bluequartz.net > Principal Software Engineer Dayton, Ohio > _______________________________________________ > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
