itaps-parallel Notes and assignments

[Tim Tautges]

Comments on various TODO items in header file:

prefix_getNumOfTypePar: I agree with the last statement from Carl, Lori 
and RPI.  However, one item missing is a way for apps to tell the 
interface what criteria to use to determine that sets are the same.  In 
my apps, I identify tag names which, if their values are the same, mean 
two sets are the same (e.g. DIRICHLET_SET for boundary conditions).  I 
think that's an application's call because different apps will have 
different kinds of criteria.  Maybe that's not critical for the first 
go-round, assuming implementations will initialize in parallel knowing 
which sets are shared, but it will prevent some apps from working on 
iMesh alone.

prefix_addEntToPart, etc.: we should avoid #define'ing these, because it 
confuses the issue of whether set-based functions can be used.  It 
should be made clear from a very high level that a group of entity set 
functions operates on parts too.

- tim

Devine, Karen D wrote:
> OK, we're in the home stretch in preparation for bootcamp.
> 
> Our next phone conf is scheduled 2/28 at 1pm PST.  The biggest issues still
> in question are (1) copies and communication for them, (2) communication of
> tag info, and (3) what should be included in prefix_UpdatePartitionPar.
> 
> We probably have only two phone confs left before bootcamp, so please
> schedule 1.5 hours for the call on 2/28.  I'd like to make significant
> progress on (1) and (2).
> 
> Assignments:
> 
> Carl & Onkar:  Revise the functions for copies and non-collective
> communication.
> 
> Tim:  Submit functions for exchanging tag data.
> 
> All:
> -  Send a list of data you'd like to have pre-computed in
> prefix_UpdatePartitionPar (allowing other functions to work without
> communication).
> 
> -  Vote for your favorite definition of part neighbor (or submit your
> objections to both along with a definition that you like better):
> 
>    Definition X:  Two (or more) parts are neighbors with respect to entity
> type A if at least one entity in each of the parts has a common lower- or
> higher-dimensional adjacent entity of specified entity type A.
> 
>    Definition Y:  Two (or more) parts are neighbors with respect to entity
> type A if any entity of specified entity type A has at least one adjacent
> higher- or lower-dimensional entity in each of the parts.
> 
> -  Read the attached updated DraftInterface.h, paying attention to items
> marked TODO.
> 

-- 
================================================================
"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