2.5 Text Proposal File

2.5.1 Basic Syntax Rules

Users (particularly RPS2 old-timers) should be aware that some changes to the original RPS2 format were necessary to accommodate enhancements that came with APT; also, some of the syntax has been made stricter in order to make parsing of the file more robust (e.g., for special requirements).

Here are a few basic rules that must be followed:

• Commas or semicolons must be used to delimit items in a list (see specific rules in the following bullets). New lines for each item will not be sufficient delimiters.
• Semicolons must be used to delimit Special Requirements items.
• Commas must be used to delimit items in all other lists including target descriptions, target position, fluxes, optional parameters, and spectral elements.
• Only the shortest forms of the special requirements will be accepted (e.g., POSition TARGet must be POS TARG). For more information on special requirements see Chapter 7.
• Exposure lists in Special Requirements must be specified as a single range. No commas are allowed in an exposure list (e.g., use 1-5 instead of 1,2,3-5). As before, visit lists can have comma delimters.
• The Time_Per_Exposure must be specified in seconds.
• Dates should be in the form 01-Jan-2005:00:00:00 (as an example) with the hours:minutes:seconds being optional. Other formats will not be supported except for JD, which is used for ZERO-PHASE.

2.5.2 Sample Text Proposal File Template

Your Text Proposal File should include the following and in the order given. Optional blocks are in square brackets ([]). The use of colons is required in the form given. Note that at least one of the three target types (Fixed, Solar System, or Generic) must be present. You can make your own template in APT from your Phase I proposal by opening it in APT and changing it to Phase II. Then enter your Phase II ID number, add a visit, and then export to a text proposal file (If you have already retrieved your proposal from STScI using the Phase II ID given to you by your PC, then the Phase II ID number will have already been filled in).

Proposal_Information

Title:

Proposal_ID:

Proposal_Category:

Cycle:

[Avail_Ok:]

[StScI_Edit_Number:]
 

[Parallel_Information

Parallel_Pointing_Tolerance]
 

Investigators

PI_Honorific:

PI_First_Name:

PI_Middle_Initial:

PI_Last_Name:

PI_Institution:
 
[CoI_Name:
 
CoI_Honorific:
 
CoI_Middle_Initial:

CoI_First_Name:

CoI_Last_Name:

CoI_Institution:

[Contact:]]
 

Abstract

Questions

Observing_Description:

[Real_Time_Justification:]

[Calibration_Justification:]

[Additional_Comments:]
 

[Fixed_Targets

Target_Number:

Target_Name:

[Alternate_Names:]

Description:

Position:

Equinox:J2000

Coordinate_Source:

[RV_or_Z:]

[RA_PM:]

[Dec_PM:]

[Epoch:]

[Annual_Parallax:]

Flux:

[Other_Fluxes:]

[Comments:]]
 

[Solar_System_Targets

Target_Number:

Target_Name:

Description:

Level_1:

[Level_2:]

[Level_3:]

[Window:]

[Ephem_Uncert:]

[Acq_Uncert:]

Flux:
 
[Other_Fluxes:]

[Comments:]]
 

[Generic_Targets

Target_Number:

Target_Name:

Description:

Criteria:

Flux:

[Other_Fluxes:]

[Comments:]]
 

[Pattern_Data

Pattern_Number:

Primary_Pattern:

Pattern_Type:

Pattern_Purpose:

Number_Of_Points:

Point_Spacing:

Line_Spacing:

Coordinate_Frame:

Pattern_Orient:

Angle_Between_Sides:

Center_Pattern:

[Secondary_Pattern:

Pattern_Type:

Pattern_Purpose:

Number_Of_Points:

Point_Spacing:

Line_Spacing:

Coordinate_Frame:

Pattern_Orient:
 
Angle_Between_Sides:

Center_Pattern:]
 
[Pattern_Comments:]]
 

Visits

Visit_Number:

[Visit_Priority:]

[Visit_Requirements:]

[On_Hold_Comments:]

[Visit_Comments:]
 

 
Exposure_Number:

[Exposure_Label:]

Target_Name:

Config:

Opmode:

Aperture:

Sp_Element:

[Wavelength:]

[Optional_Parameters:]

Number_of_Iterations:

Time_Per_Exposure:

[Special_Requirements:]
 
[Sub_Exposures:]

[Comments:]