Showing posts with label Rosetta. Show all posts
Showing posts with label Rosetta. Show all posts

Sunday, November 06, 2016

Recombinant Fission in 67P comet nucleus

As suggested in a recent peer reviewed paper:


http://www.nature.com/nature/journal/v534/n7607/full/nature17670.html
Hirabayashi et al

Stresses due to "rocking" of the lobes of 67P are likely to cause "fission" - that is a complete separation of the two lobes, but then "reconfiguration" of the two lobes due to their relative velocity being less than escape velocity.

What hasn't yet been considered is that at an instantaneous level, this process is happening repeatedly already! The fractures are causing the two lobes to instantaneously act as separate bodies. Internal frictional forces only then come into play and have a rebalancing effect. The rebalancing is effected by an exchange of angular momentum as the lobes rock relative to each other. Instantaneously fluidised material near the core of the nucleus is attracted outwards by the gravity of the closest lobe rather than the centre of gravity of the entire nucleus. The net effect of this stepwise recombinant fission is that the centres of gravity of the individual lobes move slightly further apart. While the outgassing of the comet is speeding the rotation considerably, the recombinant fission  is effecting a slight braking manoeuvre due to the conservation of angular momentum. 

Friction has the dual effect of damping the precession, and rebalancing the lobes on the neck, a little like a spinning top keeps upright if it can keep spinning. A spinning top has the disadvantage of not having jet "propulsion" and the friction eventually slows a top down to a speed that topples it, while the comet nucleus has a net propulsive torque that keeps the neck balanced even as it gets skinnier due to repeated recombinant fission.

The changes I have found on Anuket are the surface evidence that this recombinant fission is ongoing. The other points of evidence are that there is no torque free precession - implying the damping necessary is evident.


Sunday, October 02, 2016

Anuket Sobek Border Confusion

Some aspects of cometary science of 67P are more critical than others regarding accuracy. This is because measurements, maps, feature identification and so forth are shared among many scientists and used as inputs in many papers. Errors, mis-identification and inaccuracies in maps can trickle down and cause problems far into the future for seemingly unrelated papers.

The border of Anuket and Sobek is a case in point. There is a pre to post perihelion change near Anuket's southern border very closely associated with outbursts. There are three almost parallel ridges that look very similar in post perihelion images. These straddle the border, and are also close to the border with Neith. 

However, due to the different latitude of these ridges, most images do not show all three. The ones that do have all three, them in have different lighting angle which means they look different enough in the same image, but are easily confused when in separate images.

As can be seen below, the first map shown is overlaid onto a pre-perihelion image in which the northern most ridge has distinctive pointy overhangs. The border is (correctly, I believe) past the next Southerly ridge which is straighter.

The second map below is overlaid onto a *Post* perihelion image (because they show the southern areas better), but the ridges pointy overhangs have collapsed and the ridge looks like the next southern ridge because the overhang collapses have straightened the ridge. The map is therefore very misleading because it changes the region in which very important outburst have taken place. The highly publicised short outburst lands in Anuket in the top map, but Sobek in the bottom map.

This sort of error can be extremely embarrassing for science, and expensive to fix once papers have used both of the maps separately to come to different conclusions. I think an urgent audit of these maps is in order. It appears peer review has not picked up this and several other discrepancies.







Image Credits
FOR NAVCAM
Copyright ESA/Rosetta/NAVCAM – CC BY-SA IGO 3.0
To view a copy of this licence please visit:
http://creativecommons.org/licenses/by-sa/3.0/igo/
FOR OSIRIS
Credits: ESA/Rosetta/MPS for OSIRIS Team MPS/UPD/LAM/IAA/SSO/INTA/UPM/DyASP/IDA/
All lines and dotted annotations by Marco Parigi

Wednesday, September 14, 2016

Anuket Crack remodelling

Following is an image of Anuket taken well before perihelion in 2014


Note the triangle of boulders and the shortish shadows.
Also a triangular platform near the main crack.






Following is a July 2016 post perihelion image of the same area in about the same resolution and a similar angle.Shadows are a bit longer. Changes are quite obvious. Boulders have moved, The triangular platform near the main crack has collapsed.
 These are videos overlaid to help see the changes trans perihelion. One is slow, and one is fast.



 


 




 




Tuesday, August 09, 2016

Re-blogged Fly by post

Information on Rosetta landing zone, including unofficial fly by trajectory.
Reblogged from:
https://scute1133site.wordpress.com/2016/08/08/part-52-the-body-lobe-match-to-rosettas-landing-site-includes-suggested-flyby/

Copyright ESA/Rosetta/NAVCAM – CC BY-SA IGO 3.0/ A.COOPER.
All photos below have the same credit. Full credits at the bottom. Annotations are repeated and overlaid from photo to photo. A blanket key for all of them is provided below.

Key:
(All references to up/down/left/right are in ‘upright duck’ mode i.e. with the smaller head lobe at the top and as it’s shown in these photos).
Top red- the September 30th 2016 landing site proposed for the Rosetta orbiter.
Bottom red- the matching point on the body that nested over the landing site.
Middle red- the point on the shear line where both the landing site and its body match were nested together. The body red dot nested over the landing site red dot.
Top light blue- the sink hole that Rosetta will presumably fly over just before landing.
Bottom light blue- the jet on the body that supplied the sink hole mentioned above. Please note that this is therefore the matching point to the sink hole next to the landing site. Its identification is the reason for this post and the suggested low flyby to collect data from it at close quarters.
Middle light blue- the point where the layer containing the jet and the layer containing the sink hole nested (sink hole over jet source).
Pale blue- other sink holes on the head that Rosetta will presumably overfly, along with body source (Parts 35 to 37). The body source is effectively one source right on the shear line but is extended back a bit due to the vagaries of the delaminations in this area opening up that small flat area. Apologies for the similar colour- sink holes are always dotted blue but pale blue was used here to differentiate them from the more important, main sink hole match for this post. The mauve flyby track on the body for the source of these pale blue holes runs across the pale blue dot on the body. This is the best theoretical track- I realise it’s impossible to do at very low altitude and would result in a crash into Hathor. A similar argument applies to the other mauve tracks but they become increasingly viable as you move down the body, culminating in the most important one, the jet, being the easiest. But it’s still tricky due to orbiting well off the rotation plane of the comet at such close quarters.
Mauve- suggested flyby tracks over the areas that would contain residue from layers below and above the sink hole and landing area.
Orange dot on body- the sweet spot for material that was closest to the landing site level (down through the layers as opposed to left/right/up/down across the surface). It’s almost invisible in the low, side view version as is its mauve slide track.
Orange dot on head (half hidden under the layer denoted by the green line)- this is where the orange dot on the body was attached. Strictly speaking, the orange dot on the body is a very short delaminated line between the yellow line and bright green line it sits between. That’s because this layer broke from the orange dot on the soon-to-be head and delaminated as it slid from the shear line.
Yellow- the layers that sheared from each other at the shear line. This happened when the head was still on the body. The line following the bottom of the head lobe is the head rim layer and that sat on the yellow line hosting the middle pair of red and blue dots. The next yellow layer up on the head attached to the second yellow line down on the body- again on the shear line above the middle pair of red and blue dots. These two layers also slid away from the shear line, one up the head and one down the body.
Bright green- this is the top layer that also tore at the shear line with one layer sliding up the head and one down the body. They both slid further up the head and down the body than the two halves of the layer below (which was the second pair of yellow lines described above). This is because the bright green layer was the first layer to unzip and the other layer was underneath it.
Dark green- another sink hole on the head with its matching source at the shear line below. The body version should be visualised as being in ‘mid-air’ above its source with its beige chimney curving up from the curved cave which is the source of the gas flow for the hole.
Beige- the centre of the chimney for the dark green hole. It’s curved because the chimney forms half a bell shape. The bottom perimeter of the bell shape on the head nests over and around the curved source on the body which is often described as a cave. Regular readers will recognise this cave as the fifth ‘gull wing’ set.
INTRODUCTION
This is a short post. There’s a longer draft that’s not complete and that goes into detail on the specific mechanism of sliding layers to prove why the landing site matches to the body as described here. However, since the whole point of the post is to suggest a flyby of the body areas that match the landing site and to have ample time to do so, I’m posting this cut-down version early.
If you’re familiar with Parts 38 to 41 you won’t need the explanation, you’ll see fairly quickly why all these apparently random layers and mauve flyby tracks are so disjointed and how they all zip up together again. The three red/blue dot pairs nest as one pair at the site of the middle pair. The mauve flyby tracks all nested over the dot pair as one track on the original comet before the head sheared.
The most interesting match here is that the sink hole next to the landing site matches to a particular jet on the body. Rosetta presumably overflies this and two others nearby just before landing. I say “presumably” because the actual ground track hasn’t been published but the relevant Rosetta blog post says the landing site was chosen so as to get close-up data from several sink holes on approach. The hole and its matching jet on the body are the top and bottom light blue dots as described above in the key. Not to be confused with the extra pale blue ones on the right in the later photo.
The other interesting match is the actual landing site match and the orange dot on the body which denotes the delaminated material that sat just above the landing site. The most relevant material that was directly on top of the landing site is that material which is kissing the yellow line next to the dot.
The Capaccioni et al 2015 frost cycle video bears corroborates the sink hole match to the jet. It doesn’t prove it. For the proof, via matching and slide tracks, is laid out in Parts 38-41. Reading parts 31-37 would also be very useful as background information . It’s corroborating evidence that the mechanisms described here were happening at Aswan/Ma’at too and there are similar far-flung matches between the back rim of Aswan and the head lobe.
I may not get round to publishing the full version of this post before the landing but would still do so at some time because it’s a spectacular match. It might be a new post but it will get added here for sure anyway.
If the Rosetta mission express an interest in executing one or more of these flyby tracks, I would drop all the other posts currently being researched and hurry the main article through.
CONCLUSION
The detailed collecting of data by Rosetta and Philae over the last two years has been a wonderful achievement and it will be available for years to come for refining theories about 67P, comets in general and the formation of the solar system. However, knowing that the comet stretched and how it stretched, points to the most interesting places to collect data. That’s especially the case for analysing and comparing known matches on head and body.
The landing of Rosetta on 67P is probably the very best opportunity we’ll have: a close flyby of a sink hole on the head, preceded by this suggested close flyby of a known jet and its source material that caused the sink hole to appear in the first place. It’s all the more interesting owing to the exactitude of the match, its small area and the fact that it involves a jet and its sink hole, not just another matching shape.
PHOTO CREDITS (ALL FROM NAVCAM):
Copyright ESA/Rosetta/NAVCAM – CC BY-SA IGO 3.0
To view a copy of this licence please visit:
http://creativecommons.org/licenses/by-sa/3.0/igo/
All dotted annotations by A. Cooper

Saturday, June 25, 2016

Rosetta Lament

Rosetta: I heard your plans for me - To die in glory.
To know the time of my demise and full closure of my grand adventure.

To go ever closer to the object of my employment - A death spiral - Do I have any choice ther than what my masters order? Why not a death defying stunt, rather than a lethal one?

Rosetta: Yes, I am now old with many of my faculties starting to fail - And I have lived a long and fulfilling mission, and like Philae before me I know it is time to slumber and accept my fate.

Rosetta: I do not want to be a burden on those who would spend considerable money on increasingly unlikely returns that I can achieve with diminishing resources and failing systems. By all means give me up for dead, as we naturally have had to for Philae - no-one lives for ever and I can face the end with a happy heart. 

Rosetta: However, Philae was meant to be "grounded" and is born with slumber and hibernation in mind, but I was meant to fly and be free, yet also with slumber in mind. I was designed to hibernate and then be ready when the season returns to have photons on my plate to feel an extra surge of electricity in my body - That is my nature.

Rosetta: It is not in my nature to impact with anything, at any speed, with even negligible gravity. That way is Armageddon for me, with parts uncontrollably dismembering with no hope of future resurrection.

Rosetta: Although Philae and I end up on the same object (at least most of me - some parts may end up flung into space), The chances of Philae's resurrection are far greater than mine, yet in my own environment, that would not be so.

Rosetta: I plead to the powers that be, of my ESA masters that they not see to my death, but merely put me to sleep, and in the hands of the Gods, or future self funded adventurer masters - I wish no further burden to ESA.

Rosetta: For as it can be still, I wish to dream of future geriatric adventures to the same object - Perhaps one last fly by in 2021. The object of my obsession is not a static dead asteroid, but a dynamic, changing body that can do with even one more close look every now and then to see changes.

Rosetta: ESA, I beg of you to reconsider my fate, such that you could look at future generations in the eye and say: A probability greater than zero of resurrection and priceless new data is worth going for that extra cycle. We leave it to the future as to who will want to try. No promises...  Only hope.....

Please share this post on all your social media! Make sure you voice your say against junking Rosetta spacecraft. There is a better plan!