Browse
this table...

XMMSSC - XMM-Newton Serendipitous Source Catalog (3XMM DR5 Version)

HEASARC
Archive

Overview

This table contains the Third XMM-Newton Serendipitous Source Catalog, Fifth Data Release, or 3XMM-DR5.

3XMM-DR5 is the third generation catalog of serendipitous X-ray sources from the European Space Agency's (ESA) XMM-Newton observatory, and has been created by the XMM-Newton Survey Science Centre (SSC) on behalf of ESA. It is an incremental release of the 3XMM catalog and contains 354 more observations and about 34,701 more detections than the preceding 3XMM-DR4 catalog, which was made public in July 2013. The advantage of this catalog is that it corrects one of the minor issues in 3XMM-DR4 (see Watchout 3 at http://xmmssc-www.star.le.ac.uk/Catalogue/xcat_public_3XMM-DR4.html). This issue was due to an uninitialized variable in a subroutine of the source detection chain, and it caused a subset of the error values in the 3XMM-DR4 catalog to have been over-estimated, and a very small portion of the errors to have been under-estimated.

The catalog contains source detections drawn from a total of 7,781 XMM-Newton EPIC observations made between 2000 February 3 and 2013 December 20; all datasets included were publicly available by 2013 December 31 but not all public observations are included in this catalog. For net exposure time >= 1 ksec, the total area of the catalog fields is ~ 1500 deg2 but taking account of the substantial overlaps between observations, the net sky area covered independently is ~ 877 deg2.

The catalog contains 565,962 X-ray source detections above the processing likelihood threshold of 6. These X-ray source detections relate to 396,910 unique X-ray sources, that is, a significant fraction of sources (70,453, 18%) have more than one detection in the catalog (up to 48 repeat observations in the most extreme case).

The catalog distinguishes between extended emission and point-like detections. Parameters of detections of extended sources are only reliable up to the maximum extent measure of 80 arcseconds. There are 69,276 detections of extended emission, of which 15,077 are 'clean' (in the sense that they were not manually flagged) and 9,082 comprise the 'cleanest' set where no flags are set and they are not in fields with high background levels

Due to intrinsic features of the instrumentation as well as some shortcomings of the source detection process some detections are considered to be spurious or their parameters are considered to be unreliable. It is recommended to use either a detection flag or an observation flag (and, possibly, a high background flag) as filters to obtain what can be considered a 'clean' sample. There are 456,904 out of 565,962 detections that are considered to be clean (i.e., summary flag < 3).

For about 133,026 detections, EPIC spectra and time series were automatically extracted during processing, and a chi2-variability test was applied to the time series. 4,668 detections in the catalog are considered variable, within the timespan of the specific observation, at a probability of 10-5 or less based on the null-hypothesis that the source is constant. Of these, 2,684 have a summary flag < 3.

The median flux (in the total photon-energy band from 0.2 - 12 keV) of the catalog detections is ~ 2.4 x 10-14 erg/cm2/s; in the soft energy band (0.2 - 2 keV) the median flux is ~ 5.7 x 10-15, and in the hard band (2 - 12 keV) it is ~ 1.3 x 10-14. About 20% have fluxes below 1 x 10-14 erg/cm2/s. The flux values from the three EPIC cameras are, overall, in agreement to ~ 10% for most energy bands. The positional accuracy of the catalog point source detections is generally < 3 arcseconds (90% confidence radius) and 90% of point sources have 1-sigma positional uncertainties < 2.4 arcseconds.

The energy bands used in the 3XMM-DR5 processing were the same as for the 2XMM catalog.

Table 1: Energy bands used in 3XMM-DR5 processing

The following are the basic energy bands:

1       =       0.2 -   0.5 keV
2       =       0.5 -   1.0 keV
3       =       1.0 -   2.0 keV
4       =       2.0 -   4.5 keV
5       =       4.5 -  12.0 keV

while these are the broad energy bands:

6       =       0.2 -   2.0 keV                 soft band, no images made
7       =       2.0 -  12.0 keV                 hard band, no images made
8       =       0.2 -  12.0 keV                 total band
9       =       0.5 -   4.5 keV                 XID band

The first table at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM_DR5.html gives an overview of the statistics of the 3XMM-DR5 catalog in comparison with the 3XMM-DR4 catalog which it supersedes.


Catalog Bibcodes

2015arXiv150407051R
2009A&A...493..339W

References

The following is the preferred citation of this version (3XMM-DR5) of the catalog:
    Rosen, Webb, Watson et al. (2015), "The XMM-Newton Serendipitous Survey.
    VII. The Third XMM-Newton Serendipitous Source Catalogue", A&A, submitted.

The following is the preferred citation of the previous 2XMM version of the catalog:

    Watson et al. (2009), "The XMM-Newton Serendipitous Survey. V. The Second
    XMM-Newton Serendipitous Source Catalogue", A&A, 493, 339-373.

Provenance

This HEASARC database table contains the 3XMM-DR5 catalog, released by ESA on 2015 April 28, and obtained from the XMM-Newton Survey Science Center Consortium (http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM_DR5.html). It is also available as a gzipped FITS file: http://heasarc.gsfc.nasa.gov/FTP/xmm/data/catalogues/3XMM_DR4cat_v1.0.fits.gz. The last two previous versions of the Serendipitous Source Catalog, 2XMMi-DR3 and 3XMM-DR4 are also available in the same directory for comparison purposes as the files 2XMMiDR3cat_v1.0.fits.gz and 3XMM_DR4cat_v1.0.fits.gz, respectively.

Description

Pointed observations with the XMM-Newton Observatory detect significant numbers of previously unknown 'serendipitous' X-ray sources in addition to the proposed target. Combining the data from many observations thus yields a serendipitous source catalog which, by virtue of the large field of view of XMM-Newton and its high sensitivity, represents a significant resource. The serendipitous source catalog enhances our knowledge of the X-ray sky and has the potential for advancing our understanding of the nature of various Galactic and extragalactic source populations.

The 3XMM-DR5 catalog is the seventh publicly released XMM-Newton X-ray source catalog produced by the XMM-Newton Survey Science Centre (SSC) consortium. It follows the 1XMM (released in April 2003), 2XMMp (July 2006), 2XMM (August 2007), 2XMMi (August 2008), 2XMMi-DR3 (April 2010) and 3XMM-DR4 (July 2013) catalogs: 2XMMp was a preliminary version of 2XMM. 2XMMi and 2XMMi-DR3 are incremental versions of the 2XMM catalog.

The 3XMM-DR5 catalog is about 7% larger than the 3XMM-DR4 catalog, which it supersedes. In terms of the number of X-ray sources, the 3XMM-DR5 catalog is the largest ever produced. 3XMM-DR5 complements deeper Chandra and XMM-Newton small area surveys, probing a large sky area at the flux limit where the bulk of the objects that contribute to the X-ray background lie. The 3XMM-DR5 catalog provides a rich resource for generating large, well-defined samples for specific studies, utilizing the fact that X-ray selection is a highly efficient (arguably the most efficient) way of selecting certain types of object, notably active galaxies (AGN), clusters of galaxies, interacting compact binaries and active stellar coronae. The large sky area covered by the serendipitous survey, or equivalently the large size of the catalog, also means that 3XMM-DR5 is a superb resource for exploring the variety of the X-ray source population and identifying rare source types.

The production of the 3XMM-DR5 catalog has been undertaken by the XMM-Newton SSC consortium in fulfillment of one of its major responsibilities within the XMM-Newton project. The catalog production process has been designed to fully exploit the capabilities of the XMM-Newton EPIC cameras and to ensure the integrity and quality of the resultant catalog through rigorous screening of the data.

The 3XMM-DR5 catalog uses the same bulk reprocessing of all the available XMM-Newton data that was used for 3XMM-DR4. It is based on a pipeline (cat9.0 - configuration 00000004_04_cat9.0_20121220.153800) that contains significant changes to the processing approach to enhance the quality of the catalog. It makes use of the SAS version 12.0.1, but with a small number of specifically updated SAS tasks and the latest calibration files available at the time of the bulk reprocessing (early 2013). For the bulk reprocessing run of all data taken until the end of 2012, the pipeline, SAS and calibration components were static throughout the run. 20 further observations were made during 2013 and became public immediately. Whilst these observations use the same pipeline, some of the calibration components were modified.

Users of the 3XMM catalog should be aware that the DETID and SRCID values bear no relation to those in the previous 2XMM series of catalogs. However, a cross-matching is provided in 3XMM-DR5 via the DR3DETID and DR3SRCID columns.


Catalog Properties

The catalog contains source detections drawn from 7,781 XMM-Newton EPIC observations made between 2000 February 3 and 2013 December 20 and which were publicly available by 2013 December 31. Net exposure times in these observations range from < 1,000 up to ~ 130,000 seconds (that is, a full orbit of the satellite). Figure 5.2 at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/Figure5.2.html shows the distribution of fields on the sky.

The total sky area of the catalog observations with effective exposure > 1 ks is ~ 1,500 deg2 which translates to ~ 877 deg2 when corrected for field overlaps.

The catalog contains 565,962 X-ray detections with total-band (0.2 -12 keV) likelihood values >= 6. These are detections of 396,910 unique X-ray sources, i.e., 239,505 X-ray sources have multiple detections in separate observations (up to 48 detections). Of the 565,962 X-ray detections, 69,276 are classified as extended, with 15,077 of these being in regions considered to be 'clean' (SUM_FLAG < 3).

Data Quality: As part of extensive quality evaluation for the catalog, each field has been visually screened. Regions where there were obvious deficiencies with the automatic source detection and parametrization process were identified and all detections within those regions were flagged (cf. 2XMM UG, Sec. 3.2.6 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatVisScreen but importantly, note Section 3.11 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#VisScreen). Such flagged detections include clearly spurious detections (many of which are classified as extended) as well as detections where the source parameters may be unreliable. Each XMM-Newton field is also evaluated to assess the fractional area of the observation that is affected by flagged detections, as reflected by the OBS_CLASS parameter. For most uses of the catalog it is recommended to use either a detection flag (SUM_FLAG, EP_FLAG or SC_SUM_FLAG) or an observation flag (OBS_CLASS) as a filter to obtain what can be considered a 'clean' sample.

Note that no attempt is made to flag spurious detections arising from statistical fluctuations in the background. An updated analysis of the false detection rate will be presented in the 3XMM catalogue paper (Rosen, Webb, Watson et al. 2015, A&A, submitted).

Sensitivity and Photometry: Figure 5.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/fig_5.4.html presents, for each of the three cameras, the distributions of flux for energy bands 1 to 5 and also for the combined (EPIC) data. These give an indication of the limiting flux available in the catalogs for each of the bands. Comparison of the detection count rates and fluxes in the 3XMM and the previous 2XMMi-DR3 version shows good agreement between the two catalogs. A more detailed analysis of photometric issues will be presented in the 3XMM catalog paper (Rosen, Webb, Watson et al. 2015, A&A, submitted).

Astrometry: As noted in section 3.4 of the 3XMM-DR4 user guide at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Astrom, the 3XMM catalog benefits from a number of improvements to the astrometry, several of which resulted from effects only discovered in the process of compiling the catalog. The net effect for 3XMM source positions is a small improvement in the statistical position errors, a reduction in the position error systematics and increased confidence in the reliability of the position errors. A more detailed analysis of these issues will again be presented in the 3XMM catalog paper (Rosen, Webb, Watson et al. 2015, A&A, submitted).


Key Changes in 3XMM-DR5 with Respect to 3XMM-DR4

Data selection: XMM-Newton observations considered for inclusion in the 3XMM-DR5 catalog were those with ODFs available for processing up to 2013 December 20 and which had public release dates up to 2013 December 31. After allowing for a small number (< 100) of observations which failed in processing for a variety of reasons, 7,781 observations were available to make the 3XMM-DR5 catalog. Table 2.1 at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3xmmdr5_obslist.html gives the list of the final 7,781 observations which are included in the 3XMM-DR5 catalog.

3XMM-DR5 contains 440 observations that were public and available for inclusion in 2XMMi-DR3, but were not included in 2XMMi-DR3. Many of these cases are fields with high backgrounds, while others are cases that failed in previous processing but processed satisfactorily during the processing for 3XMM-DR5. There are 31 observations in 2XMMi-DR3 that did not make it in to 3XMM-DR5, mainly due to software/pipeline errors during processing. Typical examples of the latter problems are due to revised ODFs (e.g. with no useful time-correlation information), more sophisticated SAS software that identified issues hitherto not trapped, or issues with exposure corrections of background flare light curves and pn time-jumps.

Mosaic mode data: Most XMM-Newton observations are performed in pointing mode, where the spacecraft is locked on to a fixed position on the sky for the entire observation. Prior to XMM-Newton revolution 1812 (2009-Oct-30), a few special case observations were performed that involved attitude step changes during the observation, generally for the purposes of tracking a moving target. However, in the AO8 observing cycle, a specific mosaic observing mode (see http://xmm.esac.esa.int/external/xmm_user_support/documentation/uhb_2.6/node109.html) was introduced in which the satellite pointing direction is stepped across the sky, taking snapshots at points (sub-pointings) on a user-specified grid. Data from dedicated mosaic mode or tracking (mosaic-like) observations are recorded into a single ODF for the observation.

It has been established that the ODFs of a subset of the mosaic-mode observations (see http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Mosaics) have been incorrectly split in to sub-pointings. Where the considerable overlaps in the time series are present, these observations have been removed from the catalog. A further ten parent cases (involving 26 sub-pointings, of which 19, involving 975 detections) are in the 3XMM-DR5 catalog. Some of these sub-pointings are affected by this bug, but only MOS1 and/or MOS2 data are impacted. The cause appears to be related to incorrect time-tagging of events due to telemetry gaps, which the splitting process handled incorrectly.

The 18 mosaic-mode parent problem-case observations that have been removed from the catalog (encompassing 89 sub-pointings) are listed at http://xmmssc-www.star.le.ac.uk/Catalogue/mosaicmode_problem_fields.list. Two comma-separated-variable format files, http://xmmssc-www.star.le.ac.uk/Catalogue/problem_mosaics_all_data_affected.csv for the cases where all data are affected and http://xmmssc-www.star.le.ac.uk/Catalogue/problem_mosaics_some_data_affected.csv for cases where some data are affected, are provided which contain the DETID, OBS_ID, RA, DEC and INSTRUMENT(s) affected for detections from the relevant problematic sub-pointings.

For those cases where only some of the data are affected, the XMM SOC believe that only timeseries data/products are affected and only for the MOS1 and/or MOS2 instruments. However, the SOC have been reprocessing all the mosaic mode data and the corrected pipeline products for mosaic mode data will soon be made available via the XSA.

New naming convention for the DETID and the SRCID: To streamline the procedure for attributing the DETID number (which is unique to each detection) and the SRCID number (that is unique to each unique source) and to keep the same numbers from catalog to catalog, without providing supplementary columns in the catalogue with the DETID and SRCID from previous releases, starting in 3XMM-DR5 the numbering convention has been modified.

The OBSID which always remains the same for an observation is now coupled with the source number SRC_NUM to make the DETID. The SRCID attributed for a unique source is determined by using the first DETID attributed to that source (i.e. in the earliest observation that that source was detected).


New Calibrations and Fluxes

A number of improvements in the calibration of the MOS and pn have occurred which lead to slight changes in the Energy Conversion Factors (ECFs) (see http://xmm2.esac.esa.int/external/xmm_sw_cal/calib/epic_files.shtml for information on the EPIC response files) that are used for converting EPIC band count rates to fluxes. Of note is the fact that MOS redistribution matrices are now provided for 13 epochs and for three areas of the detector that reflect the so-called 'patch', 'wings-of-patch' and 'off-patch' locations.

For 3XMM-DR5 a simple approach has been adopted. ECFs were computed following the prescription of Mateos et al. (2009, A&A, 496, 879), for energy bands 1-5 and band 9, for full-frame mode, for each EPIC camera, for each of the Open, Thin, Medium and Thick filters. For pn, the ECFs are calculated at the on-axis position. The pn response is sufficiently stable that no temporal resolution is needed.

For MOS, to retain a direct connection between the ECFs and publicly available response files, the ECFs used are taken at epoch 13 and are for the 'off-patch' location. The latter choice was made because the large majority of detections in an XMM-Newton field lie outside the 'patch' and 'wings-of-patch' regions, which only relate to a region of radius <= 40 arcseconds, near the center of the field. The use of a single epoch (epoch 13) was made to retain simplicity in the processing and because the response of the MOS cameras exhibits a step function change between epochs 5 and 6, with different but broadly constant values either side of the step. None of the 13 calibration epochs represent the average response and thus no response file exists to which average ECFs can be directly related. The step-function change in the responses for MOS is most marked in band 1 (0.2-0.5 keV) for the 'patch' location, where the maximum range in ECFs either side of the step amounts to 20%. Outside the 'patch' region, and for all other energy bands, the range of the ECF values with epoch is <= 5% and is <= 2.5% for the 'off-patch' region. Epoch 13 was chosen, somewhat arbitrarily, as being typical of epochs in the longer post-step time interval.

The ECFs, in units of 1011 counts cm2/erg, adopted for the bulk reprocessing of data used for 3XMM-DR5, are provided in Table 8 (shown below), for each camera, energy band and filter. The camera rate and flux are related via the relation ca_FLUX = (ca_RATE/ECF).

Table 8: Energy Conversion Factors used for converting EPIC band count rates
to fluxes in 3XMM-DR5

Camera 	Band 	Open 	Thin 	Medium 	Thick
PN 	1 	16.9783 	9.5248 	8.3696 	5.1065
	2 	10.0696 	8.121 	7.8681 	6.0479
	3 	6.1551 	5.867 	5.7673 	4.9893
	4 	1.9844 	1.9527 	1.929 	1.8282
	5 	0.5782 	0.5774 	0.5764 	0.5698
	9 	5.098 	4.5586 	4.4602 	3.7636
MOS-1 	1 	3.0896 	1.7345 	1.5258 	0.9977
	2 	2.1152 	1.7461 	1.6974 	1.3792
	3 	2.1387 	2.0407 	2.0058 	1.7871
	4 	0.7491 	0.7375 	0.7292 	0.6991
	5 	0.1452 	0.145 	0.1451 	0.143
	9 	1.5035 	1.3843 	1.3584 	1.2035
MOS-2 	1 	3.1094 	1.7336 	1.5223 	0.9907
	2 	2.1309 	1.7572 	1.7082 	1.3869
	3 	2.1407 	2.0426 	2.0079 	1.7887
	4 	0.7531 	0.7418 	0.7333 	0.703
	5 	0.1528 	0.1528 	0.1524 	0.1502
	9 	1.5097 	1.3894 	1.3634 	1.2076

Note that canned response matrices for basic XMM-Newton spectral analyses can be obtained from http://xmm2.esac.esa.int/external/xmm_sw_cal/calib/epic_files.shtml.


Credits

The production of the 3XMM-DR5 catalog is a collaborative project involving the whole XMM-Newton SSC Consortium:
  Institut de Recherche en Astrophysique et Planetologie, Toulouse, France

  University of Leicester, UK

  Mullard Space Science Laboratory, University College London, UK

  Max-Planck Institut für extraterrestrische Physik, Germany

  Leibniz-Institut für Astrophysik, Potsdam (AIP), Germany

  Service d'Astrophysique, CEA/DSM/DAPNIA, Saclay, France

  Observatoire Astronomique de Strasbourg, France

  Instituto de Fisica de Cantabria, Santander, Spain

  Osservatorio Astronomico di Brera, Milan, Italy

The SSC team are grateful to the XMM-Newton SOC for their support in the catalog production activities.

The SSC acknowledges the use of the TOPCAT and STILTS software packages (written by Mark Taylor, University of Bristol) in the production and testing of the 3XMM-DR5 catalog.


Documentation

The User Guide for the 3XMM-DR5 Catalog, available at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM-DR5_Catalogue_User_Guide.html, contains details of the catalog production process and content. A complete description of this catalog and the parameters listed therein can be found there. The list of observations used in the catalog can be found at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3xmmdr5_obslist.html. The user should particularly refer to section 6 of the 3XMM-DR5 UG, 'Known Problems and Other Issues' at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM-DR5_Catalogue_User_Guide.html#Problems as much of this material is not included in this HEASARC documentation.

Watchouts

(1) Please use SRCID and DETID columns only for the source and detection identification as these are the only columns that will persist in future versions of the catalog, see the user guide, section 3.4 at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM-DR5_Catalogue_User_Guide.html#DetID. The usage of IAUNAME is not recommended as its uniqueness is not enforced over the set of unique sources.

(2) It has been established that the ODFs of a subset of the mosaic-mode observations have been incorrectly split in to sub-pointings. Where the considerable overlaps in the time series are present, these observations have been removed from the catalog. A further ten parent cases (involving 26 sub-pointings, of which 19, involving 975 detections) are in the 3XMM-DR5 catalog. Some of these sub-pointings are affected by this bug, but only MOS1 and/or MOS2 data are impacted. The cause appears to be related to incorrect time-tagging of events due to telemetry gaps, which the splitting process handled incorrectly. The 18 mosaic-mode parent problem-case observations that have been removed from the catalog (encompassing 89 sub-pointings) are listed at http://xmmssc-www.star.le.ac.uk/Catalogue/mosaicmode_problem_fields.list. Two comma-separated-variable format files, one for the cases where all data are affected and one for cases where some data are affected, are provided at http://xmmssc-www.star.le.ac.uk/Catalogue/problem_mosaics_all_data_affected.csv and http://xmmssc-www.star.le.ac.uk/Catalogue/problem_mosaics_some_data_affected.csv, respectively. These files contain the DETID, OBS_ID, RA, DEC and INSTRUMENT(s) affected for detections from the relevant problematic sub-pointings. For those cases where only some of the data are affected, the SOC believe that only timeseries data/products are affected and only for the MOS1 and/or MOS2 instruments.


User Guide for 2XMM

The extensive User Guide (UG) for the 2XMM catalog at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html still describes many of the details of the data processing and compilation approach applicable to the 3XMM-DR5 catalog. However, a significant number of changes to the processing have been implemented for 3XMM and these are described in the 3XMM-DR4 User Guide at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Diff3XMMDR4 and in the 3XMM-DR5 User Guide at http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM-DR5_Catalogue_User_Guide.html.

Catalog Content and Organization

There are 323 parameters in the catalog. For each observation, there are up to three cameras with one or more exposures which were merged when the filter and sub-modes were the same (2XMM UG, Sec. 2.2 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#SelExp). The data in each exposure are accumulated in several distinct energy bands (see Table 1 above). Camera-level measurements can further be combined into observation-level parameters. Consequently, the source parameters can refer to some or all of these levels: on the observation level there are the final mean parameters of the source (prefix 'EP'); on the camera level the data for each of the three cameras (where available) are given (prefix 'PN', 'M1', or 'M2'), and on the energy band level the energy-dependent details of the source parameters are given (indicated by a 'b' in the column name where b = 1, 2, 3, 4, 5, 8 or 9). Finally, on a meta-level, some parameters of sources that were detected more than once (prefix 'SC') were combined, see 2XMM UG, Sec. 3.2.4 at mmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb.

Entries with NULL are given when no detection was made with the respective camera, that is, ca_MASKFRAC < 0.15 or NULL (i.e., a camera was not used in an observation).


Known Problems and Other Issues

Please refer to http://xmmssc.irap.omp.eu/Catalogue/3XMM-DR5/3XMM-DR5_Catalogue_User_Guide.html#Problems for other known problems and issues with 3XMM-DR5, including problem cases such as spurious sources arising from MOS low-energy noise, reduced sensitivity due to high background, exposure correction failure for timeseries, timeseries not corrected to on-axis position, and the treatment of high-proper-motion objects .

Parameters

Detid
A consecutive number which identifies each entry (detection) in the catalog. The correct nomenclature for references to detections in the catalog is the source name followed by a colon and the detection identification number DETID (with six digits), that is: '3XMM Jhhmmss.sSddmmss:detid'. The DETID numbering assignments in 3XMM-DR5 bear no relation to those in 2XMMi-DR3 but the DETID of the nearest matching detection from the 2XMMi-DR3 catalog to the 3XMM-DR5 detection is provided via the DR3_DETID parameter.

SrcID
A unique number assigned to a group of catalog entries which are assumed to be the same source. The process of grouping detections into unique sources has changed since the 2XMM catalog series and is described in Section 3.8 of the 3XMM-DR4 UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#DiffUniqueId. The SRCID assignments in 3XMM-DR5 bear no relation to those in 2XMMi-DR3, but the nearest unique sources from the 2XMMi-DR3 catalog to the 3XMM-DR5 unique source is provided via the DR3_SRCID column.

DR3_SrcID
The 2XMMi-DR3 source identifier of the nearest unique 2XMMi-DR3 source that lies within 10 arcseconds of the 3XMM-DR5 unique source position.

DR3_Detid
The 2XMMi-DR3 detection identifier of the nearest 2XMMi-DR3 detection that lies within 10 arcseconds of the detection position in 3XMM-DR5.

DR3_Detdist
The distance in arcseconds between the 3XMM-DR5 detection position and the nearest detection (within 10 arcseconds) in the 2XMMi-DR3 catalog.

DR3_Srcdist
The distance in arcseconds between the 3XMM-DR5 unique source position and the nearest unique source (within 10 arcseconds) in the 2XMMi-DR3 catalog.

DR3_Mult
The number of unique sources from the 2XMMi-DR3 catalog that lie within 10 arcseconds of the unique source position in 3XMM-DR5.

Dr4_SrcID
The 3XMM-DR4 source identifier of the nearest unique 3XMM-DR4 source that lies within 10 arcseconds of the 3XMM-DR5 unique source position.

Dr4_Detid
The 3XMM-DR4 detection identifier of the nearest 3XMM-DR4 detection that lies within 10 arcseconds of the detection position in 3XMM-DR5.

Dr4_Detdist
The distance in arcseconds between the 3XMM-DR5 detection position and the nearest detection (within 10 arcseconds) in the 3XMM-DR4 catalog.

Dr4_Srcdist
The distance in arcseconds between the 3XMM-DR5 unique source position and the nearest unique source (within 10 arcseconds) in the 3XMM-DR4 catalog.

Dr4_Mult
The number of unique sources from the 3XMM-DR4 catalog that lie within 10 arcseconds of the unique source position in 3XMM-DR5.

Name
The IAU designation assigned to the unique SRCID. An IAU-style identification, NAME, has been assigned to each unique source (SRCID) based upon the IAU registered classification, 3XMM, and the J2000.0 source coordinates. The form of the IAU names is '3XMM Jhhmmss.sSddmmss' where hhmmss.s is taken from the Right Ascension coordinate given in the RA parameter and Sddmmss is the Declination taken from the Dec parameter.

Src_Num
The decimal source number in the individual source list for this observation; when expressed in hexadecimal it identifies the SAS task srcmatch source-specific product files belonging to this detection. (See Appendix A.1 of the 2XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#AppProd for more details).

ObsID
The XMM-Newton observation identification.

XMM_Revolution
The XMM-Newton revolution number in which the observation took place.

Time
The start time of the observation (converted from the Modified Julian Date format given in the original input file).

End_Time
The end time of the observation (converted from the Modified Julian Date format given in the original input file).

Obs_Class
The quality classification of the whole observation based on the area flagged as bad in the manual flagging process as compared to the whole detection area, see 2XMM UG Section 3.2.6 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatVisScreen. 0 means nothing has been flagged; 1 indicates that 0% < area < 0.1% of the total detection mask has been flagged; 2 indicates that 0.1% <= area < 1% has been flagged; 3 indicates that 1% <= area < 10% has been flagged; 4 indicates that 10% <= area < 100% has been flagged; and 5 means that the whole field was flagged as bad.

PN_Filter
The type of PN filter used. The options are Thick, Medium, Thin1, Thin2, and Open, depending on the efficiency of the optical blocking.

M1_Filter
The type of M1 filter used. The options are Thick, Medium, Thin1, and Open, depending on the efficiency of the optical blocking.

M2_Filter
The type of M2 filter used. The options are Thick, Medium, Thin1, and Open, depending on the efficiency of the optical blocking.

PN_Submode
The PN observing mode. The options are full frame mode with the full FOV exposed (in two sub-modes), and large window mode with only parts of the FOV exposed, see Table 2.3 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/modes.html.

M1_Submode
The M1 observing mode. The options are full frame mode with the full FOV exposed, partial window mode with only parts of the central CCD exposed (in different sub-modes, see Table 2.3 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/modes.html), and timing mode where the central CCD was not exposed ('Fast Uncompressed').

M2_Submode
The M2 observing mode. The options are full frame mode with the full FOV exposed, partial window mode with only parts of the central CCD exposed (in different sub-modes, see Table 2.3 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/modes.html), and timing mode where the central CCD was not exposed ('Fast Uncompressed').

RA
The corrected Right Ascension of the detection in the selected equinox after statistical correlation of the emldetect coordinates, RA_UNC and DEC_UNC, with the USNO B1.0, 2MASS or SDSS (DR8) optical/IR source catalogs using the SAS task catcorr (the process of correcting the coordinates is also referred to as field rectification). In cases where the cross-correlation is determined to be unreliable, no correction is applied and this value is therefore the same as RA_UNC. The RA was given in J2000.0 decimal degrees in the original table.

Dec
The corrected Declination of the detection in the selected equinox after statistical correlation of the emldetect coordinates, RA_UNC and DEC_UNC, with the USNO B1.0, 2MASS or SDSS (DR8) optical/IR source catalogs using the SAS task catcorr (the process of correcting the coordinates is also referred to as field rectification). In cases where the cross-correlation is determined to be unreliable, no correction is applied and this value is therefore the same as DEC_UNC. The Declination was given in J2000 decimal degrees in the original table.

Error_Radius
The total positional uncertainty, in arcseconds, (called POSERR in the original table) calculated by combining the statistical error RADEC_ERROR (called RADEC_ERR in the original table) and the error arising from the field rectification process SYSERRCC as follows:

     POSERR = SQRT (RADEC_ERROR2 + SYSERRCC2 ).
  
For a 2-dimensional Gaussian error distribution, this radius reflects a 63% probability that the true source position lies within this radius of the measured position. The corresponding 68% confidence radius is 1.075*RADEC_ERR.

LII
The corrected Galactic Longitude of the detection in degrees.

BII
The corrected Galactic Latitude of the detection in degrees.

RADec_Error
The statistical 1-sigma error in the detection position, in arcseconds. This is a radial error on the position, computed as sqrt(ra_err2 + dec_err2), in arcseconds, where ra_err and dec_err are the 1-sigma uncertainties in the RA and DEC coordinates respectively. The ra_err and dec_err quantities are provided, in image pixel units, in the X_IMA_ERR and Y_IMA_ERR columns, respectively, in the POMSRLI.FIT pipeline product file of each observation - they are not provided directly in the catalog.

Syserrcc
The estimated error arising from the field rectification process, in arcseconds. If the SAS task catcorr results in a statistically reliable cross-correlation with the USNO B1.0, 2MASS or SDSS (DR8) optical/IR catalogs, SYSERRCC combines the 1-sigma errors on the translational shifts in the RA (rashift_error) and DEC (decshift_error) directions, together with the rotational error component, derived from the catalog that yields the 'best' solution, as follows:

     SYSERRCC = SQRT (rashift_error2 + decshift_error2 +
                       (r * thetarot_error)2)
  
where r is the radial off-axis angle of the detection from the spacecraft boresight, in arcseconds, and thetarot_error is the error on the rotational correction, in radians. Where catcorr fails to obtain a statistically reliable result, SYSERRCC is set to 1.5 arcseconds (see 3XMM-DR4 UG, Sec. 3.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Astrom for details). Note that rashift_error, decshift_error and thetarot_error are not provided separately in the catalog.

Refcat
An integer code reflecting the absolute astrometric reference catalog which gave the statistically 'best' result for the field rectification process (from which the corrections are taken). It is 1 for the SDSS (DR9) catalog, 2 for 2MASS and 3 for USNO B1.0. Where catcorr fails to produce a reliable solution, REFCAT is a negative number, indicating the cause of the failure. The failure codes are

  -1 = Too few matches (< 10),
  -2 = poor fit (goodness of fit parameter in catcorr < 5.0),
  -3 = error on the field positional rectification correction is > 0.75
       arcseconds
  
See 3XMM-DR4 UG, Sec. 3.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Astrom for more details.

Poscorok_Flag
This Boolean flag [T/F] parameter signifies whether catcorr obtained a statistically reliable solution or not. This parameter is redundant in the sense that if REFCAT is positive, then a reliable solution was considered to have been found (see 3XMM-DR4 UG, Sec. 3.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Astrom for details).

RA_Unc
The Right Ascension of the detection in the selected equinox, as determined by the SAS task emldetect by fitting a detection simultaneously in all cameras and energy bands. This was given in J2000.0 decimal degrees in the original SSC table.

Dec_Unc
The Declination of the detection in the selected equinox, as determined by the SAS task emldetect by fitting a detection simultaneously in all cameras and energy bands. This was given in J2000.0 decimal degrees in the original SSC table.

EP_1_Flux
The EPIC band 1 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_1_Flux_Error
The uncertainty in EPIC band 1 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_2_Flux
The EPIC band 2 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_2_Flux_Error
The uncertainty in EPIC band 2 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_3_Flux
The EPIC band 3 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_3_Flux_Error
The uncertainty in the EPIC band 3 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_4_Flux
The EPIC band 4 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_4_Flux_Error
The uncertainty in the EPIC band 4 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_5_Flux
The EPIC band 5 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_5_Flux_Error
The uncertainty in the EPIC band 5 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_8_Flux
The EPIC combined band 8 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors. Combined band fluxes for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

EP_8_Flux_Error
The uncertainty in the EPIC combined band flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

EP_9_Flux
The EPIC band 9 (XID) flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts. The EPIC flux in each band is the mean of the band-specific detections in all cameras weighted by the errors.

EP_9_Flux_Error
The uncertainty in the EPIC band 9 flux (erg/cm2/s). The error in the weighted mean of the EPIC flux in band b is given by:

            EP_b_FLUX_ERR = SQRT (1.0 / SUM (1 / ca_b_FLUX_ERR2 ))
  
where ca = PN, M1, M2, and b is the band (1, 2, 3, 4, 5, 8, 9). The flux errors are calculated from the respective band count rate error using the respective energy conversion factors

PN_1_Flux
The PN band 1 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_1_Flux_Error
The uncertainty in the PN band 1 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

PN_2_Flux
The PN band 2 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_2_Flux_Error
The uncertainty in the PN band 2 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

PN_3_Flux
The PN band 3 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_3_Flux_Error
The uncertainty in the PN band 3 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

PN_4_Flux
The PN band 4 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_4_Flux_Error
The uncertainty in the PN band 4 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

PN_5_Flux
The PN band 5 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_5_Flux_Error
The uncertainty in the PN band 5 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

PN_8_Flux
The PN combined band flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. Combined band fluxes (band 8) for the individual cameras are the sum of the fluxes from each band (1 - 5).

PN_8_Flux_Error
The uncertainty in the PN combined band flux (erg/cm2/s). Combined band fluxes and errors (band 8) for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

PN_9_Flux
The PN band 9 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

PN_9_Flux_Error
The uncertainty in the PN band 9 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_1_Flux
The M1 band 1 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_1_Flux_Error
The uncertainty in the M1 band 1 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_2_Flux
The M1 band 2 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_2_Flux_Error
The uncertainty in the M1 band 2 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_3_Flux
The M1 band 3 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_3_Flux_Error
The uncertainty in the M1 band 3 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_4_Flux
The M1 band 4 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_4_Flux_Error
The uncertainty in the M1 band 4 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_5_Flux
The M1 band 5 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_5_Flux_Error
The uncertainty in the M1 band 5 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M1_8_Flux
The M1 combined band flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. Combined band fluxes and errors (band 8) for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

M1_8_Flux_Error
The uncertainty in the M1 combined band flux (erg/cm2/s). Combined band fluxes and errors (band 8) for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

M1_9_Flux
The M1 band 9 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M1_9_Flux_Error
The uncertainty in the M1 band 9 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_1_Flux
The M2 band 1 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_1_Flux_Error
The uncertainty in the M2 band 1 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_2_Flux
The M2 band 2 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_2_Flux_Error
The uncertainty in the M2 band 2 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_3_Flux
The M2 band 3 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_3_Flux_Error
The uncertainty in the M2 band 3 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_4_Flux
The M2 band 4 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_4_Flux_Error
The uncertainty in the M2 band 4 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_5_Flux
The M2 band 5 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_5_Flux_Error
The uncertainty in the M2 band 5 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

M2_8_Flux
The M2 combined band flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. Combined band fluxes and errors (band 8) for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

M2_8_Flux_Error
The uncertainty in the M2 combined band flux (erg/cm2/s). Combined band fluxes and errors (band 8) for the individual cameras are the sum of the fluxes and errors from each band (1 - 5).

M2_9_Flux
The M2 band 9 flux (erg/cm2/s). Fluxes are calculated by the SAS tasks emldetect and by srcmatch for the various input bands. Note that they correspond to the flux in the entire PSF and do not need any further corrections for PSF losses. For the individual cameras, individual-band fluxes (bands 1 - 5, 9) are calculated from the respective band count rate using the filter- and camera-dependent energy conversion factors given in Table 8 above and corrected for the dead time due to the read-out phase. These can be 0.0 if the detection has no counts

M2_9_Flux_Error
The uncertainty in the M2 band 9 flux (erg/cm2/s). These errors are calculated from the respective band count rate error using the respective energy conversion factors.

EP_8_Rate
The EPIC combined band count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable. The combined band count rate (band 8) for each camera is calculated as the sum of the count rates in the individual bands 1 - 5. The EPIC rates are the sum of the camera-specific count rates in the respective band.

EP_8_Rate_Error
The uncertainty in the EPIC combined band 8 count rate (ct/s).

EP_9_Rate
The EPIC band 9 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable. The EPIC rates are the sum of the camera-specific count rates in the respective band.

EP_9_Rate_Error
The uncertainty in the EPIC band 9 count rate (ct/s).

PN_1_Rate
The PN band 1 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_1_Rate_Error
The uncertainty in the PN band 1 count rate (ct/s).

PN_2_Rate
The PN band 2 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_2_Rate_Error
The uncertainty in the PN band 2 count rate (ct/s).

PN_3_Rate
The PN band 3 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_3_Rate_Error
The uncertainty in the PN band 3 count rate (ct/s).

PN_4_Rate
The PN band 4 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_4_Rate_Error
The uncertainty in the PN band 4 count rate (ct/s).

PN_5_Rate
The PN band 5 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_5_Rate_Error
The uncertainty in the PN band 5 count rate (ct/s).

PN_8_Rate
The PN combined band 8 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_8_Rate_Error
The uncertainty in the PN combined band 8 count rate (ct/s).

PN_9_Rate
The PN band 9 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

PN_9_Rate_Error
The uncertainty in the PN band 9 count rate (ct/s).

M1_1_Rate
The M1 band 1 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_1_Rate_Error
The uncertainty in the M1 band 1 count rate (ct/s).

M1_2_Rate
The M1 band 2 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_2_Rate_Error
The uncertainty in the M1 band 2 count rate (ct/s).

M1_3_Rate
The M1 band 3 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_3_Rate_Error
The uncertainty in the M1 band 3 count rate (ct/s).

M1_4_Rate
The M1 band 4 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_4_Rate_Error
The uncertainty in the M1 band 4 count rate (ct/s).

M1_5_Rate
The M1 band 5 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_5_Rate_Error
The uncertainty in the M1 band 5 count rate (ct/s).

M1_8_Rate
The M1 combined band 8 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_8_Rate_Error
The uncertainty in the M1 combined band count rate (ct/s).

M1_9_Rate
The M1 band 1 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M1_9_Rate_Error
The uncertainty in the M1 band 9 count rate (ct/s).

M2_1_Rate
The M2 band 1 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_1_Rate_Error
The uncertainty in the M2 band 1 count rate (ct/s).

M2_2_Rate
The M2 band 2 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_2_Rate_Error
The uncertainty in the M2 band 2 count rate (ct/s).

M2_3_Rate
The M2 band 3 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_3_Rate_Error
The uncertainty in the M2 band 3 count rate (ct/s).

M2_4_Rate
The M2 band 4 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_4_Rate_Error
The uncertainty in the M2 band 4 count rate (ct/s).

M2_5_Rate
The M2 band 5 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_5_Rate_Error
The uncertainty in the M2 band 5 count rate (ct/s).

M2_8_Rate
The M2 combined band 8 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_8_Rate_Error
The uncertainty in the M2 combined band count rate (ct/s).

M2_9_Rate
The M2 band 9 count rate (ct/s), as derived by the SAS task emldetect. The individual-band count rate (bands 1 - 5, 9) is the band-dependent source counts (ca_b_CTS) divided by the exposure map, which combines the mirror vignetting, detector efficiency, bad pixels and CCD gaps, and an OOT-factor (Out Of Time), depending on the PN modes (PN_SUBMODE). The source counts and with it the count rates were implicitly background subtracted during the fitting process. They correspond to the count rate in the entire PSF and do not need any further corrections for PSF losses. Note that rates can be 0.0 (but not negative) if the source is too faint in the respective band to be detectable.

M2_9_Rate_Error
The uncertainty in the M2 band 9 count rate (ct/s).

EP_8_Cts
The EPIC combined band 8 source counts, as derived by the SAS task emldetect. The individual-band source counts (not given in this catalog) are derived under the total PSF (point spread function) and corrected for background. The PSF is fitted on sub-images of radius 60 arcseconds in each band (CUTRAD), which means, that in most cases at least 90% of the PSF (if covered by the detector) was effectively used in the fit. Combined band source counts (band 8) for each camera are calculated as the sum of the source counts in the individual bands 1 - 5. The EPIC band 8 counts are the sum of the (available) individual camera band 8 counts.

EP_8_Cts_Error
The uncertainty in the EPIC combined band source counts, being the statistical 1-sigma error in the total source counts of the detection, as derived by the SAS task emldetect.

PN_8_Cts
The PN combined band 8 source counts, as derived by the SAS task emldetect. The individual-band source counts (not given in this catalog) are derived under the total PSF (point spread function) and corrected for background. The PSF is fitted on sub-images of radius 60 arcseconds in each band (CUTRAD), which means, that in most cases at least 90% of the PSF (if covered by the detector) was effectively used in the fit. Combined band source counts (band 8) for each camera are calculated as the sum of the source counts in the individual bands 1 - 5.

PN_8_Cts_Error
The uncertainty in the PN combined band source counts, being the statistical 1-sigma error in the total source counts of the detection, as derived by the SAS task emldetect.

M1_8_Cts
The M1 combined band 8 source counts, as derived by the SAS task emldetect. The individual-band source counts (not given in this catalog) are derived under the total PSF (point spread function) and corrected for background. The PSF is fitted on sub-images of radius 60 arcseconds in each band (CUTRAD), which means, that in most cases at least 90% of the PSF (if covered by the detector) was effectively used in the fit. Combined band source counts (band 8) for each camera are calculated as the sum of the source counts in the individual bands 1 - 5.

M1_8_Cts_Error
The uncertainty in the M1 combined band 8 source counts, being the statistical 1-sigma error in the total source counts of the detection, as derived by the SAS task emldetect.

M2_8_Cts
The M2 combined band source counts, as derived by the SAS task emldetect. The individual-band source counts (not given in this catalog) are derived under the total PSF (point spread function) and corrected for background. The PSF is fitted on sub-images of radius 60 arcseconds in each band (CUTRAD), which means, that in most cases at least 90% of the PSF (if covered by the detector) was effectively used in the fit. Combined band source counts (band 8) for each camera are calculated as the sum of the source counts in the individual bands 1 - 5.

M2_8_Cts_Error
The uncertainty in the M2 combined band 8 source counts, being the statistical 1-sigma error in the total source counts of the detection, as derived by the SAS task emldetect.

EP_8_Det_ML
The EPIC combined band detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain. To calculate the maximum likelihood values for the combined band 8 and EPIC the sum of the individual likelihoods is being normalized to two degrees of freedom using the function ML_corr = gammaq (ndof/2, ML), where ndof = 2 (for xpos,ypos) + N_images for point sources, ndof = 3 (for xpos,ypos,extent) + N_images for extended sources, gammaq = - ln (Q(a,x)) = - ln (1 - P(a,x)), and P is the incomplete gamma function.

EP_9_Det_ML
The EPIC band 9 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_1_Det_ML
The PN band 1 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_2_Det_ML
The PN band 2 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_3_Det_ML
The PN band 3 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_4_Det_ML
The PN band 4 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_5_Det_ML
The PN band 5 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_8_Det_ML
The PN combined band 8 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

PN_9_Det_ML
The PN band 9 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_1_Det_ML
The M1 band 1 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_2_Det_ML
The M1 band 2 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_3_Det_ML
The M1 band 3 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_4_Det_ML
The M1 band 4 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_5_Det_ML
The M1 band 5 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_8_Det_ML
The M1 combined band 8 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M1_9_Det_ML
The M1 band 9 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_1_Det_ML
The M2 band 1 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_2_Det_ML
The M2 band 2 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_3_Det_ML
The M2 band 3 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_4_Det_ML
The M2 band 4 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_5_Det_ML
The M2 band 5 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_8_Det_ML
The M2 combined band 8 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

M2_9_Det_ML
The M2 band 9 detection likelihood. Maximum likelihoods are derived by the SAS task emldetect. The individual-band maximum likelihood values (bands 1 - 5, 9) stand for the detection likelihood of the source, L = - ln p, where p is the probability of the detection occurring by chance. While the detection likelihood of an extended source is computed in the same way, systematic effects such as deviations between the real background and the model, have a larger effect on extended sources and thus detection likelihoods of extended sources are more uncertain.

EP_Extent
The EPIC extent radius (arcseconds). The extent radius and error as well as the extent likelihood of a source detected as extended is determined by the SAS task emldetect. It is determined by convolving a beta-model profile with the source PSF and fitting the result to the source image. Anything below 6" is considered to be a point source and the extent is set to zero. To avoid non-converging fitting an upper limit of 80" is imposed.

EP_Extent_Error
The uncertainty in the EPIC extent radius (arcseconds). The extent radius and error as well as the extent likelihood of a source detected as extended is determined by the SAS task emldetect. It is determined by convolving a beta-model profile with the source PSF and fitting the result to the source image. Anything below 6" is considered to be a point source and the extent is set to zero. To avoid non-converging fitting an upper limit of 80" is imposed.

EP_Extent_ML
The EPIC extent likelihood. The extent radius and error as well as the extent likelihood of a source detected as extended is determined by the SAS task emldetect. The extent likelihood is the likelihood of the detection being extended as given by EXTENT_ML = - ln(P), where P is the probability of the extent occurring by chance.

EP_HR1
The EPIC hardness ratio HR1 for bands 1 and 2. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

EPIC hardness ratios are calculated by the SAS task srcmatch and are averaged over all three cameras (PN, M1, M2). Note that no energy conversion factor was used and that the EPIC hardness ratios are de facto not hardness ratios but an equivalent number helpful to characterize the hardness of a source.

EP_HR1_Error
The uncertainty in the EPIC hardness ratio for bands 1 and 2. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

EP_HR2
The EPIC hardness ratio HR2 for bands 2 and 3. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

EPIC hardness ratios are calculated by the SAS task srcmatch and are averaged over all three cameras (PN, M1, M2). Note that no energy conversion factor was used and that the EPIC hardness ratios are de facto not hardness ratios but an equivalent number helpful to characterize the hardness of a source.

EP_HR2_Error
The uncertainty in the EPIC hardness ratio for bands 2 and 3. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

EP_HR3
The EPIC hardness ratio HR3 for bands 3 and 4. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

EPIC hardness ratios are calculated by the SAS task srcmatch and are averaged over all three cameras (PN, M1, M2). Note that no energy conversion factor was used and that the EPIC hardness ratios are de facto not hardness ratios but an equivalent number helpful to characterize the hardness of a source.

EP_HR3_Error
The uncertainty in the EPIC hardness ratio for bands 3 and 4. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

EP_HR4
The EPIC hardness ratio HR4 for bands 4 and 5. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

EPIC hardness ratios are calculated by the SAS task srcmatch and are averaged over all three cameras (PN, M1, M2). Note that no energy conversion factor was used and that the EPIC hardness ratios are de facto not hardness ratios but an equivalent number helpful to characterize the hardness of a source.

EP_HR4_Error
The uncertainty in the EPIC hardness ratio for bands 4 and 5. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

PN_HR1
The PN hardness ratio HR1 for bands 1 and 2. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

PN_HR1_Error
The uncertainty in the PN hardness ratio for bands 1 and 2. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

PN_HR2
The PN hardness ratio HR2 for bands 2 and 3. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

PN_HR2_Error
The uncertainty in the PN hardness ratio for bands 2 and 3. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

PN_HR3
The PN hardness ratio HR3 for bands 3 and 4. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

PN_HR3_Error
The uncertainty in the PN hardness ratio for bands 3 and 4. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

PN_HR4
The PN hardness ratio HR4 for bands 4 and 5. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

PN_HR4_Error
The uncertainty in the PN hardness ratio for bands 4 and 5. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M1_HR1
The M1 hardness ratio HR1 for bands 1 and 2. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M1_HR1_Error
The uncertainty in the M1 hardness ratio for bands 1 and 2. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M1_HR2
The M1 hardness ratio HR2 for bands 2 and 3. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M1_HR2_Error
The uncertainty in the M1 hardness ratio for bands 2 and 3. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M1_HR3
The M1 hardness ratio HR3 for bands 3 and 4. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M1_HR3_Error
The uncertainty in the M1 hardness ratio for bands 3 and 4. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M1_HR4
The M1 hardness ratio HR4 for bands 4 and 5. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M1_HR4_Error
The uncertainty in the M1 hardness ratio for bands 4 and 5. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M2_HR1
The M2 hardness ratio HR1 for bands 1 and 2. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M2_HR1_Error
The uncertainty in the M2 hardness ratio for bands 1 and 2. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M2_HR2
The M2 hardness ratio HR2 for bands 2 and 3. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M2_HR2_Error
The uncertainty in the M2 hardness ratio for bands 2 and 3. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M2_HR3
The M2 hardness ratio HR3 for bands 3 and 4. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M2_HR3_Error
The uncertainty in the M2 hardness ratio for bands 3 and 4. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

M2_HR4
The M2 hardness ratio HR4 for bands 4 and 5. The hardness ratios for each camera are derived by the SAS task emldetect. They are defined as the ratio between the bands A and B:

              HR(A,B) = (band B - band A) / (band A + band B).
  

Note that in the case where the rate in one band is 0.0 (i.e., too faint to be detected in this band) the hardness ratio will be -1 or +1 which is only a lower or upper limit, respectively. In cases where the rate in both bands is zero, the hardness ratio is undefined (NULL).

There are four hardness ratios (n) using the following bands:

  HR1:	bands 1 & 2
  HR2:	bands 2 & 3
  HR3:	bands 3 & 4
  HR4:	bands 4 & 5
  

M2_HR4_Error
The uncertainty in the M2 hardness ratio for bands 4 and 5. Errors are the 1-sigma error on the hardness ratio 1 as derived by the SAS task emldetect.

PN_1_Exposure
The PN band 1 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

PN_2_Exposure
The PN band 2 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

PN_3_Exposure
The PN band 3 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

PN_4_Exposure
The PN band 4 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

PN_5_Exposure
The PN band 5 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M1_1_Exposure
The M1 band 1 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M1_2_Exposure
The M1 band 2 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M1_3_Exposure
The M1 band 3 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M1_4_Exposure
The M1 band 4 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M1_5_Exposure
The M1 band 5 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M2_1_Exposure
The M2 band 1 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M2_2_Exposure
The M2 band 2 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M2_3_Exposure
The M2 band 3 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M2_4_Exposure
The M2 band 4 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

M2_5_Exposure
The M2 band 5 exposure map value (s). The exposure maps are made by the SAS task eexpmap; they combine the mirror vignetting, detector efficiency, bad pixels and CCD gaps. The exposure map values in the catalog are given in seconds and are derived by the SAS task emldetect as the PSF weighted mean of the area of the sub-images (radius 60 arcseconds) in the individual-band exposure maps.

PN_1_Bg
The PN band 1 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

PN_2_Bg
The PN band 2 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

PN_3_Bg
The PN band 3 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

PN_4_Bg
The PN band 4 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

PN_5_Bg
The PN band 5 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M1_1_Bg
The M1 band 1 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M1_2_Bg
The M1 band 2 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M1_3_Bg
The M1 band 3 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M1_4_Bg
The M1 band 4 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M1_5_Bg
The M1 band 5 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M2_1_Bg
The M2 band 1 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M2_2_Bg
The M2 band 2 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M2_3_Bg
The M2 band 3 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M2_4_Bg
The M2 band 4 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

M2_5_Bg
The M2 band 5 background map value (ct/pixel). The background maps are made by the SAS task esplinemap; they are made using a 12 x 12 nodes spline fit on the source-free individual-band images. The background map values in the catalog are given in counts per pixel and are derived by the SAS task emldetect as the background map value at the given detection position. Note that the source fitting routine uses the background map itself rather than the single value given here. The value is zero if the detection position lies outside the FOV.

PN_1_Vig
The PN band 1 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

PN_2_Vig
The PN band 2 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

PN_3_Vig
The PN band 3 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

PN_4_Vig
The PN band 4 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

PN_5_Vig
The PN band 5 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M1_1_Vig
The M1 band 1 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M1_2_Vig
The M1 band 2 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M1_3_Vig
The M1 band 3 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M1_4_Vig
The M1 band 4 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M1_5_Vig
The M1 band 5 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M2_1_Vig
The M2 band 1 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M2_2_Vig
The M2 band 2 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M2_3_Vig
The M2 band 3 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M2_4_Vig
The M2 band 4 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

M2_5_Vig
The M2 band 5 vignetting value. The vignetting values in the catalog are derived by the SAS task emldetect; they are a function of energy band and off-axis angle. (Vignetting values used in the source parametrization come from the vignetted exposure maps.)

PN_Ontime
The PN total good exposure time after GTI filtering, in seconds, of the CCD where the detection is positioned. Note that some source positions fall into CCD gaps or outside of the detector and will have therefore a NULL given.

M1_Ontime
The M1 total good exposure time after GTI filtering, in seconds, of the CCD where the detection is positioned. Note that some source positions fall into CCD gaps or outside of the detector and will have therefore a NULL given.

M2_Ontime
The M2 total good exposure time after GTI filtering, in seconds, of the CCD where the detection is positioned. Note that some source positions fall into CCD gaps or outside of the detector and will have therefore a NULL given.

EP_Ontime
The largest total good exposure time after GTI filtering, in seconds, of any of the individual cameras used.

PN_Offax
The distance between the detection position and the on-axis position on the PN detector, in arcminutes. Note that the off-axis angle for a camera can be larger than 15 arcminutes when the detection is located outside the FOV of that camera.

M1_Offax
The distance between the detection position and the on-axis position on the M1 detector, in arcminutes. Note that the off-axis angle for a camera can be larger than 15 arcminutes when the detection is located outside the FOV of that camera.

M2_Offax
The distance between the detection position and the on-axis position on the M2 detector, in arcminutes. Note that the off-axis angle for a camera can be larger than 15 arcminutes when the detection is located outside the FOV of that camera.

EP_Offax
The smallest off-axis angle (the angular distance between the detection position and the on-axis direction) of the individual camera values, in arcminutes.

PN_Maskfrac
The PSF weighted mean of the PN detector coverage of a detection as derived from the detection mask. It depends slightly on energy; only band 8 values are given here which are the minimum of the energy-dependent maskfrac values. Sources which have less than 0.15 of their PSF covered by the detector are considered as being not detected.

M1_Maskfrac
The PSF weighted mean of the M1 detector coverage of a detection as derived from the detection mask. It depends slightly on energy; only band 8 values are given here which are the minimum of the energy-dependent maskfrac values. Sources which have less than 0.15 of their PSF covered by the detector are considered as being not detected.

M2_Maskfrac
The PSF weighted mean of the M2 detector coverage of a detection as derived from the detection mask. It depends slightly on energy; only band 8 values are given here which are the minimum of the energy-dependent maskfrac values. Sources which have less than 0.15 of their PSF covered by the detector are considered as being not detected.

Dist_NN
The distance to the nearest neighbor detection, in arcseconds; it is derived by the SAS task emldetect. Emldetect uses an internal threshold of 6 arcseconds (before positional fitting) for splitting a source into two.

Sum_Flag
The summary flag of the source, derived from the EPIC flag (EP_FLAG, see 2XMM UG Sec. 3.1.2(h) at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#AutFlags and 2XMM UG Sec. 3.2.6 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatVisScreen, but note also sections 3XMM-DR4 UG 3.11 and 3.7 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatVisScreen and http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OOTFlag, respectively). It is 0 if none of the nine flags was set; it is set to 1 if at least one of the warning flags (flag 1, 2, 3, 9) was set but no possible-spurious-detection flag (flag 7, 8); it is set to 2 if at least one of the possible-spurious-detection flags (flag 7, 8) was set but not the manual flag (flag 11); it is set to 3 if the manual flag (flag 11) was set but no possible-spurious-detection flags (flag 7, 8); it is set to 4 if the manual flag (flag 11) as well as one of the possible-spurious-detection flags (flag 7, 8) is set. The meaning is thus:

  0 = good
  1 = source parameters may be affected
  2 = possibly spurious
  3 = located in a area where spurious detection may occur
  4 = located in a area where spurious detection may occur and possibly spurious
  
For details see Sec. 3.2.7 of the 2XMM UG, but note that flag 12 is no longer used in 3XMM-DR4.

EP_Flag
The EPIC flag string made of the flags 1 - 12 (counted from left to right): it combines the flags in each camera (PN_FLAG, M1_FLAG, M2_FLAG), that is, a flag is set in EP_FLAG if at least one of the camera-dependent flags is set.

PN_Flag
The PN flag string made of the flags 1 - 12 (counted from left to right) for the PN source detection. A flag is set to True according to the conditions summarized in Tab. 3.3a of the 2XMM Users Guide for the automatic flags, and in Tab. 3.3b of the 2XMM Users Guide for the manual flags. In cases where the camera was not used in the source detection, a dash is given. In cases where a source was not detected by the PN, the flags are all set to False (default).

M1_Flag
The M1 flag string made of the flags 1 - 12 (counted from left to right) for the M1 source detection. A flag is set to True according to the conditions summarized in Tab. 3.3a of the 2XMM Users Guide for the automatic flags, and Tab. 3.3b of the 2XMM Users Guide for the manual flags. In cases where the camera was not used in the source detection, a dash is given. In cases where a source was not detected by the M1, the flags are all set to False (default).

M2_Flag
The M2 flag string made of the flags 1 - 12 (counted from left to right) for the M2 source detection. A flag is set to True according to the conditions summarized in Tab. 3.3a of the 2XMM Users Guide for the automatic flags, and Tab. 3.3b of the 2XMM Users Guide for the manual flags. In cases where the camera was not used in the source detection, a dash is given. In cases where a source was not detected by the M2, the flags are all set to False (default).

Tseries_Flag
This flag is set to T(rue) to indicate that the source has a time series made in at least one exposure (see Sec. 3.6 of the UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OptSSPExtr).

Spectra_Flag
This flag is set to T(rue) to indicate that the source has a spectrum made in at least one exposure (see Sec. 3.6 of the UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OptSSPExtr).

EP_Chi2prob
The chi2 probability (based on the null hypothesis) that the source, as detected by any of the cameras, is constant. The minimum value of the available camera probabilities (PN_CHI2PROB, M1_CHI2PROB, M2_CHI2PROB) is given.

PN_Chi2prob
The chi2 probability (based on the null hypothesis) that the source as detected by the PN camera is constant. The Pearson's approximation to chi2 for Poissonian data was used, in which the model is used as the estimator of its own variance (see the documentation of ekstest for a more detailed description). If more than one exposure (that is, time series) is available for this source the smallest value of probability was used. See Sec. 3.1.4 of the 2XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#ProcSsp for more details but note also changes described in 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OptSSPExtr.

M1_Chi2prob
The chi2 probability (based on the null hypothesis) that the source as detected by the M1 camera is constant. The Pearson's approximation to chi2 for Poissonian data was used, in which the model is used as the estimator of its own variance (see the documentation of ekstest for a more detailed description). If more than one exposure (that is, time series) is available for this source the smallest value of probability was used. See Sec. 3.1.4 of the 2XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#ProcSsp for more details but note also changes described in 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OptSSPExtr.

M2_Chi2prob
The chi2 probability (based on the null hypothesis) that the source as detected by the M2 camera is constant. The Pearson's approximation to chi2 for Poissonian data was used, in which the model is used as the estimator of its own variance (see the documentation of ekstest for a more detailed description). If more than one exposure (that is, time series) is available for this source the smallest value of probability was used. See Sec. 3.1.4 of the 2XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#ProcSsp for more details but note also changes described in 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#OptSSPExtr.

PN_Fvar
The fractional excess variance measured in the PN timeseries of the detection. Where multiple PN exposures exist, it is for the one giving the largest probability of variability (PN_CHI2PROB). This quantity provides a measure of the amplitude of variability in the timeseries, above purely statistical fluctuations. See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

PN_Fvar_Error
The error on the fractional excess variance for the PN timeseries of the detection (PN_FVAR). See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

M1_Fvar
The fractional excess variance measured in the MOS1 timeseries of the detection. Where multiple MOS1 exposures exist, it is for the one giving the largest probability of variability (M1_CHI2PROB). This quantity provides a measure of the amplitude of variability in the timeseries, above purely statistical fluctuations. See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

M1_Fvar_Error
The error on the fractional excess variance for the MOS1 timeseries of the detection (M1_FVAR). See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

M2_Fvar
The fractional excess variance measured in the MOS2 timeseries of the detection. Where multiple MOS2 exposures exist, it is for the one giving the largest probability of variability (M2_CHI2PROB). This quantity provides a measure of the amplitude of variability in the timeseries, above purely statistical fluctuations. See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

M2_Fvar_Error
The error on the fractional excess variance for the MOS2 timeseries of the detection (M2_FVAR). See Sec. 3.9 of the 3XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#Fvar. This parameter was first introduced in 3XMM-DR4.

Var_Flag
This flag is set to T(rue) if the source was detected as variable (chi2 probability < 1E-5, see PN_CHI2PROB, M1_CHI2PROB, M2_CHI2PROB) in at least one exposure, to F(alse) if the source was tested for variability but did not qualify as such, or to N(ull) or U(ndefined) if there was no timeseries file for the given detection or insufficient points were left in the timeseries after applying background flare GTIs,. See Sec. 3.2.8 of the 2XMM UG at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatVarFlag.

Var_Exp_ID
If the source is detected as variable (that is, if VAR_FLAG is set to T(rue)), the exposure ID ('S' or 'U' followed by a three-digit number) of the exposure with the smallest chi2 probability is given here.

Var_Inst_ID
If the source is detected as variable (that is, if VAR_FLAG is set to T(rue)), the instrument ID (PN, M1, M2) of the exposure given in VAR_EXP_ID is listed here.

SC_RA
The mean Right Ascension in the selected equinox of all detections of the source SRCID, weighted by the positional errors POSERR (called error_radius in this table) values. This was given in J2000.0 decimal degrees in the original table.

SC_Dec
The mean Declination in the selected equinox of all detections of the source SRCID, weighted by the positional errors POSERR (called error_radius in this table) values. This was given in J2000.0 decimal degrees in the original table.

SC_Poserr
The error of the weighted mean position given in SC_RA and SC_DEC, in arcseconds (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Det_ML
The total band detection likelihood of the source SRCID, i.e., the maximum of the likelihoods of all detections of this source (EP_8_DET_ML).

SC_Ep_1_Flux
The mean band 1 flux (0.2 - 0.5 keV) of all the detections of the source SRCID (see EP_1_FLUX) weighted by the errors (EP_1_FLUX_ERROR), in erg/cm2/s.

SC_Ep_1_Flux_Error
The error in the weighted mean band 1 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_2_Flux
The mean band 2 flux (0.5 - 1.0 keV) of all the detections of the source SRCID (see EP_2_FLUX) weighted by the errors (EP_2_FLUX_ERROR), in erg/cm2/s.

SC_Ep_2_Flux_Error
The error in the weighted mean band 2 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_3_Flux
The mean band 3 flux (1.0 - 2.0 keV) of all the detections of the source SRCID (see EP_3_FLUX) weighted by the errors (EP_3_FLUX_ERROR), in erg/cm2/s.

SC_Ep_3_Flux_Error
The error in the weighted mean band 3 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_4_Flux
The mean band 4 flux (2.0 - 4.5 keV) of all the detections of the source SRCID (see EP_4_FLUX) weighted by the errors (EP_4_FLUX_ERROR), in erg/cm2/s.

SC_Ep_4_Flux_Error
The error in the weighted mean band 4 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_5_Flux
The mean band 5 flux (4.5 - 12.0 keV) of all the detections of the source SRCID (see EP_5_FLUX) weighted by the errors (EP_5_FLUX_ERROR), in erg/cm2/s.

SC_Ep_5_Flux_Error
The error in the weighted mean band 5 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_8_Flux
The mean combined band flux (0.2 - 12.0 keV) of all the detections of the source SRCID (see EP_1_FLUX) weighted by the errors (EP_8_FLUX_ERROR), in erg/cm2/s.

SC_Ep_8_Flux_Error
The error in the weighted mean band 8 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Ep_9_Flux
The mean band 9 flux (0.5 - 4.5keV) of all the detections of the source SRCID (see EP_9_FLUX) weighted by the errors (EP_9_FLUX_ERROR), in erg/cm2/s.

SC_Ep_9_Flux_Error
The error in the weighted mean band 9 flux, in erg/cm2/s (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_HR1
The mean hardness ratio of the bands 1 and 2 of all the detections of the Source SRCID (EP_HR1) weighted by the errors.

SC_HR1_Error
The error in the weighted mean hardness ratio of bands 1 and 2 of all the detections (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_HR2
The mean hardness ratio of the bands 2 and 3 of all the detections of the source SRCID (EP_HR2) weighted by the errors.

SC_HR2_Error
The error in the weighted mean hardness ratio of bands 2 and 3 of all the detections (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_HR3
The mean hardness ratio of the bands 3 and 4 of all the detections of the source SRCID (EP_HR3) weighted by the errors.

SC_HR3_Error
The error in the weighted mean hardness ratio of bands 3 and 4 of all the detections (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_HR4
The mean hardness ratio of the bands 4 and 5 of all the detections of the source SRCID (EP_HR4) weighted by the errors.

SC_HR4_Error
The error in the weighted mean hardness ratio of bands 4 and 5 of all the detections (see 2XMM UG, Sec. 3.2.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#CatComb for details).

SC_Extent
The total band extent, i.e., the weighted average of the EPIC extents in the total band of all the detections of the source, in arcseconds.

SC_Ext_ML
The total band detection likelihood of the extended source SRCID, i.e., the largest of the extent likelihoods of all detections of this source.

SC_Chi2prob
The chi2 probability (based on the null hypothesis) that the unique source SRCID as detected by any of the observations is constant, that is, the minimum value of the EPIC probabilities in each detection, EP_CHI2PROB, is given.

SC_Fvar
The fractional excess variance of the unique source. It is the value corresponding to the exposure and instrument that shows the lowest probability of being constant (i.e. it is the PN_FVAR, M1_FVAR or M2_FVAR value corresponding to EP_CHI2PROB, SC_CHI2PROB. This parameter was first introduced in 3XMM-DR4.

SC_Fvar_Error
The error on the fractional excess variance of the unique source. It is the value corresponding to the exposure and instrument that shows the lowest probability of being constant (i.e. it is the PN_FVARERR, M1_FVARERR or M2_FVARERR value corresponding to EP_CHI2PROB, SC_CHI2PROB. This parameter was first introduced in 3XMM-DR4.

SC_Var_Flag
The variability flag for the unique source SRCID which is set to the value of VAR_FLAG for the most variable detection of this source. Note that where a timeseries is not available or insufficient points are left in the timeseries after applying background flare GTIs, the value is set to NULL or U(ndefined).

SC_Sum_Flag
The summary flag for the unique source SRCID is taken to be the worst flag of all detections of this source (SUM_FLAG).

SC_Ep_8_Fmin
The minimum EPIC band 8 flux (EP_8_FLUX), in erg/cm2/s, among any of the constituent detections of the unique source. This parameter was first introduced in 3XMM-DR4.

SC_Ep_8_Fmin_Error
The error on the minimum EPIC band 8 flux (EP_8_FLUX_ERR), in erg/cm2/s, among any of the constituent detections of the unique source. This parameter was first introduced in 3XMM-DR4.

SC_Ep_8_Fmax
The maximum EPIC band 8 flux (EP_8_FLUX), in erg/cm2/s, among any of the constituent detections of the unique source. This parameter was first introduced in 3XMM-DR4.

SC_Ep_8_Fmax_Error
The error on the maximum EPIC band 8 flux (EP_8_FLUX_ERR), in erg/cm2/s, among any of the constituent detections of the unique source. This parameter was first introduced in 3XMM-DR4.

Obs_First
The start date of the earliest observation of any constituent detection of the unique source. This parameter was first introduced in 3XMM-DR4.

Obs_Last
The end date of the last observation of any constituent detection of the unique source. This parameter was first introduced in 3XMM-DR4.

N_Detections
The number of detections of the unique source SRCID used to derive the combined values.

Confused_Flag
This flag parameter is normally set to (F)alse, but is set to (T)rue when a given detection has a probability above zero of being associated with two or more distinct sources. The SRCID is that of the match with the highest probability, but there remains some uncertainty about which source is the correct match for the detection.

High_Background_Flag
The flag is set to True if this detection comes from a field which, during manual screening, was considered to have a high background level which notably impacted on source detection (see Sec. 6.1.2 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/UserGuide_xmmcat.html#HighBkg). This parameter was first introduced in 3XMM-DR4.


Contact Person

Questions regarding the XMMSSC database table can be addressed to the HEASARC User Hotline.

Page Author: Browse Software Development Team
Last Modified: 29-Apr-2015