itaps-parallel FMDB_iMeshP is updated

[txie at scorec.rpi.edu]

Hi all,

One minor thing, the FMDB_iMeshP.tgz tarball is changed to fmdb-1.0.tar.gz
in /usr/local/itaps/Dist directory on the mesh machine.

Thanks,

Ting


> Hi all,
>
> We have finished the following updates to FMDB_iMeshP (as per recent
> requests).
>
>  * 1. Put a tarball of FMDB_iMeshP.tgz in /usr/local/itaps/Dist/  on the
> mesh machine. And put the latest FMDB_iMeshP version into the repository.
>
>  * 2. Modified iMesh_protos.h and iMeshP_protos.h files, and solve Fortran
> name mangling through configure in GNU autoconf.
>
>  * 3. About the iMesh_getEnt2ndAdj() function, I suggest that we can use
> "bridge_entity_type" and "requested_entity_type" both in the
> specification and in the function declaration.  They seems to be more
> clear.
>
>  /**\brief Get "2nd order" adjacencies to an entity
>  * Get "2nd order" adjacencies to an entity, that is, from an entity,
> through
>  * other entities of a specified "bridge" dimension, to other entities
> of another
>  * specified "to" dimension.
>  * \param instance iMesh instance for this call
>  * \param entity_handle Entity from which adjacencies are requested
>  * \param bridge_entity_type  Type of bridge entity for 2nd order
> adjacencies
>  * \param requested_entity_type Type of adjacent entities returned
>  * \param adjacent_entities Adjacent entities
>  * \param adjacent_entities_allocated Allocated size of returned array
>  * \param adjacent_entities_size Occupied size of returned array
>  * \param err
>  */
>   void iMesh_getEnt2ndAdj( iMesh_Instance instance,
>                            iBase_EntityHandle entity_handle,
>                            int bridge_entity_type,
>                            int requested_entity_type,
>                            iBase_EntityHandle** adjacent_entities,
>                            int* adjacent_entities_allocated,
>                            int* adjacent_entities_size,
>                            int* err );
>
>   * 4. Modified and updated the iMesh-Defs.inc.in file based on Lori and
> Karen's suggestions, and iMesh-Defs.inc file can be created through
> autoconf.
>
>   * 5. Make sure that iMesh_load function can load *.sms and *.vtk file.
>
> Please let us know if there are any problems (which will mostly be
> considered after SC08). Also keep in mind that we are not considering any
> further changes to FMDB install (and tar ball) on mesh-machine before SC08
> (only typos and critical bugs are likely to be considered before SC08).
>
> Thanks,
> Ting (and RPI team)
>
>
>
>