Minutes from Internal Penn Array "CDR Needs" Meeting
-------------------------------------------------------

ATTENDANCE: Brian Mason, Nicole Radziwill, John Ford, Roger Norrod,
Richard Prestage, Phil Jewell

04jun03 bsm

Software

-We should make clear to Penn our intent re: the control software,
which is to be responsible ourselves for what gets put on the
telescope, and to write our own manager with interfaces at the
device-driver level.

-To do this we need specifications: Penn will be responsible for
reverse engineering the system and, generally, doing whatever is
necessary to document all the degrees of freedom, what they mean, and
how they are to be manipulated to observe successfully.

-We should distinguish between hardware interface specifcations
and operational procedures in this process.

Mechanical/Packaging

-we are in a pretty good state on the electronics packaging, and
need to close this iteration.

-once we know what electronics they have, we can design the rfi
enclosure.  this will take a few weeks work, but needs to propagate
through the queue. we shouldn't hold the cdr for this, but should
define an envelope for the rfi enclosure for the cdr (mount points
etc)

-We should get a statement from Bob Anderson and Dennis Egan re: the
acceptable weight for the receiver.

-Once we have good drawings of the receiver from Penn, we can assess
the mounting strategy/mount points in some detail.  When we have these
drawings we will give them to our engineers who will do so.  From the
point that we have the drawings this will probably take a couple of
months.

Acceptance Tests

 *should include cryo performance as a function of ZA

 *should include RFI tests on finished system

 *in connection with the software-- Penn must demonstrate
	the ability to control all degrees of freedom
	necessary for on-telescope operations including
	observing.  They can do this however they like
	(java with labview, etc).  As indicated above
	these operations should be documented.

Commissioning Strategy

-We should pursue an aggressive/minimal delay first light strategy.
	This involves 1) a reasonably conservative bandpass;
	2) not allowing delays for a filterwheel (which could follow
	the next season if funded).

-We should be explicit & firm about not commissioning before
	the M&C software is ready.  It is our job to have this
	ready on time.

Schedule/Organization

-Given the work required, we are looking at a CDR a few months away.

-We should check Penn's schedule-- we think they are usefully employed
in the meantime without a CDR (eg, on the electronics & software), but
must make sure we're not proceeding on things that need to be
reviewed.

-A project meeting soon is needed.  Reasonable dates seem to be: July
2,3, and 7 through 11.  We should get Dominic Benford here for that.


SUMMARY OF ACTIONS
------------------

*Brian: follow up with Penn on
	a) the commissioning strategy & lab reqmts
	b) their schedule through the summer, leading up to
	a CDR later on.
	c) the reverse-engineering approach to the 
	electronics interface and division of responsibilities
	d) also, relay to them the suggestion to get a
	review of the optics before the CDR.
	e) obtaining mechanical drawings
	f) closing the current iteration on electronics

*Brian: close the loop with Dennis & Bob on the acceptable weight

*Richard/Phil: dig up some examples of acceptance tests from
	previous projects

*John & Roger: Agree on the list of required drawings I'm to 
	pass on to Penn this week.

*John: Follow up on closing the current electronics iteration
	-send penn a serial to fiber solution for the
	 cal switch  (tx/rx; solid state relay output)
	-check on whether we have space for the computer, 
	GPIB/fiber box, and serial/fiber box in an existing
	cabinet in the RX room (although we may now be open
	to putting everything on the rx?)