search

openEXO / cloud-kepler

Cloud Kepler is a cloud enabled Kepler Planet searching pipeline
8 stars 3 forks source link

Ability to examine lightcurve concurrently with dip-blip diagram #44

Closed emprice closed 10 years ago

emprice commented 10 years ago

Based on comment from @peter-r-mccullough in today's meeting. Current progress in that direction is shown in the attached image. screen shot 2014-07-08 at 3 35 10 pm

scfleming commented 10 years ago

Looks like this might be one of the small gaps, and it's fitting as @peter-r-mccullough thought regarding the polynomial picking up on one feature and not the other. This reminds us that we probably want to include a ticket for dealing with data gaps in reasonable ways….

emprice commented 10 years ago

I don't see a gap in this one... The top panel is the light curve and the best-fit polynomial; the bottom panel is the detrended light curve (blue) with the best blip (red) and dip (green).

scfleming commented 10 years ago

Can you plot with the 'ko' option to include data points? I was guessing that sharp vertical line is actually stretched across a small gap…

emprice commented 10 years ago

Oh, I see now. Yeah, that could be a gap of 1 or 2 data points. screen shot 2014-07-08 at 3 53 27 pm

peter-r-mccullough commented 10 years ago

My first attempt at replying to this through the github.

Kostov can help us if we wish to ask him about all the various flags in the Kepler data. I don't know if we're using them or not right now, but we could. You all may already know of these.

In any case, very cool that you've so quickly made this diagnostic tool! Wonderful!

On Tue, Jul 8, 2014 at 3:53 PM, emprice notifications@github.com wrote:

Oh, I see now. Yeah, that could be a gap of 1 or 2 data points. [image: screen shot 2014-07-08 at 3 53 27 pm] https://cloud.githubusercontent.com/assets/3172578/3515837/8bf5cf52-06d9-11e4-9aa5-7ec951fedad2.png

— Reply to this email directly or view it on GitHub https://github.com/openEXO/cloud-kepler/issues/44#issuecomment-48391551.

scfleming commented 10 years ago

This is done and the one remaining issue will be fixed in v1.15.