Quote:
Originally Posted by Zubenel
Turns Out Astrojunks ( Thx Johnathon) kindly provided coordinates didnt align with what gel with Sky safari 5 was telling me. So much for relying on it in the future. Sky safari 7 shoed a different location for the asteroid with coordinates looking plausible . So 700 frames at 3sec were trashed. Moving to the SS7 position high cloud rolled in. Got 200 frames which may or may not have tge asteroid. I’d like to look into integrating plate solving and auto go to with the Argonavis/ servocat combo. Gary might like to incorporate in the new model!!!
|
Wes,
The probable reason for your issue is that the orbital elements in SS might be incorrect. I extracted the current Bessel elements out of MPEph. Simulation curriculum may have entered the elements years ago before the orbit was refined. The elements in my version of Sky Safari 6 are all different to the current MPEph element components. As far as I know, SS doesn't allow you to edit object orbital elements. It's "big" brother SNP does support that.
Just use horizons to generate an ephemeris for your location. Works every time. If you calc the ephemeris, go to a star on the path and wait, the asteroid will drift through.
If any of your other software allows orbit refinement, use MPEPH to generate fresh elements and re-enter the objects elements or edit the existing Besselian elements.
Here are the elements for this object extracted from MPEph
Number 2015 RN35
Mag._____23.15
a________1.474578
e_________0.347406
i_________0.2342
Node ____147.958
w________269.6934
L________51.0989
Epoch____2460000.5
It's not rocket science....oh hang on....
it is rocket science but don't worry, MPEph does all the heavy lifting for you.
Horizons indicates a predicted magnitude around 13.5-15 for a few nights so you still have a few nights to try this.
Good Luck
Joe