Re: [Libmesh-users] how to install libmesh with vtk support

[Jahrul A. <al...@mu...>]

Hello, John:

I will post a dropbox link to the file, config.log. Unfortunately, I have a
failed drive in my raid array, and I have to turn off the array, while
 waiting for the replacement hdd from Dell. So, I will get back to
installing libMesh after I have the raid array.

Thanks

Jahrul



On Mon, Sep 28, 2020 at 10:26 AM John Peterson <jwp...@gm...> wrote:

> On Sat, Sep 26, 2020 at 1:08 PM Jahrul Alam <al...@mu...> wrote:
>
> > Hello
> >
> > First, I get the following error/info regarding vtk support, while
> > configuring libmesh:
> >
> > ./configure --with-vtk-include=/usr/include/vtk/
> --with-vtk-lib=/usr/lib64
> >
> > <<< Configuring library with Qhull version 2012.1 support >>>
> >
> > <<< Configuring library with GMV support >>>
> >
> > checking /usr/include/vtk//vtkConfigure.h usability... yes
> >
> > checking /usr/include/vtk//vtkConfigure.h presence... yes
> >
> > checking for /usr/include/vtk//vtkConfigure.h... yes
> >
> > <<< Linking a test program against the VTK libraries failed >>>
> >
> > <<< libMesh requires VTK to be configured with -DVTK_Group_MPI:BOOL=ON
> >>>
> >
>
> LibMesh uses the vtkXMLPUnstructuredGridWriter, so it requires a VTK that
> is built with MPI enabled, using the Cmake flag shown above. However,
> that's not the only reason that linking can fail. To check the exact
> reason, you'll need to look at the config.log or post a link to it so I can
> take a look (unfortunately, no attachments are allowed on this mailing
> list).
>
>
>
>
> >
> > <<< Configuring library without VTK support >>>
> >
> > Second, if I save a mesh and a solution as "output.e" for exodusII
> format,
> > parview reads only the portion that belongs  to processor #0. It seems
> like
> > libmesh warns that it writes the entire mesh. I am running paraview-5.5.2
> > from my iMac, but running libmesh on my Dell with fedora 31.
> >
>
>
> >
> > using:
> >
> > io.write_nodal_data (name, sol, vn);
> >
> > WRITING: result in
> > /autofs/research/alamj/results/awcm3d/3d/helmholtz3d/cyl3d.0000.e
> >
> > Warning:  This MeshOutput subclass only supports meshes which have been
> > serialized!
> >
> > Warning:  This MeshOutput subclass only supports meshes which have been
> > serialized!
> >
>
> Can you share the entire code you used to write the mesh? The Exodus writer
> serializes DistributedMeshes when writing, so you should get one mesh file
> with the entire contents of the Mesh in the case you are describing.
>
> --
> John
>
> _______________________________________________
> Libmesh-users mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-users
>