Äîêóìåíò âçÿò èç êýøà ïîèñêîâîé ìàøèíû. Àäðåñ îðèãèíàëüíîãî äîêóìåíòà : http://www.stsci.edu/ftp/documents/p2pi/p2pi_ENG_v10.pdf Äàòà èçìåíåíèÿ: Thu Mar 8 18:56:33 2001 Äàòà èíäåêñèðîâàíèÿ: Sat Dec 22 12:00:41 2007 Êîäèðîâêà: Ïîèñêîâûå ñëîâà: earth's atmosphere

Version 10.0.2 3/7/01

HST Phase 2 Proposal Instructions for Cycle 10

Hubble Division 3700 San Martin Drive Baltimore, Maryland 21218 help@stsci.edu

Operated by the Association of Universities for Research in Astronomy, Inc., for the National Aeronautics and Space Administration


Revision History
Version Date January 31, 2001 December 29. 2000 Editor David Soderblom David Soderblom

10.0.2 10.0.1

· Version 10.0.2 corrects version 10.0.1 with minor formatting changes. · Version 10.0.1, issued in coordination with RPS2 release 10.0. This version is intended to be fully compliant with Cycle 10 changes to RPS2. · Version 10.0.1 is issued as a General Observer version. The most recent GO version is 10.0.2. · Shelf life: This version should not be used after March 30, 2001 without checking for a more recent version.

This is not the General Observer version. If you would like some hints on how to read and use this PDF document, click on: Some PDF Pointers

This is the Engineering-Only version
If you can view this paragraph, you are reading the engineering-only version. See Special Note to Engineering Version Users in Chapter 1: About This Document on page 1-3 for an explanation of how to view this version properly. If you do not see this paragraph in color (green), you are not viewing this document properly.


How to get help:
1. Visit STScI's web site: http://www.stsci.edu/

where you will find resources for observing with HST and working with HST data.
2. Contact your Program Coordinator (PC) or Contact Scientist (CS).

These individuals were identified in the notification letter from STScI.
3. Send e-mail to help@stsci.edu, or call 1-800-544-8125.

From outside the United States, call 1-410-338-1082.

Send comments or corrections to: Hubble Division Space Telescope Science Institute 3700 San Martin Drive Baltimore, Maryland 21218 E-mail: help@stsci.edu



Table of Contents
Part A: Phase 2 Proposal Writing
............................... 1 .................... 3

Chapter 1: About This Document

Special Note to Engineering Version Users.................... 3 Document Design and Structure ....................................... 5 Changes Since the Previous Version ............................... 5
Document Presentation ........................................................ Technical Content ................................................................. Where to Find Additional Information ............................... Some PDF Pointers .............................................................. 5 6 7 7

Chapter 2: The Basics of Phase 2 Proposals .........................................................................

9

How to Submit Phase 2 Information ................................. 9 What to Submit .................................................................... 11 General Instructions............................................................ 11
Proposal Information [Proposal_Information]..................... Parallel Information [Parallel_Pointing_Tolerance]............. Investigators [Investigators]................................................ Abstract [Abstract].............................................................. Proposal Text Sections [Questions] ................................... Target Information [Fixed_Targets, Solar_System_Targets, Generic_Targets].................... Visit Information [Visits]...................................................... Data Distribution Information ............................................. Examples and General Advice ......................................... Acquisitions and Pointings .................................................. Examples ............................................................................ Common Problems ............................................................. 12 14 14 14 15 15 16 16 17 17 18 18

v


vi

Table of Contents

Consideration of Limited Resources ................................... Proposal Template .............................................................. Proposal_Information.......................................................... [Parallel_Information ........................................................... Abstract:.............................................................................. Questions:........................................................................... [Fixed_Targets .................................................................... [Solar_System_Targets ...................................................... [Generic_Targets ................................................................ Visits ...................................................................................

19 20 20 20 21 21 21 21 22 22

Chapter 3: Fixed and Generic Targets [Generic _Targets] .................................................

23 Tables and Figures ............................................................. 24 Target Number [Target_Number] .................................... 25

Target Name [Target_Name and Alternate_Names] .......................................................... 25
Catalog Name ..................................................................... Uncataloged Targets .......................................................... Common Names ................................................................. Special Targets ................................................................... Target Description [Description] ...................................... Target Position [Position] .................................................. Required Accuracies of Target Positions ........................... Equatorial Coordinates ....................................................... Positional Offsets ................................................................ Region of Sky (Extended Targets) ..................................... Determining Coordinates in the Guide Star Selection System (GSSS) Reference System .............................. A Caution on Astrometry Prepared from STScI Plate Scans ................................................................... Prohibition on the Use of GSC Version 1.2 ........................ Special Catalogs ................................................................. Equinox for Coordinates [Equinox] ................................. 26 28 28 29 29 34 34 36 39 41 42 43 43 44 45

Source of Specified Coordinates [Coordinate_Source] ..................................................... 45 Radial Velocity or Redshift [RV_or_Z]............................ 47 Is Proper Motion or Parallax Relevant? ......................... 48
Proper Motion and Parallax Data ....................................... 48


vii

Flux Data [Flux] .................................................................... 49
General Guidelines on What Flux Data to Include ............. 50 Bright-Object Constraints .................................................. 53 Comments [Comments] ..................................................... 54

Generic Targets List [Generic_Targets]......................... 55
Target Number(s) [Target_Number]................................... Target Name [Target_Name].............................................. Target Description [Description]......................................... Flux Data [Flux]................................................................... Comments [Comments]...................................................... Generic Target Specifications............................................. Getting Coordinates Coordinated .................................... 55 55 55 56 56 56 58

Chapter 4: Solar System Targets List [Solar_System_Targets] ...................................
Target Target Target Target

59 Tables and Figures ............................................................. 60

64 65 Target Position Level 1 [Level_1]....................................... 66 Target Position Level 2 [Level_2]....................................... 68 Target Position Level 3 [Level_3]....................................... 75

Number [Target_Number] .............................. Name [Target_Name]..................................... Description [Description] ...................................... Position .....................................................................

61 62

Ephemeris Uncertainty [Ephem_Uncert] ................... 75 Acquisition Uncertainty [Acq_Uncert] ........................ 75 Observing Windows [Window] ......................................... 76
Default Target Windows ..................................................... 81

Flux Data [Flux] ......................................................... Comments [Comments] ............................................. Illustrations of Orbital Longitude ...................................... Examples of Target List Blocks .......................................

82 84
84 85 89 90 91 91

Chapter 5: Visits and Exposures

.................... Tables and Figures ............................................................. Visit Number [Visit_Number] ............................................ Visit Priority [Visit_Priority] ................................................

Visit-level Special Requirements


viii

Table of Contents

[Visit_Requirements] ..................................................... On Hold Comments [On_Hold_Comments].................. Visit Comments [Visit_Comments] .................................. Exposure Number [Exposure_Number] ......................... Target Name [Target_Name] ...........................................
Astronomical Targets .......................................................... Special Targets ................................................................... Instrument Configuration [Config] ................................... Operating Mode [Opmode] ............................................... Aperture or Field of View [Aperture] ............................... Spectral Element [Sp_Element]......................................

92 92 93 93 93 94 94 95 96 96 97

Central Wavelength or Range if Grating or Prism Used [Wavelength] ............................................ 97 Optional Parameters [Optional_Parameters] ............... 98 Number of Times to Iterate the Exposure [Number_of_Iterations] ................................................. 98 Time per Exposure [Time_Per_Exposure] .................... 98 Exposure-level Special Requirements [Special_Requirements] ............................................. 100 Exposure-level Comments [Comments] ...................... 100

Chapter 6: Parallel Science Exposures....................................................................

101

Parallel Science Limitations ............................................ 102 Pure Parallels ..................................................................... 103 Coordinated Parallels ....................................................... 105
Instrument Configuration .................................................. Targets.............................................................................. Special Requirements....................................................... Optional Parameters ......................................................... Ordering Restrictions and Interpretations ......................... Efficiency Considerations ................................................. 105 106 107 109 110 110


ix

Chapter 7: Special Requirements [Visit_Requirements and Special_Requirements] ...................................

111 Tables and Figures .......................................................... 112

Introduction to Special Requirements: Syntax and Rules ......................................................... 112 Visit-level Special Requirements ................................... 117
Guiding ............................................................................. Target Orientation ............................................................. Special Observation Requirements .................................. Timing Requirements........................................................ Conditional Requirements ................................................ Exposure-level Special Requirements ......................... Target Acquisition ............................................................. Target Position.................................................................. Special Observation Requirements .................................. Special Communications Requirements ........................... Timing Requirements........................................................ 117 119 129 131 134 134 134 137 139 141 143

Implementation Special Requirements (Engineering)................................................................. 147
Visit Special Requirements (Engineering) ........................ 147 Exposure Special Requirements (Engineering) ................ 148

Chapter 8: Pointings and Patterns

.............. 153

Pointing the Telescope .................................................... 153 Introduction to Patterns .................................................... 154 How to Fill Out the Pattern Parameters Form ............ 155
Pattern Parameters........................................................... Convenience Patterns ...................................................... WFPC2 Patterns ............................................................... STIS Patterns ................................................................... ACS Patterns (for Cycle 11) ............................................. NICMOS Patterns (for Cycle 11) ...................................... 156 159 160 162 165 167


x

Table of Contents

Part B: Supported Science Instruments

........... 177

Chapter 9: Wide Field Planetary Camera 2 (WFPC2) ...............................................

179 Tables and Figures ........................................................... 180 Introduction to WFPC2 ..................................................... 180

Mode = IMAGE Configuration = WFPC2 ............................................. 182
Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 183 184 184 185 187 187

Mode = DECON Configuration = WFPC2 (Restricted) ...................... 188
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Elements............................................................. Time Per Exposure ........................................................... 188 188 188 189

Mode = POM Configuration = WFPC2 (Restricted) ...................... 189
Optional Parameters ......................................................... 190

Mode = AFM Configuration = WFPC2 (Restricted) ...................... 190
Optional Parameters ......................................................... 191 Tabular Reference Data .................................................. 191

WFPC2 Internal Calibration Targets (Available but Unsupported) ...................................... 195 WFPC2 Aperture Coordinate System .......................... 197

Chapter 10: Space Telescope Imaging Spectrograph (STIS)

..................... 199 Tables and Figures ........................................................... 200 Introduction to STIS .......................................................... 200


xi

Mode = ACQ Configuration = STIS/CCD ................................................................. 203
Aperture or FOV ............................................................... Spectral Element .............................................................. Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 203 204 204 205 205 205

Mode = ACQ/PEAK Config = STIS/CCD ..................................................... 206
Aperture or FOV ............................................................... Spectral Element .............................................................. Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 206 206 207 209 209 209

Mode = ACCUM Config = STIS/CCD ..................................................... 210
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations and Time Per Exposure .................. 210 210 210 211 214

Mode = ACCUM Config = STIS/FUV­MAMA, Config = STIS/NUV­MAMA ...................................... 215
Aperture or FOV ............................................................... Supported Spectral Elements ........................................... Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations and Time Per Exposure .................. 215 215 216 216 218

Mode = TIME­TAG Configuration = STIS/FUV­MAMA, Configuration = STIS/NUV­MAMA .......................... 218
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations and Time Per Exposure .................. Special Requirements....................................................... 218 218 219 219 220 220


xii

Table of Contents

Mode = ALIGN (Restricted) Configuration = STIS (Restricted) ............................ 221
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 221 221 221 221 222 222 222

Mode = ANNEAL (Restricted) Configuration = STIS (Restricted) ............................ 223
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 223 223 223 223 223 223 223

Mode = MSMOFF (Restricted) Configuration = STIS (Restricted) ............................ 224
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... STIS Central Wavelengths .............................................. Target_Name = WAVE ..................................................... Aperture ............................................................................ Spectral Element .............................................................. Optional Parameter........................................................... Target_Name = CCDFLAT ............................................... Aperture ............................................................................ Spectral Element .............................................................. Target_Name = BIAS (Restricted) .................................... Aperture ............................................................................ Spectral Element .............................................................. 224 224 224 224 224 225 225 226 227 228 228 228 229 231 231 231 231 231

STIS Internal Calibration Targets .................................. 227


xiii

Target_Name = DARK (Restricted) .................................. Aperture ............................................................................ Spectral Element .............................................................. STIS Coordinate System ................................................. The Official STIS Aperture List for Cycle 10 ...............

231 232 232 232 234

Chapter 11: Fine Guidance Sensors (FGS) ................................................................................

243 Tables and Figures ........................................................... 244 Introduction to the FGS .................................................... 244

Mode = POS Configuration = FGS ................................................... 245
Aperture or FOV ............................................................... Spectral Element .............................................................. Optional Parameters ......................................................... Special Requirements....................................................... Time Per Exposure ........................................................... 246 246 246 248 248

Mode = TRANS Configuration = FGS ................................................... 248
Aperture or FOV ............................................................... Spectral Element .............................................................. Optional Parameters ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... Tables and Illustrations .................................................... 249 249 249 250 250 251

Chapter 12: Advanced Camera for Surveys (ACS) .................................................

253 Tables and Figures ........................................................... 254 Introduction to the ACS .................................................... 254

Mode = ACCUM Configuration = ACS/WFC......................................... 256
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 256 257 257 257 260 260


xiv

Table of Contents

Mode = ACCUM Configuration = ACS/HRC ......................................... 261
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 261 261 261 262 265 265

Mode = ACQ Configuration = ACS/HRC ......................................... 265
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 265 266 266 266 266 266

Mode = ACCUM Configuration = ACS/SBC.......................................... 267
Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... 267 267 267 267 268 268

Mode = ALIGN Configuration = ACS/WFC or ACS/HRC (Restricted) ................................................ 268
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 268 268 268 269 269 269 269 269

Mode = ANNEAL Configuration = ACS (Restricted) ............................ 270
Target Name ..................................................................... 270 Aperture or FOV ............................................................... 270


xv

Spectral Element .............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... Tabular reference Data .................................................... Spectral Elements for WFC and HRC .............................. Ramp Filter Wavelength Ranges ...................................... Spectral Elements for ACS/SBC.......................................

270 270 270 270 270 271 271 273 273

Chapter 13: Near Infrared Camera and Multi-Object Spectrometer (To be supported in Cycle 11) (NICMOS) ......................................................................

275 Tables and Figures ........................................................... 276 Introduction to NICMOS................................................... 276

Mode = ACCUM Configuration = NIC1 or NIC2 or NIC3 ................... 278
Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 278 278 279 279 281 282

Mode = MULTIACCUM Configuration = NIC1 or NIC2 or NIC3 ................... 282
Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 282 282 282 283 285 285

Mode = ACQ Configuration = NIC2 .................................................. 289
Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... 289 289 289 289


xvi

Table of Contents

Number of Iterations ......................................................... 289 Time Per Exposure ........................................................... 289 Special Requirements....................................................... 290

Mode = BRIGHTOBJ Configuration = NIC1 or NIC2 or NIC3 (Available but Unsupported) ...................................... 290
Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... 290 291 291 291 291 291

Mode = ALIGN Configuration = NIC1 or NIC2 or NIC3 (Restricted) .................................................................... 292
Target Name ..................................................................... Aperture or FOV ............................................................... Spectral Elements............................................................. Wavelength ....................................................................... Optional Parameters ......................................................... Number of Iterations ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... Tabular Data ....................................................................... TPG_TIME Values ............................................................ NICMOS Apertures ........................................................... NICMOS Spectral Elements ............................................. NICMOS Internal Calibration Targets (Available but Unsupported)......................................................... Illustrations .......................................................................... 292 292 292 292 293 293 294 294 294 294 295 296 298 299

Chapter 14: Cosmic Origins Spectrograph (COS) ...........................................

303 Tables and Figures ........................................................... 304 Introduction to the COS ................................................... 304

Mode = TIME-TAG Configuration = COS/NUV ......................................... 304
Aperture or FOV ............................................................... 304 Spectral Element .............................................................. 304


xvii

Wavelength ....................................................................... Additional Parameter ........................................................ Number of Iterations ......................................................... Time Per Exposure ........................................................... Special Requirements....................................................... Tabular reference Data ....................................................

305 305 306 306 306 306

Part C: Engineering Modes (Limited Access) ......................................................... Chapter 15: Corrective Optics Space Telescope Axial Replacement (Restricted) (COSTAR) .....................................

309

311

Mode = DOB, Configuration = COSTAR (Restricted).................... 313
Optional Parameters ......................................................... 313

Mode = FOC, Configuration = COSTAR (Restricted).................... 313
Optional Parameters ......................................................... 314

Mode = SENSOR, Configuration = COSTAR (Restricted).................... 314
Optional Parameters ......................................................... 314

Mode = FOS, Configuration = COSTAR (Restricted) ................ 315 Optional Parameters ................................................... 315 Mode = GHRS, Configuration = COSTAR (Restricted).................... 316
Optional Parameters ......................................................... 316

Chapter 16: S/C Mode (Restricted)

............. 317

Mode = DATA Configuration = S/C (Restricted) .............................. 318
Aperture or FOV ............................................................... 318 Special Requirements....................................................... 318

Mode = POINTING Configuration = S/C (Restricted) .............................. 319
Aperture or FOV ............................................................... 319


xviii

Table of Contents


List of Figures
Orbital Longitude for Satellites ...................................................... 84 Orbital Longitude for Planets ......................................................... 85 ORIENTation computation for WFPC2 ........................................ 121 ORIENTation computation for STIS. ........................................... 123 ORIENTation computation for FGS1R, in TRANS mode. ........... 124 WFPC2 Aperture Coordinate System.......................................... 197 STIS coordinate system (shown projected onto the sky, as used with the POS TARG Special Requirement). ............. 233 The FGS POS TARG and interferometer coordinate systems. ... 252 NICMOS Coordinate System....................................................... 299 Definition of Orientation for NICMOS. ......................................... 300 Guide-Star Availability with NICMOS Patterns. ........................... 301

xix


xx


List of Tables
Table 2.1: Limited-Resource Special Requirements ..................... 20 Table 3.1: Designations of Special Targets ................................... 29 Table 3.2: Target Categories ......................................................... 30 Table 3.3: Descriptive Keywords for STAR and EXT-STAR ......... 31 Table 3.4: Descriptive Keywords for STELLAR CLUSTER and EXT-CLUSTER ........................................................................ 32 Table 3.5: Descriptive Keywords for GALAXY .............................. 32 Table 3.6: Descriptive Keywords for CLUSTER OF GALAXIES ............................................................................... 32 Table 3.7: Descriptive Keywords for ISM and EXT-MEDIUM........ 33 Table 3.8: Descriptive Keywords for UNIDENTIFIED.................... 33 Table 3.9: Descriptive Keywords for CALIBRATION ..................... 33 Table 3.10: Discrete Features and Descriptors for All Categories ................................................................................ 34 Table 3.11: Required Coordinate Accuracies ................................ 36 Table 3.12: Required Coordinate Accuracies for NICMOS (Restricted)............................................................................... 36 Table 3.13: Formats for Specification of Target Flux Data ............ 52 Table 3.14: Bright-Object Constraints ........................................... 54 Table 3.15: Bright-Object Constraints for NICMOS (Restricted)............................................................................... 54 Table 4.1: Solar System Standard Targets ................................... 63 Table 4.2: Target Description Keywords ...................................... 64 Table 4.3: Positional Parameters for TYPE = COMET.................. 67 Table 4.4: Positional Parameters for TYPE = ASTEROID ........... 67 Table 4.5: Parameters for TYPE = PGRAPHIC ........................... 69 Table 4.6: Parameters for TYPE = POS_ANGLE ........................ 70 Table 4.7: Parameters for TYPE = MAGNETO ............................ 71

xxi


xxii

List of Tables

Table 4.8: Parameters for TYPE = TORUS .................................. 71 Table 4.9: Parameters for TYPE = SAT ....................................... 73 Table 4.10: Parameters for TYPE = PCENTRIC (Available but Unsupported) .................................................... 74 Table 4.11: Keywords for Observing Windows ............................ 77 Table 4.12: Operators for Observing Windows ............................ 77 Table 4.13: Formats for Specification of Target Flux Data ............ 83 Table 5.1: Internal Calibration Target Names ............................... 94 Table 5.2: Special External Target Names .................................... 95 Table 5.3: Instrument Configurations and Operating Modes ......... 95 Table 5.4: Aperture and Field of View Names ............................... 96 Table 7.1: Supported Formats for Visit Level Special Requirements ......................................................................... 114 Table 7.2: Supported Formats for Exposure Level Special Requirements ........................................................................ 115 Table 7.3: Accuracies of Guiding Modes ..................................... 117 Table 7.4: Instrument Orientations with respect to U3-Direction ........................................................................... 126 Table 7.5: Approximate Separation and Orientations between Instrument Detectors ............................................... 127 Table 9.1: Supported Instrument Parameters for WFPC2 .......... 181 Table 9.2: WFPC2 Apertures ...................................................... 184 Table 9.3: Valid WFPC2 Exposure Times (seconds) .................. 191 Table 9.4: WFPC2 Supported Spectral Elements (Filters) .......... 192 Table 9.5: Linked Spectral Element/Aperture Combinations for Wood's and Quadrant Filters ................................................. 194 Table 9.6: Internal Calibration Targets for the WFPC2 (Available but Unsupported) .................................................. 196 Table 10.1: Supported Optional Parameters for STIS Instrument Modes .................................................................. 201 Table 10.2: Supported Central Wavelengths for STIS Gratings ................................................................................. 226 Table 10.3: Time_Factor for Spectral Elements and Wavelenghts. ......................................................................... 230 Table 10.4: Supported STIS Apertures ....................................... 235 Table 11.1: Supported Instrument Parameters for the FGS ........ 245 Table 11.2: Spectral Elements for the FGS ................................. 251


xxiii

Table 11.3: Internal Calibration Targets for the FGS (Restricted)............................................................................. 251 Table 12.1: Supported Instrument Parameters for the ACS ........ 255 Table 12.2: Internal calibration Targets for the ACS ................... 256 Table 12.3: Spectral Elements for use with ACS/WFC and ACS/HRC Configurations ....................................................... 272 Table 12.4: Wavelength Ranges for the WFC/HRC Ramp Filters ........................................................................... 273 Table 12.5: Spectral Elements for use with the ACS/SBC Configuration .......................................................................... 273 Table 13.1: Supported Instrument Parameters for NICMOS ....... 277 Table 13.2: Predefined Sample Sequences for MULTIACCUM Mode (seconds) ............................................ 287 Table 13.3: Quantized Legal NICMOS TPG Expose Times ........ 294 Table 13.4: NICMOS Apertures .................................................. 296 Table 13.5: Spectral Elements for the NICMOS .......................... 297 Table 13.6: Internal Calibration Targets for the NICMOS ........... 298 Table 14.1: Supported Instrument Parameters for the COS ...... 304 Table 14.2: COS Spectral Elements and Central Wavelengths ......................................................................... 307 Table 15.1: Instrument Parameters for the COSTAR .................. 312


xxiv

List of Tables


PART A:

Phase 2 Proposal Writing
The chapters in this part explain how to use the Phase 2 Instructions, how to fill out the RPS2 template, and how to submit the information to STScI. It will also explain where to go for help, and describe the information that must be submitted to STScI by GOs and GTOs during Phase 2.

1


2


CHAPTER 1:

About This Document
In this chapter. . .
Document Design and Structure Changes Since the Previous Version Document Presentation Technical Content Where to Find Additional Information Some PDF Pointers / / / / / / 5 5 5 6 7 7

Special Note to Engineering Version Users
The Phase 2 Proposal Instructions are issued in two forms, a GO version, and this one, an Engineering version. GO text is in black. Engineering-only text is in color and has change bars. Any text seen in color is not provided to the GOs. Text in green signifies comments for the engineering-only version. Engineering-only options are of two types. · Available-but-Unsupported items may be used by GOs and GTOs if there is strong scientific justification. In such cases calibrations will not be provided by STScI. There is limited user support from STScI for the reduction and analysis of data taken with Available-but-Unsupported modes, and that support may be provided at a low priority. Available-but-Unsupported-mode observations will be taken on a shared-risk basis, which means that observations that fail due to the use of the Available-but-Unsupported capability will not be repeated. Available-but-Unsupported modes can only be invoked if the Avail_Ok flag is set in the Phase 2 program. · Available but Unsupported modes are shown in magenta.

3


4

Chapter 1: About This Document

· Restricted items generally have no valid scientific use at all and are only used for instrumental calibration and maintenance. These should never be used without the approval of an Instrument Scientist for the SI in question. The word Restricted accompanies the descriptions of Restricted items. Restricted modes are shown in red. Use with caution!

Note: Text in blue shows cross-references to other parts of this document.

.Note to users of the Engineering version: Cross-references in non-black text are active (you can click on them and jump to that location), but they are not in blue for reasons beyond my control.

Proposals to observe with Hubble Space Telescope (HST) are reviewed in two phases managed by the Space Telescope Science Institute (STScI). In Phase 1, proposers submitted an Observation Summary for review by the Telescope Allocation Committee (TAC). The Observation Summary provides only general descriptions of the targets and of the proposed observations. The TAC review results in a list of accepted proposals. During Phase 2, General Observers (GOs) with accepted proposals, as well as Guaranteed Time Observers (GTOs), must provide complete details of their proposed observations so that STScI can conduct a full technical feasibility review. The Phase 2 information will then be used to schedule the actual observations and obtain data. This document, the Phase 2 Proposal Instructions, has the following purposes: · To describe the information that must be submitted to STScI by GOs and GTOs during Phase 2. · To describe how to fill out the RPS2 (Remote Proposal Submission 2) template. · To show how to submit the information to STScI.


Document Design and Structure

5

It is assumed that readers of this document are familiar with the Cycle 10 Call for Proposals, issued in June, 2000, and with the Instrument Handbooks.

Document Design and Structure
These Instructions are meant to be read on-line, not on paper, although many readers may wish to print selected portions. Many cross-references have been added to make navigation easy and convenient. A comprehensive Table of Contents allows you to go directly to chapters, sections, subsections, tables, and figures. These Instructions are divided into Parts, mostly to organize similar material, but you can find navigation pointers at the beginning of each Part. Each chapter starts with a listing of sections and subsections, each linked to its page. Tables of information and illustrations are also listed and cross-referenced. Most chapters have a table of specific items discussed there that lies one or two pages after the start of the chapter; this table has links for convenient navigation. An index has also been provided.

Changes Since the Previous Version
Document Presentation
The RPS2 Manual The RPS2 Users Manual for Cycle 10 is not in this version of the Phase 2 Proposal Instructions, but can be reached at:
http://www.stsci.edu/public/rps2-users.html

The Engineering Version (Engineering) The types of engineering-only text were described in the first four paragraphs of the Engineering version in this chapter. Note that change bars remain as an aid to identification, but the parallel bars next to individual blocks of text have been deleted. Instead, any text that is engineering-only has (almost) always been set as a separate paragraph.


6

Chapter 1: About This Document

On paper, these colors print as shades of grey. The critical items are those tagged "Restricted," and those always have that word at the beginning of such an entry. Navigation The navigation buttons have been removed from the individual pages of the document because the same functions are available in Acrobat, the PDF reader. Use the table of contents that runs down the left side of the window to go to chapters, the Table of Contents, or index. Web versus Paper We urge all proposers to access this information via the web. The web versions of the Phase 2 Proposal Instructions will be the only ones that you can be certain are up-to-date. They are easily downloaded and printed if you wish, but the on-line versions should provide superior cross-referencing and accessibility.

It is especially important that users of the Engineering version use the on-line document to ensure they are viewing the most recent changes.

Reader Feedback We have strived to present this critical, detailed, and complex information in a form that allows it to be used accurately and effectively. Your comments on its good and bad qualities will help us in the future; send e-mail to help@stsci.edu.

Technical Content
Available Science Instruments for Cycle 10 Neither NICMOS nor FOC is supported for use in Cycle 10. The only supported instruments in Cycle 10 are WFPC2, STIS, and FGS. The Advanced Camera for Surveys (ACS) and NICMOS should be available in Cycle 11. Instrument Modes, Special Requirements, etc. Some changes have been made to these Instructions since the previous version to correct errors and omissions, and to document new modes or


Where to Find Additional Information

7

options. There are too many to list, but as long as you use the most recent version the information provided should reflect our current state of knowledge.

Where to Find Additional Information
You will probably need to consult the Instrument Handbooks for one or more Science Instruments as you write your Phase 2 proposal. They are also available on the Web. However, in this version of these Instructions there are not yet cross-links to the Instrument Handbooks. There are some policies that were delineated in the Call for Proposals, which asked for Phase 1 proposals. You may wish to review those, particularly the sections discussing limited resources.

Some PDF Pointers
If you're new to Adobe's Portable Document Format (PDF), here are some hints that you may find useful: · PDF has links, just like HTML. Everything in blue in this document is a link you can click on to go somewhere else. · "Table of Contents" and "Index" take you to those chapters, which are designed to provide a thorough listing of the information available.

· PDF can print selected pages while HTML cannot. Note that the page numbers you enter are PDF's sequential numbers (look at the bottom of the Acrobat window to see where you are). · You can move up or down page by page using the scroll bar on the right of your Acrobat window; just click above or under the indicator that shows your relative position. You can also click and hold on this indicator to speed through the document. · If you wish to save this document as a PDF file on your local machine, click with your right mouse button on the Institute's web page that has the Phase 2 information at the spot where you link to the PDF file. In other words, your left button opens the file in Acrobat, but the right button lets you save the file if you pull down to "Save Link as." · Look at Acrobat's help facility (the help button is in the upper right corner of the Acrobat window) for more pointers.


8

Chapter 1: About This Document

If you are familiar with what is developing on the web you will see that PDF is an emerging standard for the commercial sector because it is easily produced with modern documentation software and has many excellent features. We welcome your comments and thoughts for improving how we provide information to you.


CHAPTER 2:

The Basics of Phase 2 Proposals
For an explanation of this engineering-only version, see Special Note to Engineering Version Users in Chapter 1: About This Document on page 3.

In this chapter . . .
How to Submit Phase 2 Information What to Submit / General Instructions / Examples and General Advice / Table 2.1: Limited-Resource Special Requirements / Proposal Template / /9 11 11 17 20 20

How to Submit Phase 2 Information
The computer software used to schedule and execute HST observations can interpret the proposal information only if it is in the proper format. Therefore, proposals must be filled out accurately, completely, and in strict accordance with the instructions in this document. Observers now have the capability and responsibility (with the help of their Program Coordinator and Contact Scientist) for creating and submitting proposals that are not only syntactically correct but also feasible and schedulable. This is possible using the revised Remote Proposal Submission (RPS2) software. An observer prepares the Phase 2 information at his or her home institution and then submits it electronically to STScI using the RPS2 software. They will be provided with a template RPS2 file which, for GOs, contains all relevant information from their Phase 1 submission (e.g. the title and

9


10

Chapter 2: The Basics of Phase 2 Proposals

abstract) already filled in. Observers should consult the RPS2 User's Manual for detailed instructions on how to install and use RPS2 at their home institutions. This will enable the proposal to be checked before electronic submission to STScI. (Observers without access to suitable computer equipment should contact their Program Coordinator to make other arrangements.) To get the User's Manual, go to: The RPS2 software allows the proposer to create a Phase 2 program which is free from errors and is feasible and schedulable. However, observers are urged to discuss their proposals and any problems encountered in filling out the Phase 2 template or using the RPS2 software with their assigned Program Coordinator and/or Contact Scientist. The RPS2 submission system will give the submitter an automatic electronic acknowledgment. This will generally be followed in a few days by an acknowledgment from the Program Coordinator. If, at the time of submission, the proposal contains outstanding errors, the RPS2 submission system will give a warning, but will allow the proposal to be submitted. However, the proposal will be flagged as having outstanding errors, and the observer will be contacted by the Program Coordinator within a few days to discuss how to proceed (if they have not discussed this already).

The resolution of errors in the Phase 2 Program is the responsibility of the Principal Investigator. The fact that RPS2 may allow you to submit a program that contains errors does not mean that program can or will be scheduled. These Instructions are, essentially, a programming language, and therefore they need to compile successfully before they can execute. We strive to make RPS2 useful and complete for preparing and checking your Phase 2 program, but it is nevertheless imperfect. On rare occasions syntax errors are not detected, and RPS2 does not check for guide stars. Caution and common sense are needed. In particular, many problems arise when programs are edited directly as text rather than using the facilities in PED. If you edit outside of PED, be sure to check the output from the DG to see if anything was lost, and consult with your Program Coordinator for advice.


What to Submit

11

What to Submit
Observers must submit the Remote Proposal Submission Two (RPS2) file to STScI by the Phase 2 deadline. It will contain the following: · Updated general information section. This section contains the title, proposer information, abstract, and proposal text sections. Please note that some general information is very useful for a thorough and helpful technical review of your proposal. You may wish to include parts of your Phase 1 science discussion, but please note that all the Phase 2 information that you provide is made freely available via the web. · Target List. One or more of the Fixed, Solar System, or Generic Target Lists must be completed. If necessary, proper motion and parallax information should be supplied for fixed targets. Detailed instructions for filling out the target lists, as well as the proper motion and parallax information, are provided in Chapter 3: Fixed and Generic Targets [Generic _Targets] on page 23 and Chapter 4: Solar System Targets List [Solar_System_Targets] on page 59 of this document. · Visit and Exposure Specifications. The Visit and Exposure Specifications must be completed. General instructions for completing the Visit/Exposure Template are provided in Chapter 5: Visits and Exposures on page 89 of this document.

General Instructions
In this section, we describe how to fill out the RPS2 template (the #.prop file, where # is the Phase 2 proposal identification number which will be supplied by your Program Coordinator). Information about retrieving samples of completed RPS2 files is presented in Examples and General Advice on page 17, along with a discussion of common questions and problems observers might have when filling out the template. Note the following general instructions and conventions when filling out the RPS2 template: · Entries must conform precisely to the formats specified in this document and their order must be correct as well (see Proposal Template on page 20).


12

Chapter 2: The Basics of Phase 2 Proposals

· Some information transferred from your Phase 1 proposal to the Phase 2 template may no longer be clear. For example, a table originally formatted in LaTeX may now be an unintelligible run-on of symbols. Please verify that all general information intended for inclusion in Phase 2 is readable. · Information that must be entered into the RPS2 template exactly as shown is indicated in BOLD TYPE. Items to be replaced by specific entries are enclosed in . For example, SEQ NON-INT could become SEQ 2-3 NON-INT or SEQ 10, 23, 15 NON-INT, depending on the appropriate exposure numbers. · Proposal data may contain only standard ASCII characters. All other symbols must be spelled out. Greek letters must be spelled out (e.g. BETA-LYR, H-ALPHA). The degree sign should be replaced with "D" (e.g. BD+16D516). Subscripts and superscripts are not allowed. · Information that cannot be made to conform to the required formats may be entered in a "Comments" line. Comment lines are not interpreted by the software but are maintained in the database and do appear on printouts of the forms. · Keywords on the Target Lists and Visit and Exposure Specifications can be deleted if no entry is required (i.e., the value is not relevant to your observations or the default value is acceptable). If you are unable to use the RPS2 software, please contact your Program Coordinator (listed in your notification letter) to make other arrangements.

Proposal Information [Proposal_Information]
This block contains basic information about the proposal including the · Title, · Proposal_Category, and · Cycle. The template you receive from your Program Coordinator will have all the above filled out based on your Phase 1 submission. For those Phase 2 submissions that are not based on a Phase 1 proposal (e.g., GTO programs), the Proposal_Category should be selected from one of the following:
GO (General Observer) SNAP (snapshot proposals) GO/DD (Director's Discretionary time)


General Instructions

13

The following proposal categories may also be used internally to STScI, but only as Restricted: CAL/WF2, CAL/FOC, CAL/NIC, CAL/STIS, CAL/AST, CAL/OS, CAL/OTA, ENG/WF2, ENG/NIC, ENG/STIS, ENG/FGS, ENG/AST, ENG/COS, ENG/FOC, ENG/SC, ENG/OTA, NASA, ERO, SM3. GTO/ACS, CAL/ACS, ENG/ACS. The following are available for SM3B: SM3/ACS, SM3/ERO, SM3/FGS, SM3/NIC, SM3/STIS, SM3/WF2, SM3/SC. Note the combination of "SM3" plus the Cycle number distinguished between SM3A and SM3B. New proposal types can be created, but only if needed. A Proposal_Category of SNAP is used for "snapshot" programs. By their nature these programs take advantage of otherwise-unused blocks of telescope time for relatively short exposures. SNAP exposures therefore must carry as few restrictions as possible. In particular, Special Requirements should not ordinarily be used with SNAP programs (consult with your Program Coordinator if you feel you need to do so). Also, less-restrictive guiding is ordinarily used for SNAP exposures because that is adequate for short exposures and because that helps extend FGS lifetimes. Some special policies apply to SNAP programs. In particular, STScI will not repeat failed SNAP exposures. The Cycle should be 10; multiple values of Cycle are not permitted. In pure parallel proposals (see Pure Parallels on page 103), the suffix /PAR should be added to the appropriate type from the above list. This identifies the proposal as a pure parallel. The Avail_Ok keyword is intended for GOs and GTOs who want to use "Available but Unsupported" engineering-only options, which are described throughout this document. The only legal value for Avail_Ok is YES. GOs and GTOs may use Available but Unsupported options only if this keyword has been enabled by the Contact Scientist, who will need to determine that the use of an Available but Unsupported mode is justified. If the Avail_Ok keyword is enabled, RPS2 will perform full error checking on exposures with Available but Unsupported options in GO and GTO proposals. Otherwise RPS2 will report a syntax error and any other problems with the exposure will not be detected. Proposal types beginning with CAL, ENG, or SM3 may use any engineering-only option and are not required to supply the Avail_Ok keyword.


14

Chapter 2: The Basics of Phase 2 Proposals

Parallel Information [Parallel_Pointing_Tolerance]
This information is required with pure parallel proposals (those with a Proposal_Category ending in /PAR). It does not apply to primary proposals. The Parallel_Pointing_Tolerance gives the maximum acceptable variation in pointing at the parallel aperture during a parallel visit. The units are arcsec but must be explicitly stated. The number must be non-negative (e.g., 10"). This will normally be set to the maximum pointing change that still allows exposures taken at slightly different pointings to be combined later during data analysis.

Investigators [Investigators]
This block contains the names of the Principal Investigator (PI_Name), all Co-Investigators (CoI_Name), and their institute affiliations (PI_Institution and CoI_Institution). This information has been filled out based on the Phase 1 submission. If one of the Co-Investigators (or other individuals) is to serve as the contact for a program, then the Contact keyword should be set to Y. The Contact is the person the Principal Investigator has designated to receive all (non-budgetary) questions/information on the program and to be the official voice for the team. Only one person may be designated as the Contact. Once designated, only the Contact may make Change Requests so that conflicting requests are not made. If any of the Investigators have changed addresses between the Phase 1 and Phase 2 submissions (or any time after the Phase 1 submission), please contact your Program Coordinator with the updated address. You cannot use the Phase 2 submission to implement address changes. For Phase 2 submissions that are not based on a Phase 1 proposal, please fill in the information accordingly.

Abstract [Abstract]
The Abstract from your Phase 1 submission has been included in your Phase 2 template. You may need to update this text based on your final TAC allocation. Although we have attempted to convert frequently-used special LaTeX symbols, you should review this text carefully. Also, you may need to reformat some tabular information. If a Phase 2 submissions is not based on a Phase 1 proposal, please fill in missing information.


General Instructions

15

Proposal Text Sections [Questions]
These four sections are needed for STScI to execute your program properly. Not all questions will need to be answered by every observer, and note that the answers to these questions will be made public along with the rest of the RPS2 file. As with the Abstract, please review this text to make certain all special symbols have been correctly converted, and reformat tabular information if necessary. Description of Observations [Observing_Description] Provide a detailed description of your observing plans. Text from your Phase 1 proposal has been inserted, but it will need updating based on your final TAC allocation and on details worked out in Phase 2. Justification of Real-time observations and Special Scheduling Requirements [Real_Time_Justification] Provide an explanation for any real-time or special scheduling requirements, if they have been requested. Information from your Phase 1 proposal (Item 14) has been inserted, but it is possible that the text will need updating based on your final TAC allocation, to include the details worked out in Phase 2, and to remove any special calibration requirements (see below). Justification of Special Calibration Requirements [Calibration_Justification] Provide a justification for any special calibrations required for your program, if requested. Additional Comments [Additional_Comments] Provide any additional comments that you feel STScI needs to know in order to properly implement your program.

Target Information [Fixed_Targets, Solar_System_Targets, Generic_Targets]
Chapter 3: Fixed and Generic Targets [Generic _Targets] on page 23 and Chapter 4: Solar System Targets List [Solar_System_Targets] on page 59 describe how to fill out the Target Lists.


16

Chapter 2: The Basics of Phase 2 Proposals

Visit Information [Visits]
Chapter 5: Visits and Exposures on page how to fill out the Visit and Exposure submitting parallel observations are given Exposures on page 101, and the detailed, are described in Part B: Supported Science 89 of this document describes Specifications. Instructions for in Chapter 6: Parallel Science instrument-specific parameters Instruments on page 177.

Data Distribution Information
HST observers are now expected to retrieve their proprietary data via the web, using either the archive's web retrieval form interface or StarView. It is possible to request "hard" media (either an 8 mm or a DAT tape) by using one of these tools. Observation summaries (previously called "paper products") are also available, but only via the web. The Principal Investigator (or the Contact identified by the PI; see Investigators [Investigators] on page 14)will be informed automatically by e-mail when observational data and observation summaries are ready for retrieval. Anyone requiring access to proprietary data should be both a registered user and an authorized user of the HST archive. If you are only a registered user, you have access only to public data via your archive username and a password. The registration address you provide is where any hard media will be sent, but the address is not otherwise used. You can become a registered user by filling out a registration form on the World-Wide Web
http://archive.stsci.edu/registration_form.html

or by contacting the Archive Hotseat at archive@stsci.edu. Authorization additionally allows a PI and individuals selected by the PI to have access to the PI's proprietary data and privileged web access to the observation summaries (which are PDF files). To become an authorized user, contact the Archive Hotseat. Authorization requests will be inspected very carefully. For this reason, authorization may take a little longer than simple registration. We strongly encourage PIs desiring this option to become registered and authorized well in advance of the execution of their program.


Examples and General Advice

17

Examples and General Advice
Acquisitions and Pointings
Getting HST located and oriented properly lies at the heart of successful observations, especially when a small aperture is being used, and there are a number of ways to do that. The remarks here apply specifically to fixed targets, and mostly apply to the use of small apertures, although many of them can be applied to moving targets as well. For more information, see Target Position [Position] on page 34. First, you have to acquire an object successfully that is at or near the position at which the science observation will be made. The object to be acquired should meet these conditions:
1. It should be a point source or nearly enough to point-like that the cen-

tering algorithms can determine a precise centroid.
2. The object's coordinates must be both precise and accurate and any

proper motion must be known. This requirement boils down to the need for the object to fall within the search region at the time of the acquisition. For this to happen the coordinates must also be consistent with the Guide Star Catalog or they must fall within another system that can be related to the GSC. This is why the source of the acquired object's coordinates are required.
3. The object must be neither too bright nor too faint for the instrument

mode used. These conditions are described in the various Instrument Handbooks. The coordinates for the acquired object can be specified in several ways: · As explicit absolute celestial coordinates, i.e., RA and DEC. See Equatorial Coordinates on page 36. · As celestial coordinates relative to another nearby object, using RA-OFF and DEC-OFF or XI-OFF and ETA-OFF. See Positional Offsets on page 39. · As a REGION; see Region of Sky (Extended Targets) on page 41. Second, once the acquisition has been made, the telescope must be repositioned to the precise point desired. This step is unnecessary, of course, if the object acquired in the first instance is the object to be observed. Repositioning can be implicit or explicit. By an implicit offset is meant the case where a target such as "XX-OFFSET" is acquired with some ACQ mode, and then "XX" is observed via a science exposure. This often leads to confusion because no


18

Chapter 2: The Basics of Phase 2 Proposals

specific motion of the telescope has been provided, but that motion is implied by specifying the separate targets with different coordinates. "XX-OFFSET" is specified for the acquisition because it is bright enough and point-like enough to be acquired successfully, but the coordinates specified by "XX" are what is to be observed. An explicit offset means using a Special Requirement such as POS TARG (see POSition TARGet , ) to move the telescope away from the position acquired. In this scheme, the position specified in the acquisition is placed at the fiducial point for the aperture requested (in general the geometric center of the aperture). The POS TARG then moves the telescope relative to that nominal position. Thus POS TARGs are not cumulative, and always refer back to the original acquired position.

Examples
Examples of HST observing programs are available as RPS2 formatted files on the STScI web pages. Many of the most popular observing techniques are represented. Once these files are downloaded, they may be easily edited for the specific targets and wavelengths desired. Start by going to the web page for the instrument you are using: For those observers who wish to try an observing sequence not shown there, help may be obtained from your Program Coordinator.

Common Problems
Incorrect Proposal Format The formats described in this document must be followed exactly, since the information in the forms is interpreted by computer software. Some items that warrant repetition are: · Target numbers and visit numbers must be unique. · Target names must be spelled exactly the same throughout the proposal. · The format for target positions must be followed to the letter. · The format for flux data must be followed. Only those defined in the instructions are acceptable. · The format for Optional Parameters and Special Requirements must be followed. Only those defined in these Instructions are acceptable.


Examples and General Advice

19

· Observations which cannot be defined using the syntax in these Instructions may be described in Comments fields, but such comments should be used very sparingly, if at all, and their use may impede execution of a program. For more information on coordinates, see Getting Coordinates Coordinated on page 58. Imprecise Target Positions See the discussion of required position accuracies in Table 3.11: Required Coordinate Accuracies. The requirements are much more stringent than is typically the case for ground-based observations. Lack of Acquisition Exposures with Small Apertures When exposures are requested in very small apertures or fields of view (e.g., STIS), a separate acquisition exposure is generally required.

Consideration of Limited Resources
Proposers should be aware that several of the Special Requirements impose serious constraints on the scheduling system because they require the use of limited resources; for example, RT ANALYSIS requires real-time use of the TDRSS that is only available some of the time. Hence these Special Requirements should be requested only if they are absolutely necessary to achieve the scientific goals of a project. It is quite possible that some proposals will be impossible to schedule because of their resource requirements, rather than a lack of scientific merit. The limited-resource Special Requirements can force the planning system to schedule the observations at a less than optimal time. The use of limited-resource Special Requirements by many observers can reduce the overall efficiency with which the planning system can schedule the science program. For these reasons, these Special Requirements should only be used when necessary to achieve the science objectives of the program. The STScI will review the necessity for the Special Requirements and in some cases may suggest removing them, or using alternate methods to obtain the same goal. The following table summarizes the Special Requirements that involve seriously limited resources. The need for many of these Special Requirements must be justified in the Questions section of the RPS2 template. Note that several of these Special Requirements must have been justified in the Phase 1 Proposal in order to be used legitimately in Phase 2; those are CVZ, SHADOW, and Targets of Opportunity.


20

Chapter 2: The Basics of Phase 2 Proposals Table 2.1: Limited-Resource Special Requirements
Limited Resource ON HOLD [FOR ] RT ANALYSIS, REQuires UPLINK ORIENTation TO , SAME ORIENTation AS SHADOW, LOW-SKY, CVZ AFTER , BETWEEN AND , BEFORE , SEQuence WITHIN , SEQuence NON-INTerruptible, PHASE TO , NO SPLIT Reason for constraint Require special handling. Requires real-time TDRSS links, which are difficult to schedule and may be withdrawn at last moment. A specific orientation can be available for as little as a one-week period every six months. Available for only a fraction of orbits.

Constrain scheduling opportunities. Can be mutually incompatible.

Proposal Template
Your proposal template 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 unless the proposal contains only internal or predefined pointings.

Proposal_Information
Title: Proposal_Category: Cycle: [Avail_Ok:]

[Parallel_Information
Parallel_Pointing_Tolerance]

Investigators
PI_Name: PI_Institution:


Proposal Template [CoI_Name: CoI_Institution: [Contact:]]

21

Abstract: Questions:
Observing_Description: [Real_Time_Justification:] [Calibration_Justification:] [Additional_Comments:]

[Fixed_Targets
Target_Number: Target_Name: [Alternate_Names:] Description: Position: Equinox: Coordinate_Source: [RV_or_Z:] [RA_PM:] [Dec_PM:] [Epoch:] [Annual_Parallax:] Flux: [Comments:]]

[Solar_System_Targets
Target_Number: Target_Name: Description: Level_1: [Level_2:] [Level_3:] [Window:] [Ephem_Uncert:] [Acq_Uncert:] Flux: [Comments:]]


22

Chapter 2: The Basics of Phase 2 Proposals

[Generic_Targets
Target_Number: Target_Name: Description: Criteria: Flux: [Comments:]]

Visits
Visit_Number: [Visit_Priority:] [Visit_Requirements:] [On_Hold_Comments:] [Visit_Comments:]

Exposure_Number: Target_Name: Config: Opmode: Aperture: Sp_Element: [Wavelength:] [Optional_Parameters:] Number_Of_Iterations: Time_Per_Exposure: [Special_Requirements:] [Comments:]


CHAPTER 3:

Fixed and Generic Targets [Generic _Targets]
For an explanation of this engineering-only version, see Special Note to Engineering Version Users in Chapter 1: About This Document on page 3.

In this Chapter . . .
Target Number [Target_Number] Target Name [Target_Name and Alternate_Names] Target Description [Description] Target Position [Position] Equinox for Coordinates [Equinox] Source of Specified Coordinates [Coordinate_Source] Radial Velocity or Redshift [RV_or_Z] Is Proper Motion or Parallax Relevant? Flux Data [Flux] Bright-Object Constraints Comments [Comments] Generic Targets List [Generic_Targets] / / / / / / / / / / / / 25 25 29 34 45 45 47 48 49 53 54 55

23


24

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Tables and Figures
Table 3.1: Designations of Special Targets Table 3.2: Target Categories Table 3.3: Descriptive Keywords for STAR and EXT-STAR Table 3.4: Descriptive Keywords for STELLAR CLUSTER and EXT-CLUSTER Table 3.5: Descriptive Keywords for GALAXY Table 3.6: Descriptive Keywords for CLUSTER OF GALAXIES Table 3.7: Descriptive Keywords for ISM and EXT-MEDIUM Table 3.8: Descriptive Keywords for UNIDENTIFIED Table 3.9: Descriptive Keywords for CALIBRATION Table 3.10: Discrete Features and Descriptors for All Categories Table 3.11: Required Coordinate Accuracies Table 3.12: Required Coordinate Accuracies for NICMOS (Restricted) Table 3.13: Formats for Specification of Target Flux Data Table 3.14: Bright-Object Constraints Table 3.15: Bright-Object Constraints for NICMOS (Restricted)

The use of the RPS2 "FIXED_TARGETS" and "GENERIC_TARGETS" blocks are described in this chapter. To make the presentation of this material more concise, the section on solar system targets has been made into a separate chapter; see Chapter 4: Solar System Targets List [Solar_System_Targets] on page 59.

The Target List tells us where you wish to point HST and so must be filled out with care, precision, and accuracy. The Target List also provides the information that defines and describe the targets, and which was used to determine exposure times. Three different kinds of Target Lists exist for the following three classes of targets, but only the Target List(s) required for your proposal need be submitted: · Fixed targets (all targets outside the solar system whose positions can be defined by specific celestial coordinates); · Solar-system targets (all moving targets);


Target Number [Target_Number]

25

· Generic targets (targets defined by certain properties, rather than by specific coordinates). In this chapter, each heading has a description followed by a keyword in square brackets (e.g., Target_Number). The keyword must be used in your RPS2 form. Elsewhere, items in boldface (e.g., RA-OFF) show words or phrases that are to be used directly as RPS2 entries. Items in brackets (e.g., ) show entries you are to provide. Parameters listed in square brackets (e.g., [A1 = ]) are optional, whereas those not in square brackets are required.

Target Number [Target_Number]
Each target that will be observed must be assigned its own unique number. Target numbers must be positive and monotonically increasing (but not necessarily consecutive) integers. A different target must be defined whenever different coordinates or a different target description are required. Separate targets should be defined and listed if you plan to take observations at several points within an extended object. For example, if you were to take spectra at three different locations in the Crab Nebula, each point must have its own target number, name, and coordinates, such as CRAB1, CRAB2, and CRAB3. If more than one type of Target List is used (such as both fixed and generic target lists), continue with the same numbering scheme used on the preceding Target List but start with a target number which is larger than the last target number on the preceding list. All target numbers and names within a proposal must be unique (within that proposal).

Target Name [Target_Name and Alternate_Names]
Target names are used to provide unique designations for the targets that will be used throughout the proposal. These names will also be used to designate targets in the HST data archive. Prospective proposers and archival researchers will use these names to determine whether HST has observed a particular object. This facility will be most useful if consistent naming conventions are used. The following conventions must be followed in naming targets:


26

Chapter 3: Fixed and Generic Targets [Generic _Targets]

·

A new target name must be defined for each (celestial) target. For example, for several pointings within a galaxy, one might define target names such as NGC4486-NUC, NGC4486-JET, NGC4486-POS1, and NGC4486-POS2.

· The maximum allowable length of a target name is 30 characters. · No blanks are permitted in target names. Blanks between a letter and a numeral must be suppressed (e.g., HD140283, NGC4378), but a hyphen (and not an underscore) must replace blanks between two letters or two numerals (e.g., ALPHA-CEN, NGC224-0040+4058). Also, a hyphen should be used where required for clarity (e.g., NGC4486-POS1). · Only letters, numerals, hyphens, periods (.), and + or ­ are allowed in target names; other punctuation is not permitted (e.g., BARNARDS-STAR is valid, but BARNARD'S-STAR is not). Greek letters must be spelled out (e.g., ALPHA-ORI). Letters may be upper-case or lower-case, but will always be treated as if they are upper case (e.g. Alpha-Cen will be treated as if written ALPHA-CEN). · Degree signs must be represented by an upper-case "D" (e.g., CD-42°14462 becomes CD-42D14462). · Some special target names are reserved for calibrations and other purposes and may not be used for external pointings; see Table 3.1: Designations of Special Targets. Whenever possible, two types of designations should be provided for each target. The first will be a "catalog name" (for example, HD124897), and the second will be at most two "common names" (e.g., ALPHA-BOO, ARCTURUS). The "catalog name" is entered in Target_Name and the "common names" are entered in Alternate_Names. Only the catalog name is used when the target name is repeated in the Visit and Exposure Specifications. If the target is in the STScI Guide Star Catalog (GSC), the GSC name should be included as one of the common names (e.g., GSC5637-12345).

Catalog Name
The preferred order for catalogs to be used for the designation of various classes of objects is provided below. It is arranged in order of decreasing preference. If a target is not contained in these catalogs, other catalog designations may be used (e.g., 4U X-ray catalog designation, Villanova white-dwarf catalog


Target Name [Target_Name and Alternate_Names]

27

number, etc.). The use of positional catalogs (SAO, Boss, GC, AGK3, FK4, etc.) is discouraged. For uncataloged targets, see Uncataloged Targets on page 28. Stars
1. Henry Draper Catalog number (e.g., HD140283)is preferred. HDE

numbers are discouraged, except in the Magellanic Clouds.
2. Durchmusterung number (BD, CD, or CPD). In the southern hemi-

sphere, adopt the convention of using CD north of ­52 degrees and CPD south of there (e.g., BD+30D3639, CD-42D14462, CPD-65D7691).
3. General Catalog of Variable Stars designation, if one exists (e.g.,

RR-LYR, SS-CYG).
4. AFGL designation. 5. IRC designation. 6. IRAS designation.

Star Clusters and Nebulae
1. New General Catalog (NGC) number (e.g., NGC6397, NGC7027). 2. Index Catalog (IC) number (e.g., IC418). 3. For planetary nebulae for which you do not have an NGC or IC des-

ignation, the Perek-Kohoutek designation (e.g., PK208+33D1) may be used.
4. For H II regions for which you do not have an NGC or IC designa-

tion, the Sharpless catalog number (e.g., S106) may be used.
5. For IR nebulae, AFGL designation.

Galaxies and Clusters of Galaxies
1. NGC number (e.g., NGC4536). 2. IRAS designation. 3. IC number (e.g., IC724). 4. Uppsala Catalog number, only if an NGC or IC number is not avail-

able (e.g., UGC11810).
5. For clusters of galaxies, the Abell catalog number, but only if an

NGC or IC number is not available (e.g., ABELL2029).


28

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Quasars and Active Galaxies
1. The name defined in the compilation by Veron-Cetty and Veron (ESO

Report No. 7, 1989) must be used (e.g., 3C273).

Uncataloged Targets
Objects that have not been cataloged or named must be assigned one of the following designations:
1. Isolated objects must be designated by a code name (the allowed

codes are STAR, NEB, GAL, STAR-CLUS, GAL-CLUS, QSO, SKY, FIELD, and OBJ), followed by a hyphen and the object's J2000 equatorial coordinates, if possible, rounded to seconds of time and seconds of arc (e.g., for a star at J2000 coordinates RA = 1H 34M 28S, DEC = ­15D 31' 38", the designation would be STAR-013428-153138).
2. Uncataloged objects within star clusters, nebulae, or galaxies must

be designated by the name of the parent body followed by a hyphen and the rounded J2000 coordinates, if possible, of the object (e.g., for a target within NGC 224 with J2000 coordinates RA = 0H 40M 12S, DEC = +40D 58' 48", the designation would be NGC224-004012+405848).
3. Positions within nebulae or galaxies may also be designated by the

name of the parent object followed by a hyphen and a qualifier. The qualifier should be brief, but informative (e.g., the jet in NGC 4486 could be designated NGC4486-JET). Other examples are: NGC5139-ROA24, LMC-R136A, ABELL30-CENTRAL-STAR, NGC205-NUC.

Common Names
In addition to the catalog name, a target should be assigned at most two "common names," or aliases, if they exist. Examples of common names are the following:
1. Stars: The Bayer (Greek-letter) designation or Flamsteed number

with standard three-letter constellation abbreviation (e.g., ZETA-CAP, 22VUL, OMICRON2-ERI-B); the Bright Star Catalog number (e.g., HR5270); other names, if they exist (e.g., CYG-X1, BARNARDS-STAR, PROXIMA-CEN).
2. Star clusters, nebulae, galaxies, and clusters of galaxies: Commonly

used names (e.g., HYADES, OMEGA-CEN, CRAB-NEBULA, ABELL63, COMA-CLUSTER); Messier numbers (e.g., M13, M31, M67).


Target Description [Description]

29

Special Targets
The names of certain types of targets must be designated by appending a code to the target name. For example, -CALIB should be appended to the name of a target that is being observed only as a calibration standard for other observations. These designations will assist in planning of the observing schedule. The three possible codes are listed in Table 3.1.
Table 3.1: Designations of Special Targets
Target Type External calibration target Code -CALIB Description An astronomical target used for calibration (e.g., BD+28D4211-CALIB). Internal calibration sources (e.g., WAVE) and calibrations using the Earth must not be included in the Target List. Stars used to determine astrometric positions of other targets (e.g., HD20731-01-REF would designate reference star 01 near HD 20731). Note that the "parallax star" (the target whose position is being measured) may not have a ­REF suffix. A target that will be used for an offset acquisition; it is the object that will be acquired first, from which an offset will be applied to move to the target of interest (e.g., 3C273-OFFSET). Two separate exposures must be defined on the Visit and Exposure Specifications; an acquisition of the -OFFSET target, and a science exposure of the (target of interest) program target. The location of the latter target may be specified either by equatorial coordinates or by an offset (see Target Position [Position] on page 34). For example: to observe the JET in 3C273, first acquire "stellar-like" source 3C273-OFFSET, then offset to program target 3C273-JET. These are reserved designations and may not be used as the names of external pointing in a target list:

Astrometric reference star

-REF

Offset acquisition target

-OFFSET

Special designations

ANTI-SUN, ANY, BIAS, CCDFLAT, DARK, EARTH-CALIB, INTFLAT, KSPOTS, NONE, ORBIT-POLE, ORBIT-POLE-NORTH, ORBIT-POLE-SOUTH, UVFLAT, VISFLAT, WAVE

Target Description [Description]
A target description must be provided for each target. The Target Description will be one of the key fields used by archival researchers in


30

Chapter 3: Fixed and Generic Targets [Generic _Targets]

searching through the HST data archive; thus it is extremely important that the information be filled out completely and accurately for each target. Each target must be assigned a single primary category from Table 3.2, and at least one descriptive keyword, chosen from the appropriate Table 3.3 through Table 3.9 (see Table 3.2 for which table is appropriate for each category). The discrete features and descriptors in Table 3.10 may be used as descriptive keywords for any category. A maximum of five descriptive keywords may be specified. It is possible, but not required, to specify a second category for a target, followed by one to five descriptive keywords from the appropriate tables, as described for the primary category. Whether one or two categories are used, all values must be separated from each other by commas. For example, suppose the STAR category is chosen with the descriptive keywords Polar and Interacting Binary. This target description would be specified as STAR, Polar, Interacting Binary. The categories in Table 3.2, and some of the descriptive keywords in Table 3.3 through Table 3.10, are followed by explanatory text in parentheses. This text is provided only for explanatory purposes and is not part of the category or keyword itself. Only the non-parenthesized portion, which appears in bold in the tables, should be entered into the RPS2 file.
Table 3.2: Target Categories
Descriptive Keywords Discrete Features and Descriptors

Category SOLAR SYSTEM (Solar System Object) STAR (Galactic Stellar Object) EXT-STAR (Star in an External Galaxy) STELLAR CLUSTER (Galactic Star Cluster, Group, or Association) EXT-CLUSTER (Star Cluster in an External Galaxy) GALAXY (Galaxy or AGN) CLUSTER OF GALAXIES (Galaxy Groupings, Clusters, Large-scale Structure) ISM (Interstellar Medium of the Galaxy) EXT-MEDIUM (Interstellar Medium of an External Galaxy) UNIDENTIFIED (Unidentified Objects) CALIBRATION (Calibration Observations)

Chapter 4: Solar System Targets List [Solar_System_Targets] on page 59 Table 3.3 Table 3.3 Table 3.4 Table 3.4 Table 3.5 Table 3.6 Table 3.7 Table 3.7 Table 3.8 Table 3.9 See Table 3.10


Target Description [Description] Table 3.3: Descriptive Keywords for STAR and EXT-STAR
Brown Dwarf Wolf Rayet Wolf Rayet ­ WC Wolf Rayet ­ WN Main Sequence O Giant O Supergiant O OE OF SDO WDO B0-B2 V-IV B3-B5 V-IV B6-B9.5 V-IV B0-B2 III-I B3-B5 III-I B6-B9.5 III-I BE BP SDB DB DA DC DZ A0-A3 V-IV A4-A9 V-IV A0-A3 III-I A4-A9 III-I AE AM AP AGB Star Post-AGB Star Composite Spectral Type F0-F2 F3-F9 FP Late-type Degenerate G V-IV G III-I K V-IV K III-I M V-IV M III-I S Star Carbon Star Long Period Variable Irregular Variable Regular Variable Luminous Blue Variable Dwarf Nova Classical Nova Nova-like Recurrent Nova Polar (AM Her Star) Intermediate Polar (DQ Her Star) Symbiotic Star T Tauri Star FU Orionis Star Shell Star Eta Carinae Star YSO Herbig Ae/Be Horizontal Branch Star Interacting Binary X-ray Novae X-ray Burster X-ray Transient LMXB (Low Mass X-ray Binary) Gamma Ray Burster MXB (Massive X-ray Binary) RS CVn Star W UMa Star Beta Lyrae Star Algol System Barium Star Blue Straggler Neutron Star Pulsar Binary Pulsar FK Comae Star Pulsating Variable PG1159 Star ZZ Ceti Star Cepheid Supernova Supernova Type Ia Supernova Type Ib Supernova Type II RR Lyrae Star Planetary Nebula Central Star Emission Line Star

31


32

Chapter 3: Fixed and Generic Targets [Generic _Targets] Table 3.4: Descriptive Keywords for STELLAR CLUSTER and EXT-CLUSTER
Globular Cluster Open Cluster OB Association T Association

Table 3.5: Descriptive Keywords for GALAXY
Spiral (Spiral Galaxy) Lenticular (Lenticular Galaxy) Elliptical (Elliptical Galaxy; Not A Dwarf Elliptical) Dwarf Elliptical Magellanic Irregular Amorphous Irregular Dwarf Compact (Dwarf Compact/HII Galaxy) Dwarf Spheroidal BCM (Brightest Cluster Member) BGM (Brightest Group Member) LSB (Low Surface Brightness/HI Rich Galaxy) Seyfert QSO (Radio Quiet) Quasar (Radio Loud) Radio Galaxy BL Lac (BL Lac or BLAZAR) Liner Starburst Ultraluminous IR Gal Interacting Galaxy Lyman Alpha Cloud Protogalaxy Gravitational Lens Einstein Ring High Redshift Galaxy (z > 0.5)

Table 3.6: Descriptive Keywords for CLUSTER OF GALAXIES
Supercluster Void Group Rich Cluster Poor Cluster High Redshift Cluster (z > 0.5) Galaxy Pair Interacting Galaxy BCM (Brightest Cluster Member) BGM (Brightest Group Member) Gravitational Lens Einstein Ring Blank Sky


Target Description [Description] Table 3.7: Descriptive Keywords for ISM and EXT-MEDIUM
Description Herbig-Haro Object Planetary Nebula HII Region Reflection Nebula Dark Cloud SNR (Supernova Remnant) Ring Nebula HI Cloud High Velocity Cloud Intermediate Velocity Cloud IRAS Cirrus Cometary Nebula Molecular Cloud Bipolar Outflow Absorption Line System Absorption Line System ­ Galactic Absorption Line System ­ Extragalactic Damped Lyman Alpha Cloud (Extragalactic) Coronal Gas (105­106 K) Hot Gas (107­108 K) IGM ICM

33

Table 3.8: Descriptive Keywords for UNIDENTIFIED
Radio Emitter Infrared Emitter Optical Emitter Ultraviolet Emitter X-ray Emitter Gamma Ray Emitter Blank Field Parallel Field High Latitude Field Low Latitude Field

Table 3.9: Descriptive Keywords for CALIBRATION
Astrometric Photometric Wavelength Point Spread Function Occulting Finger Location Ion Taled Scattered Light Test Sky Background Instrument Sensitivity Test Narrow Band Filter Calibration FGS Stability Quantum Efficiency Test Pointing and Jitter Test Raster & Step/Dwell Scan Verification Spatial Distortion Test Polarimetry Aperture Location Detector Linearity Test Carrousel Stability Test Target Acquisition Test Detector Sensitivity Test Focus Test Spacecraft Glow Occultation Mode Test Throughput Test Echelle Blaze Function Virtual Pointing FGS Transfer Function Test Shutter Control Test


34

Chapter 3: Fixed and Generic Targets [Generic _Targets] Table 3.10: Discrete Features and Descriptors for All Categories
Corona Ring Ansae Protoplanetary Disk Wind Accretion Disk Jet Lobe Hotspot Nucleus Halo Disk Bulge Polar Ring Dust Lane Spiral Arm Shell Tidal Tail Bar Multiple Nuclei Cooling Flow Emission Line Nebula BLR (Broad Line Region) NLR (Narrow Line Region) Filament Ejecta Knot Star Forming Region Shock Front Ionization Front Conduction Front Undesignated

Target Position [Position]
A position is required for each fixed target. The position may be expressed in any one of three different ways: · By specifying the equatorial coordinates (RA and DEC) of the target; · By specifying a positional offset from another target; or · By specifying a region (area) of the sky. It is also possible to specify that the coordinates were obtained using the Guide Star Selection System (GSSS; see Determining Coordinates in the Guide Star Selection System (GSSS) Reference System on page 42), or that they are currently uncertain or unknown, and that more accurate coordinates will be provided by the observer after an early acquisition exposure is taken, or in real time during the HST observations.

Required Accuracies of Target Positions
The HST Scientific Instruments (SIs) typically have very small apertures and fields of view. Target-acquisition apertures for several of the SIs are only a few seconds of arc in size. Since the HST has no analog to the video acquisition cameras common on many ground-based telescopes, it is essential to have accurate coordinates for targets. In many cases targets will be placed in the final observing aperture after a sequence of target-acquisition observations. This will only work, however, if the target


Target Position [Position]

35

coordinates are sufficiently accurate and precise to place the target in the first of these acquisition apertures. HST uses two guide stars to stabilize the pointing of the telescope and to place the target in the desired aperture. The fundamental problem, then, is to determine the position of the target relative to the guide stars in the surrounding area with sufficient accuracy to place the target in the aperture. The specific pair of guide stars to be used cannot be determined in advance of the observation; several possible pairs will often be available for each target. The guide stars are chosen from the Guide Star Catalog (GSC). The uncertainty of the relative positions of a group of potential guide stars in the GSC is 0.33 arcsec (1 sigma) in the north and about 0.5 arcsec in the south. The accuracies of positions typically needed for target acquisition with each of the SIs are shown in Table 3.11; these are predicated upon the positions being in the coordinate system of GSC, which is based upon the AGK3 and SAO reference systems. Note that several of the SIs have multiple acquisition apertures of different sizes that may be used. Be sure when selecting acquisition apertures to keep the coordinate uncertainties in mind. Furthermore, be sure to provide 1 sigma uncertainties with your positions so that STScI may check the appropriateness of your acquisition exposures. Inaccurate target coordinates can result in failed target acquisitions and can therefore waste valuable HST observing time. As indicated in Table 3.11, it is the observer's responsibility to provide accurate coordinates in all cases, but in particular they must be in the GSC reference frame when using STIS, and NICMOS with the NIC1 and NIC2 detectors. Please contact your PC if you need additional information. Although GSC frame-based coordinates are not required for FGS and WFPC2 observations, it is still prudent to check the accuracy of your coordinates. All observers will be provided target confirmation charts by their PC to help them verify the target coordinates in the GSC reference frame. The Principal Investigator of a program is responsible for ensuring that target coordinates are accurate, both at the time of program submission, and later when target confirmation charts are provided. The following address has pertinent information on target confirmation charts: Note: HST proposals executed before July 1991, as well as engineering proposals of type OV, SV, SMOV, and CAL, should not be used to derive target coordinates. Coordinates from such proposals may be unreliable owing to poor calibration and/or engineering-related pointing changes made during the observations.


36

Chapter 3: Fixed and Generic Targets [Generic _Targets] Table 3.11: Required Coordinate Accuracies
Instrument Configuration WFPC2 (WFC) WFPC2 (PC) STIS FGS Accuracy Required (1 sigma, arcsec) 10 5 1 1 GSC Coordinates Required? No No Yes No

Table 3.12: Required Coordinate Accuracies for NICMOS (Restricted)
Instrument Configuration NIC1a (Restricted) NIC2 (2) (Restricted) NIC3 (2) (Restricted) Accuracy Required (1 sigma, arcsec) 3 5 10 GSC Coordinates Required? Yes Yes No

a. If multiple NICMOS detectors are being used in parallel, the primary detector (the detector used for the exposures in the of the PARallel WITH Special Requirement; see PARallel WITH ) determines the required coordinate accuracy for the observation and whether GSC frame-based coordinates are required.

Equatorial Coordinates
If you specify the target position directly in terms of equatorial coordinates (as opposed to specifying an offset or a region), then the right ascension and declination and their uncertainties are required, using the following format: RA = +/­ , DEC = +/­ · The comma following the right-ascension uncertainty is required. · The uncertainties represent the accuracy (1 sigma) of the target coordinates, not the region within which a target could be observed (e.g., for a sky measurement). See Region of Sky (Extended Targets) on page 41 for instructions on how to designate regions as targets. · The right-ascension value must be expressed either in hours (H), minutes (M), and seconds (S) of time; or in decimal degrees (D). For example, RA = 108.14375D and RA = 7H 12M 34.5S are equivalent.


Target Position [Position]

37

· The declination value must be expressed either in degrees (D), minutes ('), and seconds (") of arc; or in decimal degrees (D). Thus DEC = -12D 55M 33.3S and DEC = -12.92592D are equivalent. · Units must be provided for both a value and its uncertainty. The uncertainty must be expressed in one and only one of the units used to express the related RA and/or DEC, with the additional units of minutes (') of arc or seconds (") of arc being allowed for right ascension. (In other words, the RA may be expressed as a combination of three units [H, M, S], but its uncertainty must be in terms of a single unit such as S or ".) To clarify:
Quantity and units specified RA: H-M-S RA: Degrees DEC: D-M-S DEC: Degrees Acceptable units for uncertainty timemin, timesec, arcmin, arcsec degrees degrees, arcmin, arcsec degrees

An example: RA = 12H 7M 13.33S +/­ 0.15S, DEC = +27D 3' 8.0" +/­ 0.1" and RA = 181.80554D +/- 0.00063D, DEC = +27.05222D +/- 0.00003D are equivalent. Note: If the sign of the declination is not indicated, a positive declination is assumed, but we urge you to always include the sign as a way of reducing errors.

The following text is made Engineering until the issue of coordinate uncertainties is resolved.

If you specify the target position directly in terms of equatorial coordinates (as opposed to specifying an offset or a region), then the right ascension and declination are required, using the following format: RA = [ +/­ ], DEC = [ +/­ ] · The comma following the right-ascension is required. · The right-ascension value must be expressed either in hours (H), minutes (M), and seconds (S) of time; or in decimal degrees (D). For example, RA = 108.14375D and RA = 7H 12M 34.5S are equivalent.


38

Chapter 3: Fixed and Generic Targets [Generic _Targets]

· The declination value must be expressed either in degrees (D), minutes ('), and seconds (") of arc; or in decimal degrees (D). Thus DEC = -12D 55M 33.3S and DEC = -12.92592D are equivalent. · The uncertainties, if specified, represent the accuracy (1 sigma) of the target coordinates, not the region within which a target could be observed (e.g., for a sky measurement). See Region of Sky (Extended Targets) on page 41 for instructions on how to designate regions as targets. · Uncertainties for these values are no longer required, but units must be provided for both a value and its uncertainty when both are listed. The uncertainty should be provided if it is larger than about 2 arcsec; it is used in computing slew times for some Special Requirements that reuse positional offsets from a previous visit. If provided, the uncertainty must be expressed in one and only one of the units used to express the related RA and/or DEC, with the additional units of minutes (') of arc or seconds (") of arc being allowed for right ascension. (In other words, the RA may be expressed as a combination of three units [H, M, S], but its uncertainty must be in terms of a single unit such as S or ".) To clarify: Quantity and units specified RA: H-M-S RA: Degrees DEC: D-M-S DEC: Degrees An example: RA = 12H 7M 13.33S +/­ 0.15S, DEC = +27D 3' 8.0" +/­ 0.1" and RA = 181.80554D +/- 0.00063D, DEC = +27.05222D +/- 0.00003D are equivalent. Acceptable units for uncertainty timemin, timesec, arcmin, arcsec degrees degrees, arcmin, arcsec degrees


Target Position [Position]

39

IMPORTANT: Both SAVE OFFSET and USE OFFSET rely on accurate coordinate uncertainties in order to calculate slew times properly. Unspecified target coordinate uncertainties may lead to a failure in execution of USE OFFSET. Program Coordinators should ensure that target coordinate uncertainties have been provided by the observer and that they are accurate.

Note: If the sign of the declination is not indicated, a positive declination is assumed, but we urge you to always include the sign as a way of reducing errors.

Positional Offsets
The position of a target may alternatively be specified as an offset from a reference target. It is possible to specify offsets in equatorial coordinates, in rectangular coordinates, or in polar coordinates, all of which have their origin at the reference target. Note, however, that offsets larger than 30 arcsec may complicate the target acquisition procedure. If larger offsets are desired, please contact your Program Coordinator. Equatorial and rectangular offsets are always in the sense offset = target-coordinates minus offset-reference-coordinates, while a polar offset is expressed as an angular separation and position angle of a line drawn from the offset reference target to the target. As with other similar quantities, we urge you to include the sign of the offset, even when it is positive, as a means of removing ambiguity. Note that in the examples below, FROM 6, 3, and 4 are the target numbers which contain the equatorial coordinates of the reference targets, and that the reference-target names have ­OFFSET appended (see Table 3.1). Positional offsets are only a convenient method of specifying target coordinates, and do not automatically imply a particular method of target acquisition; observers must explicitly specify any target acquisitions on the Visit and Exposure Specifications via Special Requirements (see Chapter 7: Special Requirements [Visit_Requirements and Special_Requirements] on page 111).


40

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Warning: If your object has significant proper motion no correction may be applied. See Is Proper Motion or Parallax Relevant? on page 48, where it notes that the proper motion for the target is taken to be the same as for the offset object.

As with coordinates, uncertainties are no values of zero if you do not provide an only in special cases that involve reusing even then the uncertainty is not ordinarily

longer required. RPS2 will insert uncertainty. Uncertainties matter offsets from previous visits, and of significance.

1. The format for the specification of an offset as a difference in EQUA-

TORIAL coordinates is: RA-OFF = +/­ , DEC-OFF = +/­ , FROM Note the uncertainties and the commas separating the three items. The value for RA-OFF may be in units of seconds (S) of time or in decimal degrees (D), and the value for DEC-OFF may be in units of arcmin (') or arcsec ("), or in decimal degrees (D). The uncertainty must be expressed in one and only one of the units used to express the related RA and/or DEC. In the following example, a target's right ascension is 1.1 seconds of time greater than, and its declination is 10 arcsec less than, the right ascension and declination of target number 6: RA­OFF = +1.1S +/­ 0.2S, DEC­OFF = ­10" +/­ 1", FROM 6
2. Offsets in RECTANGULAR coordinates are interpreted as displace-

ments in the tangent plane whose origin is located at the reference target. For displacements of less than about one degree, they may be interpreted as the offsets that are measured on a photographic plate, without making errors larger than about 0.5 arcsec. The format for the specification of an offset in rectangular coordinates is: XI-OFF = +/- , ETA-OFF = +/, FROM Note: North and east displacements are considered positive (+), south and west are negative (­). The values of XI-OFF and ETA-OFF are required to both be expressed in arcmin (') or arcsec ("), and the uncertainties must be expressed in the same units (in other words, all four angular quantities must be in the same units). In the following example, a target has been measured on a sky-survey plate, with a scale of 67


Target Position [Position]

41

arcsec/mm, to lie 0.5 mm west of, and 1 mm north of, target number 3, with an accuracy of 1 arcsec: XI­OFF = ­33" +/­ 1", ETA­OFF = +67" +/­ 1", FROM 3
3. The format for a POLAR offset specification is:

R = , PA = , FROM Note that uncertainties must not be included in this type of specification. The separation is expressed in units of minutes (') or seconds (") of arc. The position angle of the target with respect to the reference target is measured east of north, and the unit of measurement (degrees) is required. In the following example, a target lies 10 arcsec from target number 4, at a position angle, measured at target 4 from north through east, of 60 degrees: R = 10", PA = 60D, FROM 4

Region of Sky (Extended Targets)
Sometimes it is necessary to define a region of sky rather than a specific point. Examples are extended targets (such as emission nebulae and galaxies) and blank-sky regions for background measurements (if it is acceptable to make the observation anywhere within a region). It is possible to specify rectangular or circular regions. An Equinox value should be specified with the region coordinates (see Equinox for Coordinates [Equinox] on page 45). The units used for regions should be used in the same way as for coordinates; see Equatorial Coordinates on page 36. Rectangular Region For a rectangular region, the format for equatorial coordinates must be used, followed by a comma and the word REGION; the values following +/­ will then be interpreted as one-half the lengths of the sides of the rectangular area, rather than as uncertainties in the coordinates. In the following example, a region 4 arcmin wide in right ascension by 2 arcmin high in declination is specified: RA = 3H 51M 27S +/­ 2', DEC = ­37D 13' 25" +/­ 1', REGION Circular Region If it is desired to specify a circular region, REGION must be followed by another comma and the radius of the region in the format R = ; in this case, no uncertainties should be attached to the RA and DEC. Here is an example of a circular region with a radius of 2 arcmin:


42

Chapter 3: Fixed and Generic Targets [Generic _Targets]

RA = 3H 51M 27S, DEC = ­37D 13' 25", REGION, R = 2' Note that the units of R must be specified.

Determining Coordinates in the Guide Star Selection System (GSSS) Reference System
The HST reference frame is defined by the HST Guide Star Catalog (GSC) that STScI has created. For observations that require accurate coordinates, such as those listed as "GSC Coordinates Required" in Table 3.11, it is vital that you provide positions derived in the same reference frame as the original GSC plate material. Access to the GSC, as well as lightly compressed versions of the plates used to construct the GSC, is available on the CASB WWW server. Begin at http://www-gsss.stsci.edu/support/phase2.html and follow the links under "General Guidelines." Coordinates produced using these facilities will be in the same reference frame as the GSC. Here are some more detailed guidelines for different categories of brightness and type:
1. Stars with m(V) between about 9 and 14 (at high galactic latitude) or

between about 9 and 13 (at low galactic latitude): Most of these are contained in the GSC. You can retrieve GSC coordinates using a form available on the CASB Web server listed above. When you have the GSC coordinates, enter them in the Position field of the Target List, followed by the plate identification number (not the region number) from the GSC, using the format PLATE­ID = . This identifies the target coordinates as coming from the GSC. Also enter the GSC name as a target alias in Alternate_Names. An example: RA = 12H 13M 14.27S +/­ 0.3", DEC = ­13D 11' 03.3" +/­ 0.3", PLATE­ID=00TB For stars brighter than about m(V) = 9, coordinates from the Hipparcos Input Catalogue have been added to the GSC; these coordinates can be recognized as having a plate designation of +056. Enter the GSC name as a target alias, but do not include the PLATE­ID for coordinates derived from the Hipparcos Input Catalogue (but do indicate in the target-level Coordinate_Source field that the coordinates are from Hipparcos). Note that coordinates from the Hipparcos Output Catalog are on a different system from the GSC; but the differences are negligible in almost all instances.


Target Position [Position]

43

2. Stars fainter than about m(V) = 13 ­ 14, and extended sources: The

plate material that was used to construct the GSC will generally allow identification of targets to magnitudes of V = 19 in the northern- and J = 22 in the southern hemisphere. Use the facility and instructions available on the CASB Web server listed above to determine coordinates of targets on the GSC plates. Once coordinates have been obtained, Position should again contain the plate ID from GSC, using the PLATE­ID = format. Contact your Program Coordinator if you need assistance.
3. Stars fainter than about m(V) = 13 ­ 14, and extended sources (for

which special plates or ground-based CCD images were obtained): You must transfer the GSC reference frame to your special plates or CCD images. You will need about ten stars from GSC as your reference stars when carrying out plate reductions. Enter the coordinates in Position, again with the PLATE­ID = format, to indicate which GS plate provided the coordinates used for the plate reduction. As part of preparing your observations, your Program Coordinator will provide, as a final check that the coordinates are correct, a Confirmation Chart showing the target coordinates (as entered in the proposal) overlaid on the field from the plate material used to construct the Guide Star Catalog. You are responsible for verifying that the coordinates are correct. (See Required Accuracies of Target Positions on page 34.)

A Caution on Astrometry Prepared from STScI Plate Scans
Note that the set of plates used to construct the GSC is NOT the same one that is contained in the 102-volume set of CD ROMs distributed as the Digitized Sky Survey (DSS-I) and that is available elsewhere at the stsci.edu Web site. The DSS-I uses the 1950 epoch POSS-E plates for the north, whereas the GSC in the north is based on the 1982 epoch Palomar Quick V. Similarly, in a few cases, the southern plates used in the GSC are not the ones in the DSS-I. HST users may use the DSS-I CD ROMs to prepare their Phase 2 submissions only if they verify that the DSS-I plates are the same as those used in the GSC, i.e., the plate ID field must be identical.

Prohibition on the Use of GSC Version 1.2
Preliminary access to an improved (astrometrically recalibrated) GSC, version 1.2, has been provided via a WWW server. As this revision has significantly different astrometry from the GSC currently used by HST


44

Chapter 3: Fixed and Generic Targets [Generic _Targets]

operations (version 1.1), GSC version 1.2 must not be used for Phase 2 target determinations. Note that all GSC CD ROMs in circulation are from version 1.1 or lower. Uncertain or Unknown Coordinates If it is impossible to obtain adequate plate material to measure coordinates to the required accuracy (e.g., a very crowded field which cannot be resolved using ground-based observations), it may be necessary to obtain an early acquisition image or to perform an acquisition that involves real-time interaction with the telescope (see Target Acquisition on page 134). In that case, coordinates as accurate as possible must be entered on the Target List.

Special Catalogs
The option PLATE-ID can be used to specify one of the special guide star catalogs which have been created by the STScI to accommodate special guide star requirements. These catalogs are primarily used for selecting guide stars from a subset of stars in the region which have certain properties or more accurate relative positions. This option is most commonly used when the relative accuracy of guide stars and target stars must be known with great precision. The Special Catalogs currently available are:
PLATE-ID ZZZZ ZZZX ZZZW ZZZV ZZZU ZZZT ZZZR ZZZQ SKY REGION NGC188 Iota Carinae HR6636 HR6850 HR6945 NGC5617 Omega Centauri Eta Carinae

Only a modest number of specific objects are listed in these catalogs; contact your PC.


Equinox for Coordinates [Equinox]

45

Equinox for Coordinates [Equinox]
Specify the year of the equator and equinox to which the coordinates are referred, optionally preceded by a J or B to indicate the Julian or Besselian system. Integer or decimal values for the year may be used. If the year is given without a prefix (for example, 1975), the Besselian system is assumed for years prior to 2000 and the Julian system is assumed for the year 2000 and beyond. If a prefix is given, it must be B for years prior to 2000 and J for the year 2000 and beyond. The values J2000 and B1950 correspond to commonly used catalogs; it is recommended that one of these be specified unless there is a good reason to use something else. It is not necessary to apply precession corrections to coordinates from positional catalogs. The Guide Star Catalog and the Hipparcos Input Catalogue both use the J2000 equinox. (Note, however, that the Hipparcos output catalogue is epoch 1991.25, which means proper motions can have significant effects if you are not careful.) An Equinox value is required. For some notes on Equinox, Epoch, and units, see Getting Coordinates Coordinated on page 58.

Source of Specified Coordinates [Coordinate_Source]
In this field please specify the source of the celestial coordinates that you list for each target. Most faint targets will use "Other_Source." Valid entries are: Guide_Star_Catalog To be used if the source is the HST Guide Star Catalog. Include the Plate ID (from the "Plt" column in the GSC) with your coordinates. Note: If the Plt value is 56, then the true source is the Hipparcos Input Catalogue, which should be listed (see below, and please note that Plate ID should not be specified).


46

Chapter 3: Fixed and Generic Targets [Generic _Targets]

GSC_Survey_Plate To be used if coordinates were measured from a Guide Star Catalog survey plate. Include the Plate ID with your coordinates, taking it from the PLATEID keyword in the FITS header. HST_Image To be used if coordinates were measured from an existing HST image. Include the Plate ID, which can be determined from the guide star IDs listed in the observation's Standard Header Packet. All HST observations have at least one guide star ID in the Standard Header Packet (SHP). SHP data are in the _jif.fits file for WFPC2 observations, or in the .spt file for STIS data. The guide stars that were used during any pointing of HST will be recorded in the SHP as character strings associated with specific header keywords. The primary, or dominant, guide star is given by the GSD_ID keyword, while SGESTAR lists the secondary, or sub-dominant, guide star. The guide star ID is a concatenation of the star number, the region number (from the Guide Star Catalog), and the particular FGS used in the pointing. For example, "0123406789F2" means guide star 01234 06789 was used with FGS2. To find the Plate ID, go to the GSC web site:
http://www-gsss.stsci.edu/support/phase2.html

The form will prompt you for the guide star ID (in two fields); you should use only the primary guide star. You should then be given the coordinates, estimated magnitude, associated errors, flags internal to the catalog structure, and the PLATE-ID. For most guide stars there will be multiple entries (and multiple PLATE-IDs because the fields of the plates overlapped. The first line of the output lists the primary plate, and this is the one you should list. If the observation used only a single guide star then it is possible that a a secondary plate was used; contact your Contact Scientist. Image_Tied_To_GSC_Frame To be used if you measured several visible stars on a Guide Star Catalog survey plate and then used them to determine pseudo-GSC coordinates for a target imaged with another telescope. Include the Plate ID (from the PLATEID keyword in the FITS header) with your coordinates.


Radial Velocity or Redshift [RV_or_Z]

47

PPM_Star_Catalogue To be used if coordinates are from the PPM (Catalog of Positions and Proper Motions). Hipparcos_Input_Catalogue To be used if coordinates are from the Hipparcos Input Catalogue, or, equivalently, they are from the Guide Star Catalog and the "Plt" column lists "56" (in this instance please do not specify plate ID). Because of systematic differences in coordinates, we urge you not to use the HIC as a coordinate source; the Hipparcos/Tycho Catalogue should be used instead. Hipparcos/Tycho_Catalogue To be used if the coordinates are from the Hipparcos/Tycho missions. Note that coordinates from the Hipparcos/Tycho_Catalogue have equinox J2000 but epoch 1991.25. This earlier epoch means that it is important to provide a proper motion for your target if it is at all significant. In some cases the Catalogue of Positions and Proper Motions (PPM) may be a better source for proper motions because of its longer time baseline. Other_Source: To be used if none of the above apply to your coordinates. You must include a short description of where the coordinates are from, for example: Coordinate_Source: Other_Source: HDF Catalog (Williams et al. 1996, AJ, 112, 1335) The explanation cannot be very long, and so we recommend an entry like "Coordinate_Source: Other_Source: See comment" if you need more space.

Radial Velocity or Redshift [RV_or_Z]
Give, if known, the heliocentric radial velocity or redshift of the target. The format is V = or Z = ; examples are V = +1198 and Z = 1.95. The units must not be specified.


48

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Is Proper Motion or Parallax Relevant?
If a small aperture or occulting spot is to be used, even a relatively small proper motion or parallax may cause difficulties in acquiring the target. In such cases, the Proper Motion/Parallax data must be provided. Note, however, that proper motion and parallax values may not be specified for a target which is specified by a positional offset. Such targets will be taken to have the same proper motion and parallax as the reference target. Offset targets have coordinates given with (RA­OFF, DEC­OFF), (ETA­OFF, XI­OFF), or (R, PA). The observer must determine whether or not proper motion or parallax is relevant. In general, this will depend on the size of the acquisition aperture of the SI that will be used and the epoch of the coordinates that have been provided. For example, the STIS uses a target acquisition area of 5 arcsec square. For a star whose coordinates are given for the epoch 1950, and that will be observed in 1997, a proper motion of approximately 0.5*2.5/(1997­1950) = 0.027 arcsec per year would be "relevant," with a resulting offset of half the minimum center-to-edge distance. If special plate catalogs are being used (see Special Catalogs on page 44), proper motions are probably not included (the HST Guide Star Catalog, for example, does not include proper motion). If the relative accuracy of the target and guide stars is essential, the proper motion should be included for the target star if the special catalog includes proper motions.

Proper Motion and Parallax Data
The following information is required for targets where proper motion and parallax are "relevant"; note that uncertainties for RA_PM, Dec_PM, and Annual_Parallax are not required. If a sign is not given for RA_PM or Dec_PM, a positive value will be assumed, but it is better to be explicit. · RA_PM: For Proper Motion in RA, the value should be in units of seconds of time/year. To convert from arcsec/year to seconds of time/year, divide by 15 cos DEC. · Dec_PM: For Proper Motion in DEC, the value should be in units of arcsec/year. · Epoch: The "Epoch of position" is the date of the "Target Position" which was defined in the Target List (see Target Position [Position] on page 34). · The "Epoch of position" may or may not be the same as the date of "Equinox for Coordinates" in the Target List (see Equinox for Coordinates [Equinox] on page 45). Remember that the "Epoch of posi-


Flux Data [Flux]

49

tion" is the date the target position is referred to, whereas the "Equinox of Coordinates" is the date of orientation of the coordinate system in which the position is measured. For example, a star with a large proper motion may have its coordinates given in the J2000 system, but the numbers themselves are for epoch 1984, meaning that the star was at the specified position on January 1, 1984. As with Equinox, Epoch should be of the form B19xx for years before 2000, and J20xx for 2000 and later. · Ordinarily the epoch of position is earlier than the present date. In the Guide Star Catalog (GSC), the equinox is J2000 while the epoch depends on the individual plate. Do not adjust your coordinates to be those that would be measured if the plate were taken in the year 2000. However, some catalogs contain coordinates already adjusted to an epoch of J2000: the Hipparcos Input Catalogue (often used in the GSC for stars brighter than m(V) ~= 9) and the PPM Star Catalog. When these catalogs are being used, it is appropriate to specify an epoch of J2000. (These remarks do not apply to the Hipparcos Output Catalog.) · Annual_Parallax: The unit for parallax is arcsec. The example below is for the object DM­9D697 (Epsilon Eridani), where the proper motion data are taken from the SAO Catalog.
RPS2 Keyword RA_PM: DEC_PM: Epoch: Annual_Parallax: Explanation Proper Motion in RA Proper Motion in DEC Epoch of Position Annual parallax Units sec/yr arcsec/yr Byyyy or Jyyyy arcsec Example ­0.0662 0.019 B1950 0.30488

For some notes on proper motions and units, see Getting Coordinates Coordinated on page 58.

Flux Data [Flux]
Flux information must be provided for all targets, and there can be more than one entry for a given target. All entries are values as observed at the Earth, rather than intrinsic values. STScI uses flux information to test for over-illumination of sensitive detectors. In particular, STIS proposals cannot be implemented without flux information for all targets and other sources in the fields of view


50

Chapter 3: Fixed and Generic Targets [Generic _Targets]

because of the critical requirements to protect its detectors from damage by excessively bright objects. The first flux information given should generally be a broad-band magnitude or surface brightness. For stars, the spectral type and color index should also be included (when possible). As many additional flux values as appropriate for the requested exposures should be provided. For example, ultraviolet or emission-line fluxes should be given if the target is to be observed in the ultraviolet or through a narrow-band filter, or several magnitudes might be provided if the target is a variable star to be observed at various brightness levels. In some cases (Targets of Opportunity, variable objects, etc.) the estimated flux data may be very uncertain, but the best available estimates should nevertheless be given, along with appropriate uncertainties and comments. It may be important to specify the flux of a background source as well as the target flux. For example, a globular cluster in M87 may be seen against the bright background of the galaxy. The keyword ­BKG should be appended to a background flux specification in this case (see footnote b to Table 3.13). Use a comma to separate entries if more than one flux value is given. Flux must be given as F(lambda) rather than F(nu). Recall that the conversion is:
F(lambda) = (3 x 10^18 F(nu)) / lambda^2,

where lambda is in ångstroms and F(nu) is in erg/(cm^2 sec Hz). For example, if lambda = 1500å, and F(nu) = 1.0 x 10^-26, then F(lambda) = 1.3 x 10^-14. The flux data are to be expressed in the format shown in Table 3.13. Do not enter explicit units.

General Guidelines on What Flux Data to Include
The following summary provides general guidelines for what flux information must be included in five general cases. See the Instrument Handbooks for more detailed descriptions of how to make the exposure time calculations. Point source, non-dispersive instrument
1. Target flux: V magnitude, (B­V), E(B­V), spectral type.

Flux at specified wavelength may be substituted for V magnitude. If no entry for E(B­V) is given, E(B­V) = 0 will be assumed.


Flux Data [Flux]

51

2. Background (optional): Broad-band surface brightness or surface

brightness at specified wavelength; ­BKG must be specified in the name of the flux parameter.
3. Flux in wavelength range of observation.

Extended source, non-dispersive instrument
1. Target flux: V surface brightness, (B­V), E(B­V).

Flux at specified wavelength may be substituted for V surface brightness. If no entry for E(B­V) is given, E(B­V) = 0 will be assumed.
2. Background (optional): Broad-band surface brightness or surface

brightness at specified wavelength; ­BKG must be specified in the name of the flux parameter.
3. Surface flux at wavelength of observation and size of the region spec-

ified. Point source, dispersive instrument
1. Target flux: V magnitude, (B­V), E(B­V), spectral type.

Flux at specified wavelength may be substituted for V magnitude. If no entry for E(B­V) is given, E(B­V) = 0 will be assumed.
2. Background (optional): Surface brightness of continuum; ­BKG

must be specified in the name of the flux parameter.
3. Continuum flux in wavelength range of observation. 4. Line flux and line width of brightest emission line in the wavelength

range of observation. Extended source, dispersive instrument
1. Target flux: V surface brightness, (B­V), E(B­V).

Flux at specified wavelength may be substituted for V surface brightness. If no entry for E(B­V) is given, E(B­V) = 0 will be assumed.
2. Background (optional): Surface brightness of continuum; ­BKG

must be specified in the name of the flux parameter.
3. Surface flux at wavelength of observation and size of the region spec-

ified.
4. Line surface flux and line width of brightest emission line in the

wavelength range of observation.


52

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Infrared source
1. Target flux: J magnitude, (J­K). Flux at specified wavelength may be

substituted for J magnitude.
2. Background (optional): Broad-band surface brightness at specified

wavelength; ­BKG must be specified in the name of the flux parameter.
3. Note that this refers to the astronomical background and not the ther-

mal background.
4. Flux in wavelength range of observation. Note that this must be in

units of erg/(cm^2 sec å). The NICMOS units conversion tool on the STScI WWW pages can help you convert your source flux from J magnitude or flux in Janskys into this flux unit.

Note: Details of how the above flux information was derived must be given in the proposal text section in the Observing_Description (see the Call for Proposals). If any of the required flux data cannot be provided or are deemed to be unnecessary, these points must also be explained in that section. Incomplete flux information may delay the implementation of your proposal, especially in the case of STIS observations.

Table 3.13: Formats for Specification of Target Flux Data
Parameter Examples for Stars: Broad-band magnitudea Spectral type Color Indexa Color Excess Background Surface Brightnessb V=13.1 +/­ 0.5 TYPE=G5III B-V = 0.86 +/­ 0.2 E(B-V) = 0.3 +/­ 0.2 SURF-BKG(B) = 20 +/­ 0.2 magnitude magnitude mag/arcsec2 magnitude Format example Units

Examples for Galaxies, Nebulae, and other extended sources: Surface Brightnessa,b Surface Brightnessa SURF(V) = 25.0 +/­ 1.0 SURF(B) = 24.5 +/- 0.5 mag/arcsec2 mag/arcsec2


Bright-Object Constraints

53

Parameter Color Excess

Format example E(B-V) = 2.5 +/­ 0.2

Units mag

Plus whatever other fluxes are relevant to your science program. Some other examples are listed below: Interstellar Extinction Flux at a specified wavelength Continuum Fluxc Line Fluxc,d,e Line Widthf Surface Brightness at specified wavelengthb Surface Brightness at continuum wavelengthb Surface Brightness of line emissionc,d,e Size (FWHM of circular region)g A(V) = 1.3 +/­ 0.1 F(5100) = 51 +/­ 3 E-15 F-CONT(3500) = 57 +/­ 3 E-15 F-LINE(3727) = 5 +/­ 1 E-14 W-LINE(3727) = 2.4 +/­ 0.2 SURF(5100) = 11 +/­ 2 E-15 SURF-CONT(5000) = 52 +/­ 2 E-15 SURF-LINE(5007) = 52 +/­ 2 E-15 SIZE = 25 +/­5 mag erg/(cm2 sec å) erg/(cm2 sec å) erg/(cm2 sec å) å erg/(cm2 sec å arcsec^2) erg/(cm2 sec å arcsec^2) erg/(cm2 sec arcsec^2) arcsec

a. The following broad-band magnitudes may be used: U,B,V,R,I,J,H,K. b. You may append "­BKG" to this reference (just before the wavelength designation) to indicate that it is a background flux value (e.g., SURF-BKG(V) = 18.2 +/­ 0.5; SURF-CONT-BKG(5100) = 10 +/­ 3 E-15). c. Give wavelength used in keyword in rest frame, but flux in observed frame. d. Line flux should be relative to the continuum, if specified, or relative to zero if not specified. e. Whenever the S/N refers to a spectral line, W-LINE must be given along with F-LINE or SURF-LINE. Values of F-LINE and SURF-LINE outside the Earth's atmosphere are required. f. W-LINE is the full width at half maximum (FWHM). g. SIZE should be included if the exposure time estimate assumed the flux was spread over an extended region; if omitted, the highest spatial resolution of the observing mode will be assumed.

Bright-Object Constraints
Several of the Scientific Instruments must be protected against over-illumination. Table 3.14 summarizes the safety restrictions by instrument. You should not propose observations which violate these guidelines. Non-linearity, saturation, or other temporary effects which may occur at substantially fainter limits than those identified below are described in the Instrument Handbooks.


54

Chapter 3: Fixed and Generic Targets [Generic _Targets] Table 3.14: Bright-Object Constraints
Instrument STIS Description The STIS MAMA (UV) detectors are subject to strict bright-object controls to prevent potentially fatal damage. Maximum permissible local and global count rates have been established for the STIS MAMA detectors, both for imaging and spectroscopy; see the STIS Instrument Handbook. These limits have been translated into extensive tables of magnitude and flux guides for the various configurations and modes; consult the STIS Instrument Handbook. Some of these limits are quite faint. All potential targets should be checked for safety with the STIS Exposure Time Calculator on the Web. Measured UV fluxes must be provided for any objects within 1 magnitude of the spectroscopic limits; if not previously available, they must be first observed with a safe STIS mode. Magnitudes and colors, or a UV image, must be provided for all objects in the fields of proposed PRISM and MAMA direct-imaging observations, including the background fields of solar-system targets. There are no safety-related brightness limits for the STIS CCD. See the STIS Instrument Handbook for a description of saturation levels, residual charge, and other effects. There are no safety-related brightness limits for the WFPC2. See the WFPC2 Instrument Handbook for a description of saturation levels, residual charge, etc. The FGS may not be used to view objects brighter than mV = 1.8. The FGS may view objects brighter than mV = 8.0 only if the neutral-density filter is in place.

WFPC2 FGS

Table 3.15: Bright-Object Constraints for NICMOS (Restricted)
Instrument NICMOS Description There are no safety-related brightness limits for the NICMOS. See the NICMOS Instrument Handbook for a description of saturation levels, residual charge, etc.

Comments [Comments]
Information that cannot be made to conform to the required formats may be entered in a "Comments" line. Comment lines are not interpreted by the software, but are maintained in the data base and do appear on printouts of the forms.


Generic Targets List [Generic_Targets]

55

Generic Targets List [Generic_Targets]
Generic targets are those that during Phase 2 can only be described in terms of astronomical characteristics or general location in the sky. This category is used only for Targets of Opportunity and parallel exposures. For parallel exposures, both pure-parallel and coordinated-parallel (see Chapter 6: Parallel Science Exposures on page 101), the pointing is determined by the primary observation, and the specification of a generic target for the parallel exposure denotes a region within which the parallel aperture is expected to point. If the parallel pointing does not matter and the intent is simply to sample whatever the parallel aperture happens to detect, it is not necessary to define a generic target; instead the special target ANY should be used (see Target Name [Target_Name] on page 93). Note: Generic Target region coordinates are assumed to be in the J2000 reference frame.

Target Number(s) [Target_Number]
Generic targets should be given individual names and numbers just like fixed targets; however, it is possible to enter a range of target numbers associated with a single target name. If a range is specified, the number of targets must reflect the number of separate fields that will be observed. For example, if WFPC2 observations of 10 different fields, all named QSO-SURVEY-FIELD, are required for a quasar search, the value of the Target_Number keyword would be 1­10.

Target Name [Target_Name]
A descriptive name must be provided. If a name cannot be specified in advance, a provisional name should be supplied. When the actual observation is made, a more specific name will be added to the target designation. Either the provisional name or the updated name can then be used for archival searches (e.g., SN might be the provisional name, while SN-1995D might be the updated name). A unique target name must be assigned to each generic target.

Target Description [Description]
See Target Description [Description] on page 29.


56

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Flux Data [Flux]
See Flux Data [Flux] on page 49. Flux data are not required for pure parallel observations of generic targets.

Comments [Comments]
See Comments [Comments] on page 54.

Generic Target Specifications
A way to specify generic celestial regions and target lists in a machine-readable fashion is described below, and should be used for the Generic Targets List. It is important that these instructions be followed in order for pure parallels with generic targets to be schedulable. Two types of generic target specifications are permitted: · Region generic targets: a celestial region specified in one of three coordinate systems · Target Lists: lists of fixed or generic targets The Selection Criteria column should use the syntax specified below whenever the selection criteria can be fully specified by a celestial region in one of the supported coordinate systems, or by a list of fixed or generic targets. In all other cases a text description should continue to be provided after the "Other:" header. Region Generic Targets Three coordinate systems are supported: · Equatorial: right ascension (RA) and declination (DEC) · Galactic: Galactic longitude (LII) and Galactic latitude (BII) · Ecliptic: ecliptic longitude (LAMBDA) and ecliptic latitude (BETA) Regions may be any of:
1. "Rectangular" regions, i.e. bounded by latitude and longitude limits

in the appropriate coordinate system
2. Circular regions, specified as within some angular limit of a point

specified in any of the three supported coordinate systems
3. Polar caps or equatorial bands in any supported coordinate system


Generic Targets List [Generic_Targets]

57

The following table provides examples of each of these types of region specifications. Note that the same rules for specifying RA and Dec apply as for fixed targets (See "Equatorial Coordinates" on page 36.)

Region type rectangular

Equatorial coordinates RA = 5H 30M 0S +/180M, DEC = -65D +/- 10D

Galactic coordinates LII = 45D+/-10D, BII = 15D+/-10D LII = 0D, BII = 15D, R=5D BII < -30D ABS_BII > 30D ABS_BII < 30D

Ecliptic coordinates LAMBDA = 56D+/-5D, BETA = 60D+/-15D LAMBDA = 45D, BETA = -15D, R = 5.5D BETA > 10D ABS_BETA > 10D ABS_BETA < 45D

circular

RA = 1H 30M 0S, DEC = -15D, R=10D

polar cap both polar caps equatorial band

DEC > 60D ABS_DEC > 60D ABS_DEC < 10D

Note that for rectangular and circular regions, the syntax is identical to that of fixed target regions except that the indicator REGION is omitted, and galactic and ecliptic coordinates are allowed. Target Lists In some cases it may be desirable to specify as a Generic Target any of a list of Fixed Target positions or Generic Target regions. In this case the fixed targets should be provided as usual on the Fixed Target List, and the generic target regions should be specified as above on the Generic Target List. Then a new generic target can be defined with Selection Criteria specified by: TARGETS = This will be taken to indicate that any of the targets in are suitable as targets. Note that target numbers are required to be unique across all targets in a proposal, whether on the Fixed, Generic, or Solar System Target Lists. This type of target is particularly useful when a known list of objects of interest is available, and it is desired to observe one of these objects with an imaging SI when a primary exposure with a spectrograph is positioned appropriately nearby.


58

Chapter 3: Fixed and Generic Targets [Generic _Targets]

Getting Coordinates Coordinated
Observers are responsible for the accuracy and appropriateness of the coordinates they supply and any changes made to them. Only you can determine where we should point HST. Equinox is always a critical quantity when specifying coordinates. All astronomical coordinates change with time because of the precession of the Earth's rotation axis. Equinox specifies a time to which a coordinate system is tied. Thus J2000 refers to the location of an object in celestial coordinates for the coordinate reference frame of January 1, 2000. Epoch is generally important only for objects that move. In particular, the epoch of a star's coordinates refers to a specific time at which the star is at that location. For example, the Hipparcos output catalogue lists coordinates of the brighter stars in the ICRS reference system (which is very nearly the same as J2000), and the coordinates themselves are for epoch 1991.25. The proper motions in the Hipparcos output catalogue are also epoch 1991.25, the midpoint of the mission. If you specify the epoch and equinox correctly, we can easily compute the location of an object at the time it will be observed with HST. (Note: An epoch is purely a time, and one of the form "J1991.25" is nonsensical.) Proper motions sometimes cause problems. Units are especially crucial. The proper motion in Right Ascension (RA_PM) is to be listed in sec/yr, meaning seconds of time per year. If you have a value for RA_PM in arcsec per year, you need to divide it by 15 (to convert from arcsec to time sec), and to then divide by cos because lines of constant RA converge in going to the poles. DEC_PM is almost always listed in arcsec/yr, which are the units needed for HST observing. As we have emphasized above, we urge to use signs on quantities, even when they are not required. A value of +0.060 for RA_PM, say, makes it clear that the sign has been considered. Just specifying 0.060 leaves ambiguity because sometimes observers forget a minus. One more thing: be very careful if your target lies near a celestial pole. Many precession routines break down in this regime, and uncertainties in position can cause problems too. Also, patterns that you may execute with an instrument could cross the pole, leading to confusion in position. All these issues can be resolved, but careful attention is needed.


CHAPTER 4:

Solar System Targets List [Solar_System_Targets]
For an explanation of this engineering-only version, see Special Note to Engineering Version Users in Chapter 1: About This Document on page 1-3.

In this chapter . . .
Target Number [Target_Number] Target Name [Target_Name] Target Description [Description] Target Position Target Position Level 1 [Level_1] Target Position Level 2 [Level_2] Target Position Level 3 [Level_3] Ephemeris Uncer tainty [Ephem_Uncer t] Acquisition Uncer tainty [Acq_Uncer t] Observing Windows [Window] Flux Data [Flux] Comments [Comments] Illustrations of Orbital Longitude Examples of Target List Blocks / / / / / / / / / / / / / / 61 62 64 65 66 68 75 75 75 76 82 84 84 85

59


60

Chapter 4: Solar System Targets List [Solar_System_Targets]

Tables and Figures
Table 4.1: Solar System Standard Targets Table 4.2: Target Description Keywords Table 4.3: Positional Parameters for TYPE = COMET Table 4.4: Positional Parameters for TYPE = ASTEROID Table 4.5: Parameters for TYPE = PGRAPHIC Table 4.6: Parameters for TYPE = POS_ANGLE Table 4.7: Parameters for TYPE = MAGNETO Table 4.8: Parameters for TYPE = TORUS Table 4.9: Parameters for TYPE = SAT Table 4.10: Parameters for TYPE = PCENTRIC (Available but Unsupported) Table 4.11: Keywords for Observing Windows Table 4.12: Operators for Observing Windows Table 4.13: Formats for Specification of Target Flux Data Figure 4.1: Orbital Longitude for Satellites / 84 Figure 4.2: Orbital Longitude for Planets / 85 HST is able to point at and track solar system targets with sub-arcsecond accuracy. In order for target acquisition and tracking to succeed, planetary observers must specify positions for their targets in a precise and unambiguous manner. Therefore, it is imperative that the Solar System Target List (SSTL) be carefully and correctly completed. This section explains how to fill out the SSTL for any solar system target. Ephemerides are generated using fundamental ephemeris information from NASA's Jet Propulsion Laboratory (JPL). Ephemerides can be generated for all known types of solar system targets, including planets, satellites, comets, asteroids, surface features on planets and satellites, and offset positions with respect to the centers of all the above bodies. The following instructions demonstrate how to define solar system targets in a way that allows accurate ephemeris generation. The body-axes definitions, body dimensions, directions of rotation poles, rotation rates, and the definitions of cartographic coordinates used by STScI are normally identical to the values adopted in the report of the "IAU Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 1982" (Davies, M.E., et al., Celestial Mechanics, 29, 309-321, 1983). In a few instances, the latter data have been updated due to new results obtained from the flyby spacecraft.


Target Number [Target_Number]

61

Also, some new bodies have been added which were unknown at the time of the IAU report. For Jupiter and Saturn, the lambda(III) coordinate system is assumed, but lambda(I) or lambda(II) can be used. For Uranus and Neptune, coordinates follow the "Report of the IAU/IAG/COSPAR Working Group on Cartographic Coordinates and Rotation Rates of the Planets and Satellites" (Celestial Mechanics and Dynamic Astronomy, 46, 197, 1989). If you need further information on these, please contact your Program Coordinator. One exception exists to the requirements outlined above. Observers for solar system Targets of Opportunity (e.g. a "new" comet or asteroid, a solar-wind disturbance reaching the Jovian magnetosphere, etc.), should complete the Generic Target List (See "Generic Targets List [Generic_Targets]" in Chapter 3.) and the Visit and Exposure Specifications (to the extent possible) in time for the Phase 2 deadline. If and when a suitable target appears, the proposer must complete the Solar System Target List and update the Visit and Exposure Specifications. No target can be observed until the complete Phase 2 information is provided. In this chapter, each heading has a description followed by a keyword in square brackets (e.g., Target Number [Target_Number]). The keyword must be used in your RPS2 form. Elsewhere, items in boldface (e.g., RA-OFF) show words or phrases to be used directly as RPS2 entries. Items in brackets (e.g., ) show entries you are to provide. Parameters listed in square brackets (e.g., [A1 = ]) are optional, whereas those not in square brackets are required.

Target Number [Target_Number]
Each target that will be observed must be assigned a unique target number. Target numbers must be positive, monotonically increasing (but not necessarily consecutive) integers. A different target should be defined whenever a different target position or timing description is required. For example, separate targets should be defined if you plan to take spectra of several different surface features on a planet, or if you plan to observe the same feature with different timing constraints. If more than one type of Target List is used (if your program also requires filling out the Fixed Target List or the Generic Target List), the target numbers should continue consecutively from one list to the next. All target numbers within a proposal must be unique.


62

Chapter 4: Solar System Targets List [Solar_System_Targets]

Target Name [Target_Name]
The name is used to identify a target; all target names within a proposal must be unique. The target name can be selected from the STScI list of standard targets (see Table 4.1; explanations of "Level 1" and "Level 2" are given below), or a name can be defined by the GO. The use of standard names is encouraged whenever it is possible. The following conventions should be followed in naming targets: · The maximum allowable length of a target name is 31 characters. · No blanks are permitted in target names. A hyphen should replace blanks that would normally be used to separate fields (e.g. IO-TORUS, COMET-BRADFIELD-1979X). · Only letters and numerals are allowed in target names; punctuation (other than hyphens and + or ­) is not permitted. · Target names must begin with a letter, not a numeral. · Construct target names so they make sense for your observing program. For example, if your program consisted of consecutive observations of three surface features on Mars, then three appropriate target names might be: MARS-FEATURE1, MARS-FEATURE2, and MARS-FEATURE3.

Do not use just a standard name for a target when a specific portion of a body is being observed. For example, do not use "Saturn" as the target name for a feature or specific location that is defined relative to the position of Saturn as a standard body because this is confusing for the software that computes the positions of moving targets.


Target Name [Target_Name] Table 4.1: Solar System Standard Targets
Level 1 Sun Mercury Venus Earth Mars Jupiter Moon Phobos Io Callisto Elara Lysithea Leda Metis (1979J3) Saturn Mimas Dione Hyperion Janus (1980S1) Telesto (1980S13) Prometheus (1980S27) Uranus Ariel Oberon Ophelia (1986U8) Desdemona (1986U6) Rosalind (1986U4) Neptune Triton Thalassa Larissa Pluto Charon Enceladus Rhea Iapetus Epimetheus (1980S3) Calypso (1980S25) Pandora (1980S26) Umbriel Miranda Bianca (1986U9) Juliet (1986U2) Belinda (1986U5) Nereid Despina Proteus Tethys Titan Phoebe Helene (1980S6) Atlas (1980S28) Pan Titania Cordelia (1986U7) Cressida (1986U3) Portia (1986U1) Puck (1985U1) Naiad Galatea Deimos Europa Amalthea Pasiphae Carme Thebe (1979J2) Ganymede Himalia Sinope Ananke Adrastea (1979J1) Level 2

63

If you are uncertain whether or not your target can be referenced by name, contact your Program Coordinator for guidance.


64

Chapter 4: Solar System Targets List [Solar_System_Targets]

Alternate names are given in parentheses for some bodies but these should not be listed in the RPS2 file. They are given here for identification purposes only.

Target Description [Description]
The target description is used to sort the solar system targets by class and will be useful to archival researchers. The first word in any target description must be one of the keywords listed below. The keyword is then followed with text that depends on the target class as described below.
Table 4.2: Target Description Keywords
Keyword PLANET SATELLITE Description If the target is the center of a planet, enter PLANET followed by the name of the planet (e.g., PLANET JUPITER, PLANET SATURN). If the target is the center of the satellite of a planet, enter SATELLITE followed by the satellite name (e.g., SATELLITE GANYMEDE, SATELLITE 1980S27) If the target is the nucleus of a comet, enter COMET followed by its common name or catalog designation (e.g., COMET HALLEY, COMET 1979X) If the target is the center of an asteroid, enter ASTEROID followed by its common name or its catalog number (e.g., ASTEROID CERES, ASTEROID 452) If the target is a surface feature, enter FEATURE followed by the name of the parent body (e.g., FEATURE JUPITER, FEATURE IO) If the target is an offset position with respect to a solar system body (but not a feature on its surface), enter OFFSET followed by the name of the parent (reference) object (e.g., OFFSET COMET HALLEY, OFFSET JUPITER) If the target is in a ring, enter RING followed by the name of the parent object (e.g., RING JUPITER, RING SATURN) If the target is a plasma torus, enter TORUS followed by the name of the parent object (e.g., TORUS JUPITER) If your target cannot be classified under any of the categories above, then enter OTHER followed by some description of the type of observation planned (e.g., ASTROMETRIC REFERENCE, INTERPLANETARY MEDIUM, ZODIACAL LIGHT)

COMET

ASTEROID

FEATURE OFFSET

RING TORUS OTHER


Target Position

65

Target Position
Target pointing Specification (TPS) and "Levels" Three fields are used to describe the target's position, referred to here as the Target Pointing Specification (TPS). The TPS has been defined using a hierarchical structure. · Level 1 refers to a target in orbit about the Sun. Examples of Level 1 targets include planets, asteroids, and comets. When a Level 1 object is the desired target for observation, complete the Level 1 field and leave the other two target position fields blank. · Level 2 refers to a target whose motion is normally described with respect to a Level 1 object. Examples of Level 2 targets include planetary satellites, surface features on planets or asteroids, and non-nuclear positions in the coma of a comet. When a Level 2 object is the desired target for observations, the Level 1 field contains information on the parent body, and the Level 2 field gives positions relative to this body. In this case, leave the Level 3 field blank. · Level 3 refers to a target whose motion is normally described with respect to a Level 2 object. Examples are a surface feature on a planetary satellite or a pointing which is offset from the center of a planetary satellite. When a Level 3 object is the desired target for observation, then all three fields must be completed, with Level 1 giving the parent of the body described in Level 2, and Level 3 giving the position of the observed target with respect to the body in Level 2.

No more than three levels are allowed. If you believe that your target cannot be described in this form, contact your Program Coordinator.

Describing Targets The targets specified in the target position fields can be described in up to four ways: · By a name selected from a list of targets · By orbital elements · By coordinates with respect to another object · Via target selection during a real-time observing session


66

Chapter 4: Solar System Targets List [Solar_System_Targets]

Table 4.1 gives the list of valid names for solar system targets. PIs are responsible for obtaining up-to-date orbital elements for bodies not in this table. Objects must be denoted by their IAU-adopted name. A good reference for object names can be found in the Astronomical Almanac, and in the Marsden comet catalog (Marsden, B. G., Catalog of Cometary Orbits, Enslow Publishers, Hillside, NJ, 1983). If you are uncertain whether or not your target can be referenced by name, contact your Program Coordinator. In those cases where the target's position is given with respect to one of the standard objects, the latest available data from JPL on the bodies' physical dimensions, orientation, and rotation rates are used in calculating the target's position. In those cases where all or part of the TPS for your target can be described using standard names, we strongly recommend that you do so. Generally, this will result in the most accurate ephemeris generation for your target. Specifying Time Whenever there is an entry involving "time" (anywhere on the form), the format for that entry must be: DD-MMM-YYYY:hh:mm:ss.s, where DD is the day of the month, MMM is the first three letters of the month name, YYYY are the full four digits of the Gregorian calendar year, hh is the hour, mm is the minute, and ss.s are the decimal seconds. Only the necessary precision need be specified. Examples: 02-AUG-1993:13:04:31 15-JAN-1994 Two different systems of time are used in this document. TDB refers to Barycentric Dynamical Time and can be considered synonymous with ET (Ephemeris Time), which was used before 1984. UTC refers to Coordinated Universal Time. The precise interpretation of each time value depends on the context in which it is used.

Target Position Level 1 [Level_1]
Specify your target in one of the following ways:
1. STD =