Browse
this table...

XMMSSC - XMM-Newton Serendipitous Source Catalog (2XMMi DR3 Version)

HEASARC
Archive

Overview

This table contains the Second XMM-Newton Serendipitous Source Catalog, Third Data Release, or 2XMMi-DR3.

2XMMi-DR3 is the latest increment of the second 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. The catalog has 836 more observations and about 64000 (22%) more detections than the preceding 2XMMi catalog, which was made public in August 2008. The processing used to generate the 2XMMi-DR3 catalog is essentially the same as used for 2XMM and 2XMMi and is based on the pipeline developed for the re-processing of all XMM observations conducted in 2006/7.

The catalog contains source detections drawn from a total of 4953 XMM-Newton EPIC observations made between 2000 February 3 and 2009 October 08; all datasets included were publicly available by 2009 October 31 but not all public observations are included in this catalog. The total area of the catalog fields is ~ 814 deg2, but taking account of the substantial overlaps between observations, the net sky area covered independently is ~ 504 deg2.

The catalog contains 353191 X-ray source detections above the processing likelihood threshold of 6. The 353191 X-ray source detections relate to 262902 unique X-ray sources, that is, a significant fraction of sources (41979) have more than one detection in the catalog.

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 30470 detections of extended emission, of which 5770 are 'clean' (i.e., have not received a manual flag).

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 as a filter to obtain what can be considered a 'clean' sample. There are 284270 out of 353191 detections that are considered to be clean (i.e., summary flag < 3), and 2318 out of 4953 fields are considered to have no or at most a couple of spurious detections in them (observation class < 2).

For 56017 detections spectra and time series were automatically extracted during processing, and a chi2-variability test was applied to the time series. 3177 detections in the catalog are considered variable at a probability of 10-5 or less based on the null-hypothesis that the source is constant.

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

Though the 2XMMi-DR3 catalog is a catalog of serendipitous sources, the observations from which it has been compiled are pointed observations with one or more targets. An analysis to identify the target of each observation and to classify the contents of the field with regard to its serendipity has been carried out. In about 62% of the cases, one or (occasionally) more detections could be directly identified with the target of the observations.

New energy bands were used in the 2XMM processing (2XMM, 2XMMi and 2XMMi-DR3) compared to 1XMM. The following are the basic energy bands:

1       =       0.2 -   0.5 keV
2       =       0.5 -   1.0 keV                 (formerly part of band 2)
3       =       1.0 -   2.0 keV                 (formerly part of band 2)
4       =       2.0 -   4.5 keV                 (formerly band 3)
5       =       4.5 -  12.0 keV                 (formerly bands 4 and 5)

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

Catalog Bibcode

2009A&A...493..339W

References

The production and content of the 2XMM catalog is described in detail in Watson et al. (2008). Note that there are no differences in the processing between the 2XMM and 2XMMi observations. The following is the preferred citation of this 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 2XMMi-DR3 catalog, released by ESA on 2010 April 28, and obtained from the XMM-Newton Survey Science Center (http://xmmssc-www.star.le.ac.uk). It is also available as a gzipped FITS file: http://heasarc.gsfc.nasa.gov/FTP/xmm/data/catalogues/2XMMiDR3cat_v1.0.fits.gz. The previous versions of the Serendipitous Source Catalog, 1XMM, 2XMMp, 2XMM, and 2XMMi, are also available in the same directory for comparison purposes in the files ssc_xmmcat_v1.1.0.fits.gz, ssc_2xmmpcat_v1.0.fits.gz, 2XMMcat_v1.0.fits.gz, and 2XMMicat_v1.1.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 2XMMi-DR3 catalog is the fifth publicly released XMM X-ray source catalog produced by the XMM Survey Science Centre (SSC) consortium. It follows the 1XMM (released in April 2003), 2XMMp (July 2006), 2XMM (August 2007) and 2XMMi (August 2008) catalogs: 2XMMp was a preliminary version of 2XMM. 2XMMi and 2XMMi-DR3 are incremental versions of the 2XMM catalog.

With this increment catalog, for the first time, as part of the catalog naming convention we introduce the concept of a data release (DR) as a means of distinguishing between increments - see version definitions at http://xmmssc-www.star.le.ac.uk/Catalogue/index_devel.html#CatVers . In this scheme, 2XMM is considered as DR1, 2XMMi as DR2 and the present catalog as DR3.

The 2XMMi-DR3 catalog is about 22% larger than the 2XMMi catalog, which it supersedes, due to the ~1.5-year longer baseline of observations included. As such, it is the largest X-ray source catalog ever produced, containing more than twice as many discrete sources as either the ROSAT survey or pointed catalogs. 2XMMi-DR3 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 2XMMi-DR3 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 2XMMi-DR3 is a superb resource for exploring the variety of the X-ray source population and identifying rare source types.

The production of the 2XMMi-DR3 catalog has been undertaken by the XMM-Newton SSC consortium in fulfilment of one of its major responsibilities within the XMM-Newton project. The catalog production process has been designed to exploit fully 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 earlier 2XMM catalog was made from a subset of public observations emerging from a re-processing (in 2006/7) of all XMM observations made prior to that point. The first increment, 2XMMi, included a further 626 observations. These came from a) observations from the re-processing that had been proprietary at the time of the 2XMM release but which subsequently became public before 01 May 2008 and b) 90 observations that had been processed as part of the routine, day-to-day XMM data processing performed by the SSC, after the 2006/7 re-processing and which were also public at 01 May 2008. The processing pipeline used for the latter was essentially identical to that used for the re-processing.

The new 2XMMi-DR3 catalog augments the 2XMMi data with a further 836 observations, 89 of which come from the 2006/7 re-processing and were public by 31 October 2009. The bulk of the extra data are from suitable observations from the more recent routine day-to-day pipeline processing operations which were also public by 31 October 2009. It should be noted that 14 observations (675 detections) in the 2XMMi-DR3 catalog come from day-to-day processings performed since 15 April 2009 using a pipeline in which newer energy conversion factors (ECFs) are used in converting count rates to fluxes than were used for 2XMM/2XMMi (see Sec 6.2.1 and Sec 6.2.2 of the User Guide at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi-DR3/UserGuide_xmmcat.html#ProblECFs ). The largest change in ECF is approximately 8% and affects the MOS1 and MOS2 band 1 fluxes when observing with the THICK filter. Otherwise the changes in the ECFs are < 5%.

Users of the 2XMMi-DR3 catalog should note that every detection in 2XMM and 2XMMi appears in 2XMMi-DR3 with the same detection identifier, DETID. New detections have DETID values > 289084. In general the 2XMM and 2XMMi unique source identifiers, SRCID, have also been preserved but in a small number of cases, detections from 2XMM or 2XMMi sources were regrouped and, in rare cases (essentially restricted to complex regions), sources from 2XMM or 2XMMi no longer appear in 2XMMi-DR3, being replaced by new sources comprised of different arrangements of detections (see Sec 3.2 of the User Guide (UG) at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi-DR3/UserGuide_xmmcat.html#DiffUniqueId ). Since detections can occasionally be allocated to a different source in the 2XMMi-DR3 catalog, earlier SRCID values can disappear but they are not reallocated so that gaps in the SRCID sequence can occur. The 2XMMi-DR3 catalog provides information that indicates where changes have occurred.


Credits

The production of the 2XMM catalog is a collaborative project involving the whole SSC Consortium:
    University of Leicester, UK

    Mullard Space Science Laboratory, University College London, UK

    Institute of Astronomy, Cambridge, UK

    Max-Planck Institut fuer extraterrestrische Physik, Germany

    Astrophysikalisches Institut Potsdam, Germany

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

    Centre d'Etude Spatiale des Rayonnements, Toulouse, France

    Observatoire Astronomique de Strasbourg, France

    Instituto de Fisica de Cantabria, Santander, Spain

    Osservatorio Astronomico di Brera, Milan, Italy

The SSC team is pleased to acknowledge the contributions to the SAS software, on which the catalog processing is based, made by ESA's Science Operations Centre staff. Significant contributions to the production of the catalog were also made by NASA Goddard Space Flight Centre HEASARC staff resident for much of the project at the University of Leicester.


Documentation

The User Guide for the 2XMMi-DR3 Catalog, available at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi-DR3/UserGuide_xmmcat.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, as well as the list of observations used in the catalog at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi-DR3/xcat_summary.html .

Differences and Additions of 2XMMi-DR3 with respect to the 2XMMi Catalog

The selection of XMM-Newton observations for inclusion in the 2XMMi-DR3 catalog follows the same guidelines as for the 2XMM and 2XMMi catalogs but with a new cut-off for the public release date: All observations that have a public release date prior to 2009 October 31 were eligible for inclusion. The table at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi-DR3/xcat_summary.html gives the list of the final 4953 observations (3491 from 2XMM, 626 from 2XMMi and 836 new) which are included in the 2XMMi-DR3 catalog.

The details of the procedure used for matching detections in to unique sources on the sky is described in the 2XMM UG, Sec. 3.2.3 a) at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMM/UserGuide_xmmcat.html#UniqueId . For 2XMMi, essentially the same process was adopted, albeit with a small correction but it was necessary to consider the impact of merging the new detections available for 2XMMi with the ones already in 2XMM. This was explained in the 2XMMi UG, Sec. 3.2.1 a) at http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi/UserGuide_xmmcat.html#DiffReMatch . As noted above, this process can result in a change of the unique source to which a previous detection is allocated. For 2XMMi-DR3, we have adopted essentially the same mechanism for merging detections, allowing the detections to be grouped from scratch. However, we describe below some alterations to the way in which such changes are flagged in the 2XMMi-DR3 catalog.

The process of finding the set of detections which appear to come from the same source and thus have a single SRCID number is simple and unambiguous in most of the sky. However, in a few areas, for example in ridges of extended emission or in shells around SNRs, the detection-matching process produces results which are occasionally unstable in the sense that minor changes to the parameters of the algorithm produce slightly different matches.

In addition, the inclusion of new detections in the catalog can lead to cases where previous sources can be coalesced or a single source can fragment. In either case, or in cases where a new detection simply joins an existing unique source, the parameters of the unique source can be modified.

In 2XMMi, two flags were introduced, SC_CHFLAG1 (see http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi/col_unsrc.html#scchflag1 ) and SC_CHFLAG2 (see http://xmmssc-www.star.le.ac.uk/Catalogue/2XMMi/col_unsrc.html#scchflag2 ), to signify the detailed nature of such changes. In 2XMMi-DR3 this useful but somewhat complicated flagging scheme is replaced by a simpler concept. In 2XMMi-DR3, we utilize the following two flags:

i) SC_DR_FIRST signifies the data release of the catalog in the 2XMM series in which the source with this SRCID first appeared (DR1 represents 2XMM, DR2 represents 2XMMi and DR3 represents 2XMMi-DR3). Note that where SC_DR_FIRST = DR1, the IAU name retains the 2XMM prefix, whereas if SC_DR_FIRST = DR2 the IAU name prefix is 2XMMi and it is also 2XMMi when SC_DR_FIRST = DR3;

ii) SC_DR_LAST signifies the data release of the catalog in the 2XMM series in which the source with this SRCID was last updated in any way.

In 2XMMi-DR3 we also introduce another new flag which indicates where there is uncertainty about which unique source a detection is assigned to. The CONFUSED_FLAG value is set true for a unique source if any detections that comprise it overlap with another unique source. This is taken to be the case if the 3 sigma positional error (3 * SC_POSERR) of the detection overlaps the corresponding 3 sigma positional error of any other unique source (which is located within 7 arc-seconds of it).

Note that the only changes in the catalog parameters refer to the unique source identification (SRCID), source (SC_* ) parameters and IAUNAME. All parameters referring to an observation or adetection remain unchanged.

A consequence of the fact that detections can be re-grouped during the matching procedure is that 170 sources in 2XMMi do not appear in 2XMMi-DR3 and 438 sources from 2XMM are absent from 2XMMi-DR3 but the detections are still present with different SRCID values. The SRCID_2XMMi parameter can be used to find the original 2XMMi source ID for detections from the 170 sources from 2XMMi that are not in 2XMMi-DR3.

An IAU-styleidentification, NAME, has been assigned to each unique source (SRCID) based upon the IAU registered classifications 2XMM and 2XMMi: a source that is included in the 2XMM catalog has kept its 2XMM IAU identification; a source that appeared for the first time in 2XMMi retains its 2XMMi IAU identification; all new sources in 2XMMi-DR3 are also assigned an IAU name with a 2XMMi prefix. The form of the IAU names is "2XMM Jhhmmss.sSddmmss" or "2XMMi Jhhmmss.sSddmmss" where hhmmss.s is taken from the averaged and eposcorr-corrected right ascension coordinate given in the column RA and Sddmmss is the averaged and eposcorr-corrected declination taken from the column DEC of the respective catalog. Note that the averaged coordinates may have changed with respect to 2XMM but the IAU name with the 2XMM prefix will be the same as in the 2XMM catalog. The situation is similar for sources in the 2XMMi catalog where the 2XMMi-prefixed IAU name is maintained.

The correct nomenclature for references to detections in the catalog is the NAME followed by a colon and the detection identification number DETID (with six digits), that is: "2XMM Jhhmmss.sSddmmss:detid" and "2XMMi Jhhmmss.sSddmmss:detid".

The distribution of the six observation classes has slightly changed with respect to 2XMM and 2XMMi due to the continued trend of increasing occurences of 'noisy' CCDs (mainly CCD 4 of MOS1 and CCD 5 of MOS 2) in the more recent observations. The table below lists the observation class, the fractional area of exclusion with respect to the total detection area, and the percentage of observations affected for the 2XMMi-DR3, 2XMMi and 2XMM catalogs as well as for the new observations:

Table: Distribution of observation class for the 836 new observations and for
the overall observation sets used in the 2XMMi-DR3, 2XMMi and 2XMM catalogs

Obs class 'bad' area         New     2XMMi-DR3  2XMMi     2XMM
          fraction       observations

0         0% area            26%       35%       37%       38%
1         0% < area < 0.1%   10%       12%       12%       12%
2         0.1% <= area < 1%  12%       10%       9%        10%
3         1% <= area < 10%   35%       28%       26%       25%
4         10% <= area < 100% 15%       12%       11%       10%
5         100%                3%        4%        5%        5%

Total no. of observations    836      4953      4117      3491

Parameters

Detid
A consecutive number which identifies each entry (detection) in the catalog.

SrcID
A unique number assigned to a group of catalog entries which are assumed to be the same source. To identify members of the same group the distance in arcseconds between each pair of sources was compared on the two-sigma level of both positional errors. A maximum distance of 7" was assumed, which was reduced to 0.9 * DIST_NN (distance to the nearest neighbour) where necessary.

Srcid_2xmmi
The 2XMMi SRCID unique source identifier where a source has a match with an existing 2XMMi source. Due to the nature of the matching algorithm, there are cases where the new SRCID differs from the previous one.

Name
The IAU designation assigned to the unique SRCID. An IAU-styleidentification, NAME, has been assigned to each unique source (SRCID) based upon the IAU registered classifications 2XMM and 2XMMi: a source that is included in the 2XMM catalog has kept its 2XMM IAU identification; a source that appeared for the first time in 2XMMi retains its 2XMMi IAU identification; all new sources in 2XMMi-DR3 are also assigned an IAU name with a 2XMMi prefix. The form of the IAU names is "2XMM Jhhmmss.sSddmmss" or "2XMMi Jhhmmss.sSddmmss" where hhmmss.s is taken from the averaged and eposcorr-corrected right ascension coordinate given in the column RA and Sddmmss is the averaged and eposcorr-corrected declination taken from the column DEC of the respective catalog. Note that the averaged coordinates may have changed with respect to 2XMM but the IAU name with the 2XMM prefix will be the same as in the 2XMM catalog. The situation is similar for sources in the 2XMMi catalog where the 2XMMi-prefixed IAU name is maintained.

Src_Num
The decimal source number in the individual source list for this observation; in hexadecimal it identifies the source-specific product files belonging to this detection.

ObsID
The XMM-Newton observation identification.

XMM_Revolution
The XMM-Newton revolution number of the observation.

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

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), 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), 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 source catalog using the SAS task eposcorr. 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 coordinates 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 source catalog using the SAS task eposcorr. 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 Declination was given in J2000 coordinates 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_ERR and the systematic error SYSERR as follows:

            POSERR = SQRT (RADEC_ERR2 + SYSERR2)
  

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.

Syserr
The estimated systematic 1-sigma error in the detection position in arcseconds. It is set to be 0."35 if the SAS task eposcorr results in a statistically reliable cross-correlation with the USNO B1.0 optical catalog, otherwise the error is set to 1."0.

RA_Unc
The J2000 Right Ascension of the detection in degrees, as determined by the SAS task emldetect by fitting a detection simultaneously in all cameras and energy bands.

Dec_Unc
The J2000 Declination of the detection in degrees, as determined by the SAS task emldetect by fitting a detection simultaneously in all cameras and energy bands.

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. 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, etc.).

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. 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, etc.).

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. 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, etc.).

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. 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, etc.).

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. 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, etc.).

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. 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, etc.).

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. 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, etc.).

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.

PN_1_Flux_Error
The uncertainty in the PN band 1 flux (erg/cm2/s).

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.

PN_2_Flux_Error
The uncertainty in the PN band 2 flux (erg/cm2/s).

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.

PN_3_Flux_Error
The uncertainty in the PN band 3 flux (erg/cm2/s).

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.

PN_4_Flux_Error
The uncertainty in the PN band 4 flux (erg/cm2/s).

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.

PN_5_Flux_Error
The uncertainty in the PN band 5 flux (erg/cm2/s).

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 and errors from each band (1 - 5).

PN_8_Flux_Error
The uncertainty in the PN combined band flux (erg/cm2/s).

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.

PN_9_Flux_Error
The uncertainty in the PN band 9 flux (erg/cm2/s).

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.

M1_1_Flux_Error
The uncertainty in the M1 band 1 flux (erg/cm2/s).

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.

M1_2_Flux_Error
The uncertainty in the M1 band 2 flux (erg/cm2/s).

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.

M1_3_Flux_Error
The uncertainty in the M1 band 3 flux (erg/cm2/s).

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.

M1_4_Flux_Error
The uncertainty in the M1 band 4 flux (erg/cm2/s).

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.

M1_5_Flux_Error
The uncertainty in the M1 band 5 flux (erg/cm2/s).

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 (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).

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.

M1_9_Flux_Error
The uncertainty in the M1 band 9 flux (erg/cm2/s).

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.

M2_1_Flux_Error
The uncertainty in the M2 band 1 flux (erg/cm2/s).

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.

M2_2_Flux_Error
The uncertainty in the M2 band 2 flux (erg/cm2/s).

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.

M2_3_Flux_Error
The uncertainty in the M2 band 3 flux (erg/cm2/s).

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.

M2_4_Flux_Error
The uncertainty in the M2 band 4 flux (erg/cm2/s).

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.

M2_5_Flux_Error
The uncertainty in the M2 band 5 flux (erg/cm2/s).

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 (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).

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.

M2_9_Flux_Error
The uncertainty in the M2 band 9 flux (erg/cm2/s).

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. Combined band count rate (band 8) for each camera are 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 subimages 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 subimages 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 subimages 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 subimages 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.

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 (arcsec). 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 fitting a beta-model profile to the source PSF. 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" has been introduced.

EP_Extent_Error
The uncertainty in the EPIC extent radius (arcsec).

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. It is determined fitting a beta-model profile to the source PSF. 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" has been introduced. 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 case 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 characterise 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 case 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 characterise 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 case 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 characterise 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 case 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 characterise 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 case 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 case 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 case 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-sigmaerror 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 case 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 case 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 case 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 case 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 case 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 case 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 case 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 case 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 case 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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 subimages (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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 offaxis 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 the 3 EPIC instruments (PN, M1 and M2).

PN_Offax
The distance between the detection position and the on-axis position of PN detector, in arcminutes. Note that the offaxis 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 of M1 detector, in arcminutes. Note that the offaxis 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 of M2 detector, in arcminutes. Note that the offaxis 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 3 EPIC instruments (PN, M1 and M2), 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 arseconds; it is derived by the SAS task emldetect. Emldetect uses an internal threshold of 6 arseconds (before positional fitting) for splitting a source into two.

Sum_Flag
The summary flag of the source, derived from the EPIC flag (EP_FLAG). 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
  

EP_Flag
The EPIC flag string made of the flags 1 - 12 (counted from left to right), where flag 10 is not used: 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). Flag 10 is not used.

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). Flag 10 is not used.

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). Flag 10 is not used.

Tseries
This flag is set to T(rue) to indicate that the source has a time series made in at least one exposure.

Spectra
This flag is set to T(rue) to indicate that the source has a spectrum made in at least one exposure.

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.

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.

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.

Var_Flag
This flag is set to T(rue) if this source was detected as variable (chi2 probability < 1E-5, see PN_CHI2PROB, M1_CHI2PROB, M2_CHI2PROB) in at least one exposure).

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 J2000 Right Ascension of all detections of the source SRCID, in degrees, weighted by the positional errors ERROR_RADIUS values.

SC_Dec
The mean J2000 Declination of all detections of the source SRCID, in degrees, weighted by the positional errors ERROR_RADIUS values

SC_Poserr
The error of the weighted mean position given in SC_RA and SC_DEC, in arcseconds.

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.

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, in erg/cm2/s.

SC_Ep_1_Flux_Error
The error in the weighted mean band 1 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_2_Flux_Error
The error in the weighted mean band 2 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_3_Flux_Error
The error in the weighted mean band 3 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_4_Flux_Error
The error in the weighted mean band 4 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_5_Flux_Error
The error in the weighted mean band 5 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_8_Flux_Error
The error in the weighted mean band 8 flux, in erg/cm2/s

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, in erg/cm2/s.

SC_Ep_9_Flux_Error
The error in the weighted mean band 9 flux, in erg/cm2/s

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.

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.

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.

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.

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

SC_Ext_ML
The total band detection likelihood of the extended source SRCID, i.e., the average 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_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.

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_Dr_First
This parameter signifies the data release of the catalog in the 2XMM series in which the source with this SRCID first appeared (DR1 represents 2XMM, DR2 represents 2XMMi and DR3 represents 2XMMi-DR3). Note that where SC_DR_FIRST = DR1, the IAU name retains the 2XMM prefix, whereas if SC_DR_FIRST = DR2 the IAU name prefix is 2XMMi and it is also 2XMMi when SC_DR_FIRST = DR3;

SC_Dr_Last
This parameter signifies the data release of the catalog in the 2XMM series in which the source with this SRCID was last updated in any way.

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

Confused_Flag
This boolean flag [T/F] parameter is set to true for a unique source if any detections that comprise it overlap with another unique source. This is taken to be the case if the 3-sigma positional error (3 * SC_POSERR) of the detection overlaps the corresponding 3 sigma positional error of any other unique source (which is located within 7 arc-seconds of it).


Contact Person

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

Page Author: Browse Software Development Team
Last Modified: 28-Aug-2012