Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Kong, Fande
On Thu, Sep 14, 2017 at 11:26 AM, Matthew Knepley wrote: > On Thu, Sep 14, 2017 at 1:07 PM, Kong, Fande wrote: > >> >> >> On Thu, Sep 14, 2017 at 10:35 AM, Barry Smith wrote: >> >>> >>> > On Sep 14, 2017, at 11:10 AM, Kong, Fande

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Matthew Knepley
On Thu, Sep 14, 2017 at 1:07 PM, Kong, Fande wrote: > > > On Thu, Sep 14, 2017 at 10:35 AM, Barry Smith wrote: > >> >> > On Sep 14, 2017, at 11:10 AM, Kong, Fande wrote: >> > >> > >> > >> > On Thu, Sep 14, 2017 at 9:47 AM, Matthew

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Kong, Fande
On Thu, Sep 14, 2017 at 10:35 AM, Barry Smith wrote: > > > On Sep 14, 2017, at 11:10 AM, Kong, Fande wrote: > > > > > > > > On Thu, Sep 14, 2017 at 9:47 AM, Matthew Knepley > wrote: > > On Thu, Sep 14, 2017 at 11:43 AM, Adriano Côrtes

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Barry Smith
> On Sep 14, 2017, at 11:10 AM, Kong, Fande wrote: > > > > On Thu, Sep 14, 2017 at 9:47 AM, Matthew Knepley wrote: > On Thu, Sep 14, 2017 at 11:43 AM, Adriano Côrtes > wrote: > Dear Matthew, > > Thank you for your return. It

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Jed Brown
"Kong, Fande" writes: >> Given the way I/O is structured on big machines, we believe the multiple >> file route is a huge mistake. Also, all our measurements >> say that sending some data on the network is not noticeable given the disk >> access costs. >> > > I have slightly

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Kong, Fande
On Thu, Sep 14, 2017 at 9:47 AM, Matthew Knepley wrote: > On Thu, Sep 14, 2017 at 11:43 AM, Adriano Côrtes > wrote: > >> Dear Matthew, >> >> Thank you for your return. It worked, but this prompts another question. >> So why PetscViewer does not write

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Matthew Knepley
On Thu, Sep 14, 2017 at 11:43 AM, Adriano Côrtes wrote: > Dear Matthew, > > Thank you for your return. It worked, but this prompts another question. > So why PetscViewer does not write both files (.h5 and .xmf) directly, > instead of having to post-proc the .h5 file (in

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Adriano Côrtes
Dear Matthew, Thank you for your return. It worked, but this prompts another question. So why PetscViewer does not write both files (.h5 and .xmf) directly, instead of having to post-proc the .h5 file (in serial)? And what about big 3D simulations? PETSc always serialize the output of the

Re: [petsc-users] SNES ex12 visualization

2017-09-14 Thread Matthew Knepley
On Thu, Sep 14, 2017 at 10:30 AM, Adriano Côrtes wrote: > Dear all, > > I am running the SNES ex12 and I'm passing the options -dm_view > hdf5:sol.h5 -vec_view hdf5:sol.h5::append to generate an output file. The > .h5 file is generated, but I'm not being able to load it

[petsc-users] SNES ex12 visualization

2017-09-14 Thread Adriano Côrtes
Dear all, I am running the SNES ex12 and I'm passing the options -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append to generate an output file. The .h5 file is generated, but I'm not being able to load it in Paraview (5.4.0-64bits). Paraview recognizes the file and offers severel options to read