-
Notifications
You must be signed in to change notification settings - Fork 0
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
MJD in database for legacy data is incorrect #53
Comments
Could you show an example of some of the rows? This may only be an issue for certain types of rows in the DB. The basic data reduction tutorial shows that the MJD values are good for at least some of the rows. @JohnGood might be able to comment further about what rows might not have good values in all columns. |
search_string = "select DATE, OBTYPE, FILENAME, TARGET, MJD, BJD from FILES where TARGET like 'HD185144';" url = state.search(sql=search_string)
|
search_string = "select DATE, OBTYPE, FILENAME, TARGET, MJD, BJD from FILES where TARGET like 'HD19773';" url = state.search(sql=search_string)
|
Uh, the column spacing got messed up on that. The "Target" column is actually the MJD |
Interesting, @JohnGood are we missing the MJD field (last column) in kbcvel.ascii during the initial workspace database initialization? |
The MJD values for all of the legacy data in the database are incorrect. They are all 2.400000e+06.
The text was updated successfully, but these errors were encountered: