Space Telescope Science Institute
FGS Data Handbook
help@stsci.edu
Table of Contents Previous Next Index Print


Fine Guidance SensorData Handbook > Chapter 3: Calibration > 3.2 Initial Data Processing - calfgsa

3.2
The STSDAS task calfgsa (in hst_calib.calfgs) accomplishes several general tasks, regardless of whether the observations were gathered in Position Mode or Transfer Mode. The pipeline:
1.
2.
3.
4.
Determines the status of the guiding FGSs, checking whether zero, one, or two FGSs were actively maintaining the pointing of the telescope and whether they were guiding in CoarseTrack or FineLock.
5.
Inspects the flags/status bits to determine whether the astrometry observation succeeded or failed, and in the case of a failure, to identify the reason for the failure.
6.
Prepares output files with keywords whose values are either extracted from the input header files or computed from contents of the data files.
7.
Assesses the data quality of successful observations, masking outliers, ­garbled telemetry, and telemetry dropouts. (Outliers are data that do not appear to be garbled but make no sense when viewed in the context of neighboring data points.)
3.2.1
The data acquired during a Transfer Mode observation include the initial target acquisition sequence in addition to the individual target scans. (see the FGS Instrument Handbook for details on target acquisition). Processing Transfer Mode data with calfgsa is limited to locating each scan in the astrometer’s data file, editing out bad data (due to telemetry drop-outs, etc.), and determining the median position and standard deviations of guide star positions in the guiding FGSs during each Transfer Mode scan.
The pipeline generates three ASCII files for every scan, one for each FGS. Each file contains the 40 Hz raw star selector A and B encoder angles, used to derive the x- and y-position of the FGS’s Instantaneous Field of View (IFOV) at all times along the scan, and the photon counts per 25msec in each of the four photomultiplier tubes (PMTs). The guide star data, which spans the entire Transfer Mode observation, are provided for (optional) de-jittering of the astrometer’s IFOV during post-pipeline processing. Each of these files begins with a small header containing keywords whose values pertain globally to the observation or specifically to the scan, such as the observed filter or the universal time (UT) at the start of the scan. The HST state vector is also included in the header.
The calfgsa task does not carry out further processing of Transfer Mode data. This is most appropriately left to the programs and tasks discussed in Chapter 4.
An example of a session using calfgsa to process Transfer Mode data from the FGS calibration program 8834 (data set f6b00201m) is shown below. User input is highlighted as bold.
Reference directory (/data/phoenix4/testcalfgs/refdir/fgsa_ref/):<ret>
In this example, calfgsa outputs 45 files (3 FGSs x 15 scans), each containing the 40 Hz star selector angles and PMT photon counts from each FGS for a specific scan. These files will follow the naming convention rootname.isn, where "rootname" is the unique exposure ID (in this example, f6b00201m), i = 1,2,3 identifies the FGS, and n identifies the number of the Transfer Mode scan. Thus the file f6b00201m.1s13 contains data from FGS1 for scan #13.
An excerpt from a calfgsa output file for Transfer Mode data is shown below.
calfgsa also produces an ASCII file named "rootname.tab" (e.g., f6b00201m.tab) which contains information pertinent to the entire exposure, not just individual scans. An example of a (Position Mode) *.tab file is shown in Section 3.4.
3.2.2
Position Mode observations with the FGS are primarily used for wide angle (>10") astrometric studies, such as parallax determinations and/or the measurement of a star’s reflex motion in response to the gravitational influence from a bound companion. These programs employ an observing technique where the target star and several nearby reference stars (also in the FGS Field of View) are observed in a sequential fashion as many times as possible during the visibility period of HST’s orbit (see the FGS Instrument Handbook for more details about Position Mode observing). Typically, on the order of twenty individual exposures are obtained in a Position Mode visit.
Two pipeline processors, first calfgsa and then calfgsb, are used to process the Position Mode data. For each observation, calfgsa sequentially ingests the raw GEIS file and inspects the flags and status bits to determine if the observation was successful. If the observation succeeded, calfgsa extracts the 40 Hz star selector encoder angles and PMT counts, masks out bad data, and computes the median (x, y) centroid of each star in FGS detector-space during the FineLock/DataValid (FL/DV) interval (when the FGS was tracking the star’s interferometric fringes). The average PMT counts during the FL/DV interval are determined. The same quantities for the guiding FGSs are computed over the identical time interval.
The most convenient way to process a visits’s worth of data with calfgsa is to input a file which contains the rootnames of the exposures contained within the visit.
An example using calfgsa to process the Position Mode data from the FGS calibration program 8897 (monitoring the scale and distortions of the FGS1r Field of View) is given below. In this example, the exposures have rootnames f6iy0301m, f6iy0302m, f6iy0303m, ..., f6iy030zm, a total of 45 exposures. These rootnames are listed, one entry per line, in the user-generated file obs.list. User input is noted in bold.
cl> calfgs
te> calfgsa
While processing the data sets associated with each exposure, calfgsa produces the output *.tab files, such as f6iy0302m.tab. These contain the median (x, y) FGS detector-space centroid of the star's position in that exposure, along with other data needed for further processing by calfgsb. The content of f6iy0302m.tab is available as an example from the FGS Web site.
These contain the median (x, y) FGS detector-space centroid of the star’s position in that exposure, along with other data needed for further processing by calfgsb. As an example, the content of f6iy0302m.tab is shown in “calfgsa Output: The *.tab File”.

Table of Contents Previous Next Index Print