News

PUMI: PUMI 1.0.0 Released

Added by E. Seegyoung Seol about 4 years ago

Announcing PUMI v1.0.0 release with new api spec.

PUMI LICENSE

OSI 3-clause BSD

PUMI Components

1. pcu with header file pumi_comm.h

2. pumi_geom with header file pumi_geom.h

3. pumi_util with header file pumi.h

4. pumi_mesh with header filepumi_mesh.h

5. parma with header file "pumi_partition.h" (NOT SUPPORTED in V1.0)

6. pumi_field with header file "pumi_field.h" (NOT SUPPORTED in V1.0)

PUMI API Naming

ALL PUMI api function names consists of three words connected with ’_’.

  • the first word is ”PUMI”
  • the second word is an operation target. The first letter is upper case and the rest of letters are lower case. If the operation target is system-wide, the second word is ommited. For instance, the function that initializes the PUMI service, PUMI_Init, doesn’t have the second word.
  • the third word is the operation description. If the api function returns an error code indicating the operation succeeded or not, the third word starts with verb. Otherwise, the third word starts with noun. The first letter of verb and noun is upper case. The rest of letters are lower case. For example, the function PUMI_Part_GetNumEntType gets the number of mesh entities in a part with specific type and returns 0 (PUMI_SUCCESS) or an error code defined in pumi_errorcode.h. The function _PUMI_MeshEnt_I_D returns mesh entity’s ID.

Build Instruction

1. Check out pumi_build.sh from

svn co http://redmine.scorec.rpi.edu/anonsvn/fmdb/software/trunk/FMDB/FMDB/buildScripts

2. Edit pumi_build.sh

3. Run functions with pumi_build.sh

./pumi_build.sh checkout_all: to checkout source codes from the svn repository
./pumi_build.sh update all: to update source codes from the svn repository
./pumi_build.sh setup_all: to set-up before build
./pumi_build.sh install_all: to build and install
./pumi_build.sh uninstall_all: to uninstall
./pumi_build.sh download_and_build_zoltan: download, build, and install zoltan

4. PUMI Application Development

  • Include compilation flag PUMI_PARALLEL for parallel development

Remarks

Note not all services are available. The following are UNDER DEVELOPMENT.
  • parma library
  • pumi_field library

PUMI_MESH (FMDB): FMDB 1.4.0 Released

Added by E. Seegyoung Seol about 5 years ago

Announcing FMDB v1.4.0 release with focus on enrichment of multi-part related functions & static partitioning performance improvement

  • Click here for full release note
[NEW/IMPROVED FEATURES]
  • FMDB_Mesh_LoadFromFile - mesh loading time reduced to one third (1/3) of the original
      - prev: the same migration algorithm was used for both static and dynamic partitioning
      - new: migration algorithm developed for static partitioning
  • FMDB_Mesh_Merge
      - merging N part mesh (migrating all parts to part 0 on master process)
  • (#405) FMDB_Vtx_GetLoadPartOrderPair
      - For a vertex, getting loading part id and read-in order from mesh file
  • weight control for dynamic partitioning through Zoltan/ParMETIS
      - FMDB_Ent_Set/Get/DelWeight - set/get/delete weight of individual entity.
      - FMDB_Topo_Set/Get/DelWeight - set/get/delete weight of all entities of topology.
  • FMDB_Mesh_DspStat - mesh load imbalance ratio computation improved to be consisitent with Zoltan/ParMETIS
       - prev: mesh load imbalance ratio computed based on # partition object entities (e.g. regions in 3D)
       - new:  mesh load imbalance ratio computed based on weights per process/part
[ERROR FIX]
  • (#416) FMDB_Mesh_Verify collective status report
  • (#415) FMDB_Mesh_Verify for optimized calls
  • (#414) FMDB does not compile on BG/P
[FASTMath INTERFACE COMPLIANCE]
  • iMesh.h pass rate: 100%
  • iMeshP.h passrate: 99%
  • iMeshP_ext.h pass rate: not applicable

PUMI_MESH (FMDB): FMDB 1.3.9 Released

Added by E. Seegyoung Seol over 5 years ago

Announcing FMDB v1.3.9 release with focus on multiple-part & p-set migration/partitioning support

  • Please be advised that the new features are supported only through FMDB.h.
  • Please obtain the source (SCUtil, FMDB) from FMDB repo or tarballs":http://www.scorec.rpi.edu/FMDB/source.html
  • Click here for full release note
[NEW FEATURES]
  • (#332) setting ZOLTAN parameters (LB_Method, LB_Approach, imbalance tolerance) for static/dynamic mesh partitioning
    - the user can control partitioning parameters for mesh partitioning
    - static mesh partitioning is to load and distribute serial mesh in parallel
    - dynamic mesh partitioning is local/global mesh re-distribution during parallel mesh modification
  • (#279) parallel mesh file i/o with p-set
    - p-set is one kind of ordered entity set which is assigned to a single part so can be designated as "partition object (a basic unit to assign destination part in migration)"
  • (#303) setting/getting #parts per process
    - The application can change # parts per process dynamically
  • (#328) getting neighboring process/parts
    - A process i neighbors process j if they share mesh entities on part boundary between parts located in process i and process j.
    - A part x neighbors part y if they share mesh entities on part boundary
  • displaying mesh statistics (click here for sample)
    - global statistics with respect to the count (#p-set, #entity) per process. E.g. mesh load imbalance ratio, avg/max/min #p-set, #entity
    - global statistics with respect to the count (#p-set, #entity) per part
    - local (per process) statistics
[ERROR FIX]
  • (#392) multi-part partitioning support with P-set
  • (#387) hang during migration after partitionedmesh loading

ITAPS: ITAPS 1.4 Released

Added by Mark Miller over 5 years ago

Announcing Release 1.4 of ITAPS Interfaces, Implementations and Services.

Users may obtain help and send feedback to itaps-users at lists.mcs.anl.gov

This announcement consists of the following information
1. Changes to ITAPS interface specifications in this release
2. Fortran interface improvements
3. Improvements in ITAPS interface and portability testing.
4. Information on obtaining the software
5. Obtaining documentation

1. Changes to ITAPS interface specifications

  • iBase.h
    • The iBase_Error struct datatype was removed because it was part of a now obselete error handling mechanism
    • The concept of the resliency in iterators was introduced to permit ITAPS callers to indicate what assumptions their call sequences make in the way of iterator behavior in the presence of container modifications. For a detailed discussion of the design considerations for this change, see http://redmine.scorec.rpi.edu/issues/198
    • In any of the ITAPS interfaces where an iterator can be requested, if a caller requests a reslient iterator and an implementation is unable to return one, the function will fail and return IBASE_NOT_SUPPORTED.
    • Advice for implementers was improved to include how to properly deal with termination of string-valued arguments.
  • iMesh.h
    • Added reslient argument in iterator creation calls
    • Replaced iMesh_areEHValid() with iMesh_optimize() and added handles_invalidated return argument to indicate if calling iMesh_optimize() potentially invalidated any entity, set, or tag handles the caller was holding prior to the call. For a detailed discussion of the design considerations for this change, see http://redmine.scorec.rpi.edu/issues/161
  • iMeshP.h
    • Added reslient argument in iterator creation calls
  • iRel.h
    • Added reslient argument in iterator creation calls
  • iField.h / iField_dfk.h
    • Added reslient argument in iterator creation calls
    • Const-qualified some input arguments

2. Fortran interface improvements

Fortran include files are now automatically generated from the C header files. The logic for handling 4-byte or 8-byte pointer sizes was simplified. It is now automated for a majority of common compiler cases as well as can be explicitly overridden during compilation with -DPOINTER_SIZE=4|8 CPP flag.

3. Improvements in iMesh/iMeshP interface and portability testing

A number of improvements have been made in the testing of ITAPS interfaces

  • Initiated regular testing of Parallel iMesh implementations.
  • Initiated regular testing with the valgrind memory checker.
  • Addressed all leaks in the iMesh implementations and most other memory errors reported by valgrind testing.
  • Initiated regular testing of Fortran example codes.
  • Identified and corrected various issues with Fortran interoperability across the implementations.
  • Adjusted tests to be more flexible in dealing with implementation defined aspects of the interfaces.
  • Enhanced iMeshP tests to test cross-implementation portability.

The ITAPS implementations are tested on a weekly basis in a variety of modes described above to ensure implementations are consistent with interface specifications as well as each other.

4. Information on obtaining ITAPS-1.4 compliant software

Various implementations of the ITAPS interfaces can be found at the following URLs. Users are also encouraged to read the respective product's release notes for additional information pertaining to this ITAPS-1.4 release as well as product-specific release details.

We have also developed a support script, called build_itaps, to facilitate the download, compilation and installation of ITAPS interface and service software. You can obtain the build_itaps script here. In addition, there is a helpful primer on using the build_itaps script to build all or just some pieces of the ITAPS softwar suite in a variety of configurations here.

5. Obtaining documentation

Reference manuals for all the ITAPS interfaces can be found here

PUMI_MESH (FMDB): FMDB 1.3.8 Released

Added by E. Seegyoung Seol over 5 years ago

Announcing FMDB v1.3.8 release with focus on

  • New Feature (#303) process grouping
    - each process group loads individual mesh onto multi-part and modify/migrate/load_balance/export the mesh independently
  • Error fix (#373) failures with iMesh fortran tests
  • Error fix (#320) FMDB_FMDB_LoadFromFile hangs with wrong input
  • Error fix (#323) multi-part file i/o
  • Error fix (#339) multi-part partitioning/migration

Please obtain

For help or more information, please refer to User's Guide and send feedback to .

PUMI_MESH (FMDB): FMDB 1.3.7 Released

Added by E. Seegyoung Seol over 5 years ago

Announcing FMDB v1.3.7 release with focus on

  • API for manual part boundary update
  • iMeshP compliance (current pass rate: 76%)
  • Error fix [valgrind error with iMesh perfTest example run]
  • Error fix (#323) [Incorrect mesh size/entities' owning part info for multi-part distributed mesh]

Please obtain

  • Tarballs (GMI, SCUtil, FMDB, IPComMan) and build instructions from FMDB web site
  • Click here for full release note

For help, please refer to User's Guide and send feedback to .

PUMI_MESH (FMDB): FMDB 1.3.6 Released

Added by E. Seegyoung Seol almost 6 years ago

Announcing FMDB v1.3.6 release with focus on

  • Valgrind memory errors with iMesh compliance test
  • Tagging import/export functionality for VTK files
  • "Multiple parts per process" support in global load balancing through FMDB API
  • Error fixes (#301) [Writing VTK files from FMDB API]

Please obtain

For help, please refer to User's Guide and send feedback to

FASTMath: FASTMath Software Strategies Redmine Site Open For Business

Added by Mark Miller almost 6 years ago

With Tim Wickberg's and RPI's help, we have created this Redmine project site to support FASTMath Software Strategies

PUMI_MESH (FMDB): FMDB 1.3.5 and GMI 1.0.1 Released

Added by E. Seegyoung Seol almost 6 years ago

Announcing FMDB v1.3.5 and GMI v1.0.1 release with focus on

  • (#305) failure with iZoltan-parallel
  • (#299) entity creation/search
  • (#294) sample mesh folder enriched with the mesh which mimics what MOAB iMeshP test constructs
  • (#203) exporting iGeom-Defs.inc

Please obtain

For help, please refer to User's Guide and send feedback to

PUMI_MESH (FMDB): FMDB v1.3.4 Released

Added by E. Seegyoung Seol about 6 years ago

Announcing FMDB v1.3.4 release with focus on

  • tagging (api, performance, code reusability)
  • memory leak error (#295)
  • make check error (#302)

Please obtain

For help, please refer to User's Guide and send feedback to

1 2 3 ... 6 Next »

Also available in: Atom