Copying this to libmesh-users in case someone knows something I don't about the exodusII input.
On Mon, 16 Dec 2013, Sahai, Amal wrote: > I am having some trouble getting the right results for my new > meshes. What's the failure look like? > Would the direction of the normal of the boundary surface (or edge > in this case) while the domain is being defined in gridgen affect > the way the mesh is read by FINS? I don't believe so. Element node ordering matters to us, but ExodusII has a canonical ordering that we translate to our own correctly. Boundary vectors get generated by us from the element mapping defined by the node ordering. > I am currently using a mesh that has the normals pointing inwards > for all the edges. Is this information utilized by LIBMESH while > reading the mesh? Not to my knowledge; hopefully one of the other libMesh developers will chime in if I'm wrong. If you're having troubles at boundaries, I have one suspicion: did you happen to define your boundary conditions as node sets rather than side sets? I got a grid recently from an experienced gridgen user which had that problem; it worked for me because the app and BCs I was using happened to work with nodal Dirichlet conditions, but FIN-S (like most libMesh apps) expects boundary IDs to be defined on faces, not points. --- Roy ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
