XMM-Newton EPIC 'Blank Sky' Background
This page concerns the XMM-Newton Blank Sky files and related software available for use with XMM-Newton EPIC data.
Blank sky files are constructed using a superposition of pointed observations that have been processed with SAS version 7.1.0.
Please refer to the paper by Carter and Read (A&A 464, p1155, 2007) for further information on the creation of these files.
NOTE: One can now receive user defined tailor-made Blank Sky files via the submission of a XMM-Newton EPIC Background Blank Sky Products Request Form.
This page has been greatly remodelled from previous versions of this page to incorporate the new file delivery system. The previous page, including acess to the pre October 2008 general Blank Sky files can be found here.
Contents:
- Latest updates to these web pages
- XMM-Newton Blank Sky event files
- Request a Blank Sky file
- Creation of the Blank Sky files
- Refilled and unfilled Blank Sky files
- Watchouts
- Threads
- Software
- Blank Sky file properties
- Link to pre October 2008 Blank Sky page
Latest Updates
- Oct-2008: Major reworking of website to incoporate new file delivery system
XMM-Newton Blank Sky event files
This page was produced as a result of work within the XMM-Newton EPIC Background Working Group. A link to the Blank Sky pages produced prior to October 2008 can be found here.When performing detailed XMM-Newton EPIC analysis, a good knowledge of the background is required. Sometimes it may be possible to extract the background from a region close to the particular source one is interested in (using a so-called 'local' background). For a large or extended source however, one may have to extract the background far from the target source (the source may in fact be so extended, that no local background is visible within the field of view). Here, a number of effects can cause the extracted local (off-axis) background to be highly inappropriate in analysing the (normally on-axis located) target source, such as the effective area of the mirrors with off-axis angle, instrumental fluorescence and the spectral response which can depend on the position on the detector. These off-axis effects are corrected in the XMM-Newton EPIC calibration.
The files available via these pages are intended to be used in case of difficulty extracting a suitable background region from a user's observation. A guide to these files and their use can be found below.
Request a Blank Sky file
To receive a tailor made Blank Sky event file, ideally suited to a user's own data, plus associated exposure maps, the user is invited to complete the XMM-Newton EPIC Background Blank Sky Products Request Form. The requested Blank Sky file is created in a semi-automatic manner. As soon as the files are available for download, the user receives an email detailing the location of the files and a summary of the request. We endeavour to produce blank sky files as quickly as possible and contact the sender of the request as soon as the files are available. This process takes approximately three working days. Using this form a user may request a specific instrument-mode-filter combination along with other specifications, such as the requesting of blank sky files within a range of XMM-Newton revolutions, within a certain radius from a pointing direction or within a range of count rates. See the form for more details. A user may wish to receive a refilled event file as opposed to an unfilled event file. Refilled and unfilled event files are described here.Blank Sky files for MOS1 and MOS2 in full-frame mode and PN in both full-frame and extended full frame mode can be requested. Each filter mode combination event file is available. Filters can be thin, medium or thick. For each event file two types of exposure map are also made available: vignetted and non-vignetted. Note that the vignetted maps apply to the energy range 0.2-10 keV.
Creation of the Blank Sky files
The component Blank Sky files that make up the final superimposed delivered Blank Sky files were created from event files processed using SAS 7.1.0. Each individual component file that becomes part of a specific instrument-filter-mode set has undergone source removal and flare-screening. The flare screening is based on the 2XMM PPS background time series files. For MOS they are created for full-field events above 14 keV, and with the selection expression (PATTERN==0) && #XMMEA_22 && ((FLAG & 0x762ba000) == 0), whereas for PN, they are created for full-field, bright-source-excluded all-pattern events between 7 keV and 15 keV. The flare removal that has been used here in the creation of the Blank Sky files (thresholds: 2 counts/s for MOS and 60 counts/s for PN) was based on the very conservative limits suggested by the EPIC instrument teams. A user may therefore wish to undertake some additional flare screening steps when using these files.Refilled and unfilled Blank Sky files
There are two types of background event file; unfilled and refilled. The unfilled event files result from the stacking of event files that have been subjected to various filtering steps, which includes the removal of sources. Therefore proper consideration of the exposure maps is required when using the final event file that applies to a set of combined observations. However, we have developed a method to fill in the source regions that are extracted from each individual observation by sampling events close to the extracted regions and filling the vacated region of the event file, randomising just the spatial coordinates. Adjustments are made for region crossovers and chips edges. This results in smooth event file images and exposure maps. Both types of event file are available here, with corresponding vignetted and non-vignetted exposure maps.
|
|
| On the left is shown an image created from a pn events file with sources removed, and on the right, the image of the events file after the event filling procedure | |
Available Files
To receive a tailor made Blank Sky event file and associated exposure maps, click here.To access the general Blank Sky files as available prior to October 2008 click here.
Watchouts
General watchouts:- Each Blank Sky file is constructed from several different event files, spanning a large range in time over the mission. Date-related and positional-related keywords, for example DATE-OBS, have therefore been removed. A few SAS tasks require date and time stamp keywords. It is recommended that these keywords be added by the user as required. Missing date and time keywords could be e.g. set to that of the user's source spectrum. This can be achieved for example using the FTOOLS viewer/editor fv.
Users should be aware of a few issues when using refilled Blank Sky files:
- The resultant BACKSCAL keyword is found to be set to 1 when a script containing the SAS task attcalc (e.g. Skycast) has been used, followed by the SAS task backscale on a spectrum created from any refilled Blank Sky file. This is due to the SAS tasks backscale and arfgen using detector based coordinates for calculation purposes. In the case of the refilled Blank Sky files, the REFXCRVL and REFYCRVL keywords have been set to zero, which results in the issue when using the Skycast script. To work around this issue, a user may wish to set the REFXCRVL and REFYCRVL keywords of the refilled Blank Sky file to that of their observation file, using the FITS editor fv. Alternatively, users can create a spectrum from the required region but using their observation event file, run backscale on this spectrum and then write the value of the BACKSCAL keyword to the header of the spectrum created from the same region but from the refilled Blank Sky file (e.g. using the FITS editor fv). A third work around is to work entirely in detector (DETX and DETY) coordinates.
- Due to the current method of creation of the refilled blank sky files, some events with particular flags may be positioned within inappropriate areas of an image, e.g. near a chip gap. We are aware of this issue and are looking at several approaches to the problem.
Threads
-
Scaling of Blank Sky exposure maps.
The Blank Sky exposure maps were created in the energy range 200 eV to 10000 eV. However, a user may wish to work in a different energy range. We can recommend the following method to scale the Blank Sky exposure maps for use in any required energy range:
- From the user's dataset create an exposure map in the required band and also create a similar exposure map in the Blank Sky band with pimin set to 200 and pimax set to 10000.
- Next, calculate the ratio map from these two maps (using, for example the FTOOLS task farith), i.e. divide the exposure map in required band by the exposure map in the original 200 - 10000 eV band. It is recommended that you pre-add (FTOOLS, fcarith) a tiny value, e.g. 1e-20, to the 200-10000 eV map to avoid division by zeros.
- Multiply the Blank Sky exposure map by this ratio map to scale the appropriate Blank Sky exposure map to the required energy range.
Software
All related software can be obtained from here.Skycast
Script to cast an XMM-Newton EPIC background dataset (or indeed any EPIC event dataset) onto the sky, at the position given by an input template event dataset (e.g. the event file you are interested in producing a background for).
BGrebinimage2SKY
Projection of Sky maps: A script to rebin and reproject exposure maps (or any DETX/DETY image of any binning) onto the sky to the spatial scale and sky position of a user-input image. This is useful when wanting to work in sky coordinates and to a different spatial scale than e.g. the 4 arcsecond scale used in the production of the exposure maps. This script is a wrapper for a fortran executable and is dependent on the user's operating system.
ghostholes_ind
A script that calls the IDL procedure ghostit_ind.pro to fill in the regions that are extracted from each individual observation (e.g. after using the SAS task regions), by sampling events close to the extracted regions and filling the vacated region of the event file, randomising just the spatial coordinates as used in the creation of the Blank Sky refilled event files. Both the script ghostholes_ind and the IDL procedure ghostit_ind.pro must be downloaded. An EPIC source list file, as created by the SAS task regions and a calibration index file are required to use this script.