You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MAST folks are interested in strategies for making sure that we retain rounding/precision in our import process, particularly for floating point values.
One potential issue is that we're reading their data that has been exported from a SQL database (where they're presumably happy with the level of control on their rounding/precision) into a CSV, and converting this string representation again into a float can be lossy.
The catalog providers may have some format or units they can provide to help us in this, but they will vary by catalog. e.g. for Allwise, we see descriptions like ra %11.7f deg (link)
The text was updated successfully, but these errors were encountered:
MAST folks are interested in strategies for making sure that we retain rounding/precision in our import process, particularly for floating point values.
One potential issue is that we're reading their data that has been exported from a SQL database (where they're presumably happy with the level of control on their rounding/precision) into a CSV, and converting this string representation again into a float can be lossy.
The catalog providers may have some format or units they can provide to help us in this, but they will vary by catalog. e.g. for Allwise, we see descriptions like
ra %11.7f deg
(link)The text was updated successfully, but these errors were encountered: