Skip to content
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

Fitsio issues #7

Open
astrobel opened this issue Aug 19, 2024 · 2 comments
Open

Fitsio issues #7

astrobel opened this issue Aug 19, 2024 · 2 comments

Comments

@astrobel
Copy link

Hi! I had trouble installing lkprf due to fitsio - I run Linux, and the issue is in how my Anaconda set-up speaks to my C backend (this is a known issue). I was able to use one of the workarounds suggested in the linked thread and get everything installed, but I have a student who is currently unable to install fitsio and lkprfon a Windows machine, where Conda issues are harder to diagnose.

To this end, I was wondering what the reason is for using fitsio instead of Astropy FITS handling? Regular Lightkurve uses Astropy for FITS and seems fine - there are parts of Astropy that interface with C, but I've never had any trouble installing or using it, and it seems like they're actively developing to keep up with gcc updates, etc.

Thanks!

@Nschanche
Copy link
Collaborator

Hi @astrobel, we went with fitsio to keep the requirements for this package as slim as possible. Adding an astropy dependency can add extra complications we were trying to avoid. However, we were unaware of the install issues for Windows systems. We will look into whether we can find a solution to make the install smoother.

In the meantime, I suggest your student may be interested in checking out TIKE. This is MAST's new virtual jupyter platform. This platform has pre-made TESS-friendly environments, relieving a lot of the install and setup burdens for students. We have tested this with lkprf successfully. Using this service is free, it just requires an StSci account.

@astrobel
Copy link
Author

astrobel commented Sep 3, 2024

Thanks @Nschanche, I appreciate the explanation!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants