Yes, we use the VTKIO class to output the solution. We also need to output
some nodal and elemental data, for which I serialize the mesh. It this
possible through the VTKIO class, by creating additional variables in the
system?
Thanks,
Harshad
On Sat, Apr 18, 2015 at 1:30 PM, Derek Gaston wrote:
Why do you need to serialize the mesh? If you're writing out any of the
serial formats (Exodus, VTK, Tecplot, etc.) then the mesh is serialized
internally... you don't need to do it yourself.
Derek
On Sat, Apr 18, 2015 at 12:03 PM Harshad Sahasrabudhe
wrote:
> Hi Roy,
>
> Sorry I forgot to pos
Hi Roy,
Sorry I forgot to post updates here. I ran the code in debug mode found
that there is no problem with MeshSerializer. The root process was running
a different collective function than other processes, which was the cause
of the crash.
I'll remind myself to run in debug mode before posting
On Thu, 16 Apr 2015, Harshad Sahasrabudhe wrote:
> I'm using MeshSerializer to serialize a mesh before output. The output
> files turn out to be fine. When I try to destroy the MeshSerializer, it
> gets stuck in the destructor on root process, while the code continues
> executing on other proces
Hi,
I'm using MeshSerializer to serialize a mesh before output. The output
files turn out to be fine. When I try to destroy the MeshSerializer, it
gets stuck in the destructor on root process, while the code continues
executing on other processes. Here is the back trace on root process:
#6 0x00
