spacer link to MAST page spacer logo image spacer

K2SUPERSTAMP

Cody et al. 2018, RNAAS, 2a, 25
Source code available on GitHub.

Introduction

Description of Data Products

Data Access

Download README


Introduction

One of the epochs from the M35 superstamps.
The K2SUPERSTAMP project consists of image data on four open clusters observed by the NASA K2 Mission. The clusters are M35, M67, Ruprecht 147, and NGC 6530-- the Lagoon Nebula Cluster (referred to here as the Lagoon). While data for these regions were previously released by K2, it consisted of small (~50x50) target pixel file stamps. In this release, the K2SUPERSTAMP team have stitched together all small stamps for each region to create one larger image for every epoch, and subsequently fit a world coordinate system (WCS) solution to each resulting FITS file.

With these products it is now possible to identify any and all stars in these open cluster regions via their right ascension and declination. Most stars that fell across the edge of the target pixel files now have spatially continous data. The data is flux in counts (e-/s), and for M67 and Ruprecht 147 only, it has been background subtracted (background was not estimated by the K2 pipeline for M35 and the Lagoon). Each file corresponds to a single timestamp at the 30 minute long cadence of K2, and may be read in via standard FITS handling programs (e.g. IRAF or Python/astropy). This format enables the production of time series photometry for cluster stars, and the resulting light curves are now being used to study stellar rotation in M35 (Cody et al. 2018, in prep.) and M67 (Giampapa et al. 2018, submitted) as well as pre-main sequence star variability in the Lagoon (Cody et al. 2018, in prep.)

Description of Data Products

The superstamps are sorted into subdirectories based on the cluster name. Each cadence's file name begins with "hlsp_k2superstamp_k2_photometer", followed by this format:

_<c#>-<cluster>-bjd<tstamp>_kepler_v1_image.fits

where:
  • c<#> is the K2 Campaign this superstamp came from, e.g., "c9"
  • <cluster> is the name of the cluster: "lagoon", "m35", "m67", or "ruprecht147"
  • <tstamp> is the BJD time of the mid-point of the epoch
Here's a full filename for one of the Lagoon epochs for reference:
hlsp_k2superstamp_k2_photometer_c9-lagoon-bjd2457572.4362_kepler_v1_image.fits

The images are stored in the first extension, along with a number of header keywords. Many of the keywords are inherited from the target pixel files, and the values are modified where needed to apply to the superstamp. These keywords are described in the Kepler Archive Manaual. The timestamps in the header are defined as follows:

  • DATE-OBS: UTC date and time of the beginning of exposure
  • DATE-END: UTC date and time of the end of exposure
  • TSTART: BJD time of the beginning of exposure
  • TSTOP: BJD time of the end of the exposure
  • MIDTIME: BJD mid-time of the exposure
Note that the RA_OBJ and DEC_OBJ coordinates refer to the center of the superstamp field.

Data Access

Bundles (.tar.gz for each
cluster directory)
cURL or wget scripts
per cluster