Register
Login
Resources
Docs Blog Datasets Glossary Case Studies Tutorials & Webinars
Product
Data Engine LLMs Platform Enterprise
Pricing Explore
Connect to our Discord channel
..

README.txt

You have to be logged in to leave a comment. Sign In
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
  1. K2 Full Frame Image Files (FFIs)
  2. The FFIs contain values for every pixel in each of the
  3. operational output channels. Nominally 2 FFIs are taken each
  4. campaign and are used to confirm the proper orientation
  5. of the detector on the sky. The files are stored in FITS
  6. format with each file containing 84 image extensions, that is,
  7. one extension for each channel. Currently 2 of the 21 modules
  8. have failed resulting in 8 channels (i.e., channels 5-8, and
  9. 17-20) containing null values.
  10. See the Kepler Archive Manual for more information on FFIs
  11. at archive.stsci.edu/kepler/manuals/archive_manual.pdf.
  12. Updated information can also be found in the K2 Data Release Notes
  13. (archive.stsci.edu/k2/data_release.html).
  14. The project produces a calibrated FFI file
  15. (e.g., ktwo2014203150825-c01_ffi-cal.fits)
  16. an uncertainty FFI file
  17. (e.g., ktwo2014203150825-c01_ffi-uncert.fits)
  18. and a raw FFI file (e.g., ktwo2017162122209-c14_ffi-orig.fits).
  19. The uncertainty file contains the propagated uncertainties
  20. on the flux for each pixel in the calibrated FFI.
  21. The raw files, which became public in February 2018,
  22. are uncalibrated and do not contain WCS parameters. Later,
  23. the mission provided software that added WCS parameters to
  24. the raw FFIs, which are available as "_ffi-orig2.fits" files.
  25. The only difference between these and the "_ffi-orig.fits" files
  26. should be the updated WCS solution based on the processed FFIs.
  27. Note the raw FFI names change when the calibrated versions
  28. are created. Initially the names do not include the campaign number.
  29. For example, the initial FFI for C15 is kplr2017246053350_ffi-orig.fits
  30. and for C16 they are kplr2017344214411_ffi-orig.fits and
  31. kplr2018030100110_ffi-orig.fits These are the only FFIs now online
  32. for C15 and C16. More documentation should be available soon.
  33. Because the intial calibrated K2 FFIs did not contain the
  34. World Coordinate System (WCS) information, the early K2 campaigns
  35. also have a fourth file type with file names beginning with "wcs-"
  36. (e.g., wcs-ktwo2014070234206-c00_ffi-cal.fits). These files were
  37. produced at MAST by submitting the existing FFI cal files to
  38. astrometry.net (see http://astrometry.net/summary.html). By
  39. detecting recognized stars, astrometry.net is able to produce
  40. the necessary WCS FITS keywords and add them to each FITS extension.
  41. (The WCS values describe the transformation between image coordinates
  42. and sky coordinates and allows one to determine the coordinates of any
  43. object in the image.) These have been moved to the old_release_files/
  44. directory, now that the mission has provided FFIs with WCS for these
  45. older Campaigns.
  46. Starting in July, 2018 the project began reprocessing data from earlier campaigns
  47. starting with Campaign 13. This meant new 'cal' and 'uncert' FFIs. The previous
  48. versions however are saved online in the old_release_files subdirectory.
Tip!

Press p or to see the previous file or, n or to see the next file

Comments

Loading...