search_lightcurvefile (and any other search) can only be used once per run
See original GitHub issueProblem description: I would like to analyze many light curves at once, but apparently I can only search for a target once per python run.
Example:
import lightkurve as lk
lk.search_lightcurvefile('TOI 509.01',mission='TESS').download()
# Do stuff
lk.search_lightcurvefile('TOI 1258.01',mission='TESS').download()
*** ERROR HERE: I/O operation on closed file
Expected behavior:
Find first target --> do what you need to do Find second target … and so on
Environment
- platform: latest windows
- lightkurve version: latest version
- installation method: conda
Issue Analytics
- State:
- Created 3 years ago
- Comments:14
Top Results From Across the Web
Investigation of variable Ap Stars in TESS continuous viewing ...
Abstract. In this work, an investigation of photometric rotational variability of chemically peculiar (CP) stars is conducted.
Read more >A guide to using Windows Search; two alternatives to Windows
These selections will be used when you run another search in the same type of folder [folder types are General items, Documents, Pictures,...
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
@LucaNap Interesting! Thanks for the report. My best guess is that your reinstall may have resulted in a newer version of
astroquery
being installed, which may have resolved the problem. Either way, it’ll be good to keep an eye open for other users reporting this problem.I strongly encourage anyone who also runs into this problem to comment below or open a new issue! 👍
Thanks for the tip!
Fortunately today I had to reinstall anaconda (for different reasons) and suddenly the issue is no longer present in Lightkurve v2.0b3. Since nobody else encountered it in v1.1.3, I think you can close this issue as it was probably linked to a new version of some dependency which has recently been fixed. However if I’ll have time to play with Lightkurve 1.1.3, I’ll let you know if I find this problem again.