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
Better support for reading in non-mission produced lightcurve fits files, e.g. to_fits() or HLSPs #289
Comments
For some clarity: from astropy.io import fits
demo_path = 'http://archive.stsci.edu/hlsps/k2sff/c16/211300000/94805/'\
'hlsp_k2sff_k2_lightcurve_211394805-c16_kepler_v1_llc.fits'
hdus = fits.open(demo_path) yields:
and then:
|
A user can currently do:
|
As part of exporting a custom mask from interact (#265), we have had to decide on a specification for how to save the mask (#264). As part of these issues, we will likely want a way to round-trip the new, saved lightcurves. These |
As of Lightkurve v2.x, the new I believe this issue can be closed! |
A common use case is: "I want to read in a Vanderburg & Johnson K2SFF lightcurve for a given target-of-interest". This High Level Science Product (HLSP) has several special features that sets it apart from a common Kepler-pipeline produced KeplerLightCurve or a custom user-produced LightCurve:
Upon discussion with @christinahedges, we think the best path forward would be:
.from_fits()
reader to support K2SFF data. Alternatively make a custom/standalone K2SFF reader/converter, perhaps inutils
.meta
keyword to the LightCurveCollection class as a catch-all destination for any type of metadata you wish to associate with your LightCurveCollection; thismeta
could store the custom aperture masks. Alternatively, store everything in an HDU extension, as was suggested in How to save custom aperture masks? #264 .I'm not sure about what to do with point
3
above, but in the very least it could be (awkwardly) crammed into themeta
--not great, but something.The mere discussion of support for a specific HLSP presupposes that interacting with HLSPs is a common and desirable operation that lightkurve should support. If we support this HLSP, why not support others?
The text was updated successfully, but these errors were encountered: