itaps-parallel inconsistencies in getAllVtxCoords

Jason Kraftcheck kraftche at cae.wisc.edu
Sun Sep 14 21:11:21 CDT 2008


Carl Ollivier-Gooch wrote:
> Onkar Sahni wrote:
>> Or in case of mesh over 3D-surface curve.
>>
>> - Onkar
>>
>>> Lori,
>>>
>>> I would say num_vtx*3 as 2D meshes can be non-aligned with x-, y- and z-
>>> axes resulting in non-constant value for the 3rd dim. (which is not
>>> considered in case of num_vtx*num_dim when num_dim=2).
> 
> I'd argue that in these cases, num_dim should be 3, not 2.  After all, 
> the call is getGeometricDimension, not getTopologicalDimension... :-)

I agree.  If the implementation (e.g. MOAB) doesn't support 
geometrically 2D meshes then it should always return 3 from 
getGeometricDimension.  If there is a need to check the topological 
dimension of a mesh, the application should just ask for the number of 
regions in the mesh.

- jason





More information about the itaps-parallel mailing list