Ticket #8 (closed defect: invalid)

Opened 2 years ago

Last modified 3 weeks ago

MOAB returns REGIONs, FACEs, and VERTEXes, but not EDGEs for the attached file

Reported by: vjleung@… Owned by: somebody
Priority: major Milestone:
Component: MOAB Version:
Keywords: Cc: kddevin@…

Description

MOAB can load the unzipped. exoII, version of the attached file and return REGIONs, FACEs, and VERTEXes, but not EDGEs. There are other exoII files that MOAB has trouble loading. I will attach those to other tickets. There are ncdf files that MOAB has trouble loading, but they are too large to attach.

Attachments

ti_300.exoII.gz (13.0 KB) - added by vjleung@… 2 years ago.

Change History

Changed 2 years ago by vjleung@…

Changed 3 weeks ago by kraftche

  • component changed from component1 to MOAB

Changed 3 weeks ago by kraftche

  • status changed from new to closed
  • resolution set to invalid

This file does not contain any explicit edges (bar elements?). It contains hexahedral elements and sidesets. MOAB creates faces to represent the sidesets. MOAB uses a reduced mesh representation. For example, faces are not created for any sides of hexahedra that are not part of a sideset. If there were no sidesets, no faces would be created. For the same reason, no edges are created. If you want MOAB to create edges, then call get_adjacencies with the 'create if missing' flag set to true. Pass that function all of the faces if you want edges only for the sidesets, or pass it all elements if you want all edges to be explicit.

Note: See TracTickets for help on using tickets.