Posts: 741
Threads: 136
Thanks Received:
18 in 17 posts
Thanks Given: 0
Joined: Nov 2019
Reputation:
2
I've got to get better at this. I thought I might have had a chance to snag 2021 NA whizzing by last night (July 2 21:00-23:00CDT). I fetched MPC NEA Today (July 2) and did the ephem for time and date when close and bright. Showed best and apparent at 22:00 July 2. This small rock was moving over 900"/min but near the limit of scope plus there were some clouds moving in and out. Did not find it. Just now compared ephem with one from Horizons and position was different. Enough that I could have easily been looking 1.5° too far SE. I need to get better at this. It takes a lot of patience to track down and chase one of these faint fast movers.
Posts: 2,397
Threads: 410
Thanks Received:
82 in 79 posts
Thanks Given: 86
Joined: Nov 2018
Reputation:
29
Hi BMG,
I noticed in your thread where you posted the osculating elements that you were getting different values for the elements for every hour. Am I interpreting that correctly? The values seemed to change in the 3rd or 4th decimal place for several elements. Wow! It's a wonder you can find anything at all under those conditions.
Phil S.
Posts: 5,121
Threads: 279
Thanks Received:
236 in 211 posts
Thanks Given: 103
Joined: Nov 2017
Reputation:
49
(2021-07-03, 06:20 AM)bigmasterdrago Wrote: I've got to get better at this. I thought I might have had a chance to snag 2021 NA whizzing by last night (July 2 21:00-23:00CDT). I fetched MPC NEA Today (July 2) and did the ephem for time and date when close and bright. Showed best and apparent at 22:00 July 2. This small rock was moving over 900"/min but near the limit of scope plus there were some clouds moving in and out. Did not find it. Just now compared ephem with one from Horizons and position was different. Enough that I could have easily been looking 1.5° too far SE. I need to get better at this. It takes a lot of patience to track down and chase one of these faint fast movers.
Wow, that's a fast one! I'd definitely use Horizons orbits, and be sure to get the orbits off their server as close to when you go out as possible, so they reflect the most recent observations.
Clear skies,
Greg
Head Dude at Skyhound
Posts: 2,397
Threads: 410
Thanks Received:
82 in 79 posts
Thanks Given: 86
Joined: Nov 2018
Reputation:
29
Thanks BMG. I haven't used the Horizons website for elements, but have looked at it in the past. The user interface is confusing to me. Are they doing perturbation calculations including the effects of earth-moon gravity 'on-the-fly' so to speak? Then showing the modified elements?Awesome, as is your video. The orbit really changed after the close approach.
Cool stuff for sure.
Phil S.
Posts: 741
Threads: 136
Thanks Received:
18 in 17 posts
Thanks Given: 0
Joined: Nov 2019
Reputation:
2
Horizons does each step calcs and creates new (osculating) elements prior to next step, so yes, takes into account the gravity of the perturbing objects. It is not a two-body calc as most of our software does (MegaStar, The Sky X, Stellarium). With really close small fast movers, we need to update elements rather often (each step) if we want good positions. There was a very old piece of software that did that called "Dance of the Planets". Doesn't run well on modern PCs. There are some online that you can create your own simulation as well as some modern software that will simulate gravity. Do a search for solar system gravity simulators. Nothing I've seen that can display/print tracks with such ease like SkyTools 4. You just need to stay close to the epoch of elements. And if done correctly, the positions in SkyTools completely agrees with Horizons. The most tricky part is determining when the best viewing window is for your location as these fast movers run the sky quickly. I'm still struggling with that a bit. Occasionally, the magnitude will be wildly off in the generated ephemeris (ST) - example - 2008 GO20 close on July 24, 12:13UT - big rock (92-210 meters) shows obvious difficulty, 5.2 mag but not shown on IA (most likely due to low altitude).
Posts: 5,121
Threads: 279
Thanks Received:
236 in 211 posts
Thanks Given: 103
Joined: Nov 2017
Reputation:
49
2021-07-05, 03:48 PM
(This post was last modified: 2021-07-05, 03:49 PM by theskyhound.)
One thing to add that you guys may not be aware of: SkyTools keeps multiple orbital elements for a single object and then picks the one with an epoch closest in time to when you are calculating the position. So for close approaches I normally have HORIZONS output elements every few hours and then pick one from the beginning of the close approach, one from closest approach, and one from after the close approach and add all three sets of elements.
For very fast movers, I add sets of elements every hour or so throughout.
Clear skies,
Greg
Head Dude at Skyhound
Posts: 2,397
Threads: 410
Thanks Received:
82 in 79 posts
Thanks Given: 86
Joined: Nov 2018
Reputation:
29
Thanks Greg,
I knew that the MP database kept element data for multiple epochs, but was not aware that additional elements could be added at multiple epochs as you described for MPs whose osculating elements change rapidly during a close approach. I've never tried to input elements from HORIZONS as BMG does.
Good to know.
Phil S.
Posts: 741
Threads: 136
Thanks Received:
18 in 17 posts
Thanks Given: 0
Joined: Nov 2019
Reputation:
2
2021-07-06, 12:30 AM
(This post was last modified: 2021-07-06, 01:27 AM by bigmasterdrago.)
I too thought that only edits could be performed not sets of individual epochs. Some experimenting needed. Playing with it currently.
When I try adding 2021 MC as a new rock and paste from Horizon, add the name back, and correct H, I get a not responding after clicking OK. Then a program close when trying any other mouse click.
So it appears that I need to edit
BUT.... if I edit, the original elements get replaced. It does not add another epoch.
FYI, I pruned and the program still crashes when I try to add another set of element with a different epoch.