-
Notifications
You must be signed in to change notification settings - Fork 58
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
new fits.open_header function, typo fixes and better verbosity #612
Conversation
# Conflicts: # vip_hci/fits/fits.py
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #612 +/- ##
==========================================
+ Coverage 56.02% 57.55% +1.53%
==========================================
Files 67 67
Lines 13446 13461 +15
==========================================
+ Hits 7533 7747 +214
+ Misses 5913 5714 -199
... and 6 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
hello there's a new function in
vip_hci.fits
for only opening FITS headers (open_header
). This is designed to be super lightweight and is a wrapper around a core astropy function with a nice VIP interface. It behaves very similar toopen_fits
but is about 40 times faster to use on an average sized SPHERE data set, depending on your disk speed and file sizes. Good for pipeline use. It allows for opening HDU headers by numbern
or by HDU nameextname
too.I adapted the new try/except in
open_fits
to better catch the specific astropy error it's meant to avoid, rather than potentially hiding something else. This came about because I noticed this try/except doesn't work on SPHERE data that has BZERO/BSCALE/BLANK header keywords as it still opens the file and raises the error later when accessing the hdulist.data containing those keywords. I don't know any way to avoid this and it's uncommon enough to probably not matter. I've also tidied the code and improved the verbosity.Every typo of FWHM has been fixed and bad pixel correction no longer reminds you that ADACS made it lighting fast even if you ask for verbose=False, but we very much appreciate their work and I've added our developer to the authors of that function.
Finally I fixed an upcoming
scipy.ndimage.filter
deprecation