Software Needs for External Development Projects
(Summary of expected work packages needed through the end of the year)
26jun03 bsm

-A note: the "continued consultation" requests have been reasonably
well supported but it would be nice if they were officially on
people's priority list with some time allocated.  This is an important
contingency for the external development projects.

I. Caltech Continuum Backend

status: CIT has delivered a complete software interface library &
backend simulator, together with documentation (much of which has been
previously reviewed, but there are some changes).

 A) Caltech Backend Manager: Target is to complete this
     in the first half of Dec03
 -ideally we would do this sooner
 -if we cannot do it soon, I would like a review of the
   code & documentation Caltech has provided soon.

 B) CDR Support
 -CDR in mid to late September (tentatively)
 -work needed: 
   -->thorough and critical review of software documentation.  if I(A) is already 
	done or in progress this task is easier.
   -->1 full day of meetings
   -->some work with BSM & Caltech developing & reviewing data 
	analysis plans, use cases

 C) Continued consultation (~1 hour per week) through the end of the year
  -One project meeting before the CDR will require a half day of meetings
	and roughly 2 hours support for each of 2 weeks.   

 D) Data analysis software for CCB.
 -Probably to be developed by BSM with Tim Pearson, in collaboration with SDD
 -BSM is unlikely to have substantial time for this until late in the year, but
   doesn't anticipate it's a very difficult job.
 -It is possible we could get Caltech to Contribute to this effort, if we can
   provide suitable guidance.  

II. 1cm Rx Manager

 -Target: To Complete this in the last half of October.
 -Galen Watts will provide an interface document prior to this.
 -sponsors will presumably be Mason & Watts.

III. Penn Array Receiver

 A) CDR support: CDR in late August or early September?

 B) Continued consultation at roughly 1 hour per week through the end of
	the year, except this summer (Jul+Aug), when we need a higher level of 
	consultation (2 hours per week), including possibly a 2-day trip 
	to U.Penn or Goddard, as Penn is working to document the device interfaces 
	and operating procedures.

    -->A major goal for us at next week's Penn Array project meeting should
	be to emerge with a plan for the software, that is, what we need to do
	to ensure that Penn Array delivers what we need in a timely manner.
  
 C) Official support for Penn Array Data analysis is probably not needed this
	year, beyond Brian's general desire to be educated & in the loop about
	the emerging framework.

	Early next year this should come up in priority as Brian & Bill Cotton
	have a better idea what we need to do.