News

ITAPS: ITAPS 1.3 Released

Added by Mark Miller over 6 years ago

Announcing Release 1.3 of ITAPS Interfaces and Services with focus on
Parallel Mesh interface, iMeshP

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

This announcement consists of the following information
1. iMeshP Release Details
2. iField Release Details
3. Details regarding other ITAPS interfaces in this release

1. iMeshP Release Details

This release focuses primarily on the Parallel Mesh interface, iMeshP.

This is an alpha release of iMeshP interface specification AND implementations.

We are making this alpha release available to users to solicit feedback on the interface specification itself as well as experiences with the available implementations of that interface, FMDB from RPI and MOAB from ANL.

Implementations of iMeshP are ongoing and will continue to evolve and improve in the coming months. This is a great opportunity for users to get involved and provide feedback.

Portions of the iMeshP interface specification are still in flux. In addition, the available implementations of iMeshP emphasize different aspects of the interface. Details of these differences can be found in each implementation's respective release notes.

Users may obtain iMeshP implementations here...

Presently, the build_itaps tool that helps users build previous (serial) releases of ITAPS software does not support parallel configuration, build and installation of ITAPS software products. Therefore, users will have to obtain and follow each implementation's respective software installation procedures.

Complete documentation on all ITAPS interfaces is available here https://redmine.scorec.rpi.edu/anonsvn/itaps/software/tags/1.3/tools/doxygen/html/modules.html

2. iField Release Details

Also included in this release is an alpha release of the ITAPS field interface specification, iField. Implementations of iField are under way but this 1.3 ITAPS release includes only the iField interface specification. The implementations are not being released at this time but will be in the next ITAPS release.

Users may obtain the iField interface specification here https://redmine.scorec.rpi.edu/anonsvn/itaps/software/tags/1.3/tools/doxygen/html/group__iField.html

3. Other Details

Minor bug fixes and enhancements to other ITAPS interfaces are also included in this release.

  • iBase:
    • iBase_NO_MESH_DATA error code has been eliminated
  • iMesh:
    • The returned error code argument, 'int *err' has been elimiinated from iMesh_getDescription() and iMesh_getErrorType().
    • Some problems with fortran header files were corrected.
Serial implementations of ITAPS-1.3 interfaces are available at...

In addition, the build_itaps tool obtained here https://redmine.scorec.rpi.edu/anonsvn/itaps/software/tags/1.3/tools/build_itaps and described here http://redmine.scorec.rpi.edu/projects/itaps/wiki/_build_itaps_primer_ is helpful in building and installing various serial ITAPS implementations and services.

PUMI_MESH (FMDB): FMDB Weekly #17 (Apr 25 - Apr 29)

Added by E. Seegyoung Seol over 6 years ago

[ Week 17 Activities ]

FMDB v1.3

  • constraint: single part per mesh and single partition
  • (on-going) entity set and entity group integration
    - mesh migration
    - distributed entity set file I/O
  • (on-going) FMDB.h development
    - entity creation/search
    - higher-order node, etc.
  • (on-going) parallel code improvement (cleanup, performance, etc.)

iMesh/iMeshP

  • (on-going) swapping issue f/u (crash with iterator)
  • (on-going) iMeshP_FMDB development (itaps spec compliance)
  • (on-going) build issues f/u (fortran support, name mangling, linking etc.)

SCUtil/iBase

  • employing SCOREC error management scheme (fault tolerance with error code)

GRM/iRel

  • NONE

[ Planned Week 18 Activities ]

FMDB v1.3

  • MeshAdapt support centric release to SCOREC
  • FMDB.h development
  • entity set/entity group integration
  • parallel code improvement (cleanup, performance, etc.)

iMesh/iMeshP

  • swapping issue f/u
  • iMeshP_FMDB development
  • build issue f/u

GMI/iGeom

  • NONE

SCUtil/iBase

  • employing SCOREC error management scheme

GRM/iRel

  • NONE

[ Independent Study ]

  • Template Meta Programming
  • Design Pattern

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #15 (Apr 11 - April 15)

Added by E. Seegyoung Seol over 6 years ago

[ Week 15 Activities ]

FMDB v1.3

  • constraint: single part per mesh and single partition
  • (on-going) entity set and entity group integration
    - mesh migration
    - distributed entity set file I/O
  • (on-going) FMDB.h development
    - entity creation/search
    - higher-order node, etc.
  • (on-going) parallel code improvement (cleanup, performance, etc.)

iMesh/iMeshP

  • (on-going) iMeshP_FMDB development
  • (on-going) build issues (fortran support, name mangling, linking etc.)

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 16 Activities ]

FMDB v1.3

  • FMDB.h development
  • entity set/entity group integration
  • parallel code improvement (cleanup, performance, etc.)

iMesh/iMeshP

  • iMeshP_FMDB development

GMI/iGeom

  • MeshModel review and improvement

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Independent Study ]

  • C++ Templates
  • Design Pattern

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #14 (Apr 4 - April 8)

Added by E. Seegyoung Seol over 6 years ago

[ Week 14 Activities ]

FMDB

  • constraint: single part per mesh
  • (on-going) entity set and entity group integration
    - mesh migration
    - distributed entity set file I/O
  • (on-going) ghosting
    - N-layer creation
    - layer accumulation
    - mesh verification
    - thesis writeup
  • (on-going) FMDB.h development
    - missing api functions (region creation, entity search, etc)
  • (on-going) User's Guide update

iMesh/iMeshP

  • (completed) iMesh_FMDB development
    - iMesh compliance test passed
  • (on-going) memory leak w/ valgrind
  • (on-going) iMeshP_FMDB development
  • (on-going) build issues (fortran support, name mangling, etc.)

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 15 Activities ]

FMDB v1.2

  • FMDB.h development
  • entity set/entity group integration
  • ghosting development
  • parallel code improvement (cleanup, performance, etc.)

iMesh/iMeshP

  • memory leak debugging w/ valgrind (serial)
  • iMeshP_FMDB development

GMI/iGeom

  • autotool support (iGeom-Defs.inc, fortran, etc.)
  • iGeom status (implementation/testing) review

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Independent Study ]

  • C++ Templates
  • Design Pattern

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #13 (March 28 - April 1)

Added by E. Seegyoung Seol over 6 years ago

[ Week 13 Activities ]

FMDB

  • constraint: single part per mesh
  • (on-going) entity set and entity group integration
    - mesh migration
    - distributed mesh file I/O
  • (on-going) ghosting
    - N-layer creation
    - layer accumulation
    - mesh verification
  • (on-going) FMDB.h development
    - missing api functions (region creation, entity search, etc)
  • (on-going) User's Guide update

iMesh/iMeshP

  • (on-going) iMesh_FMDB development
    - data type change of mesh instance from pPart to pMesh
    - memory leak w/ valgrind
  • (on-going) iMeshP_FMDB development

SCUtil/iBase

  • NONE

GRM/iRel

  • (completed) NONE type proposal review

[ Planned Week 14 Activities ]

FMDB v1.2

  • FMDB.h development
  • entity set/entity group integration
  • ghosting development

iMesh/iMeshP

  • iMesh_FMDB debugging
  • memory leak debugging w/ valgrind (serial)
  • iMeshP_FMDB development

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Independent Study ]

  • C++ Templates
  • Design Pattern

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

ITAPS: ITAPS 1.2 Released

Added by Mark Miller over 6 years ago

Announcing the 1.2 release of ITAPS interfaces & services.

This release announcement consists of the following sections

1. Overview
2. Software in this release
3. Obtaining the software
4. Interface Compliance
5. Compliance Variations

1. Overview
-----------

ITAPS is a collaboration focused on the development of common interfaces to
geometry, mesh, and associated data, and on the development of services
interacting through these interfaces. The iMesh interface provides access
to unstructured mesh and data associated with that mesh. ITAPS is also
developing the iGeom interface, for accessing CAD data, iMeshP, providing
parallel mesh functionality and constructs, and iRel, for relating entities
between these interfaces.

The 1.2 release of ITAPS consists mainly of an update to the iMesh interface,
with coordinated releases of the various services using or implementing iMesh.
A major focus of effort for this release is on software quality and interface
compliance testing, primarily for the iMesh interface. Nonetheless,
various of the software products that are part of this release also include
implementations of iGeom, iMeshP and iRel.

2. Software in this Release
---------------------------

This release consists of the following implementations of the ITAPS interfaces
(implementations marked with an asterisk (*) also include partial
implementations of iMeshP):

iMesh: FMDB*, GRUMMP, MOAB*, RefImpl
iGeom: CGM, GMI
iRel: Lasso

The following mesh-based services are also included:
Mesquite (mesh smoothing)
Swapping (topological mesh improvement)
eyeMesh browser (mesh metadata browsing)
Zoltan (mesh partitioning)
VisIt plugins (visualization)
PyTaps (Python interfaces to iMesh, iGeom, iRel)

More information on these implementations and services can be found from the
ITAPS web site (http://www.itaps.org).

3. Obtaining the software
-------------------------

To obtain and install these various software products, it is probably
easiest to use a new tool developed for this purpose; build_itaps. You
can use wget, curl or 'svn co' to obtain this tool...

https://redmine.scorec.rpi.edu/svn/itaps/software/branches/1.2RC/tools/build_itaps

See http://redmine.scorec.rpi.edu/projects/itaps/wiki/_build_itaps_primer_
for a short primer in using build_itaps.

Not all services have been integrated into the build_itaps script. For those
that are not, separate README files explain how to build those products.

4. iMesh Interface Compliance
-----------------------------

Constructing an application from a diverse set of independently developed
software components can be a challenging task. Although common interfaces
like iMesh simplify that task, it must still be verified that all
components implement the parts of iMesh required by a given application.
We have developed an iMesh compliance test suite, containing over 1000
separate checks on the implementation and behavior of various iMesh functions.
While the compliance test is not comprehensive, it does cover the majority of
functionality provided through iMesh. The iMesh implementations provided with
version 1.2 of ITAPS have the following pass rates for the current compliance
test:

iMesh implementations (-compliance)
MOAB (98
), FMDB (100%), GRUMMP (100%), RefImpl (100%)

The only major functionality in iMesh not tested in the current compliance
test is creation of 3D entities.

For implementation specific variations from the specification, please see the
individual product's release notes for more information.

5. Compliance Variations of Significance
-------------------------------------
Below we enumerate compliance variations of significance. These
are slated to be addressed by the next (1.3) release.

1. Generic data functions use void* for the data pointer type in the
specification but implementations may use void** requiring explicit
cast by caller. See http://redmine.scorec.rpi.edu/issues/188
2. Behavior of iterators when associated entity set undergoes modification
may vary between implementations.
See http://redmine.scorec.rpi.edu/issues/198
3. 3D mesh entity creation from vertices or edges not supported by all
iMesh implementations. See http://redmine.scorec.rpi.edu/issues/191

PUMI_MESH (FMDB): FMDB Weekly #12 (March 21 - March 25)

Added by E. Seegyoung Seol over 6 years ago

[ Week 12 Activities ]

FMDB

  • constraint: single part per mesh
  • (on-going) entity set and entity group integration
    - mesh migration
    - distributed mesh file I/O
  • (on-going) ghosting
    - N-layer creation
    - layer accumulation
    - mesh verification
  • (on-going) FMDB.h development
    - missing api functions (region creation, entity search, etc)
  • (on-going) User's Guide update

iMesh/iMeshP

  • (on-going) iMesh_FMDB improvement & debugging
    - tet creation error with itaps swapping
    - seg. fault with tagging

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 13 Activities ]

FMDB v1.2

  • FMDB.h development
  • entity set/entity group integration
  • ghosting development
  • memory leak debugging with Valgrind (serial)

iMesh/iMeshP

  • iMesh_FMDB debugging
  • iMeshP_FMDB development (Release target: April 3)

SCUtil/iBase

  • starting off SCOREC error code

GRM/iRel

  • NONE type proposal review

[ Active Issues/Bugs ]

  • move table of # topological entity to part level (current: global)
  • move mesh representation information to mesh level (current: part level)
  • Mesh Adapt not working with FMDB
  • region creation with vertices/edges not supported
  • iMesh mesh instance implemented with part handle
  • FMDB.h not returning actual error code
  • fortran support through itaps interface
  • legacy control return with file i/o error
  • inconsistent name mangling
  • replacing iMesh iterator with FMDB iterator api
  • memory leak proof with Valgrind
  • merging with FMDB-PIMA
  • entity set/tag file I/O support for ncdf & vtk
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • (RESOLVED - Mar 18) tet deletion error with itaps swapping
  • (DISCARDED - Mar 17) linking error with Swapping
  • (RESOLVED - Mar 17) FMDB/test/serial: mesh format portability (sms, vtk, ncdf conversion fails)
  • (RESOLVED - Mar 17) iMesh failure with vtk mesh file
  • (RESOLVED - Mar 11) set/getByteTag with data handle doesn't work
  • (RESOLVED - Mar 11) removing ITAPS compilation flag
  • (DISCARDED - Mar 11) iMesh compliance test: non-advancing iterator (type==all, topo=all)
  • (DISCARDED - Mar 9) iMesh_FMDB: running with Mesquite
  • (RESOLVED-Mar 04) removed entity, entity set, part handle are not deleted from tagging storage
  • (NEW-Mar 04) tagging improvement with tracking option for efficient forced tag deletion
  • crash on partitioned mesh loading (+512 parts on B/G)
  • deleting multiple mesh instances fails (chronic bug)
  • improper memory management with tagging
    - simultaneous, multiple mesh instances give error due to single tag management scheme across multiple mesh objects
    - multiple mesh instances a in a row give error during tag data deletion (cause: Singleton tagging management class)

[ Pended Issues/Bugs ]

  • FMDB
    - intelligent memory management & leak proof
    - regression testing suite incorporated with Automake and Nightly Build
    - local partitioning (requestor: Min)
    - FMDB.h consolidation
    - automatic attached data migration
    - merging entity group with entity set
    - improved algorithm for migration procedure
    - (held) Exodus II mesh format (requestor: Sandia)
    - (held) 2D NCDF mesh support
  • iMesh(P)
    - entity set/tag file I/O with vtk and ncdf files
    - iMeshP implmentation: linking with iZoltan
    - iMeshP compliance test: standardized autotool options
    - distributed vtk file I/O with partition info
  • GMI/iGeom
    - incorporating with entity set and iterator
    - implementing GMI.h
  • SCUtil/iBase
    - folder reorganization
    - implementing api
    - removing FMDB dependency
    - revisiting entity set for improvement (removing tight coupling with FMDB)
    - combinging entity group with entity set
    - templated tag
  • GRM/iRel
    - NONE
  • MeshAdapt
    - incorporating decision procedure to compute partition objects to migrate before calling FMDB::M_migrate
  • Miscellaneous
    - SCOREC S/W web page update
    - Doxygen

[ Independent Study ]

  • NONE

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #11 (March 14 - March 18)

Added by E. Seegyoung Seol over 6 years ago

[ Week 11 Activities ]

FMDB

  • (on-going) FMDB.h development
    - constraint: single part per mesh
    - missing api functions
    - improving ghosting & related code (e.g. FMDB_Mesh_Verify, etc.)
  • (on-going) User's Guide update
  • (completed) SCOREC release (March 18)
  • (completed) SVN repo restructuring - www, software, docs

iMesh/iMeshP

  • (on-going) iMesh_FMDB improvement & debugging
    - tet deletion error with itaps swapping
    - seg. fault with tagging (tagging spec discrepancy between FMDB and iMesh test)

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 12 Activities ]

FMDB v1.2

  • FMDB.h development
  • ghosting development

iMesh/iMeshP

  • iMesh_FMDB debugging
  • iMeshP_FMDB development (Release March 30)

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE type proposal review

[ Active Issues/Bugs ]

  • legacy control return with file i/o error
  • inconsistent name mangling
  • tet deletion error with itaps swapping
  • replacing iMesh iterator with FMDB iterator api
  • memory leak proof with Valgrind
  • merging with FMDB-PIMA
  • entity set/tag file I/O support for ncdf & vtk
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • (DISCARDED - Mar 17) linking error with Swapping
  • (RESOLVED - Mar 17) FMDB/test/serial: mesh format portability (sms, vtk, ncdf conversion fails)
  • (RESOLVED - Mar 17) iMesh failure with vtk mesh file
  • (RESOLVED - Mar 11) set/getByteTag with data handle doesn't work
  • (RESOLVED - Mar 11) removing ITAPS compilation flag
  • (DISCARDED - Mar 11) iMesh compliance test: non-advancing iterator (type==all, topo=all)
  • (DISCARDED - Mar 9) iMesh_FMDB: running with Mesquite
  • (RESOLVED-Mar 04) removed entity, entity set, part handle are not deleted from tagging storage
  • (NEW-Mar 04) tagging improvement with tracking option for efficient forced tag deletion
  • crash on partitioned mesh loading (+512 parts on B/G)
  • deleting multiple mesh instances fails (chronic bug)
  • improper memory management with tagging
    - simultaneous, multiple mesh instances give error due to single tag management scheme across multiple mesh objects
    - multiple mesh instances a in a row give error during tag data deletion (cause: Singleton tagging management class)

[ Pended Issues/Bugs ]

  • FMDB
    - intelligent memory management & leak proof
    - regression testing suite incorporated with Automake and Nightly Build
    - local partitioning (requestor: Min)
    - FMDB.h consolidation
    - automatic attached data migration
    - merging entity group with entity set
    - improved algorithm for migration procedure
    - (held) Exodus II mesh format (requestor: Sandia)
    - (held) 2D NCDF mesh support
  • iMesh(P)
    - entity set/tag file I/O with vtk and ncdf files
    - iMeshP implmentation: linking with iZoltan
    - iMeshP compliance test: standardized autotool options
    - distributed vtk file I/O with partition info
  • GMI/iGeom
    - incorporating with entity set and iterator
    - implementing GMI.h
  • SCUtil/iBase
    - folder reorganization
    - implementing api
    - removing FMDB dependency
    - revisiting entity set for improvement (removing tight coupling with FMDB)
    - combinging entity group with entity set
    - templated tag
  • GRM/iRel
    - NONE
  • MeshAdapt
    - incorporating decision procedure to compute partition objects to migrate before calling FMDB::M_migrate
  • Miscellaneous
    - SCOREC S/W web page update
    - Doxygen

[ Independent Study ]

  • NONE

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #10 (March 7 - March 11)

Added by E. Seegyoung Seol over 6 years ago

[ Week 10 Activities ]

FMDB v1.2

  • (completed) tagging & file I/O improvement
  • (on-going) FMDB.h development
    - constraint: single part per mesh
    - missing api functions (reflecting Fabien's feedback)
    - improving ghosting & related code (e.g. FMDB_Mesh_Verify, etc.)
  • (on-going) User's Guide update

iMesh/iMeshP

  • (on-going) iMesh_FMDB improvement & debugging
    - linking error with Swapping
    - seg. fault with --error (array tagging)
    - doesn't run with .vtk file (classification info)
  • (completed) ITAPS tarball release on March 10

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 11 Activities ]

FMDB v1.2

  • FMDB.h development
  • ghosting development
  • packaging for SCOREC release (March 18)
  • SVN repo restructuring
    - www: web pages and contents
    - doc: user's guide, papers, etc.
    - software: trunk, tag, branches

iMesh/iMeshP

  • iMesh_FMDB debugging
  • iMeshP_FMDB development

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Active Issues/Bugs ]

  • iMesh failure with vtk mesh file
  • replacing iMesh iterator with FMDB iterator api
  • memory leak proof with Valgrind
  • linking error with Swapping
  • merging with FMDB-PIMA
  • entity set/tag file I/O support for ncdf & vtk
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • FMDB/test/serial: mesh format portability (sms, vtk, ncdf conversion fails)
    . mesh file written from another mesh format cannot be loaded back
    . e.g. sms written from ncdf or vtk file cannot be loaded back, and vice versa
  • set/getByteTag with data handle doesn't work
  • removing ITAPS compilation flag
  • iMesh compliance test: non-advancing iterator (type==all, topo=all)
  • iMesh_FMDB: running with Mesquite
  • (RESOLVED-Mar 04) removed entity, entity set, part handle are not deleted from tagging storage
  • (NEW-Mar 04) tagging improvement with tracking option for efficient forced tag deletion
  • crash on partitioned mesh loading (+512 parts on B/G)
  • deleting multiple mesh instances fails (chronic bug)
  • improper memory management with tagging
    - simultaneous, multiple mesh instances give error due to single tag management scheme across multiple mesh objects
    - multiple mesh instances a in a row give error during tag data deletion (cause: Singleton tagging management class)

[ Pended Issues/Bugs ]

  • FMDB
    - intelligent memory management & leak proof
    - regression testing suite incorporated with Automake and Nightly Build
    - local partitioning (requestor: Min)
    - FMDB.h consolidation
    - automatic attached data migration
    - merging entity group with entity set
    - improved algorithm for migration procedure
    - (held) Exodus II mesh format (requestor: Sandia)
    - (held) 2D NCDF mesh support
  • iMesh(P)
    - entity set/tag file I/O with vtk and ncdf files
    - iMeshP implmentation: linking with iZoltan
    - iMeshP compliance test: standardized autotool options
    - distributed vtk file I/O with partition info
  • GMI/iGeom
    - incorporating with entity set and iterator
    - implementing GMI.h
  • SCUtil/iBase
    - folder reorganization
    - implementing api
    - removing FMDB dependency
    - revisiting entity set for improvement (removing tight coupling with FMDB)
    - combinging entity group with entity set
    - templated tag
  • GRM/iRel
    - NONE
  • MeshAdapt
    - incorporating decision procedure to compute partition objects to migrate before calling FMDB::M_migrate
  • Miscellaneous
    - SCOREC S/W web page update
    - Doxygen

[ Independent Study ]

  • NONE

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

PUMI_MESH (FMDB): FMDB Weekly #9 (Feb 28 - Mar 4)

Added by E. Seegyoung Seol over 6 years ago

[ Week 9 Activities ]

FMDB v1.2

  • tagging improvement
    - (completed) array/entity set tagging
    - (on-going) tagging file I/O
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - improving ghosting & related code (e.g. FMDB_Mesh_Verify, etc.)
  • (on-going) User's Guide update: chap 5 & chap 6. api and programming instructions

iMesh/iMeshP

  • iMesh_FMDB improvement & debugging
    - linking error with Swapping
    - current pass rate
    --no-save-load 97%
    --no-save-load --error 94%
    save-load 97%
    save-load --error Seg Fault
    - See "Active Issues" for iMesh bug details

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Planned Week 10 Activities ]

FMDB v1.2

  • entity set/entity group integration
  • tagging - debugging and file I/O
  • ghosting development
  • packaging for ITAPS release (March 5)

iMesh/iMeshP

  • iMesh_FMDB improvement & debugging

SCUtil/iBase

  • NONE

GRM/iRel

  • NONE

[ Active Issues/Bugs ]

  • set/getByteTag with data handle doesn't work
  • iMesh compliance test: failure with vtk mesh file
  • removing ITAPS compilation flag
  • iMesh compliance test: non-advancing iterator (type==all, topo=all)
  • iMesh_FMDB: replacing iMesh iterator with FMDB iterator from iMesh implementation
  • iMesh_FMDB: running with Mesquite
  • iMesh_FMDB: running with Swapping
  • iMesh_FMDB: memory leak proof with Valgrind
  • FMDB: linking error with Swapping
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • FMDB/test/serial: mesh format portability (sms, vtk, ncdf conversion fails)
    . mesh file written from another mesh format cannot be loaded back
    . e.g. sms written from ncdf or vtk file cannot be loaded back, and vice versa
  • (RESOLVED-Mar 04) removed entity, entity set, part handle are not deleted from tagging storage
  • (NEW-Mar 04) tagging improvement with tracking option for efficient forced tag deletion
  • crash on partitioned mesh loading (+512 parts on B/G)
  • deleting multiple mesh instances fails (chronic bug)
  • improper memory management with tagging
    - simultaneous, multiple mesh instances give error due to single tag management scheme across multiple mesh objects
    - multiple mesh instances a in a row give error during tag data deletion (cause: Singleton tagging management class)

[ Pended Issues/Bugs ]

  • FMDB
    - intelligent memory management & leak proof
    - regression testing suite incorporated with Automake and Nightly Build
    - local partitioning (requestor: Min)
    - FMDB.h consolidation
    - automatic attached data migration
    - merging entity group with entity set
    - improved algorithm for migration procedure
    - (held) Exodus II mesh format (requestor: Sandia)
    - (held) 2D NCDF mesh support
  • iMesh(P)
    - entity set/tag file I/O with vtk and ncdf files
    - iMeshP implmentation: linking with iZoltan
    - iMeshP compliance test: standardized autotool options
    - distributed vtk file I/O with partition info
  • GMI/iGeom
    - incorporating with entity set and iterator
    - implementing GMI.h
  • SCUtil/iBase
    - folder reorganization
    - implementing api
    - removing FMDB dependency
    - revisiting entity set for improvement (removing tight coupling with FMDB)
    - combinging entity group with entity set
    - templated tag
  • GRM/iRel
    - NONE
  • MeshAdapt
    - incorporating decision procedure to compute partition objects to migrate before calling FMDB::M_migrate
  • Miscellaneous
    - SCOREC S/W web page update
    - Doxygen

[ Independent Study ]

  • NONE

[ Remarks ]

  • FMDB team meeting: Wednesday 11am-12pm
  • ITAPS telecon: Thursday 12pm-1pm
  • iMeshP compliance test verification with FMDB pended due to incomplete implementation such as ghosting & multiple part per process
  • entity group migration with "splitted" entity data stream won't be considered to put into the repository
    Instead, better algorithm for migration procedure will be investigated.

« Previous 1 2 3 4 ... 6 Next »

Also available in: Atom