On May 31, 2013, at 11:45 AM, Cody Permann <codyperm...@gmail.com> wrote:
>
>
>
> On Fri, May 31, 2013 at 9:39 AM, Manav Bhatia <bhatiama...@gmail.com> wrote:
>
>
>
>
> On May 31, 2013, at 11:27 AM, Cody Permann <codyperm...@gmail.com> wrote:
>
> > The nice thing is that you can return to your big memory machine when you
> > are through to perform visualization. Paraview and other viz packages will
> > automatically read all of the output files at once and piece the final
> > result into one for you to view.
>
> Hmm... But how does one import the solution for post processing in Paraview
> if the mesh is being read from the exodus file? I have been using the vtkio
> to feed my data into Paraview.
>
> Manav
>
> Paraview reads Exodus natively including adaptive mesh results (which should
> be written to separate files as the mesh changes), or "spread" results. Just
> make sure you use Nemesis to write your solutions and everything just works.
>
> Cody
>
Ok. So, the nemesis io also stores the solution values. (?)
I wasn't aware of this. And it doesn't force Paraview to create boundaries at
mesh partitions? I had a bit of struggle there with vtkio, so I had to write
another method to write just the boundary faces in the mesh.
Manav
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
