From: Ataollah M. <am...@ti...> - 2011-07-25 16:41:50
|
Dear all, Is there a way for each node to write the output to their own exodusII file and do with a single file for all the time steps? As I was in debug phase I wrote every time step on its exodusII file which is not very efficient since I need to write the information from mesh in each time step and program has to communicate to gather everything on the head node. Thanks, Ata |
From: John P. <jwp...@gm...> - 2011-07-26 14:12:04
|
On Mon, Jul 25, 2011 at 10:12 AM, Ataollah Mesgarnejad <am...@ti...> wrote: > Dear all, > > Is there a way for each node to write the output to their own exodusII file and do with a single file for all the time steps? If I understand your question correctly, you want two distinct things: 1.) parallel output (solutions spread across multiple files) 2.) each subsequent timestep to be written to the same file The Nemesis (aka parallel exodus) output format should be able to do both 1. and 2. as long as you are not doing mesh adaptivity. > I wrote every time step on its exodusII file which is not very efficient since I need to write the information from mesh in each time step and Are you actually calling ExodusII_IO's write_timestep() function each time you want to write a solution? That should only write the new solution and not duplicate the mesh > program has to communicate to gather everything on the head node. The Nemesis file format is great when your problem is so big it won't fit on a single processor... but any performance improvement you get will depend strongly on the speed of your parallel file system. -- John |
From: John P. <jwp...@gm...> - 2011-07-26 23:13:00
|
On Tue, Jul 26, 2011 at 5:08 PM, Ataollah Mesgarnejad <am...@ti...> wrote: > Thanks John, > I looked at Nemesis_IO class and there is no write function! > (I use : ExodusII_IO(mesh).write_equation_systems right now). The write_equation_systems() is defined in the MeshOutput (base) class, so it is defined for Nemesis. But, as I mentioned, you're going to want to call write_timestep() instead of write_equation_system() when writing data at each timestep. -- John |