Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

January 2024:   For more information on MAST Drizzled data productsHubble Advanced Products (HAP), please see the following resources.

...

On April 26, 2022, the HST data calibration and archive pipelines began producing a new Hubble Advanced Product (HAP) to be distributed through MAST. These are cross-visit, cross-proposal mosaics called Multi-Visit Mosaics (MVM), which combine public observations of fields observed multiple times by ACS and WFC3 into a set of products drizzled onto a common, pre-defined pixel grid. These new products were described in a MAST Newsletter article from May 2022 and complement the existing HAP Single Visit Mosaics (SVM) released in December 2020.

Usage 

Images downloaded from the archive after reprocessing with the new Enhanced Pipeline Products code will have headerlets added as extra extensions to the FITS file. A new python notebook, 'Using updated astrometry solutions', will familiarize users with the structure of the new FITS images and demonstrate how the primary WCS may be changed to any other preferred solution. These instructions will also show how to back out the new WCS updates entirely if desired (see the section below on 'Caveats').

Alternatively, any of the new WCS solutions may be downloaded from MAST/STScI as separate headerlet files and applied to existing data. For users who wish to manually reprocess existing data, the 'updatewcs' task in the STWCS package as used by the Enhanced Pipeline Products code will be able to automatically connect to the astrometry database to retrieve and apply the headerlets. Python functions for creating, updating, and applying headerlets to FITS images are described via the Headerlet User Interface.

Guide Star Catalogs

Historically, the accuracy of HST absolute astrometry has been limited primarily by uncertainties in the celestial coordinates of the guide stars as specified in the Guide Star Catalog. GSC 1.1 had nominal rms errors of ~0.5 arcsec per coordinate, with errors as large as ~1‐3 arcsec reported near the plate edges. This accuracy improved substantially in October 2005 (during Cycle 15) with the introduction of GSC 2.3.2, where rms errors per coordinate were reduced to ~0.3 arcsec over the whole sky.  An updated version of the catalog (GSC 2.4.0) was released in October 2017, improving the celestial coordinates with the positions from Gaia DR1 and reducing errors to < 30mas over the entire sky. After including uncertainties in the positions of the science instruments (SIs) in the alignment of the focal plane to the Fine Guidance Sensors (FGS), the total error in HST absolute astrometry is ~1 arcsec for observations made with GSC 1.1, ~0.3 arcsec for those with GSC 2.3.2, and ~0.2 arcsec for those with GSC 2.4.0. These errors are reduced to ~10 mas for observations with a posteriori alignment to Gaia. A summary of pointing errors over the HST lifetime and the expected accuracy of the updated WCS solutions is provided in Table 1. 

...

Catalog

Release Date

Mean Epoch of catalog positions

Typical errors

Worst errors

Total Error (including SI to FGS alignment)

Comment

GSC 2.4.0 + Gaia FitDec 20192015.50.01"
0.01"WCSNAME=  'IDC*_FIT_*_GAIADR*'

GSC 2.4.0

Oct 2017

2015.0

0.03”


~0.2”

GSC2.3.4 aligned to Gaia DR1    

Complete GSC Summary

WCSNAME=  'IDC*-GSC240',   'IDC*-HSC30'

GSC 2.3.3Oct 2009



WFC3 installed May 2009

GSC 2.3.2

Oct 2005

1992.5

0.3”

0.75”

~0.3”

Public Release

GSC 1.1 and GSC 2.3.2 Comparison

GSC 2.2.0

Jun 2001





Public Release

ACS installed Mar 2002

GSC 2.0

Jan 2000





Science target fields only; GSC2 summary

GSC 1.1

Aug 1992

1981.8

0.5”

~1”

~1”

First version published for the user community

Used by HST operations prior to Cycle 15

WFPC2 installed Dec 1993

GSC 1.0

Jun 1989



1-2”


 GSC1 summary

HST Astrometry Project

The coordinates populated in the FITS headers of HST observations retrieved from DADS (the HST Data Archiving and Distribution Service) were derived based on the guide star coordinates in use at the time of the observation. As the accuracy in these catalogs were refined over time, the pointing accuracy of HST has also improved. Table 1 lists the catalog in use at the time of installation of the three main imaging cameras (WFPC2, ACS, and WFC3) and the typical errors at each epoch.

...

Note that a priori corrections are only relevant for observations which executed prior October 2017 (eg. prior to the release of GSC 2.4.0), and these will still include small errors in the alignment of the science instruments to the HST focal plane. The a posteriori corrections are limited to imaging instruments for which there are an adequate number sources to define a reference catalog for matching. These solutions remove uncertainties in the focal plane and are expected to have the smallest absolute astrometric error.

Implementation

The key to implementing improvements to the astrometry is the use of headerlets, self-contained FITS extensions containing a WCS transformation which can be attached to a FITS file and applied to the primary WCS. An observation can have multiple headerlets, each of which may have astrometry derived by differing methods. As HST data is processed/reprocessed, all available headerlets will be present as FITS extensions in the archived image with the best solution applied to the primary WCS.  More details on how the WCS information is stored in headerlets may be found on the page Astrometry in Drizzled Products.

WCS Naming Conventions

Successfully aligning an observation to Gaia using the a posteriori processing will result in an update of the 'active' WCS of the image with the new solution and the new headerlet extension. This headerlet not only includes the WCS keywords which define the transformation from pixels to Gaia-aligned positions on the sky, but it also contains information about how this solution was derived along with the errors to be expected based on the fit. 

...

WCSNAME

WCSTYPE

Comment

OPUS

‘distorted not aligned’

No distortion correction has been applied; analysis of these FLT/FLC files may only be performed if corrected by the instrument-specific pixel area map

IDC_0461802ej

‘undistorted not aligned'                                                                   

Distortion-corrected using the IDCTAB reference file '0461802ej_idc.fits', but not aligned to an external catalog

IDC_0461802ej-GSC240

‘undistorted a priori solution based on GSC240'

Alignment based on Guide Star Catalog v2.4.0 (GSC240).  Absolute errors ~0.1"

IDC_0461802ej-HSC30

‘undistorted a priori solution based on HSC30’

Alignment based on Hubble Source Catalog v3.0.  HSC30 errors are typically smaller than GSC240. If both corrections are available, HSC takes precedence.

IDC_0461802ej-FIT_REL_catalog

‘undistorted a posteriori solution relatively aligned to catalog’

Exposures aligned to one another, and then aligned as a set to the reference  catalog

IDC_0461802ej-FIT_REL_NONE

‘undistorted a posteriori solution relatively aligned to NONE’

Exposures relatively aligned to one another, but the quality of the fit to an absolute reference catalog is unverified and should be checked by the user

IDC_0461802ej-FIT_IMG_catalog

‘undistorted a posteriori solution aligned image-by-image to catalog’

Exposures individually aligned to the reference catalog (not as a set)

IDC_0461802ej-FIT_IMG_NONE

‘undistorted a posteriori solution aligned image-by-image to NONE’

Exposures individually aligned to a reference catalog, but the quality of the fit is unverified and should be checked by the user
IDC_0461802ej-FIT_SVM_catalog‘undistorted a posteriori solution relatively aligned filter-by-filter to catalog*’**NEW** Exposures aligned to a reference catalog and include improved relative alignment across filters in a visit

Caveats

While the majority of calibrated HST data products are now aligned to a common absolute reference frame, further improvements may be possible via manual realignment using the drizzlepac tools.  This is particularly true for exposures acquired in the same visit where the WCSNAMEs does not contain the string 'FIT_SVM_GAIA'.  For standard drizzled data products:

...