Table of Contents FeaturesEnhancementsFixes Features PR #424, #445, #461, #462, #467, #474: Significant feature additions to improve the TempestRemap-based mapping weights generation workflow – Expose both Kd-tree and advancing front intersection – Verifications of mapping weight generation for very high-res cases at scale – Improve mbconvert to transform TR supported file formats to MOAB h5m...
Read MoreThe MOAB v5.1.0 release includes some significant feature additions to support coupled multi-physics climate applications. Details on compatibility of the different tools and dependent libraries are available separately and all questions can be directed to moab-dev@mcs.anl.gov. Source tarballs can be obtained from either the Bitbucket repository or through the ftp site. For more build...
Read MoreThe SIGMA v1.3 release includes a consolidated packaging of all geometry and mesh related components. Details on compatibility of the different tools and dependent libraries are available separately and all questions can be directed to <package>-dev@mcs.anl.gov. Current release contains the following SIGMA tools: Common Geometry Module (CGM) – Version 16.0 Mesh Oriented datABase (MOAB) –...
Read MoreSIGMA v1.2.1 Release Notes SIGMA v1.2.1 Release Notes CGM Version 15.1 Enhancements Fixes MOAB Version 4.9.1 Features Enhancements Fixes MeshKit Version 1.4.1 Enhancements Fixes SIGMA v1.2.1 minor release includes a consolidated packaging of all geometry and mesh related components. Details on compatibility of the different tools and dependent libraries are available separately and all questions...
Read MoreGeneral What’s the largest mesh MOAB can read/write? We’ve read meshes of 128M tetrahedral elements and 256M hexahedral elements. For 64M tets, MOAB uses about 2.5GB of memory. MOAB also has a structured mesh representation, that requires about 57% less memory than the unstructured representation. Memory use does tend to vary depending on what you’re doing with the mesh, since...
Read More1. Current Error Handling Model of MOAB When some error occurs, an MOAB routine can return an enum type ErrorCode (defined in src/moab/Types.hpp) to its callers. To keep track of detail information about errors, a class Error (defined in src/moab/Error.hpp) is also used to store corresponding error messages. Usually, some locally defined macros (e.g. ERRORR in src/io/ReadNC.cpp) call...
Read MoreMemory Leak in ParallelComm Class Recently, an user raised a memory leak issue of ParallelComm class on exchanging tags, see exchange-tags-memory-leak. Original Example Test In original example test (see attached file mpitest1.cpp), the memory usage keeps increasing when exchange tags is called in a loop. This test depends on MOAB (the input mesh file is MeshFiles/unittest/64bricks_1khex.h5m) so...
Read MorePseudo code on MOAB’s parallel HDF5-based reading class ReadHDF5 — load_file. set_up_read parse options, allocate buffer if bcastsummary && root: get file info (vert/elem/set/tag table structures, etc.) close file bcast size of file info bcast file info open file with set_fapl_mpio, set_dxpl_mpio(collective) if options given, set hyperslab selection limit / append behavior...
Read MoreFor some geometries with complex boundaries and many geometry entities, ray-tracing can take too long time. By controlling some options related to geometry faceting process, we can improve the performance and investigate where the problem comes from. You may see a performance improvement if you set a maximum facet edge length. The dagmc_preproc tool can do this. It basically works like...
Read MoreThe layout of the HDF5 file is roughly: tstt/ | +----elemtypes | +----nodes/ | | | +---coordinates | | | +---tags/ | +----elements/ | | | +---"group"/ | | | | | +---connectivity | | | | | +---tags/ | | | +---"group"/ | | | | | +---connectivity | | | | | +---tags/ ... ... | +----sets/ | | | +----list | | | +----contents | | | +----parents | | | +----children | +----tags/ | +---"name"/ | | |...
Read More| CGM: | |
| MOAB: | |
| MeshKit: |