Hello, John: I have managed to compile with vtk, thanks for your hint about mpi. By error and trial, I found this /usr/lib64/openmpi/include/vtk/ works(have MPI) instead of default include location /usr/include/vtk/. However, I get the following error: There must be an easy fix by passing the right flag to gcc (GCC) 9.3.1 in my system; however, I would appreciate your help for how to fix it through libmesh/configure.
Here is a link to config.log https://www.dropbox.com/s/kw0mzmno58b1iog/config.log?dl=0 In file included from ../src/base/dof_map_constraints.C:39: ./include/libmesh/parallel_algebra.h: In constructor ‘TIMPI::StandardType<libMesh::Point>::StandardType(const libMesh::Point*)’: ./include/libmesh/parallel_algebra.h:218:34: error: cannot convert ‘TIMPI::StandardType<double>’ to ‘MPI_Datatype’ {aka ‘ompi_datatype_t*’} in initialization 218 | MPI_Datatype tmptype, type = T_type; | ^~~~~~ | | | TIMPI::StandardType<double> make[1]: *** [Makefile:25120: src/base/libmesh_opt_la-dof_map_constraints.lo] Error 1 make[1]: Leaving directory '/autofs/awcm/shared/awcm++/libs/libmesh/build' make: *** [Makefile:31943: all-recursive] Error 1 Thanks Jahrul On Mon, Sep 28, 2020 at 10:26 AM John Peterson <jwpeter...@gmail.com> wrote: > On Sat, Sep 26, 2020 at 1:08 PM Jahrul Alam <al...@mun.ca> 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 > Libmesh-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libmesh-users > _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
