<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 24. Oct 2018, at 12:49, Matthew Knepley <<a href="mailto:knepley@gmail.com" class="">knepley@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Oct 24, 2018 at 6:29 AM Lawrence Mitchell <<a href="mailto:wence@gmx.li" class="">wence@gmx.li</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Hi Max,<br class=""><br class="">(I'm cc'ing in the petsc-users mailing list which may have more advice, if you are using PETSc you should definitely subscribe!<br class=""><br class="">> On 24 Oct 2018, at 09:27, Maximilian Hartig <<a href="mailto:imilian.hartig@gmail.com" target="_blank" class="">imilian.hartig@gmail.com</a>> wrote:<br class="">><span class="Apple-converted-space"> </span><br class="">> Hello Lawrence,<br class="">><span class="Apple-converted-space"> </span><br class="">> sorry to message you out of the blue. My name is Max and I found your post on GitHub (<a href="https://github.com/firedrakeproject/firedrake/issues/1246" rel="noreferrer" target="_blank" class="">https://github.com/firedrakeproject/firedrake/issues/1246</a><span class="Apple-converted-space"> </span>) on DMPlex being able to read periodic gmsh files. I am currently trying to do just that (creating a periodic DMPlex mesh with gmsh) in the context of my PhD work. So far I haven’ t found any documentation on the periodic BC’s with DMPlex and gmsh in the official petsc documentation.<span class="Apple-converted-space"> </span><br class="">> I was wondering whether you’d be so kind as to point me in a general direction concerning how to achieve this. You seem experienced in using petsc and I would greatly appreciate your help.<span class="Apple-converted-space"> </span><br class=""><br class=""><br class="">I think the answer is "it depends". If you're just using DMPlex directly and all the of the functionality with PetscDS, then I /think/ that reading periodic meshes via gmsh (assuming you're using the appropriate gmsh mesh format [v2]) "just works".<br class=""></blockquote><div class=""><br class=""></div><div class="">There are two phases here: topological and geometric. DMPlex represents the periodic topological entity directly. For example, a circle is just a segment with one end hooked to the other. Vertices are not duplicated, or mapped to each other. This makes topology simple and easy to implement. However, then geometry is more complicated. What Plex does is allow coordinates to be represented by a discontinuous field taking values on cells, in addition to vertices. In our circle example, each cells near the cut will have 2 coordinates, one for each vertex, but they will not agree across the cut. If you define a periodic domain, then Plex can construct this coordinate field automatically using DMPlexLocalize(). These DG coordinates are then used by the integration routines.</div></div></div></div></blockquote><div><br class=""></div>Ok, I think I understand the concept. DMPlex reads information about both topology and coordinates from the .msh file. Creating a periodic mesh in gmsh then should allow DMPlex to identify the periodic boundaries as the “cut” and build the mesh topology accordingly. Coordinate information is handled separately.</div><div>That means, as Lawrence suggested, building periodic meshes in gmsh and reading them in to petsc’s DMPlex should indeed “just work”. (From the user perspective). The only extra step is to call DMLocalizeCoordinates() after DMPlexReadFromFile(). Sorry to reiterate, I am just trying to make sense of this. <br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">From my side, the issue is to do with mapping that coordinate field into one that I understand (within Firedrake). You may not have this problem.<br class=""></blockquote><div class=""><br class=""></div><div class="">Firedrake uses its own coordinate mapping and integration routines, so they must manage the second part independently. I hope to get change this slightly soon by making the Firedrake representation a DMField, so that it looks the same to Plex.</div><div class=""><br class=""></div><div class=""> <span class="Apple-converted-space"> </span>Thanks,</div><div class=""><br class=""></div><div class=""> Matt</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Thanks,<br class=""><br class="">Lawrence</blockquote></div><br clear="all" class=""><div class=""><br class=""></div>--<span class="Apple-converted-space"> </span><br class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class="">What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br class="">-- Norbert Wiener</div><div class=""><br class=""></div><div class=""><a href="https://www.cse.buffalo.edu/~knepley/" class="">https://www.cse.buffalo.edu/~knepley/</a></div></div></div></div></div></div></div></div></div></blockquote><br class=""></div><div><div dir="ltr" class=""></div><blockquote type="cite" class=""><div dir="ltr" class="">To read periodic meshes from GMSH, you need to use the option -dm_plex_gmsh_periodic and DMPlexCreateFromFile</div></blockquote><div><br class=""></div>Ahh, thanks. I was missing the option " -dm_plex_gmsh_periodic “. But using this option I now generate a segmentation fault error when calling VecView() on the solution vector with vtk and hdf5 viewers. Any suggestions?</div><div><br class=""></div><div> <blockquote type="cite" class=""><div class="">See src/dm/impls/plex/examples/tests/ex1.c. An example runs</div><div class=""><br class=""></div><div class="">$ ./ex1 -filename ${PETSC_DIR}/share/petsc/datafiles/meshes/cube_periodic_bin.msh -dm_plex_gmsh_periodic -dm_view ::ascii_info_detail -interpolate -test_shape</div><div class=""><br class=""></div><div class="">generating periodic meshes in gmsh may be tricky, Lisandro for sure may advice.</div></blockquote><br class=""></div><div>Thanks,</div><div>Max</div><br class=""></body></html>