Proposal for telling an implementation what adjacency info an app/service needs

[Tim Tautges]

Ok, then we do need a function that specifies what an application needs.  The last time this came up (when GRUMMP was 
being run on MOAB) that's what we'd decided should be used (the we might be Carl & me, but I'm sure it wasn't just me).

- tim

Jason Kraftcheck wrote:
> Tim Tautges wrote:
>> Hmm, I'm not sure I like this.  I thought setAdjTable was supposed to be
>> used to request which entities an application or service needed.  I've
>> coded it into MOAB's iMesh implementation that way, IIRC.  Looking at
>> the current comments to getAdjTable, we should put something there
>> describing what the values mean then.  I would vote for setAdjTable
>> being the function used to request intermediate-dimension entities.
>>
> 
>>From iMesh.h:
> 
>      * Get the adjacency table for this implementation.  This table
>      * is a 4x4 array, with indices 0-based, where A(i,j) (i=row, j=column)
>      * represents the relative cost of retrieving adjacencies between
>      * entities of dimension i to entities of dimension j
> 
> It clearly says the "cost of retrieving", not "will exist" or some such thing.
> 
> - jason
> 
> 
> 

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706