Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.stsci.edu/hst/hst/proposing/documents/cp/8_APT_Proposal_Form17.html
Дата изменения: Unknown Дата индексирования: Tue Apr 12 03:26:31 2016 Кодировка: Поисковые слова: shadow |
HST Call for Proposals and HST Primer for Cycle 24 |
help@stsci.edu |
8.16 Observation Summary (OS)The OS lists the main characteristics of the observations that you propose to obtain. In general you must include in the OS all the configurations, modes, and spectral elements that you propose to use, and (except for SNAPs) all the targets that you propose to observe. Configurations or targets that are not specified in the Phase I proposal, but are included in Phase II, may delay the program implementation, and may be disallowed. Note the following:
•
• For Long-Term Proposals, the OS should include information for all the proposed observations, not just those requested in Cycle 24.
• Parallel observations must be included in the OS, and marked as such using the relevant special requirement flags (see Section 8.16.11 and Table 8.1).
• Target acquisition observations (see Section 5.2 of the HST Primer) need not be included in the OS, unless they are themselves used for scientific analysis.
• Normal calibration observations that are often or routinely taken (e.g, fringe flats) need not be included in the OS. However, the OS should include any special calibration exposures of internal sources or external targets (see Section 4.3). Special internal calibrations should be listed separately from external calibration exposures. When these special calibrations require additional orbits, that should be specified and the orbits included in the total allocation. The need for these calibrations should be justified in the ‘Description of the Observations’ (see Section 9.2).
8.16.1 Target8.16.2 InstrumentSelect an instrument from the pull-down menu. The menu will contain all the available instruments. Only one instrument can be selected in each observation block.8.16.3 Instrument Setup(s)8.16.4 Config8.16.5 Science Mode8.16.6 CoronagraphyIf you are proposing coronagraphic observations with STIS, then set this keyword to ‘yes’. Coronagraphic observations with the ACS/SBC are not permitted (see Section 3.3.2 of the ACS Instrument Handbook).8.16.7 PolarizerIf you are proposing polarimetric observations with ACS, then set this keyword to ‘yes’. There is no polarimetry keyword in the proposal PDF file, but this sets the appropriate flag in the Phase I submission.8.16.8 Spectral Element8.16.9 OrbitsEnter the number of orbits requested (i.e., the sum of the orbits required for all the instrument setups in the observation block). Consult Chapter 6 of the HST Primer for instructions on how to calculate the appropriate number of orbits for your observations.8.16.10 Number of Iterations8.16.11 Special Requirement Checkboxes
8.16.12 Scheduling RequirementsFor all proposals, we request that you provide additional scheduling information for your observations; this request does not apply to observations of solar system or generic targets. The additional information will help STScI understand and assess the scheduling implications of your program. Be sure to read Section 9.2, ‘Description of the Observations’, as that is the primary place for describing your observing strategy. Note that these requirements do not appear in the PDF file, although they are used when running the Visit Planner (see Section 8.16.13).Set this requirement when all exposures defined in the Observation Block are affected adversely by geocoronal Lyman-alpha background emission, and therefore need to be obtained when HST is in Earth shadow. This requirement complicates scheduling and reduces HST observing efficiency, and must therefore have adequate scientific justification in the Phase I proposal. SHADOW is generally incompatible with CVZ. This requirement should not be used if low continuum background is required: in that case use LOW SKY instead.Set this requirement when all exposures defined in the Observation Block are affected adversely by scattered light (e.g zodiacal light and earthshine), and therefore need to be obtained with minimal sky background. The continuum background for HST observations is a function of when and how a given target is observed. Observations can be scheduled when the sky background is within 30% of its yearly minimum for the given target, which is done by restricting the observations to times that minimize both zodiacal light and earthshine scattered by the Optical Telescope Assembly (OTA). To minimize the zodiacal light, the scheduling algorithm places seasonal restrictions on the observations; to reduce the earthshine, the amount of time data is taken within an orbit is reduced by approximately 15%. The former complicates scheduling, while the latter reduces the observing efficiency of HST. Therefore, using the LOW SKY restriction must have adequate scientific justification included in the Phase I proposal. With this restriction, the zodiacal background light for low-ecliptic latitude targets can be reduced by as much as a factor of 4. Avoiding the earthshine at the standard earth-limb avoidance angle (see Section 2.3 of the HST Primer) can make a similar difference. LOW SKY is generally incompatible with CVZ.Setting this requirement means that all exposures defined in the Observation Block MUST be observed at the exact same ORIENT. This requirement is only meaningful if the observations are to occur in multiple visits (e.g. Number of Iterations is greater than 1, or if the Total Orbits is greater than 5).Enter the ORIENT range that all the exposures defined in the Observation Block must be observed within. If multiple ORIENT ranges are acceptable, then enter all values.Enter the range of dates that all exposures defined in the Observation Block must be observed within. If multiple BETWEENs are acceptable, then enter all values.For Large and Treasury Programs, we will contact the proposer within 1-2 weeks of the submission deadline if we need to verify our understanding of the appropriate scheduling constraints. As noted previously (Section 8.12), if a Co-I is to serve as the contact for this verification process, the Contact Co-I keyword box should be set.8.16.13 Verifying Schedule Constraints