On Tue, Oct 20, 2015 at 11:08 AM, Xujun Zhao <xzha...@gmail.com> wrote:
> Both are very useful to me! > For the stich_meshes(), how can I know the mesh_boundary_id for each mesh? > You define the boundary IDs when you make the mesh, e.g. in meshing software. Or you can add boundary IDs within libMesh via BoundaryInfo::add_*. If you're just merging the meshes into one file for the sake of visualization, you shouldn't need to worry about that though. The boundary IDs are only important if you actually want to "stitch" the meshes. David > On Tue, Oct 20, 2015 at 9:08 AM, David Knezevic < > david.kneze...@akselos.com> wrote: > >> On Tue, Oct 20, 2015 at 10:05 AM, John Peterson <jwpeter...@gmail.com> >> wrote: >> >>> On Tue, Oct 20, 2015 at 8:00 AM, Xujun Zhao <xzha...@gmail.com> wrote: >>> >>> > Hi all, >>> > >>> > Suppose I have several meshes, for example, >>> > mesh0 associated with particle 0 >>> > mesh1 associated with particle 1 >>> > mesh2 associated with particle 2 >>> > ..... >>> > >>> > For easier visualization during post processing, I would like to write >>> all >>> > the meshes into one file, so that I can only read this file in >>> ParaView or >>> > other visualization softwares. Can I do this with libMesh functions? >>> or if >>> > there are other better solutions? Thank you very much. >>> > >>> >>> No, if the meshes are different, they have to go in different files at >>> least as far as the Exodus format and the VTK format written by libmesh >>> are >>> concerned. >>> >>> Note that if you name a sequence of output files in a particular way, >>> e.g. >>> >>> foo.e-s001 >>> foo.e-s002 >>> foo.e-s003 >>> foo.e-s004 >>> foo.e-s005 >>> >>> Then opening the first one in Paraview automatically opens the entire >>> sequence for the purpose of making animations. >> >> >>> -- >>> John >>> >> >> >> You could also have a look at SerialMesh::stitch_meshes(). This is >> demonstrated in miscellaneous_ex10. If the meshes don't "touch" each other, >> then this function will just merge the meshes into a bigger mesh, and then >> you can write out the bigger mesh at the end. >> >> David >> >> >> > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
