Miguel, The ExodusI/ExodusII database has from its beginning supported multiple time steps. However, it is structured with a one-time write of the time=0.0 mesh data, and then successive point, cell and global (aka 'domain') datum sets written time step after time step. If in the optimization, the structure for the mesh has been altered, then the approach you used up to now may be your only answer. If the mesh structure has stayed the same from optimization step to optimization step and you have saved the optimization changes as point displacements, and if you have access to source coding, you might be able to repeat the optimization steps and write out into a single ExodusI/ExodusII database the sequence of optimization steps as time steps appended to the to the database. I am not in a position to tell you the subroutine calls needed to successively close and open an ExodusI/ExodusII database. You might find that information here: http://gsjaardema.github.io/seacas/html/index.html Sam Key On 2/10/2016 11:50 AM, Salazar De
Troya, Miguel wrote:
|
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview