On May 9, 2012, at 11:58 AM, Kirk, Benjamin (JSC-EG311) wrote: >>> This is indeed correct, ExodusII requires the topology to be the same. >> >> How about other output formats ? Does any of them support multiple topologies >> ? > > > Not that I'm aware of. Usually this is handled externally in the > postprocessing code (Ensight speak the 'case' file) which is sort-of > metadata tying in a number of exodus files. Paraview and tecplot have > similar ways of handling this same thing, but usually it is one file (at > least) per mesh. My only problem with multi exodusii files is that ExodusII_IO writes the mesh every time which is not a good idea when you have a huge mesh. I was thinking of HDF5 + xml files to point to the topology and the data i.e. write separate mesh topologies every time it's modified and point to the right mesh in each xml file.
Thanks, Ata ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
