Preface
In the beginning was the Hubble Data Archive (HDA), which contained data from HST. Users searched the catalog, sometimes called the DADS catalog, using Starview, a software package developed at STScI. Data were retrieved through the Data Archiving and Distribution System (DADS) and written to tapes, which were mailed to the user. As networks developed and became robust, the demand for web-based search and retrieval grew. A web interface was first made available in 1994. A few years later, the Multimission Archive at STScI (MAST), funded under a separate contract, was created to host data from optical, UV and IR space-based missions. At about the same time, on the fly calibration (OTFC), later replaced by on the fly recalibration (OTFR), was developed for some HST data. At STScI a user could find data from many missions, some available for immediate download, some delayed by OTFR processing. Starview could be used to search for data from some missions, while the web interface, sometimes called MAST web, could be used to search all missions. Some complicated searches of the HST catalog, which Starview supports, are not supported by the web. The alphabet soup of acronyms continued to grow as more missions and tools were added to the archive. The distinction between HDA and MAST lessened except in funding.
In this document the holdings at STScI, whether archived and maintained under the Hubble contract or the MAST contract, are treated as one archive, called the archive, as that's what it looks like to an outside user. No distinction is made between datasets stored on spinning disk and those stored in archive appliances. Where it is important, the distinctions between HDA and MAST are delineated. For example, there are some differences when retrieving HST or FUSE data, and some acknowledgement distinctions are made, as required by the funding sources.
While this document was in revision, work on the Hubble Legacy Archive (HLA) began. As the HLA is under development, it will not be discussed in this version of the Archive Manual.
1. Introduction to the Archive
Archives are an important component of astronomical research programs. Indeed, the Hubble Space Telescope (HST) program regularly calls for proposals for funded archival research (by U.S. investigators using HST data) as part of the HST Call for Proposals. However, research utilizing any data in the archive does not have to be funded by the archival research program. The archive is available to any individual with the interest and hardware capabilities required to analyze data from any mission in the archive. Note: The archive is not a repository of pretty, heavily processed pictures; HST press releases can be downloaded from the Web site maintained by the Office for Public Outreach (OPO) at http://hubblesite.org.
1.1 Data in the Archive
As noted above, the archive primarily contains data from UV, optical and IR spaced based missions, some of which are still active (e.g.., HST and GALEX). A complete listing of the missions is available on the MAST web site, http://archive.stsci.edu/missions.html.
Table 1.1 lists the archive holdings as of November 2007. Data from the Kepler Mission, scheduled for launch in 2008, and the EPOCh (Extrasolar Planet Observation and Characterization) portion of the EPOXI mission will be part of the archive. See the EPOXI site, http://epoxi.astro.umd.edu/, for information on the mission.
Table 1.1: Archive Holdings
Mission | Instrument | Description |
ASTRO | | ASTRO Observatory |
ASTRO | HUT | Hopkins Ultraviolet Explorer |
ASTRO | UIT | Ultraviolet Imaging Telescope |
ASTRO | WUPPE | Wisconsin Ultraviolet Photo-Polarimeter Experiment |
Copernicus | - | Copernicus |
DSS | - | Digitized Sky Survey |
EUVE | - | Extreme Ultraviolet Explorer |
FUSE | - | Far Ultraviolet Spectragraphic Explorer |
GALEX | - | Galaxy Explorer |
GSC | - | Guide Star Catalogs |
HPOL | - | Halfwave Spectropolarimeter |
HST | - | Hubble Space Telescope |
IUE | - | International Ultraviolet Explorer |
ORFEUS | | Orbiting Retrievable Far and Extreme Ultraviolet Spectrometers-SPAS |
ORFEUS | BEFS | Berkeley Extrme and Far-UV Spectrometer |
ORFEUS | IMAPS | Interstellar Medium Absorption Profile Spectrograph |
ORFEUS | TUES | Tübingen Ultraviolet Echelle Spectrometer |
VLA-FIRST | - | Very Large Array - Faint Images of the Radio Sky at Twenty-cm |
XXM-OM | - | Xray Multi-Mirror Telescope - Optical Monitor data |
For HST and FUSE, the archive contains the calibration reference files, such as flat fields.
For HST, the archive contains engineering files (aka observation logs or jitter files) that may be useful for diagnosing some questions about observations, and the spacecraft ephemeris.
Retrieved data from all missions are primarily in FITS format.
The archive has searchable catalogs of the data, consisting of information about the observations and targets. For HST data, the catalog is populated from the header keywords of the data files and is quite extensive.
The archive also holds community contributed high level science products (HLSPs). These are fully processed images and spectra that are ready for scienctific analysis. A complete list is available at http://archive.stsci.edu/hlsp .
After a request is submitted, the archive system processes it. An e-mail notification is sent immediately when the system has accepted
the request and again when the system has completed processing the request, indicating whether or not the transfer was successful. The
messages will go to the e-mail address specified on the Retrieval Options page (for anonymous retrieval) or, if an STScI SSO account
was used, to the e-mail address associated with that STScI SSO account.
How long a retrieval takes depends on a variety of factors, including: the type of
data in the request, the size of the request, the number of requests in the system at the time, and the destination of the request (the internet connections between STScI and some sites, especially those overseas, is sometimes a significant source of delay). If everything is running smoothly, one should expect a median turn around time of an hour. If it takes more than one day, and you do not think any of the factors listed above are playing a significant role, please contact us at archive@stsci.edu.
If the data are retrieved to the staging disk (STAGE option), the data will be written to a subdirectory. Each data retrieval request will be in its own subdirectory,
identified by the request ID number, which will be included in the notification message you will receive. To find your data, from your home account type:
Note the use of binary in the above example. Not all ftp clients automatically set the data mode. Any attempt to ftp fits files in ASCII mode will result in corrupted data files, with no errors from ftp.
For anonymous retrievals, the current default, enter your e-mail address. The subdirectory will be /stage/anonymous/request_ID_number.
After locating your data on the archive host, transfer them across the Internet using FTP as described in a later section. Because the disk space available to each user within the data directory is limited, the files created for you are temporary and are deleted automatically after a few days. Please transfer your data promptly and delete your data from the staging area after the transfer has completed. When disk space is tight, we would appreciate notification that you have completed copying over your retrieved files so that we may delete them. (Send email to archive@stsci.edu.)
Table 1.3: File Access Commands for Archive Users
Sample Function
|
Unix Commands
|
---|
Retrieve HST data from the data directory as named in
the acknowledgement e-mail - in this case, "dir0129" (e.g., data retrieval was
requested using an STScI SSO Credentialed account)
|
%ftp archive.stsci.edu (or stdatu.stsci.edu) (login as "anonymous") ftp>
cd staging ftp> dir ftp> binary ftp> prompt ftp> mget x* ftp> bye
|
Retrieve PostScript and/or text versions of manual, abstracts, catalogs, general information.
Files that end in .gz can be uncompressed by using the command "gunzip". The uncompressed files
are also available.
|
ftp archive.stsci.edu
(login as "anonymous") ftp> cd pub/manuals (or pub/catalogs or pub/hdf etc.)
ftp> ascii1
ftp> ls
ftp> mget *.ps.Z (or whatever) ftp> bye
|
1
As appropriate. In the case of the Hubble Deep Field images, "binary" would be the appropriate datatype.
|