2022-07-07, 12:00 AM
Hi BMD,
That's a pretty large position error. Aug 9 00:00 UT is MPC's current standard epoch for their elements, but the epochs for the NEOs are calculated daily & available over a ±15 day interval. Unfortunately I don't know how to get ST4v to use the elements for Jul 7 00:00 UT until I download them tomorrow when it's too late to be of use.
The epoch used for today's revised path prediction was Jul 6 00:00 UT. The Object Info display says Jul 5, but ST4v reports that date as the 'Evening of', so the evening of Jul 5 includes Jul 6 00:00 UT. The only way to get elements at the time of the close approach would be to obtain elements from HORIZONS & edit ST4v's MP DB to use the new elements. That's what we did last summer.
Perhaps Greg will take a shot at it. He seems to be in a good location to view it.
Phil S.
That's a pretty large position error. Aug 9 00:00 UT is MPC's current standard epoch for their elements, but the epochs for the NEOs are calculated daily & available over a ±15 day interval. Unfortunately I don't know how to get ST4v to use the elements for Jul 7 00:00 UT until I download them tomorrow when it's too late to be of use.
The epoch used for today's revised path prediction was Jul 6 00:00 UT. The Object Info display says Jul 5, but ST4v reports that date as the 'Evening of', so the evening of Jul 5 includes Jul 6 00:00 UT. The only way to get elements at the time of the close approach would be to obtain elements from HORIZONS & edit ST4v's MP DB to use the new elements. That's what we did last summer.
Perhaps Greg will take a shot at it. He seems to be in a good location to view it.
Phil S.