Phase II Roadmap for Cycle 25
help@stsci.edu
Table of Contents Previous Next Index


HST Cycle 25 Phase II Proposal Instructions > Chapter 7: Special Requirements[Visit and Exposure Special_Requirements] > 7.1 Introduction to Special Requirements: Syntax and Rules

7.1 Introduction to Special Requirements:
Syntax and Rules
Special requirements provide flexibility in specifying the scheduling requirements of observations. Many Special Requirements, directly or indirectly, restrict the times when observations can be scheduled. These should be used to provide the schedulers at STScI with enough constraints to ensure that the observations are properly scheduled. Special Requirements should not be used unless necessary to accomplish the scientific objectives of the program.
The Special Requirements are summarized in Table 7.1, Supported Formats for Visit Level Special Requirements and Table 7.2, Supported Formats for Exposure Level Special Requirements, and a detailed description of each requirement is provided in the following subsections.
Rules and Conventions
You should observe the following conventions and rules for Special Requirements:
A <date> specification in a Special Requirement must either be a geocentric date expressed in Universal Time (UT) or a heliocentric Julian Date. A UT date must be entered in the form DD-MMM-YYYY:hh:mm:ss, where MMM represents the first three letters of the month name. Fractional seconds are not allowed and anything beyond the day specification is optional. For example, 14-DEC-2001:17:05:41 refers to 14 December 2001, geocentric UT 17H05M41S. Only the necessary precision need be employed (e.g., 14-DEC-2001 might be adequate). The SOGS day of the year format, YYYY.ddd:hh:mm:ss (where ddd is the day of the year from 001 to 365), is also accepted.

Julian Dates must be entered in the form JDnnnnnnn.nnn (e.g., JD2444123.4) and are legal only for the ZERO-PHASE special requirement. All Julian Dates will be interpreted as heliocentric.
A visit-level Special Requirement (Visit_Requirements) applies to ALL the exposures within that visit.
An exposure-level Special Requirement (Special_Requirements) applies ONLY to that exposure and any other referenced exposures within the same visit.
Additional Rules and Conventions for the Text Proposal File
If you are editing the Text Proposal File to modify your program, please observe these additional syntax rules:
Multiple Special Requirements must be separated by a semi-colon (;). Please note that separate lines are not sufficient to delimit items in a list. Do not use commas to separate Special Requirements items.
Table 7.1: Supported Formats for Visit Level Special Requirements
 
 
Table 7.2: Supported Formats for Exposure Level Special Requirements  
PATTERN <#> [<exposure-list>] (Replaced by Pattern Containers in the APT User Interface))

HST Cycle 25 Phase II Proposal Instructions > Chapter 7: Special Requirements[Visit and Exposure Special_Requirements] > 7.1 Introduction to Special Requirements: Syntax and Rules

Table of Contents Previous Next Index