Aa|PHH $ d    dFootnote TableFootnote**. . / -   \\TOCHeading  R6 D      !  "  #  $  %  &  '  (  )  *  +  ,  -  .  /  0  1  2  3  4  5  6  7  8  9  :  ;  <  =  >  ?  @  A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q   5 SBgotolink Intro_lnk  Bgotolink AppDoc_lnkĨ  Xgotolink Over_lnk !/gotolink GEIS_lnk0 "gotolink Format_lnk( #pegotolink Naming_lnke 3 $ gotolink FOC_chap %Pgotolink FOC_chap &gotolink FOC_Files 'gotolink FOC_steps (gotolink FOC_grp )openlink FOC.book:FOC_SCI *openlink FOC.book:FOC_UDL +openlink FOC.book:FOC_SHPt ,gotolink FOS_chap - gotolink FOS_chap .gotolink FOS_Files /gotolink FOS_steps 0openlink FOS.book:FOS_SCI 16openlink FOS.book:FOS_IMG 2! openlink FOS.book:FOS_SHL 3openlink FOS.book:FOS_STL 4* openlink FOS.book:FOS_UDL 5openlink FOS.book:FOS_SHP 63 gotolink HRS_chap 7gotolink HRS_chap 8: gotolink HRS_Files 9gotolink HRS_steps :A openlink HRS.book:HRS_SCI ;openlink HRS.book:HRS_UDL <J openlink HRS.book:HRS_SHP =gotolink HSP_chap >gotolink HSP_chapB ?oligotolink HSP_Files @oliopenlink HSP.book:HSP_SCIo Ak Oopenlink HSP.book:HSP_UDLG Bnk0openlink HSP.book:HSP_SHPn C #gotolink WFPC_chap De 3gotolink WFPC_chap Eapgotolink WFPC_FilesC_c F &gotolink WFPC_stepsles Ggotolink WFPC_qual Hopenlink WFPC.book:WFP_SCI Inliopenlink WFPC.book:WFP_EXT Jnliopenlink WFPC.book:WFP_SHP Knligotolink FGS_chapt Lnewlink Intro_lnk M newlink Over_lnkp Nnewlink GEIS_lnkes Onewlink WFPC_chaps Pnewlink WFPC_Files QCInewlink WFPC_stepsok: previouslink!S_<$lastpagenum> F<$monthname> <$daynum>, <$year>b"<$monthnum>/<$daynum>/<$shortyear>S_;<$monthname> <$daynum>, <$year> <$hour>:<$minute00> <$ampm>"<$monthnum>/<$daynum>/<$shortyear>_s<$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear>  <$fullfilename>_  <$filename>i  <$paratext[Title]>li  <$paratext[Heading]>  <$curpagenum>op  <$marker1>P_ <$marker2>li (Continued)Pagepage<$pagenum>nHeading & Page <$paratext> on page<$pagenum>apSee Heading & Page%See <$paratext> on page<$pagenum>.s Table & Page7Table<$paranumonly>, <$paratext>, on page<$pagenum>p+ (Sheet <$tblsheetnum> of <$tblsheetcount>)k wwPcptxxPnInyyPnezzP N{{QEAl||QeAn}}PP~~PFesQnAFQ:Ar55P KS_J$laK> FI$moI<$dJ$yeK"Im>/W/<$ aQJthnQynuQr> Q$miQ$amW" nW$da $Wyea W$mo >Wynu eW oWm>/ mWhor W iWe>_  Wena  W$pa TW>li Wate iW  uWnum  W$ma _W  rW oWed) WPa eWgen Wdin eW  Wge uW eW &  eWpar  Wge uW  We7 $Wumo <Wtex  W<$p pW+  Wshe oWbls nW W wWpt WxPn Wy eW W {WAl W|Qe S}TV~PFTVAFSVV5PVVVSVTVTVTVTthnVynuSr> V$miV$amV"SWT $VT$moVWT eVTm>/VWT VSe>_VWT  VT>liVWT iVTnumVWT _VSVWV TVgenTWV eTVgeTWV e T Vpar TW V u TVe7TWV <TV<$pTWV  TVblsTWV W WW WW WW WW W UuU.duw|dv}5H$ wxu H$ TUU` THz xwyu VHz "UU`T $H$ yxzu WH$ VUU` Hz zy{u Hz iVUU` VHH{z|u SHHen`V eHH|{u HHT` H$ }~v H$  TUU` THz ~}v WHz WUU` HH~5v HH` dH3K ^ H RH RFootnoteHqv? ^ HzHz Single LineH'FootnoteW   HvDf ^ HH Double LineH  V Double LineS eH   Single Line THZW TableFootnoteEGX-Rb ^ EPoEPo TableFootnotedHH HH(K `ICD_19 R, `Fo eL ` l `,PODPS to STSDAS Interface Control Document  ` hWIntroduction  hApplicable Documents  hfProcessing Overview  h$Generic Edited Information Sets ! hFile Format " lehNaming Conventions # `  hFaint Object Camera $ h Input Files % &h# Calibrated Data Files & Lin4h2 Processing Steps and Reference Files ' Bh- ASCII files of Group Parameters ( aPhX-! SCIENCE DATA HEADER ) o^hTa UNIQUE DATA HEADER * lh) STANDARD HEADER DATA HEADER + z` hFaint Object Spectrograph , h Input Files - h + Output Files from Calibration . erfhnt@ Processing Steps, Reference Files and Reference /  h! SCIENCE DATA HEADER 0 hPr IMAGE DATA HEADER 1 hEd! SCIENCE HEADER LINE 2 h F" SCIENCE TRAILER LINE 3 h# UNIQUE DATA HEADER 4 h) STANDARD HEADER DATA HEADER 5 `  "h!High Resolution Spectrograph 6 0h Input Files 7 t>hFi+ Output Files from Calibration 8 filLhte@ Processing Steps, Reference Files and Reference 9 Zh ! SCIENCE DATA HEADER : hh UNIQUE DATA HEADER ;  vh) STANDARD HEADER DATA HEADER < S` d  HH raHH -eshncHigh Speed Photometer = h Input Files > D$h# Calibrated Data Files ? 12h! SCIENCE DATA HEADER @ @h UNIQUE DATA HEADER A ENh) STANDARD HEADER DATA HEADER B \` jh D Wide Field Planetary Camera C  xh Input Files D rh+ Output Files from Calibration E h 2 Processing Steps and Reference Files F h & Data Quality File Values G h! SCIENCE DATA HEADER H Dh# EXTRACTED DATA HEADER I A Hh) STANDARD HEADER DATA HEADER J ` hFine Guidance Sensors K UT UThIntroduction L `ra Purpose ( ZThis Interface Control Document (ICD) provides a definition of the science data interface 4 Tbetween the Post Observation Data Processing System (PODPS) and the Space Telescope @@A 0Science Data Analysis Software (STSDAS) system. DAX`Scope hg ND]This ICD defines and controls the data format of all science files which are produced by the CsPRoutine Science Data Processing system at the Space Telescope Science Institute s @EV(ST~ScI). This explicitly includes the contents of the standard science data headers. UR UTh DProcessing Overview M  VSome understanding of the variety of data which are available to the scientist can be @Lgleaned from an overview of the processing which takes place at the ST~ScI.  FiUThe PODPS system is the portion of the Science Operations Ground System (SOGS) which uVis responsible for the automatic processing of science and engineering data generated Uduring an observing session. The PODPS system provides the software to automatically Ymanage the receipt, editing, calibration, and archiving of data from the Space Telescope X(ST). In addition, PODPS generates certain types of output products from the calibrated d Pdata. The Routine Science Data Processing (RSDP) portion of PODPS performs this st @automatic processing.  es\RSDP controls the routine processing of the data obtained as a result of the execution of a M$\proposal by the ST. A specification of the data that is expected is supplied by the Science 0glWPlanning and Scheduling System (SPSS) for use by RSDP. This is in the form of a subset <stNof the final Science Mission Schedule (SMS) as reflected in the SPSS proposal HesYmanagement database. Additionally, SPSS places predicted and definitive Orbit data state Tn Nvectors into the data base management system (DBMS) where RSDP can access it. `maOAdditionally, the Observation Support System (OSS) supplies RSDP with observer scolVcomments and updates to the final Science Mission Schedule. These updates are used in xTPODPS to determine if any of the flags and indicators which affect the selection of hidc HH e HHt / e[calibration reference files and parameters to be used for RSDP calibration have changed as d b@#a result of real time interaction. lin" r WBy the time Science Instrument (SI) Science data are received from the ST Data Capture e M.MSXFacility (DCF), RSDP has prepared itself to process the data which will actually arrive y,:ctVinstead of the data which was postulated to arrive. The RSDP Data Processing function FMSZedits the SI Science data to insert fill data to take the place of any missing data, then RRS^evaluates the data for acceptable quality. During this data evaluation phase the Data Quality ^@s Ifiles describing the validity of each item of science data are produced. dl afZOnce the SI Science data is accepted, the Data Processing function converts the data to a xQgeneric format. The RSDP Calibration function then processes it using a standard ae Xinstrument-specific calibration algorithm. It is important to note that the calibration  tWroutines are exactly the same as those provided in the STSDAS environment available to a a@hethe scientists at the ST~ScI. UT UTh (%Generic Edited Information Sets N s il[For any observation the product of the ST~ScIs pipeline is not a single data file, but an Thsi]entire set of files called the Generic Edited Information Set (GEIS). At a minimum, for each catZobservation, the RSDP produces a Standard Header Packet file, a Science Data file and its [corresponding Data Quality file. Engineering data and ancillary information is produced in areXthe Unique Data log file for each instrument except for the wide field/planetary camera thV(WF/PC). For that instrument, however, a similar Extracted Engineering Data file is  @ produced. $`caStandard Header Packet i3 haLMost data in the Standard Header Packet (SHP) are common across the various se?TS\instruments, although certain data in the SHP are specific only to certain instruments. The KEdUSHP contains telemetry data for engineering data as well as data used for spacecraft eW iWoperation. The telemetry values include information such as temperature, currents, and GencatUvoltages at various parts of the instrument. The spacecraft operation values include doadZinformation such as target name, position and velocity of the telescope, and positions of { dXreference objects such as the sun and moon. Instrument-specific information may also be fi@meMrecorded in the SHP, and is described in the individual instrument sections. F`, Unique Data Log  inXThe Unique Data log (UDL) files contain the command values for each instrument, such as etYexposure parameters, aperture commands, etc. Each instruments UDL file can also contain ru\observation-specific data. The contents, structure, and size of UDL files are different for coVeach of the different instruments, and are described in more detail in the individual atVinstrument sections. The WF/PC has an extracted data file which contains similiar @vo!observation specific parameters. r`afScience Data Files lu [Every instrument pipeline calibration produces a Science Data file containing the observed of  d]image stored as a GEIS file. Usually data are represented as single-precision floating-point )reVvalues, however the WF/PC images are usually represented as short integer values. The 5at^number of Science Data files, the size of these files, and the number of dimensions will vary A aYacross the instruments and across observing modes of an instrument; these variations are LM@ta@described in more detail in the individual instrument sections. se` oData Quality Files ent ZEvery Science Data file has an accompanying Data Quality file to identify bad data values ^in the science data. Data Quality files have the same size and dimensions as their associated difHH luHHel/li SZScience Data files. Good pixel values are always marked with a zero value. The Input Data e YQuality files use the value 1 to denote a Reed-Solomon data-check error and the value 16 F alZto denote a DCF or PODPS fill. The Output Data Quality files vary across the instruments; ,@esTthe variations are described in more detail in the individual instruments sections. umEUT UThse!Wide Field Planetary Camera O T ZDuring PODPS pipeline calibration, several GEIS format data sets are created for the Wide ` QVField Planetary Camera (WF/PC). They are: the Standard Header Packet, a Science Image lntVfile, and Science Image Data Quality file, an Extracted Engineering Data file, and an xim]Extracted Engineering Data Quality file. Each data file consists of an ASCII header file and ^a binary data file. All files from a given observation have the same root file name; the type @alWof information contained in each file is distinquished by its extension (see Table 1). es   dLCALWFP provides routine calibration in both SOGS/PODPS Routine Science Data toODJProcessing (RSDP) and IRAF/STSDAS. CALWFP performs a standard sequence of vaXprocessing steps on individual WF/PC camera observations designed to remove most of the ldUknown instrumental signature. CALWFP does the AtoD fixup, determines and removes the lse\global bias level, subtracts bias, preflash, dark, and superpurge frames (after appropriate e ck[scaling), and applies the flat field frame. The Calibrated Science Image Data Quality file cte f[flags all pixels flagged in the Science Image Data Quality file and all pixels found to be sisde[saturated, to have known bad pixels (static mask), and to have been flagged in the DQFs of thamZany of the calibration reference files used in the processing sequence. Histograms of the   T^input data, the data following AtoD correction, and the calibrated output data are generated. YOperation of this program is accomplished via keywords in the header of the input image. "@va3The output images of CALWFP are listed in Table~2. tio0 ovZThis task is specific to WF/PC data and requires a large number of keywords obtained from < rWthe WF/PC Science Image Header. The Science Image File and its associated Data Quality supHteVFile are always required, the Extracted Engineering Data File and its associated Data T@maLQuality File are required if the bias level subtraction option is selected. ScnUR UT`ua Input Files al`beStandard Header Packet sa no\The SHP contains telemetry values and spacecraft operation data. This file is not currently anWused by CALWFP but is part of the standard WF/PC dataset. The SHP files are identified ^in@ f)by the extensions .SHH and .SHD. d`enScience Image File   tTThe Science Image file contains the WF/PC image data with the readout from each CCD utSdetector in each group. Hence from 1 to 4 groups may be present. The header should ic reWconform to the standard WF/PC header format. Keywords in the header are used to select magnc\the various processing steps and to specify the names of the necessary reference files. The , neTScience Image file must be an unmodified short integer WF/PC image for the ATODCORR d suWand DOSATMAP (see below) steps to be meaningful. Science Image files are identified by St@et&the extensions .D0H and .D0D. 4`s Science Data Quality File . TC rrUThe Science Data Quality file (DQF) must consist of short integers and have the same OidTdimensions and number of groups as the Science Image file. Each pixel indicates the [ImZquality of the corresponding pixel in the Science Image file. Zero valued pixels indicate gacZgood pixels in the Science Image file and nonzero valued pixels flag various problems sldTor potential problems with their corresponding pixels (see below). The Science Data h@seDQuality file is identified by the extensions .Q0H and .Q0D. ifdenHH usHHge,he`!Extracted Engineering Data File o niXThe Extracted Engineering Data (EED) file contains the two engineering columns and, H#Vfor FULL mode, the 12 columns of overclocked pixels. It has the same number of groups /muXas the Science Image file. It is required when the BLEVCORR option is selected. The EED r ;@ci /A{CellBodyf?l  CellHeadingf@i FootnotefAT .HeadingDBodyfBR ceo TableFootnotefCT   TableTitleT:Table : $$ @D $ Subsection $$ @E $ SectionfF  CellHeading fG CellBodyfHT   TableTitleT:Table : fIR ceoBody@J  eT eHeader+>@K  Su cFooter$$@L $  eText$@M $He nBodyHH@N $ AList @P tleTitlea @QR ceoTitle$$ @S $  Section$$ @T $ SubsectionFo$@U $ Body$$@Ve $ TextHH@W $ TList L  zV@  lea  @ zV  TiEmphasis  @ Subscript   Superscript   zV _ ; Z@ =@ =@eujeThinfMediumgDoublehThick@i Very Thin eeeeeeeeegHHFGFHFGFHFGFLHFGFHFGFFormat A efeeeeefHHFGFHFGFHFGFHFGFHFGFiFormat B-=-.CommentsCourierTimes Helvetica Regular Regular BoldRegularItalic-2ޫ0vUz»FY"V B=G:ٸ?Y.Xuv>ĨpM| XScwzC%RX]AXP;/eJfYrO:T0~89ó#i3p- m3ɕ#(QSpeh/=Q