Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Attempt to View 2021 NA Last Night July 2
#21
Hi Greg,

Thanks. Closing the MP DB after adding a new element set doesn't seem to work if the new elements are too close to an existing set. It's just ignored & the original set remains in place.

It would be nice if multiple element sets could be added & then have all of the auxiliary calculations & epoch calculations performed at once. Maybe that would really clog up the DB with element sets though. How does an MP with elements spaced a few hours apart affect the epoch file calculations for the other MPs, if at all?

Phil S.
Reply
#22
I think what ST is doing is displaying the column as Local Date/Time when it should be labelled GMT or UT or CDT. And the start time should indicate what time in starting local (CDT) or GMT (UT). When looking at the time/date column, I'm confused as to what time it is displaying. Should all these position be the same?

Horizons Position for 2019 AT6 @ 04:00UT July 13 From Squirrel Tree Ranch
2021-Jul-13 04:00 11 34 27.24 +35 01 51.0

Skytools Position for 2019 AT6 when Squirrel Tree Ranch configured GMT+0
2021 Jul 13 04:00 11h31m51.0s +34°42'03" alt+34°24' azi+293°24'

SkyTools Position for 2019 AT6 when Squirrel Tree Ranch configured CST-6
2021 Jul 12 23:00 11h34m27.4s +35°01'52" alt+23°20' azi+298°08

Unnamed Prog Position for 2019 AT6 from Squirrel Tree Ranch GMT & CDT
13 Jul 2021 AD, 04:00UTC 11h 34m 26.4s 35° 02' 04.6" az298.2 alt22.7
12 Jul 2021 AD, 23:00CDT 11h 34m 26.4s 35° 02' 04.6" az298.2 alt22.7

So if I'm correct, the only position I can trust is the CDT one and then mentally add the +5 hours to get GMT?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)