On Sun, Mar 24, 2013 at 7:20 PM, Manav Bhatia <[email protected]> wrote:
> -- For some reason, Paraview does not understand the temporal character > of the file names (a_1.e, a_2.e, a_3.e,…., a_n.e being the n time step > values). Once I read all of them into Paraview, incrementing the time in > its GUI does not change anything in the visualization. So, I have to > manually select a file (a_3.e, for example) to see the output from that > time step. Any suggestions here? > With Exodus you don't write a file per timestep... as long as the mesh doesn't change you just keep calling write_timestep() and it keeps adding to the same file. Personally this is really convenient... instead of ending up with thousands of output files for a transient simulation... you just have _one_. If your mesh does change you need to start writing a new Exodus file. In that case, Paraview expects the files to be named like so: some_name.e some_name.e-s002 some_name.e-s003 some_name.e-s004 Each one of those files might contain multiple timesteps in it. Derek ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
