-
-
Notifications
You must be signed in to change notification settings - Fork 405
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
Add more units to nasa_exoplanet_archive unit mapper #2218
Add more units to nasa_exoplanet_archive unit mapper #2218
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2218 +/- ##
=======================================
Coverage 61.80% 61.80%
=======================================
Files 129 129
Lines 16286 16286
=======================================
Hits 10065 10065
Misses 6221 6221
Continue to review full report at Codecov.
|
6d58a42
to
0bc3021
Compare
@bsipocz - those units should both be base 10 logs. Thanks for noting that. We will relabel to
Sounds good to me! |
right now we parse both of those as log10, hopefully, that assumption stays correct for the future, too. |
This should get rid of the unit related warnings that are turned to errors in the test suite.
@rickynilsson - please do double-check whether all of these are correct. E.g. the column definition table (https://exoplanetarchive.ipac.caltech.edu/docs/API_PS_columns.html) uses both
log
andlog10
units are those indeed both base 10 logs? There is some disagreement with the table that is returned, as e.g. for columnst_logg
the returned unit is'log(cm/s**2)'
while in the definition table it's'log10(cm/s**2)'
. OTOHst_lum
is'log(Solar)'
at both places.I've also slightly modified the warning which may result in more warnings for users (as previously it was one per unit, but now there will be one for each column that has unrecognised units, even if that unit is the same for multiple columns. However, printing the column out helps a lot during debugging to find the column description on the definition page).