-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mismatch between output file format and documentation #9
Comments
Hi, is this still an ongoing issue? I'm trying to run the code on a recent campaign, and am noticing that the "detrended" flux usually has a lot of signal in it - I initially thought the detrending was failing, but it might actually be this issue. |
Hi Stephanie
I'm afraid so! We need to update the readme ! In the k2sc output files the
flux column is the raw (input) flux, while trposi and trtime are the
position dependent (systematics) and time dependent (variability) parts of
the model. To get a systematics corrected light curve subtract trposi from
flux (you may wish to remove the median of trposi first). To get a
detrended light curve also subtract trtime.
Cheers
Suzanne
…On Tue, 29 May 2018, 18:22 Stephanie Douglas, ***@***.***> wrote:
Hi, is this still an ongoing issue? I'm trying to run the code on a recent
campaign, and am noticing that the "detrended" flux usually has a lot of
signal in it - I initially thought the detrending was failing, but it might
actually be this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AACgOWZoBZ6QRcwPsVcySDr-1HRaAEh-ks5t3YPigaJpZM4J7pVz>
.
|
Hi Suzanne, OK, thanks for the info! I'll update my code for the new outputs. Cheers, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The documentation says the FLUX column in the output files is the K2SC-detrended flux, but as things stand at the time of creating this issue it is actually a copy of the input flux. We should update the documentation or modify the writer in k2io.py (I vote for the former).
The text was updated successfully, but these errors were encountered: