News

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.

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.

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.

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.

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.

FMDB Weekly #8 (Feb 21 - Feb 25)

Added by E. Seegyoung Seol over 6 years ago

[ Week 8 Activities ]

FMDB v1.2
  • (on-going) entity set/entity group integration
  • tagging improvement
    - (completed) byte type tagging for entity/entity set/part
    - (on-going) array/entity set tagging
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - improving ghosting & related code (e.g. FMDB_Mesh_Verify, )
  • (completed) autotool packaging for Sandia release
  • (completed) User's Guide update: chap 7. compilation instructions
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - (completed) set/get adjacency table
    - See "Active Issues" for iMesh bug details
SCUtil/iBase
  • NONE
GRM/iRel
  • NONE

[ Planned Week 9 Activities ]

FMDB v1.2
  • entity set/entity group integration
  • array/entity set tagging
  • parallel FMDB.h development
  • packaging for ITAPS release (March 5)
  • User's Guide update: chap 6. programming instructions
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - revising with FMDB.h
SCUtil/iBase
  • NONE
GRM/iRel
  • NONE
[ Independent Study ]
  • NONE
[ Active Issues ]
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • iMesh compliance test: infinite loop with no-advancing entity iterator
  • 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
  • removed entity, entity set, part handle are not deleted from tagging storage
  • 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 ]

  • 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
[ 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.

FMDB Weekly #7 (Feb 14 - Feb 18)

Added by E. Seegyoung Seol over 6 years ago

[ Week 7 Activities ]

FMDB v1.2
  • (on-going) entity set/entity group integration
  • tagging improvement
    - (completed) byte type tagging for entity
    - (on-going) byte type tagging for part & entity set
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - improving 1-layer ghosting & related code (e.g. FMDB_Mesh_Verify, )
  • (completed) packaging for Sandia release (parallel)
  • (on-going) User's Guide update
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - (on-going) implementing with FMDB.h api calls
    - See "Active Issues" for iMesh bug details
SCUtil/iBase
  • NONE
GRM/iRel
  • NONE

[ Planned Week 8 Activities ]

FMDB v1.2
  • entity set/entity group integration
  • byte type tagging for part/entity set
  • parallel FMDB.h development
  • packaging for ITAPS release (Feb 25)
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - revising with FMDB.h
SCUtil/iBase
  • NONE
GRM/iRel
  • NONE
[ Independent Study ]
  • NONE
[ Active Issues ]
  • vertex coordinate precision problem (reporter: Min&Kai)
  • mesh loading failure with process grouping (reporter: Fan)
  • iMesh compliance test: infinite loop with no-advancing entity iterator
  • FMDB/test/iter: PartIter with type 4 (all types) returns double of # entities of all types
  • 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
  • removed entity, entity set, part handle are not deleted from tagging storage
  • 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 ]

  • 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
[ 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.

FMDB Weekly #6 (Feb 07 - Feb 11)

Added by E. Seegyoung Seol over 6 years ago

[ Week 6 Activities ]

FMDB v1.2
  • (on-going) entity set/entity group integration
  • (on-going) tagging improvement
    - byte type tagging & generic get/set functions
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - migration/global&local partitioning/ghosting
  • (on-going) packaging for Sandia release
  • (on-going) User's Guide update
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - (on-going) implementing with FMDB.h api calls
    - See "Active Issues" for iMesh bug details
SCUtil/iBase
  • NONE
GRM/iRel
  • NONE

[ Planned Week 7 Activities ]

FMDB v1.2
  • entity set/entity group integration
  • tagging improvement
  • parallel FMDB.h development
  • memory leak check with Valgrind
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - revising with FMDB.h
SCUtil/iBase
  • NONE
GRM/iRel
  • prototype development
[ Independent Study ]
  • NONE
[ Active Issues ]
  • PartIter with type 4 (all types) returns double of # entities of all types
  • mEntity::get (upward adjacency) crashes when no upward adjacency exists
  • 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
  • generic data tag fails
  • tag array function fails
  • 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

[ Pended Issues ]

  • FMDB
    - garbage collection (automatic or user-triggered)
    - 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
[ 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.

FMDB Weekly #5 (Jan 31 - Feb 4)

Added by E. Seegyoung Seol over 6 years ago

[ Week 5 Activities ]

FMDB v1.2
  • (on-going) entity set/entity group integration
  • (on-going) tagging improvement
    - traceable and non-traceable tag creation
    - byte type tagging & generic get/set functions
    - entity set type tagging
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - defining api for partitioning related functions (Min)
  • (on-going) packaging for Sandia release
  • (on-going) User's Guide update
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - (on-going) implementing with FMDB.h api calls
    - See "Active Issues" for iMesh bug details
SCUtil/iBase
  • NONE
GRM/iRel
  • spec review

[ Planned Week 6 Activities ]

FMDB v1.2
  • entity set/entity group integration
  • tagging improvement
  • parallel FMDB.h development
  • User's Guide update
iMesh/iMeshP
  • iMesh_FMDB improvement & debugging
    - revising with FMDB.h
SCUtil/iBase
  • NONE
GRM/iRel
  • prototype development
[ Independent Study ]
  • NONE
[ Active Issues ]
  • PartIter with type 4 (all types) returns double of # entities of all types
  • mEntity::get (upward adjacency) crashes when no upward adjacency exists
  • after mesh migration/ghosting, the mesh becomes invalid
  • 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
  • generic data tag fails
  • tag array function fails
  • 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

[ Pended Issues ]

  • FMDB
    - 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
[ 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.

FMDB Weekly #4 (Jan 24 - Jan 28)

Added by E. Seegyoung Seol over 6 years ago

[ Week 4 Activities ]

FMDB v1.2
  • (on-going) entity set/entity group integration
  • (on-going) tagging improvement
    - traceable and non-traceable tag creation
    - byte type tagging & generic get/set functions
    - entity set type tagging
  • (on-going) parallel FMDB.h development
    - constraint: single part per mesh
    - defining api for partitioning related functions (Min)
  • (on-going) packaging for Sandia release
  • (on-going) User's Guide update
ITAPS
  • iMesh_FMDB improvement & debugging
    - (on-going) implementing with FMDB.h api calls
    - See "Active Issues" for iMesh bug details
SCU/iBase
  • NONE

[ Planned Week 5 Activities ]

FMDB v1.2
  • entity set/entity group integration
  • tagging improvement
  • parallel FMDB.h development
  • User's Guide update
  • FMDB release to SANDIA
ITAPS
  • iMesh_FMDB improvement & debugging
    - revising with FMDB.h
SCUtil/iBase
  • folder restructuring
  • dependency clean-up (SCUtil shall be independent library)
[ Independent Study ]
  • NONE
[ Active Issues ]
  • 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
  • generic data tag fails
  • tag array function fails
  • 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

[ Pended Issues ]

  • FMDB
    - 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
  • FMDB/iMesh(P)
    - iMesh entity handle validity check
    - 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
  • SCU/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
[ Remarks ]
  • FMDB team meeting: Tuesday 1pm-2pm
  • FMDB-itaps meeting: Thursday 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 Next »

Also available in: Atom