-
Notifications
You must be signed in to change notification settings - Fork 25
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
TEST: Table dynamic units #243
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #243 +/- ##
==========================================
+ Coverage 64.78% 64.82% +0.04%
==========================================
Files 103 103
Lines 5688 5695 +7
==========================================
+ Hits 3685 3692 +7
Misses 2003 2003 ☔ View full report in Codecov by Sentry. |
type: string | ||
fits_keyword: TUNIT9 | ||
fits_hdu: EXTRACT1D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs an entry here for SB_VAR_RNOISE (and the increment of later TUNITS to fit). Will the default value (i.e. for the DQ column, which is unitless) be empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for finding the mistake!
The default unit for all of these is None
. If there are columns where units don't make sense (like DQ
) we should consider either:
- setting the unit as
None
in the schema (if this works) - leaving
DQ
out of thespec_table_units
attribute
I'm closing this PR as it's out of date and hopefully served it purpose of demonstrating a way to have dynamic units in JWST. |
Test/example PR to explore/demonstrate dynamic units (with a path towards no FITS_rec usage in jwst) in the context of issue: #240
Based off changes in #242