On Fri, Feb 10, 2017 at 2:43 PM, Rossi, Simone <sro...@email.unc.edu> wrote:
> Dear John, > thanks for your reply. > I’m attaching a simple test with 2 elements in which I define a system > with a single variable using first order elements of l2_lagrange family. > I initialize the variable so that each degree of freedom stores its own ID. > > If I use write_discontinuous _exodusII(), the solution is exported > correctly. If after that I export another timestep, I get some wrong values. > I believe the problem here is that ExodusII_IO::write_timestep() just calls write_equation_systems(), while write_discontinuous_exodusII() follows a different code path entirely. If you are writing out discontinuous data I don't believe you should be calling the former at all. This raises the question of how to write multiple discontinuous data sets to a single file... this may not currently be supported. In the meantime, a workaround might be to call write_discontinuous_exodusII() each timestep with and write files with the following naming convention. dg.e-s0000 dg.e-s0001 dg.e-s0002 ... Paraview should then be able to read and display these results in a time sequence. -- John ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
