Hi Boyce Griffith <[email protected]> writes:
> I think there is a way to get VisIt to recognize these as a group of > files automatically. I am not sure how to do this off the top of my > head, however. > > Here is one thing that I think will work: try making a file named > "out.visit" that contains: > > out_001.e > out_002.e > out_003.e > ... > > This will tell VisIt to group these files together and to treat each > file as corresponding to an individual time step. > > Now, there at least used to be an issue with VisIt whereby individual > files (such as ExodusII files) that could contain multiple timesteps > could not be grouped together using a .visit file. I don't know if this > limitation is still present in VisIt; I haven't tried to do this for a > long time. It took me while to figure that out, and Visit documentation on this is really silent. You should import your file as the right file type. If you just import a *.e database, its type is "Exodus". If you change the file type in the menu to "TimeVaryingExodus", the play buttons become active, and you can nicely show an animation. It would be great to either be able to save this setting (*.e is always considered "TimeVaryingExodus", or to know which ending to use (*.e is probably not the standard Exodus file format). Have fun, Martin ------------------------------------------------------------------------------ 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
