LightCurveFiles from tpf.interact lack SAP_FLUX label
See original GitHub issueWe currently can’t use the LightCurveFiles
created by tpf.interact
because the flux extension isn’t readable.
We can fix this by either changing the LightCurveFile
class to be able to read a “FLUX” extension from the fits file, or changing tpf.interact
to output fits files with “SAP_FLUX” as an extension. I think I prefer the second option.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
LightCurveFile Objects - TESS Science Support Center
LightCurveFile Object: Obtained from MAST and contains both SAP flux and PSDCSAP flux. Cadence: The rate at which TESS photometric observations are stored....
Read more >christinahedges's gists · GitHub
Now let's create our two light curves, one with the pipeline aperture and one with the new aperture. tpf.to_lightcurve() creates our SAP flux...
Read more >arXiv:1207.3093v1 [astro-ph.IM] 12 Jul 2012
For each individual Kepler target, light curve files (dis- cussed in Section 4) are accompanied by a TPF. The TPF.
Read more >Metodos do kepler - arXiv:1207 [astro-ph] 12 Jul 2012 Draft ...
Kepler light curve files contain a number of columns containing flux information. Two columns contain simple aperture photometry (SAP) flux with ...
Read more >FDL 2020 Results_Xmas Release - Calameo
Publishing platform for digital magazines, interactive publications and online ... The lack of ground truth and the vast multiplicity of characterized ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My two cents is that the Lightkurve philosophy is to make working with the data as easy as possible, while trusting the user to be smart enough to understand where data comes from and what the algorithms are doing.
I think the implication is to adopt
SAP_FLUX
as the standard extension name for simple aperture photometry, and leave it to the user to understand where the file they are using came from.Closed by #559