View Single Post
  #2  
Old 24-12-2010, 01:59 PM
mithrandir's Avatar
mithrandir (Andrew)
Registered User

mithrandir is offline
 
Join Date: Jan 2009
Location: Glenhaven
Posts: 4,161
From JPL Horizons for Stellarium:

Code:
[Elenin_C2010_X1]
# Data taken from JPL/HORIZONS
# correct for the specified time frame:
# Start Time : A.D. 2010-Dec-24 00:00:00.0000 CT 
# Stop Time  : A.D. 2010-Dec-24 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                 = 2455554.500000000
orbit_TimeAtPericenter      = 2455572.1216092836
orbit_PericenterDistance    = 5.754485624450996
orbit_Eccentricity          = 1.00003539933058
orbit_ArgOfPericenter       = 211.2547634005463
orbit_AscendingNode         = 322.0587099338747
orbit_Inclination           = 1.54681826747003
** WARNING **

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.

Since the epoch is inside or within ~30 days of the relatively short data
arc, the elements (such as they are) were numerically propagated with
perturbations, just as if they were osculating elements.
Reply With Quote