Quote:
Originally Posted by ZeroID
Forgive my ignorance but I presume that some of the below data replaces the earlier posted script for Stellarium .ini file above. ( still learning this stuff ). If that is the case I figured where the last three lines go but T & q I can't see where they would fit. ( I just wanna track and see this comet !!  ) |
It will take more observations to get a reliable set of figures to produce predictions more than a few days ahead. So far JPL only has 8 days of data with 62 observations. This is why the warning accompanies the data:
Quote:
|
The initial state available for this object was a Keplerian two-body orbital element set, not osculating elements. This means the orbit is probably very poorly determined. Predictions for times many months or years from the epoch may not be suitable for high-accuracy applications or expectations.
|
Based on the latest JPL data:
Code:
[Elenin_C2010_X1]
# Data taken from JPL/HORIZONS
# correct for the specified time frame:
# Start Time : A.D. 2010-Dec-29 00:00:00.0000 CT
# Stop Time : A.D. 2010-Dec-29 00:00:00.0000 CT
name = Comet Elenin (C/2010 X1)
parent = Sun
coord_func = comet_orbit
radius = 10
oblateness = 0.0
albedo = 1
lighting = true
halo = true
color = 1.0,1.0,1.0
tex_halo = star16x16.png
tex_map = nomap.png
lighting = false
orbit_Epoch = 2455559.500000000
orbit_TimeAtPericenter = 2455344.8351876955
orbit_PericenterDistance = 5.383678459548473
orbit_Eccentricity = 1.000050824373353
orbit_ArgOfPericenter = 187.2421383600018
orbit_AscendingNode = 321.2292862441847
orbit_Inclination = 1.521556790548213
This differs from the figures in MPEC 2010-Y24 so neither can be considered really accurate.