FMDB Developer Notes

Status

  • incomplete iMeshP support
  • incomplete iGeom
  • no iRel support

Releases

How to Update Users Guide

1. Checkout the source

  svn co http://redmine.scorec.rpi.edu/svn/fmdb/docs

2. "cd docs/tex" and edit tex files
- chap5.tex contains api specification
- chap6.contains sample programs

3. Compile

  pdflatex FMDB.tex 

4. Upload modified tex files and FMDB.pdf
- copy generated "docs/tex/FMDB.pdf" to "docs" folder and do "svn commit" from "docs" folder

Requirements for all new development

Portability Assurance

Update autotool if needed

Memory leak proof through valgrind

User's Guide and Release Note update

Performance assurance (memory and time)

Release conformance testing

  • FMDB/test/serial
  • multi-part testing in FMDB/test/parallel
       #TEST 1: load 4 part mesh and distribute to 40 parts (10 parts per process)
      $MPI_HOME/bin/mpirun -np 4 singlePart_parallel /bigtmp/shurik/meshes/cube/uniform_33k/4/geom.sms out.sms  1 0 10 0
    
       #TEST 2: load serial mesh and distribute to 50 parts (10 parts per process)
      $MPI_HOME/bin/mpirun -np 4 singlePart_parallel /bigtmp/shurik/meshes/cube/uniform_33k/geom.sms out.sms  0 0 50 0
    
  • communicator testing in FMDB/test/parallel
       #TEST 1: 2 communicators (4 processes per comm), distributed mesh loading, 10 migration and 1 load balancing
       $MPI_HOME/bin/mpirun -np 8 singlePart_parallel /bigtmp/shurik/meshes/cube/uniform_33k/4/geom.sms out.sms 1 10 
    
       #TEST 2: 3 communicators (3 processes per comm), serial mesh loading & partitioning, 20 migration and 2 load balancing
       $MPI_HOME/bin/mpirun -np 9 singlePart_parallel /bigtmp/shurik/meshes/BL/Parasolid/pipe/2k/geoms.sms out.sms 0 20 
    
  • FMDB/test/itaps
  • iMesh compliance test "https://redmine.scorec.rpi.edu/svn/itaps/software/trunk/interfaces/iMesh/test/unit"
  • FMDB with support for distributed meshes
  • Build MeshAdapt
    • The MeshAdapt tests are successful when there are no errors in the output and the adapted meshes are qualitatively the same as meshes previously verified.

Weekly Developer News