[MOAB-dev] Changing adjacency behavior

[Jason Kraftcheck]

On 10/22/2010 02:50 PM, James Porter wrote:
> Now that I look at the adjacency calls in MOAB more, I noticed that the
> following function will fail with the new behavior:
> 
>   MeshTopoUtil::get_average_position(const EntityHandle *entities,
>     const int num_entities, double *avg_position)
> 
> Inside there is a call to get_adjacencies (of dimension 0), but as far
> as I can tell, the function is only ever meant to be called with a list
> of vertices. This means that now, you end up with nothing since entities
> are not adjacent to themselves.
> 
> The question is, can I just get rid of the get_adjacencies call and use
> the entities supplied by the caller, or is the get_adjacencies call used
> for something esoteric? (Higher-order entities maybe?)
> 

Hold on a minute.  I understood the plan to be that we change only the
iMesh_getEntArrAdj behavior to conform to the spec.  I'm not so sure about
changing the underlying MBCore::get_adjacency functionality.

- jason