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
Our moons.tsv table has epoch_txt field, but these are not used to adjust M0 or orbit precessions.
The epoch texts on these are weird:
"1950 Jan. 1.00 TT"
"1997 Jan. 16.00 TT"
"2000 Jan. 1.50 TT"
"PLU042"
"PLU043"
etc... (more than a dozen different epochs)
We should create a new column and add J2000 time manually to the moons.tsv data table. Then implement internally. (A parser doesn't seem worth the effort, and won't understand "PLU42".)
The text was updated successfully, but these errors were encountered:
Our moons.tsv table has epoch_txt field, but these are not used to adjust M0 or orbit precessions.
The epoch texts on these are weird:
"1950 Jan. 1.00 TT"
"1997 Jan. 16.00 TT"
"2000 Jan. 1.50 TT"
"PLU042"
"PLU043"
etc... (more than a dozen different epochs)
We should create a new column and add J2000 time manually to the moons.tsv data table. Then implement internally. (A parser doesn't seem worth the effort, and won't understand "PLU42".)
The text was updated successfully, but these errors were encountered: