MROIFastTipTilt.DerivedRequirementsDocumentOutline History
Hide minor edits - Show changes to markup
May 21, 2010, at 04:55 PM
by jsy1001 -
Added line 8:
- Identify missing requirements
May 21, 2010, at 09:57 AM
by MF -
Changed lines 12-13 from:
to:
May 21, 2010, at 09:52 AM
by MF -
Changed lines 12-13 from:
to:
May 20, 2010, at 02:25 PM
by jsy1001 -
Changed lines 1-2 from:
This outline is under construction, by JSY and MF.
to:
This outline is under construction, by JSY and MF. Note that HTML (and hence PmWiki) doesn't support "proper" outline numbering, i.e. 1 1.1 1.2 1.1.1
Changed lines 10-11 from:
to:
Changed lines 19-20 from:
to:
Changed lines 25-27 from:
- Design assumptions
May refer to high-level features of assumed design described in "Conceptual Design Assumptions" above
to:
- Design assumptions
May refer to high-level features of assumed design described above in "Conceptual Design Assumptions"
Changed lines 71-75 from:
- Top-down image quality budget, by component
- Thermal Control
to:
- Top-down stability budget, by component
- Thermal Management
Changed lines 77-79 from:
to:
- Heat dissipation
- Power consumption
Changed lines 81-82 from:
to:
Changed lines 84-85 from:
to:
- Cooling needs
- Power budget
Added lines 110-123:
- Max EMCCD gain to be used
- Dynamic Range
- Top-level requirements: none?
- Design assumptions
- Brightest stars we want to use
- Strategy for setting frame rate and EMCCD gain as function of seeing and target magnitude
- Derived requirements
- Need for ND filters?
- Min EMCCD gain to be used
May 20, 2010, at 02:10 PM
by jsy1001 -
Added lines 1-100:
This outline is under construction, by JSY and MF.
TODO:
- Do any derived requirements depend on others? If so, how to express this in the document?
- Copy finished outline into a proper document
Derived Requirements Document
- Introduction
- Conceptual Design Assumptions
- Pixel Scale
Note that there is a top-level requirement on the pixel scale for the FLC.
- Top-level requirements
- FTT/NAS: FOV
- Design assumptions
May refer to high-level features of assumed design described in "Conceptual Design Assumptions" above
- Derived requirements
- Maximum and minimum pixel scales for FTT/NAS
- FTT mode subframe size
- Top-level requirements
- FTT-mode FOV
- Dispersion-offset guiding: rate of change of dispersion offset
- Off-axis TT sensing: Max. off-axis distance for TT reference object
- Design assumptions
- Thermal drift rate of TT zero point
- Derived requirements
- Min. subframe size /arcsec (so its independent of pixel scale)
- Image Quality
- Top-level requirements
- FTT/NAS: none
- FLC: XXX
- Design assumptions
- Two or more conceptual layouts
- Derived requirements
- Top-down image quality budget, by component
- Stability of Tip-tilt Zero Point
- Top-level requirements
- FTT/NAS: Stability req
- FLC: Looser stability req
- Design assumptions
- Two or more conceptual layouts
- Derived requirements
- Top-down image quality budget, by component
- Thermal Control
- Top-level requirements
- Design assumptions
- Derived requirements
- Closed-loop Bandwidth
- Top-level requirements
- 3dB bandwidth of 40Hz
- Design assumptions
- Servo type
- Derived requirements
- Latency budget: frame rate, camera latency, compute latency
- Limiting Sensitivity
- Top-level requirements
- Limiting magnitude and allowed TT residual at limiting magnitude
- Design assumptions
- Derived requirements
- Throughput budget
- CCD noise performance
|