Galactic Legacy Infrared Mid-Plane Survey Experiment (GLIMPSE)

Scientific Motivation

The inner workings of our own Galaxy are more mysterious than those of galaxies located millions of parsecs away, mainly because of our unfavorable location in the mid-plane outskirts of a dusty disk. The Milky Way is a typical luminous spiral of the types seen to large distances. Understanding its structure and the fundamental processes and interactions between gas and stars within it would benefit all galactic and extragalactic research programs. A Space Infrared Telescope Facility (SIRTF) Galactic Plane survey will provide a comprehensive view of the entire stellar and dust content inner Galaxy. The broad scope of these data will provide a global understanding that narrowly confined selected regions cannot, and they will provide vital information regarding two basic scientific questions:

The first question involves the appearance of the inner Galaxy to an outside observer, vital for accurately comparing it to other galaxies. The second question involves the details of the star formation process by considering young, but heavily obscured, clusters which can be resolved spatially for the first time with SIRTF. Only the broad view of a survey can answer these global questions. In addition, there are many other interesting scientific problems that can be illuminated by the survey data.

Proposed Data Products

The Catalogs

Source catalogs are a fundamental tool to answer the scientific questions posed above. Consequently, the generation of such catalogs, for both point and extended sources, is

one of our primary post-pipeline products and will be the initial focus of our analysis efforts.

We will produce a series of catalogs with the final products containing astrometric, photometric and morphological parameters for all sources detected above the 5s level. The first product will be a Bright Source Catalog (BSC), with the limit set at approximately the 20s level. The release of the first BSC is timed to

be available for Guest Observer proposals, such as spectroscopic follow-ups. The GLIMPSE Source Catalog (GSC will be released in increments). Each release should reach the 5s level, but will be restricted to a limited range in galactic longitude. Updated versions of released catalogs will occur periodically (about every 2 months) in order to incorporate any improvements in the subtraction of various background sources: zodiacal light, diffuse galactic background, extended red emission, galaxies, and solar system bodies. In addition, updates will incorporate the re-processing of the Basic Calibrated Data products (by SIRTF Science Center — SSC) due to changes in SIRTF calibration pipeline.

Mosaicked Images

The ability to examine regions larger than an individual image can be crucial in addressing many science issues. The manner in which our survey will be produces images of adjacent fields which are likely to be rotated with respect to each other. The issue of geometric distortion must also be addressed. To aid in the analysis process, we will produce a series of mosaics at each observed wavelength that can be combined to generate images of a region of an arbitrarysize and location.

GLIMPSE Database (GLIMPSEdb)

The database will be implemented in Oracle 8i probably residing on a Sun Microsystems Ultra 80 (2x450 MHz) computer. The core database schema will be implemented in the first 6 months of the program. The basic schema will likely consist of separate tables for each wavelength and post-pipeline processing level (i.e., Level A, Level B, etc.). Such

a structure provides an efficient and natural way to import/export data, as well as to update and propagate changes in the state of the SIRTF and ancillary data. Refinements of the database structure will be modified and implemented in a modular way as the post-pipeline products and tools are developed. Revisions and modifications during Phase 1 will be executed on a separate ``development'' database. Changes to the database can be easily accomplished by using products like Rational Rose Enterprise Software coupled with Oracle's Enterprise Manager. All revisions will be implemented in a scheduled manner to avoid conflicts with other ongoing development tasks. Backups of the database will be executed on a regular time schedule in both cold (shutdown) and hot (in-service) modes, providing both long and short-term recovery of all transactions.

In addition to database transactions from incremental processing of the data (i.e., reprocessing of individual frames, source extraction), allowances in data entry must be made for the delivery of bulk data sets from. Such bulk data loads will be accomplished through a series of modularized scripts (implemented in Perl) that will include a wide selection of data integrity, validity, and constraint checking (e.g. Level A processing). Only the data that pass the initial integrity checks will be loaded into the database using the automated load processes.

 

Data Formats and Required Attributes

Image Types

FRAME: A single 256x256 image (plus metadata), associated with data obtained a specific time and a specific wavelength. A unique observation identification (FRAME_ID) will be assigned in Level A processing.

"Super-Mosaic": Sequence of FRAME-level data re-sampled onto a grid which represents the area targeted by the observational program: ~6 Gigapixels per mosaic

After Level A processing:

Table "LEVELA":

Attribute Name

Type

Description

FRAME_ID

VARCHAR2(50)

Unique identification for an observation made at a specific time and at a specific wavelength

GLIMPSE_ID

NUMBER(7)

Internal Incremental Counter such that MAX(GLIMPSE_ID) is the number of unique FRAME_ID which have been inserted previously in database (what about record deletions?).

AOR_ID

NUMBER(5)

AOR ID number which produced this FRAME_ID

CHANNEL_ID

NUMBER(2)

Instrument Channel Number

COMMAND_ID

NUMBER(5)

Command sequence number

REPEAT_ID

NUMBER(5)

Repeat Observation Counter

OBJECT

VARCHAR2(60)

Image field name

INSTRUME

VARCHAR2(10)

Name of instrument (IRAC,MIPS)

CAMERA

VARCHAR2(10)

Camera (i.e., wavelength for IRAC data)

DATE_OBS

DATE

Date of observation

TIME_OBS

DATE

Time of observations

EPHEM_NAME

VARCHAR2(60)

Ephemeris ID used in SIRTF pointing calculations

OBSRA

NUMBER(14)

Frame Right Ascension (degrees)

OBSDEC

NUMBER(14)

Frame Declination (degrees)

EPOCH

FLOAT

Epoch of Frame coordinates

ORIENTAT

FLOAT

Orientation of frame, East of North (degrees)

EXPTIME

FLOAT

Exposure time (seconds)

RAW_NAME

VARCHAR2(50)

Raw data (RAW) filename

RAW_IMG

BLOB

RAW image data

BCD_NAME

VARCHAR2(50)

Basic Calibrated Data (BCD) filename

BCD_IMG

BLOB

BCD image data

FLUXERR_NAME

VARCHAR2(50)

Flux error (FLUXERR) filename

FLUXERR_IMG

BLOB

FLUXERR image data

BCDDQF_NAME

VARCHAR2(50)

BCD Data Quality File (DQF) image filename

BCDDQF_IMG

BLOB

QUAL image data

BADPIX_NAME

VARCHAR2(50)

Bad pixel (BADPIX) image filename

BADPIX_IMG

BLOB

BADPIX image data

CR_NAME

VARCHAR2(50)

Cosmic Ray (CR) map filename

CR_IMG

BLOB

CR map image data

GHOST_NAME

VARCHAR2(50)

GHOST image filename

GHOST_IMG

BLOB

GHOST image data

LATIM_NAME

VARCHAR2(50)

Latent Image (LATIM) filename

LATIM_IMG

BLOB

LATIM image data

LATMASK_NAME

VARCHAR2(50)

Latent Image Mask (LATMASK) filename

LATMASK_IMG

BLOB

LATMASK datafile

BCD_CALVER

VARCHAR2(50)

BCD pipeline calibration version

FLAT_NAME

VARCHAR2(50)

Flatfield filename

FLATDQF_NAME

VARCHAR2(50)

Flatfield DQF filename

DARK_NAME

VARCHAR2(50)

Dark Current filename

DARKDQF_NAME

VARCHAR2(50)

Dark Current DQF filename

DATE_MODIFY

DATE

Date & Time of last modification

 

Information regarding images stored in "LEVELA":

Image Name

Bit-depth1

Description

RAW_IMG

16

Raw image

BCD_IMG

32

Basic Calibrated Data

FLUXERR_IMG

32

Flux error map

BCDDQF_IMG

16

BCD data quality mask

BADPIX_IMG

16

Badpixel mask

CR_IMG

16

Cosmic Ray mask

GHOST_IMG

32

Ghost image/crosstalk map

LATIM_IMG

32

Latent Image correction map

LATMASK_IMG

16

Latent image mask

1All images are 256x256 unless otherwise noted.

 

 

Calibration images are associated with FRAME_ID, but many frames will share the same files. Calibration data should be a separate GLIMPSEdb table

Table "CALFILE" (Images used to Produce BCD from RAW):

Image Name1

Bit-depth2

No. of Planes

Description

FLAT_ID

32

2

Flatfield calibration file

FLAT_ID_MASK

16

1

Mask file for FLAT_ID

DARK_ID

32

2

Dark current calibration file

DARK_ID_MASK

16

1

Mask file for DARK_ID

CAL1_ID

32

2

Generic calibration file

CAL1_ID_MASK

16

1

Mask file for CAL1_ID

CAL2_ID

32

2

Generic calibration file

CAL2_ID_MASK

16

1

Mask file for CAL2_ID

CAL3_ID

32

2

Generic calibration file

CAL3_ID_MASK

16

1

Mask file for CAL3_ID

1Calibration filenames will be unique, i.e., changes to a flatfield calibration file by SSC will result in a new filename.

2All images are 256x256xNunber_of_Planes unless otherwise noted.

 

 

DOCUMENT REVISION HISTORY:

V1.1 (30-Apr-2001): restructure table "LEVELA"

minor typo corrections