See near top of: http://www.xdmf.org/index.php/XDMF_Model_and_Format I think that either xinclude or xpath can reduce the size of the xdmf file by acting like a macro that gets repeatedly expanded.
However, I vaguely remember that the last time I tried that approach it didn't work right off the bat and I moved on to something else. If you do get it to work, can you please post a code snippet? We can put it on the wiki for the next person who runs into that problem. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jan 17, 2013 at 9:50 PM, Pradeep Jha <[email protected]> wrote: > Hello, > > thanks for the response. I managed to create and xdmf file that seems to be > working. > > But I want to know if I can make the file more concise. I am dealing with a > simple cube of dimension 512^3 for all time steps and the name of my > variables and everything remains the same. Only the filename changes. Right > now my xmf file looks like this: > > ------------------------------------------------------------------------------------------------------------------------ > <?xml version="1.0" ?> > <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []> > <Xdmf Version="2.0"> > <Domain> > <!-- First time step --> > <Grid Name="Box" GridType="Collection" CollectionType="Temporal"> > <Grid Name="Box 0" GridType="Uniform"> > <Topology TopologyType="3DCoRectMesh" Dimensions="512 512 512"/> > <Geometry GeometryType="ORIGIN_DXDYDZ"> > <DataItem DataType="Float" Dimensions="3" Format="XML">0.0 0.0 > 0.0</DataItem> > <DataItem DataType="Float" Dimensions="3" Format="XML">0.1 0.1 > 0.1</DataItem> > </Geometry> > <Time Value="0.0" /> > <Attribute Name="w1" AttributeType="Scalar" Center="Node"> > <DataItem Dimensions="512 512 512" NumberType="Float" Precision="4" > Format="HDF"> > w1_111.h5:/w1 > </DataItem> > </Attribute> > </Grid> > <!-- second time step --> > <Grid Name="Box 7" GridType="Uniform"> > <Topology TopologyType="3DCoRectMesh" Dimensions="512 512 512"/> > <Geometry GeometryType="ORIGIN_DXDYDZ"> > <DataItem DataType="Float" Dimensions="3" Format="XML">0.0 0.0 > 0.0</DataItem> > <DataItem DataType="Float" Dimensions="3" Format="XML">0.1 0.1 > 0.1</DataItem> > </Geometry> > <Time Value="2.0" /> > <Attribute Name="w1" AttributeType="Scalar" Center="Node"> > <DataItem Dimensions="512 512 512" NumberType="Float" Precision="4" > Format="HDF"> > w1_465.h5:/w1 > </DataItem> > </Attribute> > </Grid> > </Grid> > </Domain> > </Xdmf> > ------------------------------------------------------------------------------------------------------------------------ > > But if I want to read like 10 variables from the same file, and I have > around 100 time steps, this file can become extremely long and ugly. Is > there a more elegant format of XMF file? It seems stupid to repeat the grid > and variable name information again and again unless they really change. > > Thanks > Pradeep > > > 2013/1/17 Felipe Bordeu <[email protected]> >> >> You can generate one (and only one) xdmf file with "temporal information", >> pointing to each one of your HDF5 files. So ParaView will be aware of the >> temporal dimension of your data. >> >> More info in http://www.xdmf.org/index.php/XDMF_Model_and_Format. >> >> Felipe >> >> >> Le 17/01/2013 03:17, Pradeep Jha a écrit : >>> >>> Hello, >>> >>> I have multiple HDF5 data files containing information at different time >>> steps of a flow simulation. I am using a XDMF file to visualize them. >>> >>> I want to visualize the evolution of a particular iso-surface and data >>> over a slice. How can I perform the same set of operation over all these >>> files and then combine them together to make a movie out of it? Should I >>> save a python state file of one time step and then use pvpython to combine >>> all these python state files? There are over 1000 time steps, so I cannot do >>> it manually. >>> >>> Also, is there any specific trick to make the movie in real time? >>> >>> Thanks, >>> Pradeep >>> >>> _______________________________________________ >>> 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 >> >> >> >> -- >> Felipe Bordeu Weldt >> Ingénieur de Recherche >> ------------------------------------- >> Tél. : 33 (0)2 40 37 16 57 >> Fax. : 33 (0)2 40 74 74 06 >> [email protected] >> Institut GeM - UMR CNRS 6183 >> École Centrale Nantes >> 1 Rue de La Noë, 44321 Nantes, FRANCE >> ------------------------------------- >> >> _______________________________________________ >> 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 > > > > _______________________________________________ > 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 > _______________________________________________ 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
