Browse
this table...

XMMSSC - XMM-Newton Serendipitous Source Catalog (4XMM-DR9 Version)

HEASARC
Archive

Overview

This table contains the Fourth XMM-Newton Serendipitous Source Catalog, Ninth Data Release, or 4XMM-DR9. 4XMM-DR9 is the fourth-generation catalog of serendipitous X-ray sources from the European Space Agency's (ESA) XMM-Newton observatory, and has been produced as a collaborative project involving the whole XMM-Newton Survey Science Centre (SSC) Consortium on behalf of ESA. It is a complete re-reduction of all of the data taken since the beginning of the mission using the best calibration and software at the time of reprocessing (March 2019). It contains just 962 more observations and 35642 more detections than the preceding 3XMM-DR8 catalog, which was made public in May 2018, but vast improvements to the background model, as well as other calibration have led to an important improvement in source detection, so that the majority of detections in 4XMM-DR9 are clean detections and fewer spurious sources are registered. In addition, 4XMM-DR9 provides spectra and lightcurves for more than 115074 more detections than in 3XMM-DR8 and the pn lightcurves are binned to a much higher resolution compared to 3XMM.

The catalog contains source detections drawn from a total of 11,204 XMM-Newton EPIC observations covering an energy interval from 0.2 keV to 12 keV that were made between 2000 February 1 and 2019 February 26; all datasets included were publicly available by 2018 December 18 but not all public observations are included in this catalog. For net exposure time >= 1 ksec, the total area of the catalog fields is ~ 2,010 deg2 but taking account of the substantial overlaps between observations, the net sky area covered independently is ~1,152 deg2.

The catalog contains 810,795 X-ray source detections above the processing likelihood threshold of 6. These X-ray source detections relate to 550,124 unique X-ray sources, that is, a significant fraction of sources (104,638, 19%) have more than one detection in the catalog (up to 69 repeat observations in the most extreme case).

The catalog distinguishes between extended emission and point-like detections. Parameters of detections of extended sources are only reliable up to the maximum extent measure of 80 arcseconds. There are 76,999 detections of extended emission, of which 17,295 are 'clean' (in the sense that they were not manually flagged).

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 a detection flag and an observation flag as filters to obtain what can be considered a 'clean' sample. There are 633,733 out of 775,153 detections that are considered to be clean (i.e., summary flag < 3).

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 a detection flag and an observation flag (and, possibly, a high background flag) as filters to obtain what can be considered a 'clean' sample. There are 633,733 out of 775,153 detections that are considered to be clean (i.e., summary flag < 3).

For 288,282 detections, EPIC time series and 288521 detections, EPIC lightcurves were automatically extracted during processing, and a chi2-variability test was applied to the time series. 6,696 detections in the catalog are considered variable, within the timespan of the specific observation, at a probability of 10-5 or less based on the null-hypothesis that the source is constant. Of these, 4,957 have a summary flag < 3.

The median flux (in the total photon-energy band from 0.2 - 12 keV) of the catalog detections is ~ 2.3 x 10-14 erg/cm2/s; in the soft energy band (0.2 - 2 keV) the median flux is ~ 5.3 x 10-15, and in the hard band (2 - 12 keV) it is ~ 1.2 x 10-14. About 23% of the sources have fluxes below 1 x 10-14 erg/cm2/s. The flux values from the three EPIC cameras are, overall, in agreement to ~ 10% for most energy bands. The median positional accuracy of the catalog point source detections is generally < 1.7 arcseconds (with a standard deviation of 1.4 arcseconds).

With 4XMM-DR9, the team also releases 4XMM-DR9s, available from HEASARC as XMMSTACK, a new version of the stacked catalog built from 6,604 4XMM-DR9 overlapping observations. 4XMM-DR9s contains 1,329 stacks (or groups). Most of the stacks are composed of 2 observations and the largest has 352. The catalog contains 288,191 sources, of which 218,283 have several contributing observations. Stacking observations allows yet fainter sources to be detected in sky regions observed more than once, increasing the number of detections and uncovering long-term variability on repeatedly observed objects.

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

Table 1: Energy bands used in 4XMM-DR9 processing

The following are the basic energy bands:

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

while these are the broad energy bands:

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

Catalog Bibcodes

2016A&A...590A...1R
2009A&A...493..339W

References

The following is the preferred citation of this version (4XMM-DR9) of the catalog:
    Webb et al. (submitted).
The submitted paper is available here: http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMMv3.pdf

The following is the preferred citation of the 3XMM-DR8 version of the catalog:

    Rosen, Webb, Watson et al. (2016), "The XMM-Newton Serendipitous Survey.
    VII. The Third XMM-Newton Serendipitous Source Catalogue", A&A, 590, A1.

Should you use this catalog for your research and publish the results, please use the acknowledgment:

"This research has made use of data obtained from the 4XMM XMM-Newton Serendipitous Source Catalog compiled by the 10 institutes of the XMM-Newton Survey Science Centre selected by ESA."


Provenance

This HEASARC database table contains the 4XMM-DR9 catalog, released by ESA on 2019 Dec 18, and obtained from the XMM-Newton Survey Science Center Consortium (http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMM_DR9.html). It is also available as a gzipped FITS file: http://heasarc.gsfc.nasa.gov/FTP/xmm/data/catalogues/4XMM_DR9_cat_v1.0.fits.gz. The previous four previous versions of the Serendipitous Source Catalog, 3XMM-DR5, 3XMM-DR6, 3XMM-DR7, and 3XMM-DR8, are also available in the same directory for comparison purposes as the files 3XMM_DR5cat_v1.0.fits.gz, 3XMM_DR6cat_v1.0.fits.gz, 3XMM_DR7cat_v1.0.fits.gz, and 3XMM_DR8cat_v1.0.fits.gz, respectively.

Description

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

The 4XMM-DR9 catalog is the eleventh publicly released XMM-Newton X-ray source catalog produced by the XMM-Newton Survey Science Centre (SSC) consortium. It follows the 1XMM (released in April 2003), 2XMMp (July 2006), 2XMM (August 2007), 2XMMi (August 2008), 2XMMi-DR3 (April 2010), 3XMM-DR4 (July 2013), 3XMM-DR5 (April 2015), 3XMM-DR6 (July 2016) catalogs, 3XMM-DR7 (June 2017) catalogs, and 3XMM-DR8 (May 2018) catalogs. 2XMMp was a preliminary version of 2XMM. 2XMMi and 2XMMi-DR3 were incremental versions of the 2XMM catalog.

While the 4XMM-DR9 catalog is only about 5% larger than the 3XMM-DR8 catalog, the source detection is markedly improved and the team provides spectra and lightcurves for 67% more detections than in 3XMM-DR8. In terms of the number of X-ray sources, combining the 4XMM-DR9 and 4XMM-DR9s catalogs gives a catalog that is similar in size to the Chandra Source Catalog. 4XMM-DR9 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 4XMM-DR9 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 4XMM-DR9 is a superb resource for exploring the variety of the X-ray source population and identifying rare source types.

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

4XMM-DR9 and 4XMM-DR9s are based on the pipeline configurations 18. This pipeline version contains many changes with respect to the pipeline used to make the previous major version of the catalog, 3XMM-DR5. Changes include source spectra and light curves created for pn Timing mode and small window data, source detection on pn small window data, energy dependent Charge Transfer Inefficiencies (CTI) and double event energy corrections applied, time and pattern dependent corrections of the spectral energy resolution of pn data, X-ray loading and rate dependent energy (PHA) and CTI corrections for EPIC pn Timing and Burst modes, binning of MOS spectra changed from 15 eV to 5 eV and filtering with XMMEA_EM, which is a bit-wise selection expression, automatically removing "bad events" such as bad rows, edge effects, spoiled frames, cosmic ray events (MIPs), diagonal events, event beyond threshold, etc, instead of XMMEA_SM (which removed all flagged events except those flagged only as CLOSE_TO_DEADPIX), background regions for EPIC spectra and light curves selected from the same EPIC chip where the source is found, observations of solar system objects processed such that X-ray images and spectra correctly refer to the moving target, pileup diagnostic numbers for EPIC sources included, and footprints for EPIC observations based on combined EPIC exposure maps provided as ds9 region files. Other changes carried out specifically for the production of 4XMM include a revised systematic position error, the modeling of the EPIC background and finer binning of EPIC lightcurves. More information on these changes can be found here and in the paper, Webb et al. submitted.

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


Catalog Properties

The catalog contains source detections drawn from 11,204 XMM-Newton EPIC observations made between 2000 February 1 and 2019 February 26 and which were publicly available by 2019 December 18. Net exposure times in these observations range from < 1000 up to ~130000 seconds (that is, a full orbit of the satellite). Figure 5.1 at http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/Sky-distrib.html shows the distribution of fields on the sky.

The sky area of the catalog observations corrected for field overlaps with effective exposure > 1 ks ~1,052 deg2.

The catalog contains 810,795 X-ray detections with total-band (0.2 - 12 keV) likelihood values >= 6. These are detections of 550,124 unique X-ray sources, that is, 104,638 X-ray sources have multiple detections in separate observations (up to 69 detections). Of the 810,795 X-ray detections, 76999 are classified as extended with 17295 of these being in regions considered to be 'clean' (SUM_FLAG < 1).

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

Note that no attempt is made to flag spurious detections arising from statistical fluctuations in the background. An updated analysis of the false detection rate is presented in the 4XMM catalog paper (Webb et al., submitted, available at http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMMv3.pdf).

Sensitivity and Photometry: Figure 5.4 at http://xmmssc-www.star.le.ac.uk/Catalogue/3XMM-DR4/fig_5.4.html presents, for each of the three cameras, the distributions of flux for energy bands 1 to 5 and also for the combined (EPIC) data. These give an indication of the limiting flux available in the catalogs for each of the bands.

Astrometry: Comparing the astrometry between 3XMM-DR8 and 4XMM-DR9 shows very similar results. A more detailed analysis of these issues are presented in the 4XMM catalog paper (Webb et al., submitted, available at http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMMv3.pdf).


Key Changes in 4XMM-DR9 with Respect to 3XMM-DR8

Data selection: XMM-Newton observations considered for inclusion in the 4XMM-DR9 catalog were those with ODFs available for processing up to 2019 February 26 and which had public release dates up to 2019 December 18. After allowing for a small number of observations which failed in processing for a variety of reasons, 14041 observations were available to make the 4XMM-DR9 catalog. Table 2.1 at http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4xmmdr9_obslist.html gives the list of the final 11,204 observations which are included in the 4XMM-DR9 catalog.

New naming convention for DETID and the SRCID: The procedure for attributing the detection identification number (DETID) and the unique source identification number (SRCID), both being unique to each detection and each unique source respectively, has been modified. Previously, identification numbers were re-computed for each catalog version leading to supplementary columns added to the catalog with the DETID and SRCID from previous releases.

The DETID is now constructed from the OBSID, which always remains the same for an observation, coupled with the source number SRC_NUM (SRC_NUM is the source number in the individual source list for a given observation; Sources are numbered in decreasing order of count rate (i.e. the brightest source has SRC_NUM = 1)) as follows:

       DETID = 1 + OBSID + SRC_NUM
where the '+' sign indicates string concatenation and where SRC_NUM is zero-padded to form a 4 digit number. The SRCID of a unique source is then determined from the first DETID attributed to that source (i.e. in the observation where the source was first detected) and replacing the first digit '1' by '2'.

Despite the new naming convention that aims at preserving SRCID numbers across catalog versions, a certain number of SRCID can disappear from one catalog version to another. This is a normal consequence of the algorithm that groups detections together into unique sources (see section 6 of Rosen et al. 2016). When new data are added and statistics are improved, the algorithm might find a better association of detections into unique sources. As an example, a total of 134 SRCIDs listed in 3XMM-DR7 are absent in 3XMM-DR8.

Missing detections and DETID change: In addition, the pipeline reprocessing of the full public dataset for the 4XMM version of the source catalog led to significant modifications of the detection list. There are 10,214 observations that are common between the 3XMM-DR8 and 4XMM-DR9 catalogs, resulting in 773,241 detections in 3XMM-DR8 and 726,279 detections in 4XMM-DR9. Of these, there are 608,071 point-like detections with a SUM_FLAG <= 1 in 3XMM-DR8 and 607,196 in 4XMM-DR9. However, amongst these observations, there are ~128,000 detections that appear in 3XMM-DR8 that are not matched with a detection in the same observation in the 4XMM-DR9 catalog within a 99.73% confidence region (i.e 2.27 x POSERR). About 67,000 of these were classified as the cleanest (SUM_FLAG <= 1), point-like sources in 3XMM-DR8 -- these are referred to as missing 4XMM detections in what follows. It should be noted that in reverse, there are ~164,000 detections in the 4XMM-DR9 catalog that are in common observations but not matched with a detection in 3XMM-DR8 within 99.73% confidence region, approximately 107,000 of which are classed as being clean and point-like.

This is an expected consequence of the reprocessing which was already encountered in the transition from 2XMM to 3XMM (see Section 8 and Appendix D in Rosen et al. 2016). The number of missing 4XMM detections is consistent with the number of missing 3XMM detections, where there were ~25,700 good detections that appeared in 2XMMi-DR3 that were not matched with a detection in the same observation in the 3XMM-DR5 catalog (Rosen et al. 2016). This amounts to ~4.5% which is of the same order as the number of missing sources in 4XMM (8.3%). The origin of these source discrepancies between the two catalogs are the improvements made to the pipeline and in particular the new background estimation. The majority of the detections present in 3XMM-DR8 that are not present in 4XMM-DR9 are from the lowest maximum likelihoods (see Webb et al. submitted). A small change in the parameters can cause a source with a maximum likelihood close to the cut-off of 6, but none the less slightly above, to have a value slightly below the cut-off and therefore be excluded from the catalog. Conversely, the changes in the pipeline for sources just below the maximum likelihood cut-off of 6 and therefore not in 3XMM-DR8 can mean that they will then have a higher maximum likelihood and be present in 4XMM-DR9. Fewer obviously spurious detections are found in 4XMM-DR9 than in 3XMM-DR8, where the detections found in 4XMM-DR9 and not in 3XMM-DR8 are generally more reliable (higher maximum likelihood).

Systematic position error: The astrometry of the X-ray detections is improved by using the catcorr task to cross-correlate the X-ray detections with the USNO B1.0, 2MASS or SDSS (DR8) optical/IR catalogs. However, where catcorr fails to obtain a statistically reliable result (poscorrok=false), a systematic error of 1.5'' was used to create the 3XMM catalog. To check this value, the team cross-matched SDSS quasars with the detection catalog where poscorrok=false, out to r=30 arcseconds, filtering the latter with SUM_FLAG=0 and EP_EXTENT=0, to keep only the cleanest sample of secure point-like X-ray sources. For more information about what was done, see Webb et al. submitted. The team defined the combined positional error as sigma=(Delta S2 + Delta X2/2)0.5, where Delta X = POSERR and Delta S is the radially-averaged uncertainty in the SDSS positions to which systematic 0.1'' was added in quadrature, and x = r / sigma. The final filtering retained only the 157 QSO-X-ray pairs with x < 5.

The expected probability density distribution of x should follow the Rayleigh distribution P(x) = x exp(-x2). Since this was not the case for the 157 pairs of sources found above, the team added an additional positional uncertainty, sigma, in quadrature, so that the total positional uncertainty is now sigma =(sigma2 + Sigma2)0.5, looking for the value of Sigma that minimizes the difference between the distribution of the x' = r/sigma' and the Rayleigh distribution. The team found Sigma = 1.29 +/- 0.01 arcsec, where the uncertainty (1 sigma) has been calculated by bootstrap with replacement. This value was then used to replace the 1.5 arcsec systematic error when poscorrok=false.

Modeling the EPIC background: For each input image to the source detection, the background is modeled by an adaptive smoothing technique. The method was initially applied to the proto-catalog from overlapping XMM-Newton observations and described by Traulsen et al. 2019. Since the proto-catalog was based on a selection of clean observations, the smoothing parameters were revised for the 4XMM catalogs, which cover observations of all qualities. The three parameters of the smoothing task are the cut-out radius to excise sources, the minimum kernel radius of the adaptive smoothing, and the requested signal-to-noise ratio in the map. Their best values were determined in a three-fold assessment which involved real observations, randomized images, and visual screening.

656 observations were chosen which cover positions of cluster candidates to involve a considerable number of extended and of point-like sources. Their background was modeled using different combinations of the smoothing parameters, and source detection was performed. The number of detections and recovered clusters, and the source parameters of the clusters and point-like detections were compared, opting for a reasonable compromise between total number of detections and potentially spurious content and for reliable fluxes and extent radius of the clusters. The source parameters of point-like detections were largely unaffected by the parameter choice in the tested parameter range.

The optimization was then re-run on ninety observations, in which the background was replaced by a Poissonian randomization. Finally, the two best combinations of smoothing parameters and the previously used spline fit were compared in a blind test. The detection images were inspected in randomized order, so the screeners could not know which source-detection results were based on which background model. The three parts of the assessment confirmed the preference for the adaptive smoothing approach over a spline fit and the final parameters: a brightness threshold for the source cut-out radius of 2 x 10-4 counts arcsec-2, a minimum smoothing radius of 10 pixels (40 arcsec in default image binning), and a signal-to-noise ratio of 12.

Hot areas in the detector plane: Warm pixels on a CCD (at a few counts per exposure) are too faint to be detected as such by the automatic processing, but can either push faint sources above detection level, or create spurious sources when combined with statistical fluctuations. This is an intrinsically random process, not visible over a short period of time, but which creates hot areas when projecting all sources detected over 18 years onto the detector plane.

The team addressed this by projecting all sources onto CCD coordinates PN/M1/M2_RAWX/Y, keeping only sources above the detection threshold with the current instrument alone. In that way, the team could distinguish hot areas coming from different instruments. They proceeded to detect hot pixels or columns in each CCD, using a similar method to the SAS task embadpixfind. For more information see Webb et al. submitted, available at http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMMv3.pdf. Many of warm pixels were not present at the beginning of the mission, and some appear for a short amount of time. So each hot area was tested for variability using revolution number, and the same KS-based algorithm used to detect segments of bright columns, compared to the reference established over all sources on all CCDs and all instruments. This resulted in a revolution interval for each hot area.

Sources on a hot area for a particular instrument and within the corresponding revolution interval are flagged with flag 12. PN hot areas result in 16,503 flagged sources, MOS1 in 6,245 and MOS2 in 1,382 flagged sources. The updated table for the 12 flags is given below:

   1    Low detector coverage; ca_MASKFRAC < 0.5
   2    Near other source; R <= 65 * SQRT (EP_RATE); R(min) = 10", R(max) = 400"
   3    Within extended emission; R <= 3 * EP_EXTENT; R(max) = 200"
   4    Possible spurious extended source near bright source; Flag 2 is set and EP_CTS(min) = 1000 for the causing source
   5    Possible spurious extended source within extended emission; R <= 160" and fraction of rate wrt causing source is 0.4
   6    Possible spurious extended source due to unusually large single-band DET_ML; Fraction of ca_b_DET_ML wrt the sum of all >= 0.9
   7    Possible spurious extended source; At least one of the flags 4, 5, 6 is set
   8    On bright MOS-1 corner or bright low gain PN column
   9    Near bright MOS-1 corner; R<= CUTRAD = 60" of a bright pixel the corner
  10    Detection whose center lies on any masked column or row due OoT and RGA features.
  11    Within region where spurious detections occur; Manual flag
  12    Detection on hot area

Lightcurve generation: Lightcurves are corrected using the SAS task, epiclccorr, to take into account events lost through inefficiencies due to vignetting, bad pixels, chip gaps, PSF and quantum efficiency, dead time, GTIs and exposure. epiclccorr also takes into account the background counts, using the background lightcurve, extracted over the identical duration as the source lightcurve. The time bin size for the pn lightcurves was previously a minimum of 10 s and could be as poorly sampled as tens of thousands of seconds for the faintest sources. To exploit the high time resolution and high throughput of the pn, for 4XMM the pn lightcurve was extracted such that each bin is 20 times the frame time, usually 1.46 s. The binning of the MOS data remains as it was for 3XMM.

Pile up information: As of 4XMM three new columns (PN_PILEUP, M1_PILEUP and M2_PILEUP) are provided, quantifying whether each detection may be affected by pile-up in any instrument. A value below 1 corresponds to negligible pile-up (less than a few % flux loss) while values larger than 10 denote heavy pile-up. Pile-up is dependent on time for variable sources, which is neglect here, but noted that a variable source is more piled-up than a constant one for the same average count rate. Therefore the pile-up level can be viewed as a lower limit. The slight dependence on the source spectrum due to the event grade dependence of pile-up is also neglected.

The pile-up levels are not based on a fit of the full images using a pile-up model (Ballet 1999). For point sources, they are based on the measured count rates reported in the catalog over the full energy band, transformed into counts per frame. The thresholds (at which the pile-up level is set to 1) are set to 1.3 cts/frame for MOS and 0.15 cts/frame for PN.

For extended sources, the pile-up level is based on the measured count rate per CCD pixel at the source position, and therefore refers to the peak brightness, assuming this can be considered uniform at the pixel scale (4.1 arcsec for PN). The threshold is set for all instruments to 5 x 10-3 cts/frame/pixel, such that the flux loss is also a few % when the pile-up level is 1.

Extent maximum likelihood: All detections are tested for their potential spatial extent during the fitting process. The instrumental point-spread function (PSF) is convolved with a beta extent model, fitted to the detection, and the extent likelihood EP_EXTENT_ML is calculated as described by Section 4.4.4 of Watson et al. 2009). A source is classified as extended if its core radius (of the beta-model of the PSF), rc > 6 arcsec and if the extended model improved the likelihood with respect to the point source fit such that it exceeded a threshold of Lext,min = 4. In the 4XMM catalogs, EP_EXTENT_ML is included for all detections, while it was set to undefined for point-like detections in previous catalogs. Lext,min >= 4 indicates that a source is probably extended, whilst negative values indicate a clear preference of the point-like over the extended fit. As in the previous catalog, a minimum likelihood difference of four has been chosen to mark a detection as extended. This threshold makes sure that the improvement of the extended over the point-like fit is not only due to statistical fluctuations but from a more precise description of the source profile.

The stacked catalog: A second independent catalog is compiled in parallel by the XMM-Newton SSC, called 4XMM-DR9s, where the letter 's' stands for stacked. This catalog lists source detection results on overlapping XMM-Newton observations. The construction of the first version of such a catalog, 3XMM-DR7s, is described in Traulsen et al. 2019. The construction of 4XMM-DR9s essentially follows the ideas and strategies described there with a few important changes that are described in full detail in the accompanying paper Traulsen et al. (sub.). The two main changes concern the choice of input observations and event-based astrometric corrections before source detection. Also it was found necessary to perform some visual screening of the detections, whose results are reported in the source catalog.

Observations entering 3XMM-DR7s were filtered rather strictly. Only observations with OBS_CLASS < 2, with all three cameras in full-frame mode, and with an overlap area of at least 20% of the usable area were included. All those limitations were relaxed for the construction of 4XMM-DR9s which resulted in a much larger number of observations to be included and potentially much larger stacks (more contributing observations). Before performing simultaneous source detection on the overlapping observations, individual events were shifted in position using the results from the previous catcorr positional rectification of the whole image processed for 4XMM-DR9. This led to a clear improvement of the positional accuracy in stacked source detection.

All sources found by stacked source detection are listed in 4XMM-DR9s, including those from image areas where only one observation contributes. One may expect some differences between these same sources in 4XMM-DR9 and DR9s, because their input events were treated differently. More information is given in Traulsen et al. (sub.).

4XMM-DR9s is based on 1,329 stacks (or groups) with 6,604 contributing observations. Most of the stacks are composed of 2 observations, the largest has 352. The catalog contains 288,191 sources, of which 218,283 have several contributing observations. Auxiliary data products comprise X-ray and optical images and long term X-ray light curves. Thanks to the stacking process, fainter objects can be detected and 4XMM-DR9s contains more sources compared to the same fields in 4XMM-DR9.


Credits

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

  University of Leicester, UK

  Mullard Space Science Laboratory, University College London, UK

  Max-Planck Institut fúr extraterrestrische Physik, Germany

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

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

  Observatoire Astronomique de Strasbourg, France

  Instituto de Fisica de Cantabria, Santander, Spain
The SSC team are grateful to the XMM-Newton SOC for their support in the catalog production activities.

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


Documentation

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

Watchouts

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

User Guide for 2XMM

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

Catalog Content and Organization

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

It should be pointed out that the SAS used for the bulk reprocessing (for 4XMM) was from manifest pipeline version 18, which is based on SAS 18.

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

The following table gives an overview of the statistics of this catalog in comparison with the 3XMM-DR8 catalog:

                                     4XMM-DR9      3XMM-DR8       Increment

Number of observations                11204         10242             962

Number of 'clean' observations         9441          6496            2945
 (i.e., observation class < 3)
Observing interval                   01-Feb-00     03-Feb-00         1.25 yr
                                     - 24-Feb-19   - 30-Nov-17

Sky coverage, taking overlaps        1152 sq.deg   1089 sq.deg      63 sq.deg
 into account (>=  1ksec exposure)

Number of detections                 810795        775153           35642

Number of 'clean' detections         713966        633733           80233
 (i.e., summary flag < 3)
Number of unique sources             550124        531454           18670

Number of 'cleanest' (summary         17295         12256            5039
flag = 0, not in high-background
fields) extended detections
Number of detections with spectra    288521        173277          115244

Number of detections with timeseries  28828        173207          115074

Number of detections where the         6696          5634             762
probability of timeseries being
constant is  <  1.0E-05

Known Problems and Other Issues

Please refer to http://xmmssc.irap.omp.eu/Catalogue/4XMM-DR9/4XMM_DR9.html#watchouts (the Watchouts section of the 4XMM-DR9 catalog page) for the latest information on 4XMM-DR9 catalog issues.

Parameters

DetID
A unique number which identifies each entry (detection) in the catalog. The DETID numbering assignments in 4XMM-DR9 bear no relation to those in 3XMM-DR4 and earlier but the DETID of the matching detection from the 3XMM-DR4 catalog to the 4XMM-DR9 detection is provided via the DR4_DETID column. See also section above on "Key Changes in 4XMM-DR9 with respect to 3XMM-DR8".

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

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

DR3_DetID
The 2XMMi-DR3 detection identifier of the nearest 2XMMi-DR3 detection that lies within 10 arcseconds of the detection position in 4XMM-DR9.

DR3_DetDist
The distance in arcseconds between the 4XMM-DR9 detection position and the nearest detection (within 10 arcseconds) in the 2XMMi-DR3 catalog.

DR3_SrcDist
The distance in arcseconds between the 4XMM-DR9 unique source position and the nearest unique source (within 10 arcseconds) in the 2XMMi-DR3 catalog.

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

DR4_SrcID
The 3XMM-DR4 source identifier of the nearest unique 3XMM-DR4 source that lies within 10 arcseconds of the 4XMM-DR9 unique source position.

DR4_DetID
The 3XMM-DR4 detection identifier of the nearest 3XMM-DR4 detection that lies within 10 arcseconds of the detection position in 4XMM-DR9.

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

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

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

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

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

ObsID
The XMM-Newton observation identification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

LII
The corrected Galactic Longitude of the detection in degrees.

BII
The corrected Galactic Latitude of the detection in degrees.

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

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

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

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

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

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

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

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

Ccdpn
The PN CCD number in which the detection lies.

PN_RawX
The raw X pixel position of the detection in the PN image.

PN_RawY
The raw Y pixel position of the detection in the PN image.

Ccdm1
The M1 CCD number in which the detection lies.

M1_RawX
The raw X pixel position of the detection in the M1 image.

M1_RawY
The raw Y pixel position of the detection in the M1 image.

Ccdm2
The M2 CCD number in which the detection lies.

M2_RawX
The raw X pixel position of the detection in the M2 image.

M2_RawY
The raw Y pixel position of the detection in the M2 image.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PN_Pileup
The estimate of the pile-up level in EPIC/PN detection. A value below 1 corresponds to negligible pile-up (less than a few % flux loss) while values larger than 10 denote heavy pile-up. See also discussion on "Pile-up information" under the "Key Changes in 4XMM-DR9 with respect to 3XMM-DR8" section above.

M1_Pileup
The estimate of the pile-up level in EPIC/PN detection. A value below 1 corresponds to negligible pile-up (less than a few % flux loss) while values larger than 10 denote heavy pile-up. See also discussion on "Pile-up information" under the "Key Changes in 4XMM-DR9 with respect to 3XMM-DR8" section above.

M2_Pileup
The estimate of the pile-up level in EPIC/PN detection. A value below 1 corresponds to negligible pile-up (less than a few % flux loss) while values larger than 10 denote heavy pile-up. See also discussion on "Pile-up information" under the "Key Changes in 4XMM-DR9 with respect to 3XMM-DR8" section above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

     0 = good
     1 = source parameters may be affected
     2 = possibly spurious
     3 = located in a area where spurious detection may occur
     4 = located in a area where spurious detection may occur and possibly spurious
  
For details see Sec. 3.2.7 of the 2XMM UG and the note above in the "Key Changes in 4XMM-DR9 with respect to 3XMM-DR8" section.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

SC_Extent_Error
The 1-sigma error in the total band extent, in arcseconds.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Contact Person

Questions regarding the XMMSSC database table can be addressed to the HEASARC User Hotline.
Page Author: Browse Software Development Team
Last Modified: Wednesday, 29-Jan-2020 16:36:04 EST