Last modified: 24 October 2019

URL: https://cxc.cfa.harvard.edu/csc/data_products/stack/index.html

CSC Full-Field Stacked Observation Data Products

In addition to the tabulated properties for each detected source and observation in the Master Sources Table, Stacked Observation Detections Table, and Per-Observation Detections Table, a number of full-field data products are produced for each stack of observations, in formats suitable for analysis in CIAO. These include such things as:


Full-Field Stacked Observation Data Products

A set of stacked, full-field observation detections data products is created for each observations stack that undergoes catalog processing. They are identified by the detect stack identifier (detect_stack_id), denoted 〈stkpos〉, and a three digit region identifier/component number (region_id), denoted 〈stkver〉 in the file name.

Data product Pipeline Filename
Detect stack event list Combine and Detect 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_evt3.fits
Detect stack image Combine and Detect 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈b〉_img3.fits, 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈f〉_img3.jpg
Detect stack background image Combine and Detect 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈b〉_bkgimg3.fits
Detect stack exposure map Combine and Detect 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈b〉_exp3.fits
Detect stack field of view Combine and Detect 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_fov3.fits
Detect stack limiting sensitivity Limiting Sensitivity 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈b〉_sens3.fits
Merged source detection list Stacker 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_mrgsrc3.fits

How Do I Find These Data Products?

Stacked observations, full-field data products can be retrieved using CSCview. They can be selected from the Data products pane in the Results tab of CSCview (see areas highlighted in the figure), associated to one or more rows returned by the query, and by clicking on Search. The number of data products returned by CSCview as a function of the identifiers available in the rows select is determined as described in "CSCview and CSC 2.0 Help".

[CSCView query results]


Filename Example

〈i〉 refers to detector used, formatted "acis" or "hrc", 〈s〉 is the source data "f" or "s", for "flight" data or simulated data, respectively.

For example, the stacked source region image file, acisfJ0055454p262444_001N020_b_img3.fits.gz, the 〈stkpos〉 is "J0055454p262444", which is the epoch J2000 celestial coordinates of the stack's central position: RA=0h 55m 45.4s and Dec=+26° 24′ 44″. The "p" or "m" in the stack position string refers to "+" or "-" source declination. The 〈stkver〉 is a three digit stack version, 1 in this instance.

〈v〉 is a three digit data product revision number preceded by "N", N020 means file revision version 20. 〈r〉 is the region ID, preceded by an "r" and appended by the 〈b〉 for the science energy band: "b", "h", "m", "s", "u", or "w". In this instance, in the file names, the b_ refers to the "broad" energy band. The file name is ended with the data product type and appended with the gzipped FITS file extension.