All,

The next conference call will be

	Time:   Wednesday June 27  1:00 PM EDT
  
	Agenda: Messaging API & Associated Library Functions.
               
-----------------------------------------------------------------------------
MEETING SCHEDULE
------------------------------------------------------------------------------
Looking at all the travel schedules for the summer a nearly optimal
solution for conference calls is

	Wednesday June 27
        Thursday  July 12      (Chip and Robert not available)
	Thursday  July 26      (Chip not available)
	Thursday  Aug   9
	Thursday  Aug  16 
	Thursday  Aug  30
        Thursday  Sept 13

(Also during Lattice meeting, Aug 17-25 we should find a time for
those attending to meet face to face.)


-------------------------------------------------------------------------------
SUBCOMMITTEES? 
------------------------------------------------------------------------------

I would like to take some very concrete steps toward defining and
implementing libraries for the QCD_API.  I think it is a good idea to
split into subcommittees to do a first pass at defining the API and an
associated set of library routines. (What do you all think?)

Just to start the ball rolling suppose for now we separate into 2
tasks as follows:

	QCD_API_messaging:      (my level 2) 
	Chip, Robert E, Celso,  Rich (consult with Creutz and others)

	QCD_API_linear_algebra: (my level 1)  
        Bob M., Carleton, Don H. (Andrew Pochinsky and others)


At the lowest level, both the messaging API (e.g. see http://www.jlab.org/
~watson/lqcd/MessageAPI.htm) and the per processor linear algebra API
(e.g. MILC/libraries) are independent of the lattice layout. Soon we
should form a 3rd subcommittee on

         QCD_API_data_layout:  (transition to my level 3)
	 All (talk to Greg for data formats on "tape").

choosing appropriate people to work on this when we have a clearer
definition of this task and how it interfaces with the first two.

The best,

Rich