Kerr Watch

Number of days writer Richard Kerr has failed to inform his Science readers of the confirmation of nanodiamonds at the YDB: 3 years, 9 months, and 11 days

CT Post Calendar

October 2014
M T W T F S S
« Sep    
 12345
6789101112
13141516171819
20212223242526
2728293031  

The Cosmic Tusk Newsletter

Loading...Loading...


Comet ISON, Newton’s Great Comet of 1680, Solar Flares, and the 775 AD Eichler Event

Newton’s Great Comet of 1680

Update: A couple of useful links and a popular article on the subject.

I just learned of the discovery of Comet ISON which has apparently electrified the astronomy world for months. What then caught my eye was a paper from David Eichler of Ben Gurion University published just two months later and curiously does not mention the newly discovered body.

Rather, Eichler investigated the effects of a comet the size of Hale-Bopp plunging into the sun. The result according to Eichler would be a huge solar disturbance which could perhaps explain the spike in radiocarbon at 775 AD.

ISON is apparently as large or larger than Hale-Bopp, and headed for a very, very close brush with the sun. I wonder what the probability is of Comet ISON actually plunging into the sun and resulting in an “Eichler Event?”

If it were high I would be forced to drop my regular aversion to forward catastrophism and admit the day was truly nigh.

I am also fascinated with the seemingly genetic relationship between the orbits of ISON and Newton’s Great Comet of 1680. From what I understand of comets, which is little compared to many Tusk readers, the orbital period should be relatively long because the motion of the object is relatively parabolic. I have seen mentioned that the orbital period of ISON should be something around 10,000 years (an interesting timescale to Tusk readers). But other articles seem to suggest that the Comet of 1680 and this comet may be separate pieces of a much larger body from the Orrt Cloud, sending chucks our way now and then. Instructive in its own way.

I’m interested in reader insights as always.

 

A typical science media article regarding Comet ISON from Universe Today:

New Sunskirting Comet Could Provide Dazzling Display in 2013

2013 is looking to be a promising year for potential naked-eye comets, as a new comet has been discovered that will likely skirt close to the Sun, and could provide a stunning display late next year. The comet, named Comet C/2012 S1 (ISON), as it was discovered by a Russian team at the International Scientific Optical Network (ISON), is currently about the distance of Jupiter’s orbit. But it is projected to come within less than 2 million km from the Sun at perihelion by November 28, 2013. Ernesto Guido and Giovanni Sostero from the Remanzacco Observatory in Italy, along with their colleague Nick Howes from the UK have imaged the comet with the RAS telescope in New Mexico, and say, “According to its orbit, this comet might become a naked-eye object in the period November 2013 – January 2014. And it might reach a negative magnitude at the end of November 2013.”

Read more: http://www.universetoday.com/97561/new-sun-skirting-comet-could-provide-dazzling-display-in-2013/#ixzz2GHh0o6pj

 

34 comments to Comet ISON, Newton’s Great Comet of 1680, Solar Flares, and the 775 AD Eichler Event

  • Jonny

    George, if you check out the JPL small body database for ISON http://ssd.jpl.nasa.gov/sbdb.cgi#top, you will see that its eccentricity is determined to be more than 1. This means that it is parabolic/hyperbolic, and hence does not have an orbital period (hence the n/a next to “period” in the data. Thus it is meaningless to talk about what the period of this comet would be, and it is extremely unlikely that its period is 10,000 years. Indeed having an eccentricity larger than one means that it will exit the solar system never to return, unless it interacts with a planet or two to change its eccentricity to less than unity. Non-gravitational forces from out gassing could also accomplish this (or even increase its eccentricity further). Arriving into the solar system with an eccentricity greater than 1 means that this is likely the first visit of the comet to the inner solar system.

    Its orbital elements are extremely similar to the comet of 1680 http://ssd.jpl.nasa.gov/sbdb.cgi#top, and the suggestion by one researcher that this is not coincidental, and that ISON and C/1680 V1 are perhaps were part of the same object. Although it passes close to the suns surface, it is not thought likely that it will impact the sun.

  • George Howard

    Great stuff, as always, Jonny.

  • Jonny

    Yes, late night typing can greatly effect the coherency of one’s posts. I shall try to elucidate a bit more.

    For those who have not heard of orbital elements before, one can define the orbit of a body about the sun with using 6 parameters. These parameters are the eccentricity (e), semi-major axis (a), inclination (i), Longitude of ascending node longitude of the ascending node (node), argument of perihelion (p) and the mean anomaly (M). I have used the notation of jpl small body database. These parameters will tell us the shape and orientation of an orbit in space (to know where a body is at any given time we also require the time of perihelion). You can visualize what each of these parameters refer to here http://en.wikipedia.org/wiki/Orbital_elements.

    If we look at comet ISON’s orbital elements and compare them with that of C/1680 V1 we can see the following (not sure how the editing will work)

    ISON

    e 1.00000233964133
    a -5350.118084363769
    i 61.76712649202648
    node 295.7541076262132
    peri 345.4991080203023
    M 359.9990156708353

    C/1680 V1

    e 0.999986
    a 444.4285714
    i 60.6784
    node 276.6339
    peri 350.6128
    M 359.99795

    You can see the close similarity of inclination, argument of perihelion, and mean anomaly, which has lead some to suggest that ISON and C/1680 V1 may be siblings from the same parent (especially when one considers these are two sun grazing comets, with similar perihelion distances).

    Will ISON collide with the sun at perihelion? Its not likely, since C/1680 V1 passed the sun at 0.006 AU compared to ISON’s distance of 0.0125 AU from the centre. That is, ISON will be twice as far from the sun as C/1680 V1 and it failed to collide with the sun. Will it survive perihelion? No-one knows, but we are all hopeful it will so it can put on a magnificent display.

  • Jonny

    With regards the link http://sywardus.wordpress.com/2012/12/18/comet-ison/.

    There are a number of problems with the hypothesis. The author of the article has proposed that there is a 333 year periodicity between specific events and associated with Comet ISON and C\1680 V1 (AKA the great comet of 1680). It is true that the two above comets have similar orbits, and if we do a reduced D-criterion analysis of the two orbits, which compares the orbits of two objects via their perihelia, inclination and eccentricity we obtain a value of 0.021 (the closer to zero the more similar the orbits and the more likely the two objects are dynamically related). To put this into context, the D-criterion of Taurid Complex meteors with their progenitor is typically 0.04, so the analysis for the two commentary orbits would imply a greater similarity than the orbits of Taurid meteors and their known Parent body.

    If we assume that the two comets are dynamically related, then it is possible that they are the fragments from a shared progenitor. Would the two comets be the same comet, observed 333 years apart? Well for this we will put Newton and Kepler in the driving seat. The comet of 1680 upon leaving the solar system had an almost parabolic orbit, but crucially it appeared to have an eccentricity less than 1. This means that it is bound to the sun, and will be periodic. Indeed, its semi-major axis was determined to be around 444 Astronomical units. Using Kepler’s third Law (Square of the period is proportional to the cube of the semi-major axis), then we can determine C\1680 V1’s orbital period upon leaving the inner solar system. If 1 AU corresponds to 1 year, then 444 AU corresponds to a period of 9355 years. I.e., if the comet returns, it wont return to perihelion until sometime in the 12th millennium AD. Unfortunately I don’t believe that observations were precise enough to determine if C/1680 entered the solar system on a e > 1 orbit, and was perturbed into a bound e < 1 orbit. But assuming that it is indeed periodic, it would have last visited in the 8th millennium BC. This 9355 years for C\1680 is where I imagine you got your 10,000 year orbit for ISON.

    There is no chance that ISON and C\1680 are the same object, and especially one with a period of 333 years. ISON’s orbital elements suggest that it is a new visitor to the solar system. Also to suggest that there were at least 4 fragments of the same body, all separated by 333 years seems like a case of special pleading.

    What about the speculation that C\1680 caused an outbreak of the plague? Lets assume like good catastrophists that there is indeed a link between the comets and disease. The closest C/1680 came to earth was 0.42 AU, which is about 63 million kilometres. Also, C/1680’s ascending node (the point where the comet would cross the ecliptic from below) is outside the earths orbit, meaning that its tail would be downwind from the earth. Also at this point, the earth was about 0.62 AU away. Thus it is extremely unlikely that there was any interaction between the comet and the Earth.

    As we established above there C\1680 is not likely to have had a 333 year period, but lets examine the 333 year periodicity with respect comet Negra of 1347. You will be aware of course that Mike Baillie has highlighted the coincidence of this comet with claims of a corrupted atmosphere, and a possible link with the black death, which Mike outlines in “New Light on the Black Death”. Lets take this at face value, and say that The Black Death was comet induced. If we go back 333 years, we end up at 1014 AD.

    It is strange how this date has become an “impact date”. The original suggestion of this date as an impact date comes again from Mike’s “New Light on the black death”, in which he notes that in the GRIP ice cores elevated ammonium around AD 539 and AD 1014. Given the argument for impact at AD 539, it was reasonable to assume under this paradigm that the AD 1014 signal could have been impact related also, especially given the apparent coincidence of the St Michalmas flood. Ted Bryant and Dallas Abbott seemed to have taken this date and ran with it, and found evidence for a comet impact at AD 1014. However, if we examine GRIP critically we see certain flaws. For a start the AD 539 peak is wrong. The ice core workers of GRIP have admitted that the data for this section of the core as published online is wrong, and should never have entered the public domain. The dates given in this section of the core are not genuine counted layers, but rather dates extracted from ice flow models. If one were to count the physical layers, one finds that the NH4 spike occurs around AD 546, i.e. 7 years later. We also have the issue that Mike has convincingly argued that on dendrochronological grounds that the GRIP core at this depth is systematically too old by about 7 years, implying that this ammonium signal should be around AD 553. This then explains why there is no Ammonium spike in the GISP2 core at this approximate depth, due to the core being “trashed” at this depth, i.e. the data is missing.

    So if GRIP is wrongly dated, what are the knock on effects if any? There is a strong argument now that GISP2 is actually a far more robust data set, and that it is extremely accurate in in its chronology. In GISP2 we find the only large ammonium signal in the first half of the 11th century occurring at AD 1021, which is 7 years younger than the largest ammonium signal in the same time period of GRIP, again suggesting that there is an inherent 7 year systematic error in the GRIP chronology. So if this ammonium signal is at 1021 AD, it cannot be assoicated with the AD 1014 Michlemass flood, and nor with any cometary impact at this date.

    What is strange is that based upon Mike’s suggestions of impact events around 536/540 (which due to Mike’s recent proposal of shifting GRIP counted layers by 7 years younger means that there are two volcanic signals matching dendro-evidence) and at AD 1014, Ted Bryant and Dallas Abbott have found evidences of comet impacts at these dates, even though the dates are now questionable as impact dates. A similar conclusion is found by Ted Bryant with respect to a suggested impact in AD 1491. Again Mike first raised the suggestion of this date being an impact date, due to ammonium in GISP2 as well as a tree ring downturn in Irish Oaks. It also coincides with the closest approach of of any recorded comet (C/1491 B1), on February 20th 1491. This was taken from Don Yeoman's work, and Bryant used coupled with Australian aboriginal myth to argue of an impact event near Australia, in and around the 20th February (cant remember the precise date). As it turns out though, and what is neglected in this, is that the orbit of this comet is extremely uncertain, meaning it may not have made a close approach at all. All this does not prove that impacts did not occur, but rather one should be skeptical about claims of impacts, and I am personally dubious of any claims of evidence of dated impacts by Abbott and Bryant that have been per-suggested by others.

    So after that digression, I would say that the foundations of the website’s claims are questionable, and that it is unlikely that these events are separated by 333 years, due to the questionable evidence of impact dates. It would be interesting if it is correct, since an object with an Encke like orbit of 3.33 years, could make close passages to earth every 333 years.

  • George Howard

    Wonderful Jonny!

  • Jonny

    I have read that paper, but unfortunately the uncertainty in 14C measurement gives a pretty wide estimate. The age measurement is reported as 950 – 1,170 cal years BP, which is a 220 year temporal window. This is a rather large window to try to fit in a single known date, and it is dangerous to try to fit in the 1014 Michaelmas Flood with the event discussed in the paper. If we assume that they have been good and use the conventional 14C definition of Before Present as meaning before 1950, this corresponds to a calendar date range of AD 780 – 1000 which places it just outside of AD 1014 (but still close enough). Even if they were naughty and used AD 2000 to mark before present (thus dating of 830 -1050), it doesnt detract from the fact that we still have 200 years to fit an impact event into. Personally I would want to see the dating more restrained. While the two events could be linked, the above paper cannot be used to definitively support the claim that they are the one and same event.

    If we look at the logic of it, if the two events above are linked, and occur in 1014, then we may no reason to allocate an impact origin for it, since the impact marker at 1014 in GRIP ice core could be wrong. If the GRIP ice core is wrongly dated, and the two events are linked, then the principle of least astonishment would tell us that the tsunami may be of terrestrial origin, i.e. no cosmic vector is needed. But is GRIP wrong? Or GISP2? One or both may be since the two cores were extracted 30 kilometers from each other, and so one would think that they should have the same chronology of events. Indeed this is why the location of GISP2 was selected, in an attempt to replicate the GRIP core.

  • showmemike

    COMET ISON may be the return of the STAR OF BETHLEHEM

    the orbit of COMET ISON brings it back every 333 years,
    so it can be established that the comet was here in 15 a.d.
    considering that an exact year has never been established
    for the birth of christ,
    is it more than coincidence that
    there was a census in 14 a.d. called by Caesar Augustus?

    you heard it here first !
    http://www.facebook.com/events/371628202915203/

  • George Howard

    From: Anonymous Astronomous

    Regarding John Bortle’s posting to the comets mailing list, linked to from
    the page you mention, he’s quite right that the key is (was) for e to come
    down sufficiently that the separation from C/1680 V1 can have happened up
    to just a few revolutions earlier within a reasonable timeframe (say, not
    above the 10,000 yr you mention on your page where you link to Bortle’s
    comments). Then even without the two being the same object, they could be
    linked in the way different Kreutz sungrazers are linked.

    If you look at ISON’s orbit:

    http://www.minorplanetcenter.net/db_search/show_object?object_id=C/2012+S1

    you see
    recip semimajor axis orig (AU) 0.00004782
    recip semimajor axis error (AU) 0.0000088

    reciprocal semimajor axis around 0.00005 AU (original i.e. before planetary
    perturbations on its current return) is a = 20000 AU or so which is a
    period of millions of years. The 1/a uncertainty, which I think will be
    1-sigma, is around 0.00001 which (even at 3-sigma) can’t bring the period
    down to what we want. Thus the current formal orbit computation rules out
    the genetic relationship.

    Could the orbital uncertainty analysis change sufficiently depending for
    example on the weighting given to the two prediscovery nights in 2011 Dec
    and 2012 Jan? Hard to know without an in-depth study but my guess is not.

    This supports the comment posted to your page:
    “ISON’s orbital elements suggest that it is a new visitor to the solar
    system.”

    I’d have thought it was possible within the uncertainties, at the time of
    John Bortle’s posting.

    Does leave us with the coincidence. Taking the L and B values posted by
    Peter Bus (see same page as Bortle) gives a difference in perihelion
    directions a bit above 15 deg. Could ask, what’s the chance that two
    randomly (isotropically) distributed points are within 15 or so deg?
    I think it works out as a couple of percent or so. So it’s a bit of a
    coincidence, but not absurdly so.

    Best.

  • Jonny

    Thanks for this information George. Indeed, with the eccentricity being greater than unity it is hard to see how ISON could be related to C/1680, and that this is likely ISON’s first visit to the inner solar system. I had trouble with the suggestion of a dynamic link between ISON and C\1680 since there is not much out there in the outer solar system (that we know of) that could perturb an incoming e 1 unbound orbit. By this I mean that if there was a group of comet fragments on similar orbits to C/1680 (which seems to be a long period comet), then in order for a fragment on such an orbit to return with an eccentricity greater than unity implies that it most have been perturbed some time after reaching aphelion, since if it was perturbed before aphelion to e > 1 it would not then return.

    One could always invent scenarios to alter its eccentricity of course, such as a close encounter with an as of yet undiscovered distant planet, but to do so is essentially special pleading. It is a shame that they are likely not related, as it does make for a nice story.

  • George Howard

    Thanks, Jonny. But I cannot claim that cogent comment as my own. It was a response in a private communication I had with a noted astronomer. I took the liberty of posting his thoughts anonymously. As public awareness grows of Comet ISON, your thoughts and his agreement regarding the potential relationship between the 1680 Comet and ISON should prove very informative. Cheers.

  • Jonny

    Hi George, I thought thats what it was given the context. No harm in checking facts or getting a second opinion.

  • Steve Garcia

    Jonny –

    A comment and a question:

    Comment: Your input here is great – technical yet clear enough to learn from.

    Regarding the e values for ISON (1.00000233964133) and C/1680 (0.999986),

    Question 1: How precise is the data upon which all those decimal places are determined?

    Q2: How is it possible to get so many decimal places from 333 years ago?

    Q3: The e values only differ by 0.00001633964133, which seems really small (but maybe it isn’t with comets). Just to cover this base — Is it possible for Jupiter or Saturn to affect C/1680 on its way outbound that would allow for those values to represent the same body before and after? It doesn’t seem like it would take much to make such a small change in the e value.

    I have no bone to pick in any of this. The questions are simply for information.

  • George Howard

    Thanks, Steve. Great to see you back.

    I promise to beat back the chick et al during your stay.

  • Steve Garcia

    Jonny -

    Re my 2nd question, I have doubts that an elliptical orbit can be deflected into a parabolic or hyperbolic orbit, but I’d like to know your answer. Thanks!

  • George Howard

    Program Note: I have cleaned up the post here which was quite sloppy. As usual, my apologies for all the typos and other shortcomings.

  • Jonny

    Hi Steve,

    To answer your questions as best I can.

    Question 1: How precise is the data upon which all those decimal places are determined?

    Answer 1: Obviously the ISON data is extremely precise, and far more precise than the 17th century data of C/1680. The 1 sigma uncertainty for ISONS eccentricity is 0.000000357. Unfortunately the jpl small body database does not quote the uncertainty of C/1680.

    C\1680 has the distinction of being the first comet to be analysed using Newtonian dynamics. It was a widely observed comet with teh telescope increasing the accuracy and precision of its position in the heavens. It was first observed on the 14th of November 1680 two weeks before its closest approach to earth (at 0.42 AU) and a month before its perihelion. Its last observation was on the 19th March 1681 when it was at a heliocentric distance of 2.21 AU and a distance of 2.5 AU from earth. Thus it was observed for 125 days.

    Initially Netwons analysis in the 1680′s could only fit a parabolic orbit to the elements, although he was convinced that the orbit was elliptical. Newtons work at the time was revolutionary, since he worked out an accurate way of determining orbital elements from three observations. However this analysis was in its infancy, and up until the early 19th century there was much disagreement upon the comets orbit (see Marsden BG Annu. Rev. Astron. Astrophys. 2005. 43:75–102). However, in 1818 Johann Encke published a paper (Encke JF. Z. Astron. 6:157 (1818)) in which he took 30 observations from the 125 day observation window (of which we can assume were the most accurate/precise), and determined orbital elements for the comet using much more sophisticated techniques, and it is these elements that we use today, implying that modern techniques make little improvement upon his calculations. How precise these measurements were I dont know.

    Question 2: How is it possible to get so many decimal places from 333 years ago?

    Answer 2: The use of the telescope made increased the precision of measurements. Also being such a magnificent sight made it an easier target to measure. It was also observed before and after perihelion which increased the quality of the fit. Also as mentioned above, the mathematical techniques to determine orbital elements had improved significantly by the 19th century when Encke did his calculations, meaning that more precise fits could be achieved for the orbital elements.

    Question3: The e values only differ by 0.00001633964133, which seems really small (but maybe it isn’t with comets). Just to cover this base — Is it possible for Jupiter or Saturn to affect C/1680 on its way outbound that would allow for those values to represent the same body before and after? It doesn’t seem like it would take much to make such a small change in the e value.

    Answer 3: You are correct, Jupiter and Saturn could and did affect C/1680. We can go to the JPL small database and get it to calculate the orbital elements for the comet at specific times. This determines the comets elements including perturbations from the planets. The data is listed at the end of this post where I have asked for the elements spanning the time period from first observation until January 1st 1684. Listed is the eccentricity (Ec) and the semi-major Axis (A) of the comet.

    What we see that after its last observation, its eccentircity as well as its semi-major axis increases until around october 1681, at which point they begin to drop again. As the comet moves out of teh solar system, Jupiter is moving towards its orbit (though the comet is high above the orbital plane. Thus this increase is due to the acceleration of Jupiter which in october passes below the comet around about October. After october, the comet has passed jupiter, but Jupiter starts reducing the eccentricity and semi-major axis, until it starts to settle back towards a constant value. Note after the Jupiter encounter, all other planets are too far away to cause any dramatic effect.

    So although the elements are being changed by an encounter with jupiter (primarily), what Jupiter gives on its approach, it effectively takes away on its recession. So the comet was not given enough of a kick to change its eccentricity to greater than 1 and hence be ejected from the solar system.

    This last point is important, and is indeed the most important point of all. Even if it did get a kick sufficient enough to increase its eccentricity of to greater than 1, it would not have come back, since an eccentricity greater than one means that the orbit is now hyperbolic, meaning that the total energy of the body is greater than the gravitational binding energy of the sun/solar system.

    Another argument is with the semi-major axis. In order to have an orbital period of 333 years and thus be returning now on ISON’s orbit, its semi-major axis should be in the region of 48 AU. It would need a significant encounter in order to reduce a semi-major axis of over 400 AU to 48 AU, and if in such an encounter the acceleration exerted on a body as fragile as a comet may be in excess of its tensile strength.

    Also, When Encke performed his own calculations to determine C/1680′s orbit, he calculated a period of around 9000 years, but more importantly he concluded that the period of the comet could not be less than 2000 years.

    Marsden (Annu. Rev. Astron. Astrophys. 2005. 43:75–102) gives a brief synopsis on some of the controversy of the orbit determination of C/1680 V1, which I quote below

    “The first sungrazing comet to have its orbit computed according to the law of gravitation was in fact the first comet of any description to be treated in this manner, namely, the great comet of 1680–1681, now designated C/1680 V1. The parabolic orbit published by Newton (1687) as the illustration of his geometrical method for making such computations from three observations indicated a perihelion distance q of 0.0059 AU (or 0.3 R above the sun’s surface), some 5% smaller than the value later determined by Encke (1818) from 30 observations. Newton and Encke agreed that the orbit had an inclination i of 61 degrees to the ecliptic.

    Although the success of Newton’s calculation of a parabolic orbit did much to clarify the idea that comets were, like planets, material bodies that moved in accordance with his laws, several of his contemporaries were already reviving the views of some of the ancients, such as Apollonius of Myndos and Seneca, that— again like planets—comets had relatively short orbital periods, that the total number of discrete comets was therefore not enormous and that, in particular, one could readily identify different apparitions of the same object. One such contemporary was Cassini, who, simply by comparing the observed tracks of comets across the sky, concluded that the 1680 comet, for example, was a return of the famous one observed by Tycho Brahe and others in 1577 (Cassini 1699). Although Newton had also noted some vague similarity between the 1680 and 1577 comets, the Newtonian orbit computed by Halley (1705) for the latter showed q to be as large as 0.18 AU, so the proposed relationship was clearly incorrect. As is well known, Halley himself instead linked the 1680 sungrazer with a comet (also mentioned by Newton as having been very close to the sun) seen in 1106, convincing himself and others of its 575-year period by also remarking on comets recorded in the years 531 and 44 B.C. (or −43). But Encke (1818) computed for C/1680 V1 an orbital period P of almost 9000 years—and concluded that P could not be less than 2000 years. Furthermore, the scanty data made it impossible for Halley to compute orbits for any of those earlier comets. Like Cassini’s, Halley’s scenario is therefore now discredited (cf., e.g., Marsden 1997).

    References:

    Cassini JD. 1699. Hist. Acad. R. Sci. Paris, pp. 95–100. Amsterdam ed., 1734
    Encke JF. 1818. Z. Astron. 6:157
    Halley E. 1705. Philos. Trans. 24:1882
    Marsden BG. 1997. In The Comet of 44 B.C. and Caesar’s Funeral Games, ed. JT Ramsay, AL Licht, pp. xi–xiii. Atlanta: Scholars Press
    Newton I. 1687. In Philosophiae Naturalis Principia Mathematica, Book 3, Prop. 41. London: Streater”

    With regards your doubts about elliptical orbits being deflected into parabolic or hyperbolic orbits. It is thought possible (to my knowledge anyway) that comets can be deflected into parabolic or hyperbolic orbits, if it is given enough of an energy boost by another object (such as jupiter).

    ————————————————

    Orbital elements for C\1680 V1 from 1st November 1680 (2334972.5 Julian) to 1st January 1684 (2336128.5 Julian). Ec = eccentricity, A = Semimajor axis. note scientific notation is used.

    2334972.500000000 = A.D. 1680-Nov-01 00:00:00.0000 (CT)
    EC= 9.999861487824204E-01
    A = 4.492366198345896E+02

    2335002.500000000 = A.D. 1680-Dec-01 00:00:00.0000 (CT)
    EC= 9.999859870573171E-01
    A = 4.440158808114790E+02

    2335033.500000000 = A.D. 1681-Jan-01 00:00:00.0000 (CT)
    EC= 9.999859170360890E-01
    A = 4.418076947930903E+02

    2335064.500000000 = A.D. 1681-Feb-01 00:00:00.0000 (CT)
    EC= 9.999860189075106E-01
    A = 4.450742554484596E+02

    2335092.500000000 = A.D. 1681-Mar-01 00:00:00.0000 (CT)
    EC= 9.999862029025938E-01
    A = 4.510871535902079E+02

    2335123.500000000 = A.D. 1681-Apr-01 00:00:00.0000 (CT)
    EC= 9.999865399681931E-01
    A = 4.625960769514730E+02

    2335153.500000000 = A.D. 1681-May-01 00:00:00.0000 (CT)
    EC= 9.999870375500980E-01
    A = 4.808522455282445E+02

    2335184.500000000 = A.D. 1681-Jun-01 00:00:00.0000 (CT)
    EC= 9.999877529689896E-01
    A = 5.101798457667518E+02

    2335214.500000000 = A.D. 1681-Jul-01 00:00:00.0000 (CT)
    EC= 9.999886136565175E-01
    A = 5.514106511896117E+02

    2335245.500000000 = A.D. 1681-Aug-01 00:00:00.0000 (CT)
    EC= 9.999895776774820E-01
    A = 6.080344617526165E+02

    2335276.500000000 = A.D. 1681-Sep-01 00:00:00.0000 (CT)
    EC= 9.999903434083961E-01
    A = 6.659479033254538E+02

    2335306.500000000 = A.D. 1681-Oct-01 00:00:00.0000 (CT)
    EC= 9.999905951167976E-01
    A = 6.957288466383491E+02

    2335337.500000000 = A.D. 1681-Nov-01 00:00:00.0000 (CT)
    EC= 9.999903431980111E-01
    A = 6.890899716325304E+02

    2335367.500000000 = A.D. 1681-Dec-01 00:00:00.0000 (CT)
    EC= 9.999898324680081E-01
    A = 6.628958203352731E+02

    2335398.500000000 = A.D. 1682-Jan-01 00:00:00.0000 (CT)
    EC= 9.999892428411186E-01
    A = 6.325201907093392E+02

    2335429.500000000 = A.D. 1682-Feb-01 00:00:00.0000 (CT)
    EC= 9.999887054817350E-01
    A = 6.064229981961084E+02

    2335457.500000000 = A.D. 1682-Mar-01 00:00:00.0000 (CT)
    EC= 9.999882784324278E-01
    A = 5.868559798191956E+02

    2335488.500000000 = A.D. 1682-Apr-01 00:00:00.0000 (CT)
    EC= 9.999878549117549E-01
    A = 5.683518528053927E+02

    2335518.500000000 = A.D. 1682-May-01 00:00:00.0000 (CT)
    EC= 9.999874958499377E-01
    A = 5.533392876357055E+02

    2335549.500000000 = A.D. 1682-Jun-01 00:00:00.0000 (CT)
    EC= 9.999871661676509E-01
    A = 5.400399177582572E+02

    2335579.500000000 = A.D. 1682-Jul-01 00:00:00.0000 (CT)
    EC= 9.999868835483393E-01
    A = 5.289449191148415E+02

    2335610.500000000 = A.D. 1682-Aug-01 00:00:00.0000 (CT)
    EC= 9.999866407080407E-01
    A = 5.196702728355224E+02

    2335641.500000000 = A.D. 1682-Sep-01 00:00:00.0000 (CT)
    EC= 9.999864321348013E-01
    A = 5.119153447520320E+02

    2335671.500000000 = A.D. 1682-Oct-01 00:00:00.0000 (CT)
    EC= 9.999862469996990E-01
    A = 5.051508640044879E+02

    2335702.500000000 = A.D. 1682-Nov-01 00:00:00.0000 (CT)
    EC= 9.999860687070418E-01
    A = 4.987405396985163E+02

    2335732.500000000 = A.D. 1682-Dec-01 00:00:00.0000 (CT)
    EC= 9.999858954405773E-01
    A = 4.925593647503586E+02

    2335763.500000000 = A.D. 1683-Jan-01 00:00:00.0000 (CT)
    EC= 9.999857206156755E-01
    A = 4.862681253346676E+02

    2335794.500000000 = A.D. 1683-Feb-01 00:00:00.0000 (CT)
    EC= 9.999855679049779E-01
    A = 4.806992731887228E+02

    2335822.500000000 = A.D. 1683-Mar-01 00:00:00.0000 (CT)
    EC= 9.999854512040123E-01
    A = 4.763729798013061E+02

    2335853.500000000 = A.D. 1683-Apr-01 00:00:00.0000 (CT)
    EC= 9.999853502534436E-01
    A = 4.725056969173360E+02

    2335883.500000000 = A.D. 1683-May-01 00:00:00.0000 (CT)
    EC= 9.999852770681203E-01
    A = 4.696429772855428E+02

    2335914.500000000 = A.D. 1683-Jun-01 00:00:00.0000 (CT)
    EC= 9.999852066319553E-01
    A = 4.669433541106443E+02

    2335944.500000000 = A.D. 1683-Jul-01 00:00:00.0000 (CT)
    EC= 9.999851393051888E-01
    A = 4.643636938319050E+02

    2335975.500000000 = A.D. 1683-Aug-01 00:00:00.0000 (CT)
    EC= 9.999850690994565E-01
    A = 4.616771218164620E+02

    2336006.500000000 = A.D. 1683-Sep-01 00:00:00.0000 (CT)
    EC= 9.999849961654543E-01
    A = 4.588445313464725E+02

    2336036.500000000 = A.D. 1683-Oct-01 00:00:00.0000 (CT)
    EC= 9.999849383695164E-01
    A = 4.563996535534396E+02

    2336067.500000000 = A.D. 1683-Nov-01 00:00:00.0000 (CT)
    EC= 9.999848946862195E-01
    A = 4.543550271430692E+02

    2336097.500000000 = A.D. 1683-Dec-01 00:00:00.0000 (CT)
    EC= 9.999848595030110E-01
    A = 4.526052930843416E+02

    2336128.500000000 = A.D. 1684-Jan-01 00:00:00.0000 (CT)
    EC= 9.999848329574738E-01
    A = 4.510943267615367E+02

  • Jonny

    The above post is a bit clumsily worded in parts, for which I apologise and blame the headache I was suffering from, and the two kids distracting me (the two phenomena may even be correlated!).

    I have a had a bit of time this morning to graph up some the data on a finer scale (one day increments, instead of one month) to illustrate the effects of Jupiter. Below you will see data generated by the JPL Horizons program of the separation distance between C/1680 V1 and Jupiter (I calculated this myself based upon the heliocentric distances of the comet and jupiter) after the comets perihelion passage, and the change of its eccentricity and semi-major axis. I am not sure if the images show up in this post with the html formatting, but if not you can view the images upon the direct link below

    http://i219.photobucket.com/albums/cc263/jmcaneney/C1680V1semimajoraxis_zps99ab60cd.jpg

    http://i219.photobucket.com/albums/cc263/jmcaneney/C1680V1Eccentricity_zpsa9ed6e48.jpg

  • There is a review paper out (2013) by Boslough et al. on the Younger Dryas impact hypothesis if anyone is interested. I only read the abstract so I can’t comment. But I can comment on impact fluxes and I appreciate the work you guys are doing attempting to correlate impact markers and proxies to the lesser impacts that we know must be occurring aperiodically through time, which would presumably leave atmospheric traces that would be amenable to some sort of correlative investigation. On the YD I remain ambivalent. Continuous fresh water NADW formation forcing from ice sheet decay seems to be required, and any large impact at that time may indeed have been coincidental unless it occurred directly in the Laurentide ice sheet in some opportune spot. It still seems premature to pronounce it dead, but something definitive needs to be forthcoming or else it is indeed dead. Not to imply a dead hypothesis isn’t useful, as this is one hypothesis that has been very useful across a variety of interrelated and not so interrelated scientific disciplines. I think it is up to the principles to declare this hypothesis dead when or if that time comes, and I honestly don’t think that would be anything dishonorable. It would also be nice to see something a little more definitive in terms of dating on the Corossol impact crater in the Gulf of St. Lawrence, which is an indisputable astrobleme of a relatively early age, not yet known to any precision.

  • Jonny

    In an above post I stated

    “In order to have an orbital period of 333 years and thus be returning now on ISON’s orbit, its semi-major axis should be in the region of 48 AU. It would need a significant encounter in order to reduce a semi-major axis of over 400 AU to 48 AU, and if in such an encounter the acceleration exerted on a body as fragile as a comet may be in excess of its tensile strength.”

    This was a passing thought and amounted to “stream of consciousness” at the time, and upon further considerations is probably not an accurate statement, so please disregard. My apologies for such a comment.

  • Steve Garcia

    Jonny – What part of that was incorrect? It certainly seems it would take a significant encounter to change the semi-major axis that much.

    My thinking is that with such a high inclination it seems that it can’t BE in position to so a major encounter – by the time it is out as far as Jupiter or Saturn it is far, far out of the ecliptic. Yes? With 60°-61° it spends almost no time near any planet’s orbit. Am I wrong?

  • Jonny

    Steve, the part about being inaccurate is the idea that the comet would be pulled apart for having an encounter where its semi-major axis would be altered from the region of 400 to about 50. It was a sort of top of the head argument before I thought it through completely, and I dont have any evidence for it. It may be possible, or it may not be, but the truth is, that on second thoughts about teh statement, the statement may not actually be true, hence why it is inaccurate.

    For example, you look at the change of semi-major axis for C/1680 V1 it goes from ~450 to ~700 and then back again with its encounter with Jupiter on its outward journey. This is approximately the same magnitude of change as going from ~450 to ~50. We have no evidence that it was destroyed or not at this the encounter with Jupiter. Thus I would suggest that my original statement be disregarded as an erroneous thought process.

    How far a comet is above of below the ecliptic plane at the distance of Jupiter depends upon the inclination, but it also depends upon other factors of its orbit. For example, the asteroid/comet 2003 EH1 has an inclination of about 70 degrees, but it has a node close to the orbit of Jupiter. Therefore the orientation of the orbit with respect to the ecliptic plane can effect the distance at which an object passes above the ecliptic plane at the distance of Jupiter’s orbit. Also in some cases a large eccentricity (implying that the ratio of semi-minor axis to semi-major axis is small) then the comet can remain near to the ecliptic plane even with a large eccentricity. For example, even though C/1680 had an inclination of about 60 degrees, it actually only about 1 AU above the ecliptic plane at the orbital distance of Jupiter. If Jupiter happens to be close at this time, then it can effect the comet.

    I have done a more detailed calculation of minimum pass distance of Jupiter for C/1680. In the previous graphs the separation distance is not correct as it was based upon a rather simple (and quick) assumption and didn’t take into consideration the 3 dimensional positions of Jupiter and the comet with respect to each other. Basically i located Jupiter in 3d space, but just used the heliocentric comet distance. While this gives the feel of the situation, it produces a minimum separation that is too small in size (0.123 AU).

    If we use the correct vector summation then we get the following graphs (again using JPL’s Horizons application to generate the data from 18th December 1680 to 18th December 1683).

    http://i219.photobucket.com/albums/cc263/jmcaneney/C1680V1eccentricity_zpsd32541c9.jpg

    http://i219.photobucket.com/albums/cc263/jmcaneney/C1680V1semimajoraxis_zps7b63153d.jpg

    These graphs demonstrate that even though the minimum separation between Jupiter and C\1680 was 1.455 AU, it still affected C\1680′s orbital parameters (if temporarily). Further more, around this close approach it spends about 50 days at a distance less than 1.5 AU from Jupiter.

    In principle though, comets that are highly inclined to the ecliptic have less encounters with Jupiter than ones that orbit close to the ecliptic plane, but it is not explicitly the case that high inclination orbits cannot have close encounters with Jupiter.

  • Steve Garcia

    Thanks, Jonny, for your extra work and your excellent info. Your last sentence is what I’d gathered from your previous info, plus thinking about it in 3D as best I could.

  • Thomas Lee Elifritz

    The latest now is that the 775 tree ring event MAY be linked to a highly focused cosmological gamma ray event related to the merger of heavy bodies.

    I guess time will tell, with only a single data point, but another paper claims that solar energetic particles will not be of the flux necessary to do the job.

    I don’t have any links available at this time, sorry.

  • Jonny

    The link to the gamma ray burst paper is here http://mnras.oxfordjournals.org/content/early/2013/01/08/mnras.sts378.full.pdf+html

    as I have posted elsewhere

    These hypotheses tend to be suggested because of a lack of historical records of any supernova event at that time, but to me there seems to be a flaw in the logic of assuming that just because one is not recorded does not mean that one did not occur. As discussed previously the event may have been recorded in the source material for the Anglo-saxon Chronicles and Roger of Wendower (even though they seem to disagree by a year or two). For example, Roger gives the description of

    Quote:
    “In the year of our Lord 776, fiery and fearful signs were seen in the heavens after sunset ; and serpents appeared in Sussex, as if they had sprung out of the ground, to the great astonishment of all”

    But according to the Anglo-Saxon Chronicle in 774

    Quote:
    “This year the Northumbrians banished their king, Alred, from York at Easter-tide; and chose Ethelred, the son of Mull, for their lord, who reigned four winters.
    This year also appeared in the heavens a red crucifix, after sunset; the Mercians and the men of Kent fought at Otford; and wonderful serpents were seen in the land of the South-Saxons.”

    Similarly, Roger has this to say about the year 794

    Quote:
    “In the year of our Lord 794, Humbert, archbishop of Lich field, died, and was succeeded by Higbert. The same year dreadful prodigies terrified the miserable English nation ; for fearful thunderbolts and horrible fiery dragons were seen passing through the air, foreboding a mighty famine and dreadful slaughter of the people. For the Danes with the Norwegians committed sad havoc among the people of Northumberland and of Lindesfarne, destroying the churches of Christ with their inmates. The island of Lindisfarne, which has an extent of eight miles or more, contains a noble monastery, in which was buried the illustrious father, bishop Cuthbert, with other prelates, his most holy successors. Now the Lindis is a rivulet, flowing into the sea, and is about two feet in width at low tides, but at high tides it cannot be seen.”

    While the Anglo-Saxon Chronicle has this to say in 793

    Quote:
    “In this year dire portents appeared over Northumbria and sorely frightened the people. They consisted of immense whirlwinds and flashes of lightning, and fiery dragons were seen flying in the air. A great famine immediately followed those signs , and a little after that in the same year, 8 June, the reavers of the heathen men miserably destroyed God’s church in Lindisfarne, with plunder and slaughter. And Sicga died on 22 February.”

    From the recent Gamma ray burst paper, from my understanding of the paper, the researchers were looking for a mechanism that could generate gamma rays without a visible supernova. The issue seems to be the belief that no supernova was observed/recorded at the time, hence the different hypothesised scenarios. Indeed, in the outset of the recent paper, the authors construct their argument that a supernova capable of producing enough gamma rays to explain the 14C excess should have been within 260 parsecs (about 850 light years), and so should have been visible. In order for it to remain undetected there would have to be extreme optical absorption, which would be impossible for the distance, ergo it was not an ordinary supernova, and must have been something else. But what if it was observed and recorded, for example in the sources of Roger of Wendower or the Anglo-Saxon Chronicle, or has not been recognised as being recorded, then a normal supernova should still be on the table.

  • In reference to your last link Barry, somehow I don’t think this latest round of nay-saying is going to have much effect on our favorite hypothesis. After all, there is a fundamental difference between doing real science in the field and lab, and refuting that science with unsubstantiated opinions from the comfort of a desk, and keyboard. And there is still an awful lot of field data to be considered before closing the book.

  • Barry Weathersby

    I just love settled, uncontroversial, undisputed, unquestioned resolutions of issues. That’s why I am addicted to this site. No disagreements re this idea.

  • Hermann Burchard

    Barry,
    more of this clear-cut stuff, w/permit from EPG pending.

    http://www.mail-archive.com/meteorite-list@meteoritecentral.com/msg110580.html

    There’s more where this came from.

  • George Howard

    Thanks Barry!

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>