Cody Permann wrote: The other real issue here though is that the exodus format does not support a changing mesh in the same file (to the best of my knowledge). One must write a new mesh file each time the mesh changes and deal with that on the visualization side.
Well we had write a new file for each time step with gmv anyway, so exodus is no worse off on that front (and it's better off for static mesh problems) > On Mar 15, 2010, at 10:03 AM, John Peterson wrote: > >> On Sun, Mar 14, 2010 at 3:57 PM, Nestor M. Solalinde >> <[email protected]> wrote: >>> Dear libmesh developers: >>> >>> I'm having trouble visualizing example 10 results. I can't use GMV because >>> it doesn't have an open licence anymore. Up to now, I've been saving the >>> results of my (transient) simulation using an ExodusII_IO object to store >>> each timestep, but it doesn't seem to work with example 10 (mesh >>> refinements). I tried also saving just one timestep with >>> >>> ExodusII_IO (mesh).write_equation_systems("filename.ex2",equation_systems); >>> >>> getting the following error, >>> >>> Num elem block: 1 >>> Assertion `i < this->n_nodes()' failed. >>> [0] /opt/libmesh/libmesh_3697/include/geom/elem.h, line 1183, compiled Mar >>> 14 2010 at 18:02:13 >>> terminate called after throwing an instance of 'libMesh::LogicError' >>> what(): Error in libMesh internal logic >>> make: *** [run] Aborted >>> >>> Any suggestion? thanks a lot, >> Derek can correct me if I'm wrong, but it looks like the Exodus writer >> is expecting all elements with a given subdomain ID to be of the same >> geometric type -- which isn't the case for ex10, the mesh consists of >> quads and triangles all with the same subdomain ID. >> >> In order to change over to Exodus for our default writer, we'll need >> to fix up ExodusII_IO_Helper::write_elements() to not make this >> assumption -- the subdomain IDs are completely user-defined, we can't >> assume they divide the elements into subsets of different geometric >> types. >> >> -- >> John >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Libmesh-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/libmesh-users > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
