RPS Processor Internal File Descriptions
'project'.paf (paf: Project Address File)This file contains the e-mail address of the account(s) that receive the electronically submitted proposals. This file is required for all projects. If more than one e-mail address is specified, they should all appear on the same line, separated by spaces.
'project'.phf (phf: Project Help File)This file contains mission specific help for each field on the proposal form. It is recommended that this file contain information as to which fields are required and maximum lengths for string fields. This file is required for all projects.
'project'.plf (plf: Project LaTeX File)This is project LaTeX template. This file specifies the layout of the forms. This file is required for all projects. The RPS processor substitutes the user-supplied values for the appropriate variables in the LaTeX template. All variables are prefixed with !. These variable names must match the variable names specified in the .pdf's.
'project'_*.pdf (pdf: Project Description File)Each mission must have at least the cover.pdf file. All .pdf files follow the same format and include information on the fields that appear on the proposal forms. Each line in the .pdf describes a separate field. For each field, the following must be defined:
'project'.pcf (pcf: Project Constraints File)This is the project constraints file. It is not required. Any constraints on values are specified in this file. Constraints may fall into one of four categories: value, range, logical AND, and logical OR.
RPS Development Team: RPS Help Desk
HEASARC Home | Observatories | Archive | Calibration | Software | Tools | Students/Teachers/Public