Brad, Do you have examples of the way you encode mesh informations (connectivity table, block of elements, edges, vertices) in hdf5 files, and of the xdmf files that describe that layout? As I said in a previous message, I find the xdmf format documentation quite lacking.
I also use Sieve to represent my mesh. Regards, Blaise -- Sent from a handheld device. On Jul 7, 2011, at 8:31 PM, Brad Aagaard <baagaard at usgs.gov> wrote: > Ethan- > > I think writing an Xdmf file that points to the datasets in an HDF5 file is > probably easier than creating a viewer. For PyLith we write the HDF5 file and > a corresponding Xdmf file. This allows us to simply open the Xdmf file in > ParaView; I think VisIt supports this as well. > > Brad > > > On 07/07/2011 10:12 AM, Ethan Coon wrote: >> The downside of this option is that, in order for hdf5 files to work in >> anything but python (which is smart enough to use introspection on the >> file itself) you need a special viewer (the VisIt people call this a >> "flavor" of HDF5), see >> >> http://visitusers.org/index.php?title=VisIt_and_HDF5 >> >> These work on both VisIt and Paraview, but I've never tried to write one >> myself, so I don't know how ugly they are. They basically specify the >> layout of the hdf5 file. >> >> Note that if you go with the HDF5 option, you'll likely want to move to >> petsc-dev, which includes more HDF5 functionality, such as groups. >
