Kepler selected certain pixels around targeted stars to be downloaded from the spacecraft. These were stored as target pixel files that contain data for each observed cadence. In this tutorial, we will learn how to use Lightkurve to download these raw data, plot them, and understand their properties and units.
It is recommended that you first read the tutorial on how to use Kepler light curve products with Lightkurve. That tutorial will introduce you to some specifics of how Kepler, K2, and TESS make observations, and how these are displayed as light curves. It also introduces some important terms and concepts that are referred to in this tutorial.
Kepler observed a single field in the sky, although not all stars in this field were recorded. Instead, pixels were selected around certain targeted stars. This series of cutouts were downloaded and stored as an array of images in target pixel files, or TPFs. By summing up the amount of light (the flux) captured by the pixels in which the star appears, you can make a measurement of the brightness of a star over time.
TPFs are an important resource when studying an astronomical object with Kepler, K2, or TESS. The files allow us to understand the original images that were collected, and identify potential sources of noise or instrument-induced trends which may be less obvious in derived light curves. In this tutorial, we will use the Kepler mission as the main example, but these tools equally work for TESS and K2.
import lightkurve as lk %matplotlib inline
The target pixel file (TPF) of a star contains an image for each observing cadence, either a 30-minute Long Cadence or one-minute Short Cadence exposure in the case of Kepler. The files also include metadata detailing how the observation was made, as well as post-processing information such as the estimated intensity of the astronomical background in each image. (Read the Kepler Archive Manual, Section 2.3.2 for more information.)
TPFs are stored in a FITS file format. The Lightkurve package allows us to work with these binary files without having to worry about the details of the file structure. For examples on how to work with FITS files directly, read this tutorial on Plotting Images from Kepler Target Pixel Files.
The TPFs of stars observed by the Kepler mission are stored on the Mikulksi Archive for Space Telescopes (MAST) archive, along with metadata about the observations, such as which charge-coupled device (CCD) was used at each time.
Lightkurve's built-in tools allow us to search and download TPFs from the archive. As we did in the accompanying tutorial on light curves, we will start by downloading one quarter (a Kepler observing period approximately 90 days in duration) of Kepler data for the star named Kepler-8, a star somewhat larger than the Sun, and the host of a hot Jupiter planet.
Using the search_targetpixelfile function, we can find an itemized list of different TPFs available for Kepler-8.
search_result = lk.search_targetpixelfile("Kepler-8", author="Kepler", cadence="long") search_result
In this list, each row represents a different observing period. We find that Kepler recorded 18 quarters of data for this target across four years. The
search_targetpixelfile() function takes several additional arguments, such as the
quarter number or the
mission name. You can find examples of its use in the online documentation for this function.
The search function returns a
SearchResult object which has several convenient operations. For example, we can select the fourth data product in the list as follows:
tpf = search_result.download()
This instruction is identical to the following line:
tpf = lk.search_targetpixelfile("Kepler-8", author="Kepler", cadence="long", quarter=4).download()
This file object provides a convenient way to interact with the data file that has been returned by the archive, which contains both the TPF as well as metadata about the observations.
Before diving into the properties of the
KeplerTargetPixelFile, we can plot the data, also using Lightkurve.
%matplotlib inline tpf.plot();
What you are seeing in this figure are pixels on the CCD camera, with which Kepler-8 was observed. The color indicates the amount of flux in each pixel, in electrons per second. The y-axis shows the pixel row, and the x-axis shows the pixel column. The title tells us the Kepler Input Catalogue (KIC) identification number of the target, and the observing cadence of this image. By default,
plot() shows the first observation cadence in the quarter, but this can be changed by passing optional keyword arguments. You can type
help(tpf.plot) to see a full list of those options.
You can also download TPF FITS files from the archive by hand, store them on your local disk, and open them using the
lk.read(<filename>) function. This function will return a KeplerTargetPixelFile object just as in the above example. You can find out where Lightkurve stored a given TPF by typing
Our KeplerTargetPixelFile includes the observation's metadata, loaded from the header of the TPF files downloaded from MAST. Many of these are similar to the metadata stored in the
KeplerLightCurve, which are discussed in the accompanying tutorial.
For example, the first extension ("extension 0") of the file provides metadata related to the star, such as its magnitude in different passbands, its movement and position on the sky, and its location on Kepler's CCD detector:
This is an Astropy
astropy.io.fits.Header object, which has many convenient features. For example, you can retrieve the value of an individual keyword as follows:
When constructing a KeplerTargetPixelFile from a FITS file, Lightkurve carries a subset of the metadata through into user-friendly object properties for convenience, which are available through shorthands (for example,
tpf.quarter). You can view these properties with the the
A new piece of metadata not included in the
KeplerLightCurve objects is the World Coordinate System (WCS). The WCS contains information about how pixel positions map to celestial sky coordinates. This is important when comparing a TPF from a Kepler, K2, or TESS observation to an observation of the same star with a different telescope.
You can access the WCS using tpf.wcs, which is an Astropy WCS object:
For example, you can obtain the sky coordinates for the bottom left corner of the TPF as follows:
Altogether, the metadata contains a lot of information, and you will rarely use it all, but it is important to know that it is available if you need it. For more details and a better overview of all of the metadata stored in a TPF, read the Kepler Archive Manual, specifically:
Finally, we have the most important properties of the TPF: the time and flux information. Just like a
KeplerLightCurve object, we can access the time information as an Astropy
Time object as follows:
The pixel brightness data is available as an Astropy
Quantity object named
This object is a three-dimensional array, where each entry in the array represents one observing cadence. In our example, the flux array is composed of 4116 images, which are 5x5 pixels in size each:
We can access the values of the first 5x5 pixel image as a NumPy array as follows:
At each cadence the TPF has four different flux-related data properties:
tpf.flux: the stellar brightness after the background is removed.
tpf.flux_err: the statistical uncertainty on the stellar flux after background removal.
tpf.flux_bkg: the astronomical background brightness of the image.
tpf.flux_bkg_err: the statistical uncertainty on the background flux.
All four of these data arrays are in units of electrons per second.
Note: for Kepler, the flux background isn't a measurement made using the local TPF data. Instead, at each cadence, the Kepler pipeline fits a model to thousands of empty pixels across each CCD in order to estimate a continuum background across the the CCD. For more details read the Kepler Instrument Handbook, Section 184.108.40.206. In the case of TESS, local background pixels contained within a TPF are used instead.
tpf.flux values seen above have been quality-masked. This means that cadences of observations that violated the
quality_bitmask parameter are removed, and so
tpf.flux represents the data that you probably want to use to do your science. The
quality_bitmask can also be accessed as a property of a
KeplerTargetPixelFile. For specific details on the
quality flags, read the Kepler Archive Manual, Section 220.127.116.11.
If you want to access flux and background flux measurements that have not been quality masked, you can pass a custom
quality_bitmask parameter to the
read() method as follows:
search = lk.search_targetpixelfile("Kepler-8", author="Kepler", cadence="long", quarter=4) tpf = search.download(quality_bitmask=0)
You can see that the flux array of this object now has more cadences (4397) than the original one above (4116):
Alternatively, we can access the unmasked contents of the original TPF FITS file at any time using the
If you use
astropy for published research, please cite the authors. Click the buttons below to copy BibTeX entries to your clipboard.