Last modified: 27 March 2024


The source-region, stack detections data products are the combined per-source files found in the bundle that the master source falls on, obtained from individual stacked observations (or "stacks") filtered by a rectangular region of interest around the position of the detection. These files are for the large part generated in the Source Properties pipeline run for each master source produced by the Master Match pipeline.

In addition to the tabulated properties for each source in the Master Sources Table, Stacked Observation Detections Table, and Per-Observation Detections Table, a number of file-based Level 3 data products are produced for each source and observation individually, in formats suitable for analysis in CIAO. These include such things as:

Source Region Stack Detections Data Products

A set of source-based data products is created for each detected source region in each observation stack that undergoes catalog processing. The stacked source region data products 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
Valid stack source region event list Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉_regevt3.fits
Valid stack source region image Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉〈b〉_regimg3.fits, 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉〈b〉_regimg3.jpg
Valid stack source region tricolor image Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉_reg3img3.jpg
Valid stack source region exposure map Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉〈b〉_regexp3.fits
Detect stack source region Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉_reg3.fits
Valid stack MLE source fit draws Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉_〈r〉〈b〉_draws3.fits
Valid stack source region aperture photometry PDF Source Properties 〈i〉〈s〉〈stkpos〉_〈stkver〉N〈v〉[_〈c〉]_〈r〉〈b〉_phot3.fits

How Do I Find These Data Products?

Source-region, stack detections 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.1 Help".

[Thumbnail image: CSCView query results]

[Version: full-size]

[Print media version: 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, acisfJ0025402m771522_001N020_r0010b_regimg3.fits.gz, the 〈stkpos〉 is "J0025402m771522", which is the epoch J2000 celestial coordinates of the stack's central position: RA=0h 25m 40.2s and Dec=-77° 15′ 22″. 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.

For the source region image file name, acisf11978_001N020_r0348b_regimg3.fits.gz the 〈obs〉 refers to ObsID 11978 and 〈obi〉 is the ObsID's observation interval, 1 in this case. The ObIs are numbered in three digits and the numbering within an ObsID does not have to be contiguous and might not start at zero (000).

〈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.