Blog Archive

Monday, December 30, 2019

Amors: (2019 QR6) and (2019 PR2) - investigation about cometary origin

These two asteroids have similar orbital parameters.
A possibility that should be investigated is that these asteroids separated recently from a common body ... see previous posts for a draft analysis.

Another aspect is that they might have a cometary origin.

For what's worth, considering the uncertainty (orbit condition code 4) and considering that I do not take into account non gravitational effects, I made a backward simulation with 2019 PR2

2019 PR2
Orbital Elements at Epoch 2458600.5 (2019-Apr-27.0) TDB
Reference: JPL 47 (heliocentric ecliptic J2000)
 Element Value Uncertainty (1-sigma)   Units 
e .7976773108833863 1.3756e-05  
a 5.772423469462186 0.00040358 au
q 1.167892239061442 2.2478e-06 au
i 10.98950352005738 9.7173e-05 deg
node 349.038132037726 0.00014302 deg
peri 57.08261419342178 0.00010673 deg
M 347.1019573973371 0.0013592 deg
tp 2458781.991800392675
(2019-Oct-25.49180039)
9.5194e-05 TDB
period 5065.656096365621
13.87
0.53125
0.001454
d
yr
n .07106680618494488 7.453e-06 deg/d
Q 10.37695469986293 0.00072551 au
  Orbit Determination Parameters
   # obs. used (total)      215  
   data-arc span      139 days  
   first obs. used      2019-08-10  
   last obs. used      2019-12-27  
   planetary ephem.      DE431  
   SB-pert. ephem.      SB431-N16  
   condition code      4  
   norm. resid. RMS      .40041  
   source      ORB  
   producer      Otto Matic  
   solution date      2019-Dec-28 08:29:27  

Additional Information
 Earth MOID = .236158 au 
 Jupiter MOID = .430847 au 
 T_jup = 2.149 


Clones
I generated 100 clones trying to achieve the same orbital parameters as calculated by JPL Small Body Database

Clones  Target
mean sd   mean sd
q 1.16789207 2.25e-06   1.16789224 2.25e-06
e 0.79767637 1.375e-05   0.79767731 1.376e-05
i 10.98949691 9.732e-05   10.98950352 9.717e-05
peri 57.08261449 0.00010684   57.08261419 0.00010673
node 349.03812785 0.00014309   349.03813204 0.00014302
tp 2458781.99180559 9.518e-05   2458781.99180039 9.519e-05


Simulation
Mercury6 simulator was set up like this (param.in file):



)---------------------------------------------------------------------
) Important integration parameters:
)---------------------------------------------------------------------
 algorithm (MVS, BS, BS2, RADAU, HYBRID etc) = BS
 start time (days)= 2458849.5
 stop time (days) = -1d8
 output interval (days) = 100
 timestep (days) = 0.05
 accuracy parameter=1.d-12
...
ejection distance (AU)= 1d2

As shown above, the arbitrary threshold to declare  that a clone has a cometary origin is set to 100 AU
I take into account all planets plus asteroids Ceres, Pallas and Vesta.

Simulation results 
At the end of the simulation, we find:
  • 72 out of 100 clones were ejected from the solar system
  • 2 out of 100 clones "hit" the sun

Considering that the simulation is backward in time, the above results must be read as:
  • 72 out of 100 clones have a cometary origin (they entered the solar system from a distance greater that 100 AU)
  • 2 out of 100 clones seem to have originated from the sun ! (we have to discard these as impossible results)

The following plots have been done using R scripts and package ggplot2.

First of all, we can see that there is not a "single" point in time when the clones likely to have a cometary origin have entered the solar system even though the are slightly more concentrated around 29000 years ago


Distribution of min perihelium
The simulation time has been divided into 10 slots.
In every slot, for every asteroid, we calculate the minimum perihelium that it had during that period.
The various values  are shown in a boxplot.
A similar approach is used for all the other plots. 

Distribution of max aphelium
Some clones entered the solar system on a hyperbolic trajectory, it does not make sense to calculate an aphelium (infinite) so they are not shown here:

... ooops!, an outlier ... if we omit it we have a better idea ... actually, we have to omit them about a dozen times before seeing something:

Distribution of max Orbital Period
...again after omitting several outliers:

Distribution of max Orbital Energy
In this graph, those clones with orbital energy >0 are on a hyperbolic orbit:

Distribution of Vinfinity
For those asteroids having an hyperbolic trajectory, it make sense to plot their Vinfinity:


Distribution of max eccentricity




References

Mercury6 simulator:
J.E.Chambers (1999) ``A Hybrid
      Symplectic Integrator that Permits Close Encounters between
      Massive Bodies''. Monthly Notices of the Royal Astronomical
      Society, vol 304, pp793-799.

package R:
  R Core Team (2019). R: A language and environment for statistical
  computing. R Foundation for Statistical Computing, Vienna, Austria.
  URL https://www.R-project.org/.

package ggplot2:
  H. Wickham. ggplot2: Elegant Graphics for Data Analysis.
  Springer-Verlag New York, 2016.




Cheers,
Alessandro Odasso

Sunday, November 17, 2019

Cluster of (57738) 2001 UZ160

The cluster of (57738) was identified in Pravec and Vokrouhlicky, Icarus 204 (2009) 580–588, http://www.asu.cas.cz/~ppravec/pravecvokrouhlicky2009.pdf

According to http://www.johnstonsarchive.net/astro/asteroidpairs.html the following asteroids are "suspected" pairs associated to (57738) 2001 UZ160 (and, if I understand a note correctly, some of them might be more specifically related to 436620 (2011 LF12) a very stable member of the same cluster):

18777 Hobson (1999 JA41)
363118 (2001 NH14)
381414 (2008 JK37)
436620 (2011 LF12)
450571 (2006 JH35)
465404 (2008 HQ46)
520394 (2014 JJ10)
2014 HH103
2014 OJ66
2015 KA91

I saw this msg https://groups.io/g/mpml/message/28579 from Petr Pravec where he explained that - at that time - they had yet to check whether 18777 Hobson is also a member of the cluster.

After "googling for a while" ,I was not able to find a reference to the following three asteroids, with orbital parameters similar to 436620 (2011 LF12):
(2015 HV138)
(2007 EH116)
(2015 OP104)

Do they also belong to the cluster of (57738) 2001 UZ160?

Kind Regards,
Alessandro Odasso

Thursday, November 14, 2019

2009 WQ62 and 63440 (2001 MD30) and 331933 (2004 TV14) - A cluster?

According to http://www.johnstonsarchive.net/astro/asteroidpairs.html asteroid 63440 (2001 MD30) and 331933 (2004 TV14)are considered to be an asteroid pair.

It seems to me that asteroid 2009 WQ62 (U code 2) has similar orbit parameters.

I made a simulation comparing clones of these three asteroids.
In the best case, it seems that the clones could be as near as about 20000 km (0.05 LD) and considering the periodicity maybe in the past they could be even more near.
I wonder whether these three asteroids can be considered to belong to a cluster of physically related asteroids ... or is it just a "statistical fluke"?


Quite unexpectedely, the two pairs 63440 (2001 MD30) and 331933 (2004 TV14) reached the minimum distance very recently ... but not particularly interesting as a close approach!



Actually what shown above is "the best case".
The simulation involved 100 clones for every asteroid, looking back atthe last 10^7 JD, output every 100 days.
I tried to achieve a "clone distribution" coherent with  the real ones  (with uncertainty read from JPL Horizons Web interface):

 

clones of 2004 TV14

Ephemeris | Orbit Diagram | Orbital Elements | Mission Design | Physical Parameters | Discovery Circumstances ]

[ show orbit diagram ]

Orbital Elements at Epoch 2458600.5 (2019-Apr-27.0) TDB
Reference: JPL 12 (heliocentric ecliptic J2000)
 Element Value Uncertainty (1-sigma)   Units 
e .08843948312784312 8.4849e-08
a 1.937933640687897 1.2579e-08 au
q 1.7665437911694 1.5808e-07 au
i 19.98889163261023 8.0042e-06 deg
node 229.4563583326874 1.4922e-05 deg
peri 205.5107460888095 3.7259e-05 deg
M 107.6788596209243 3.7957e-05 deg
tp 2458305.762954214937
(2018-Jul-06.26295422)
0.00010276 TDB
period 985.3868889042742
2.70
9.5939e-06
2.627e-08
d
yr
n .36533873552987 3.557e-09 deg/d
Q 2.109323490206394 1.3691e-08 au
Orbit Determination Parameters
   # obs. used (total)      166  
   data-arc span      6513 days (17.83 yr)  
   first obs. used      2001-07-01  
   last obs. used      2019-05-01  
   planetary ephem.      DE431  
   SB-pert. ephem.      SB431-N16  
   condition code      0  
   norm. resid. RMS      .60289  
   source      ORB  
   producer      Otto Matic  
   solution date      2019-Jul-13 19:23:38  

Additional Information
 Earth MOID = .787571 au 
 Jupiter MOID = 3.18038 au 
 T_jup = 3.828 
331933 (2004 TV14)
Classification: Inner Main-belt Asteroid          SPK-ID: 2331933


Clones Target
mean sd mean sd
q 1.76654379 1.6e-07 1.76654379 1.6e-07
e 0.08843948 8e-08 0.08843948 8e-08
i 19.9888926 7.9e-06 19.98889163 8e-06
peri 205.51074903 3.748e-05 205.51074609 3.726e-05
node 229.45635664 1.488e-05 229.45635833 1.492e-05
tp 2458305.76295692 0.00010125 2458305.76295422 0.00010276


clones of 2001 MD30


Ephemeris | Orbit Diagram | Orbital Elements | Mission Design | Physical Parameters | Discovery Circumstances ]

[ show orbit diagram ]

Orbital Elements at Epoch 2458600.5 (2019-Apr-27.0) TDB
Reference: JPL 22 (heliocentric ecliptic J2000)
 Element Value Uncertainty (1-sigma)   Units 
e .08842579345910323 5.0822e-08
a 1.937954727685901 7.1105e-09 au
q 1.766589543202455 9.6691e-08 au
i 19.9888850307184 5.8423e-06 deg
node 229.4570161987519 1.1316e-05 deg
peri 205.5022586712172 2.7892e-05 deg
M 110.8795473674578 2.7236e-05 deg
tp 2458296.997123521674
(2018-Jun-27.49712352)
7.3995e-05 TDB
period 985.4029722010249
2.70
5.4233e-06
1.485e-08
d
yr
n .3653327726380746 2.0106e-09 deg/d
Q 2.109319912169347 7.7392e-09 au
Orbit Determination Parameters
   # obs. used (total)      913  
   data-arc span      15178 days (41.56 yr)  
   first obs. used      1977-10-20  
   last obs. used      2019-05-11  
   planetary ephem.      DE431  
   SB-pert. ephem.      SB431-N16  
   condition code      0  
   norm. resid. RMS      .51323  
   source      ORB  
   producer      Otto Matic  
   solution date      2019-May-30 05:23:47  

Additional Information
 Earth MOID = .787609 au 
 Jupiter MOID = 3.18036 au 
 T_jup = 3.828 
63440 (2001 MD30)
Classification: Inner Main-belt Asteroid          SPK-ID: 2063440

Clones Target
mean sd mean sd
q 1.76658954 1e-07 1.76658954 1e-07
e 0.08842579 5e-08 0.08842579 5e-08
i 19.98888503 5.85e-06 19.98888503 5.84e-06
peri 205.50225416 2.817e-05 205.50225867 2.789e-05
node 229.45701705 1.135e-05 229.4570162 1.132e-05
tp 2458296.99711268 7.407e-05 2458296.99712352 7.4e-05



clones of 2009 WQ62

Ephemeris | Orbit Diagram | Orbital Elements | Mission Design | Physical Parameters ]

[ show orbit diagram ]

Orbital Elements at Epoch 2458600.5 (2019-Apr-27.0) TDB
Reference: JPL 2 (heliocentric ecliptic J2000)
 Element Value Uncertainty (1-sigma)   Units 
e .08804383689315186 1.158e-05
a 1.93801279355177 2.6273e-07 au
q 1.767382711259456 2.2659e-05 au
i 19.97084321515778 0.00012904 deg
node 229.9007989831988 5.6862e-05 deg
peri 204.9048096269857 0.010821 deg
M 167.0534712631619 0.008655 deg
tp 2458143.215595676715
(2018-Jan-24.71559568)
0.023758 TDB
period 985.4472601592967
2.70
0.00020039
5.486e-07
d
yr
n .3653163538572387 7.4287e-08 deg/d
Q 2.108642875844083 2.8586e-07 au
Orbit Determination Parameters
   # obs. used (total)      23  
   data-arc span      2927 days (8.01 yr)  
   first obs. used      2009-11-16  
   last obs. used      2017-11-21  
   planetary ephem.      DE431  
   SB-pert. ephem.      SB431-N16  
   condition code      2  
   norm. resid. RMS      .55576  
   source      ORB  
   producer      Otto Matic  
   solution date      2019-Sep-28 03:02:47  

Additional Information
 Earth MOID = .788005 au 
 Jupiter MOID = 3.18123 au 
 T_jup = 3.828 
(2009 WQ62)
Classification: Inner Main-belt Asteroid          SPK-ID: 3846838

Clones Target
mean sd mean sd
q 1.76737733 2.263e-05 1.76738271 2.266e-05
e 0.08804657 1.157e-05 0.08804384 1.158e-05
i 19.97082241 0.00012943 19.97084322 0.00012904
peri 204.90656857 0.01081596 204.90480963 0.010821
node 229.90081685 5.704e-05 229.90079898 5.686e-05
tp 2458143.21931216 0.0237189 2458143.21559568 0.023758



Clones Comparison

I compared clones of every couple (100*100 comparisons) trying to trace the minimum distance that they reached (taking note of the time and relative velocities):













 Kind Regards,
Alessandro Odasso

Monday, November 4, 2019

35448 (2018 TM7) and (2018 VR79) and (2015 PR301) - Datura cluster

Besides 2018 TM7 that I mentioned a few days ago, I wonder whether (2018 VR79) and (2015 PR301)  belong to the Datura cluster as well
                                 a            e              i           om           w  
       (2018 TM7)   2.235046 0.2073299 5.990117 97.82547 -100.5854
       (2018 VR79)  2.235106 0.2074233 5.990621 97.33788  -99.9308
       (2015 PR301) 2.234921 0.2072752 5.986435 98.29115 -101.3660
In fact, their  orbital parameters are very similar to those of these two recognized members of the Datura cluster:

                                     a         e                  i       om             w  
       (2016 TW15)     2.235612 0.2074483 5.991605 97.16207  -99.8753
433382 (2013 ST71)  2.234977 0.2081608 5.984741 97.94635 -101.1312


Kind Regards,
Alessandro Odasso