.comment-link {margin-left:.6em;}

Monday, February 04, 2013


C/2012 DA14 in Celestia

Near Earth Asteroid 2012 DA14 simulated in Celestia at the time of closest approach. Disappointingly, the simulated distance is out 10 fold (click to embiggen).

While we are waiting for the Near Earth Asteroid 2012 DA14 to come, I thought I'd set up a little Celestia file so you could play with it.

Unfortunately, like many planetarium programs, Celestia doesn't handle extreme close approaches well. Using the latest Minor Planet Center data, it places the asteroid at around 300,000 Km away at closest approach, instead of around 30,000 Km.

I've tried creating XYZ files for it, which should more accurately represent the orbit, but I'm obviously doing something wrong as they make the situation worse.

Anyway, here's the current file, have a play with it anyway.

As usual, copy the code below and save as it as a text file 2012DA14.ssc in the Celestia extras folder.
"2012 DA14" "Sol"

#Data from MPC http://cfa-www.harvard.edu/iau/MPEph/MPEph.html
#Epoch 2013 Apr. 18.0 TT = JDT 2456400.5                 MPC
#M 231.02518              (2000.0)            P               Q
#n   1.13512585     Peri.  195.60602     +0.95125404     +0.28828263             T = 2456514.12161 JDT
#a   0.9101369      Node   146.99587     -0.25703914     +0.93743151             q =     0.8285228
#e   0.0896723      Incl.   11.60623     -0.17043071     +0.19523136    Earth MOID = 0.00007 AU
#P   0.87           H   24.4           G   0.15           U   1
#From 196 observations at 2 oppositions, 2012-2013, mean residual 0".42.

    Class "asteroid"
    Mesh   "ky26.cmod"
    Texture "asteroid.jpg"
    Radius  0.02 # maximum semi-axis
    MeshCenter [ -0.000718 -0.000099 0.000556 ]

    InfoURL "http://en.wikipedia.org/wiki/2012_DA14"

    Epoch                  2456400.5      # Epoch 2013 Apr. 18.0 TT = JDT 2456400.5
    Period                 0.87           # P
    SemiMajorAxis          0.9101369      # a
    Eccentricity           0.0896723      # e
    Inclination           11.60623        # Incl.
    AscendingNode         146.99587       # Node
    ArgOfPericenter       195.60602       # Peri
        PericenterDistance      0.8285228     # q
        MeanAnomaly           231.02518       # M

        #One or other of these lines, with XYZ data, should have given a more
        #accurate orbit, they didn't
        #SampledOrbit "2012_DA14.xyz"
        #SampledTrajectory { Source "2012_DA14.xyz" }

    RotationPeriod 0.9

    Albedo 0.15


Labels: , ,

The Asteroid is a form of combination of Solid material which impact depends upon the speed to collide the place of Earth produced like power of Nuclear bomb to form on the place with light solid materiel as clouds which prevents of entering Sun rays result darkness and fail ere of formation of Natural activities.GutesWo
I tried this too with the latest data but again was out by 300,000k. I tried crudely changing some of the numbers but ended up further away. Perhaps Celestia's model of the Earth orbit doesn't quite take into account perturbations and wobbles. Oh well, it was a nice idea, thank you for making it.
Interesting, is it working in with the time accurately? Im looking for some kind of realtime 3D visualization for this Friday, so I can track exactly where it is and know when its about to pass over. Being in Australia I'll potentially have a good chance of seeing something.
To Alex Delderfield.
Download and instal Stellarium and add following text to "ssystem.ini" file. The file is located at "C:\Users\"YOUR USERNAME HERE"\AppData\Roaming\Stellarium\data\". You need to make few changes to text because comment area don't support formatting. Start new line from every point were you se ">" mark. Then remove ">" marks from the text. At bottom of following webpage you will se example of right formatting. http://www.stellarium.org/wiki/index.php/JPL_HORIZONS

---text starts from here---

># Data taken from JPL/HORIZONS
>name = 2012 DA14
>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
>orbit_Epoch = 2456084.5500000000
>orbit_TimeAtPericenter = 2456199.431669226382
>orbit_PericenterDistance = 0.8251566657007006
>orbit_Eccentricity = 0.09222268090579987
>orbit_ArgOfPericenter = 197.5168093259557
>orbit_AscendingNode = 147.1069671422395
>orbit_Inclination = 12.66183659065749
Well actually it seems to support formatting. So just remove ">" marks from the code. Then you can use stellarium and track exactly where 2012 DA14 is and know when its about to pass over.
Sorry, Stellarium, SkyMap and a host of other planetarium program's can't show the orbit of 2012 DA14 accurately, this is from the Stellaroum discussion group

"The present method of calculating general orbits in stellarium is either comet_orbit or ell_orbit. These routines using oscillating elements are good enough for distant objects but are quite inaccurate for near earth passes."

This is true of most planetarium program's (and celestia it appears)
Celestia can use a spice kernel to do it. Check http://stkwans.blogspot.com/2013/02/2012-da14-in-celestia.html for instructions.
May be a mistake while calculating date of 21.12 .2012 there is a difference of two months only , calculated 5000 years ago
Post a comment

<< Home

This page is powered by Blogger. Isn't yours?