benmontet/k2-noise

K2 has a lot of correlated noise. Let's find planets anyway!

k2-noise's Issues

Add ReadTheDocs webhook support for documentation

It should be as simple as following the steps here, but I don't have administrator privelegde's on the repo. Ben, could you please do this?

Here's what the finished product looks like: http://k2-noise.readthedocs.org/en/latest/

Deliver photometric uncertainties

It would be awesome if along with the posterior on the magnitude of the measurement, this procedure also delivered an estimate of the covariance between data points, even something simple. For example it could be something like the amp and length scale of the squared exponential kernel that best characterizes the width of the diagonal band in the covariance matrix. This could give users of the data product a quick sanity check of how much instrumental correlated noise might remain.

Utility routines to download + parse FITS files

This is a prerequisite to #1 and #3. It would be nice to have a general interface (python class?) for

• Downloading the FITS files from MAST
• Loading the FITS files and parsing them into PostageStamp/DataFrame collections

Some links to get started:

• http://keplerscience.arc.nasa.gov/Blog.shtml
• All engineering files here: ftp://archive.stsci.edu/pub/k2/tpf_eng/

License for the repository?

What do ya'll think? MIT? BSD? None?

Get t=0 dataset

In order to start developing and testing model, we need the first frame of many different postage stamps. This can reside as a data product within the repository for ease of processing.

Depends on accomplishing #4 first.

spacecraft orientation over time

Write a routine to use the short-cadence stars (~100) to determine the Euler angles of the CCD as a function of time, alpha(t), beta(t), gamma(t)

In principle, this module can be completely separate from the main DataFrame code, and use some approximations.

WCS magic

Determine minimum necessary knowledge about WCS mapping to go from focal plane coordinates to RA, DEC.

astropy.wcs might have something to say here.

It can handle distortion, too.

What we really want is just a transformation?

Create Sharelatex accounts so we can start writing paperish things.

Minimum "Test" data set

In order to proceed on #3 (short cadence) and the rest of the pipeline (long cadence), we need a minimal "test" data set of images, perhaps 10 PostageStamps, with frames truncated to only a few hours worth of data (~10 integrations).

Once #4 is complete and the DataFrame/PostageStampe object interface is complete, I can store this dataset in the github, or include a script to download it and then generate it for everyone.

Pixel Response Function

I think we agreed that we needed to do some more research into what the "pixel-beam" actually looks like, and whether a two-dimensional Gaussian is actually a reasonable approach.

Questions to answer:

• find references about CCD manufacture
• does the response look anything like a Gaussian?
• if not, what parameterization should we be using?