lightkurve should cache its SearchResult object
See original GitHub issueI think lightkurve should somehow cache the SearchResult object, so that if MAST goes down (as it frequently does) or if I’m coding on a plane (as I frequently am) if I run my lk.search_lightcurvefile('NAME')
it still gives me the same result, and .download()
will just fetch the path to the cached file.
This is quite a difficult feature to add, but I think it should be possible.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12
Top Results From Across the Web
lightkurve should cache its SearchResult object #461 - GitHub
I think lightkurve should somehow cache the SearchResult object, so that if MAST goes down (as it frequently does) or if I'm coding...
Read more >Source code for lightkurve.search
The purpose of this class is to provide a convenient way to inspect and download products that have been identified using one of...
Read more >lightkurve.SearchResult.download_all
Location where the data files will be stored. Defaults to “~/.lightkurve-cache” if None is passed. cutout_sizeint, float or tuple, optional.
Read more >Using Light Curve Files with Lightkurve
The search function returns a SearchResult object which has several convenient operations. For example, we can select the fourth data product in the...
Read more >lightkurve.LightCurve.query_solar_system_objects
These objects can move across a target's photometric aperture mask on time scales of hours to ... If True will cache the search...
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
Agreed that the lifetime of the cache would definitely have to be set/configured/checked!
We may have a look into it, time-permitting.
I am going to close this issue for now because the caching of search results is being implemented as an
astroquery
feature, most notably here: https://github.com/astropy/astroquery/pull/1634Depending on how this feature will be implemented inside astroquery, we may or may not have to open a new issue to add support for it inside Lightkurve.
Footnote: as of Lightkurve v1.9.1 the speed of search operations has been increased ten-fold, so anyone who finds this issue because their search operations are slow may want to upgrade to >1.9.1!