060622 Mosaic2

UserPreferences

Mosaic2 Engineering June 22, 2006

AGENDA

1. Funding status update (Uomoto)

TSIP funding will arrive soon (old news). All five Magellan partners have agreed to contribute to Mosaic2 construction in proportion to their Magellan telescope share. Their contributions will be for costs beyond the TSIP award, which will go only towards purchasing the CCD detectors.

2. TSIP Reporting requirements for the award (Uomoto)

Tech reps: TSIP Technical Representative is Mark Trueblood (<mtrueblood AT noao DOT edu>, 520.318.8519). Alan Uomoto is the technical counterpart at OCIW.

Meetings: Monthly progress meetings including the IMACS team and TSIP offices in Tucson.

Monthly Reports: Monthly progress reports submitted to the AURA Technical Representative on the 20th of each month for the preceeding calendar month's work. Required items are:

1. Progress summary
2. Detail on last month's progress
3. Major accomplishments
4. Milestones since last progress report
5. Problems encountered and solutions being pursued
6. Key personnel changes
7. Monthly and cumulative expenses, with comparison to budget

I'd also suggest a monthly confirmation and review of the critical path items.

Reviews: A pre-ship review is required. TSIP will nominate 2 external reviewers.

Final report: This is due within 90 days of expiration of the sub-award (May 31, 2007). See the subaward for the contents.

3. Technical requirements (Discussion)

Listing the important items, their values, and the justification. Also things that we rejected and the justification. Here are examples:

1. Wing chips: None. IMACS flexure is predictable and open loop flexure control works on the current camera.
2. X-Y motions: Yes, what's the mechanical range and resolution needed? Response time? How often will we ask for a motion?
3. Z-motion: Yes, what's the mechanical range and resolution needed? Response time? How often will we ask for a motion?
4. Z-axis angular range: What's the Z-axis direction range allowable to maintain performance? What are the contributors (motion stage, mounting repeatability, etc.) and what's the error budget?
5. F/4 ability: Yes. This is to allow use at F/4 in the event of a failure at that focus. This is a goal.
6. Rotate 90 degrees for N&S selection? This is a goal. No crane needed.
7. Focal plane flatness: How co-planar do the detectors need to be? This is probably part of the Z-axis angular range error budget
8. BFD: What's the distance between the window and CCD surface and why?
9. Dimensions
10. Readout time 90 seconds (compare with current slow, 135s, and fast, 94s, times)
11. Readout noise <3.5e
12. GUI architecture: Separate modules, a hybrid (like MIKE?), or smart?
13. Getter
14. Vaccum gauges

Other things that Dave Osip mentioned (but aren't functional requirements) are callouts of electronics, computers, fibers, controllers, etc.

4. Next meeting date

July 12, 2006, 10 AM

AU todo: create requirements document; facility instrument prep