[WIP] Adding functionality to read fits files into dictionaries. #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fits products downloaded by
lksearch
have various formats and units. We are building a more generic framework to hold and work with data like this.To interface between the fits files and the new framework, we need a standard way to turn fits files into python objects we can parse.
I'm opening this WIP to show how I think we could do this. The function
get_data_from_hdulist
will:The idea is that this converts any input fits file from the myriad TESS/Kepler/K2 data products (e.g. SPOC, TESS-SPOC, QLP, Eleanor, K2SFF, Everest, TESS-Cut) into something fairly easy to parse.
This does not do any of the checking to see if e.g. there is a flux column or to select which should be the "default" flux column in the event that there is more than one with different names.
This isn't designed to be merged [yet]. This might not be the final home for this functionality.