This week's CometWatch is an image taken with Rosetta's NAVCAM on 1 May 2016, when the spacecraft was 18.8 km from the nucleus of Comet 67P/Churyumov-Gerasimenko.
Enhanced NAVCAM image of Comet 67P/C-G taken on 1 May 2016, 18.8 km from the nucleus. The scale is 1.6 m/pixel and the image measures 1.6 km across. Credits: ESA/Rosetta/NAVCAM – CC BY-SA IGO 3.0
The view shows a portion of the large comet lobe on the left, while hints of the neck and small lobe are visible in the lower right corner. On the large lobe, the image reveals the striking difference between the Atum region, on the left, and Anubis, on the right.
The irregular terrains of Atum display the complex morphology of this region, with depressions, a wealth of linear features and only a few boulders. The adjacent Anubis, instead, is characterised by smooth terrains punctuated with several boulders.
The sharp boundary separating Anubis and Seth is visible on the right edge, and a small portion of Anuket, on the small lobe, can be see in the lower right.
A different perspective is portrayed in this recent image captured by Rosetta's OSIRIS narrow-angle camera on 3 May. In this orientation, the Wosret region, on the small comet lobe, is visible on the left, declining towards Sobek, on the neck, and further to the large lobe on the right.
OSIRIS narrow-angle camera image taken at 05:43 UTC on 3 May 2016, when Rosetta was 18.8 km from Comet 67P/C-G. The scale is 0.33 m/pixel. Credits: ESA/Rosetta/MPS for OSIRIS Team MPS/UPD/LAM/IAA/SSO/INTA/UPM/DASP/IDA
Another OSIRIS image, taken with the same camera just a few hours earlier, shows a patch of Imhotep, on the large lobe, in staggering detail, uncovering the smooth deposits and boulders that cover this region.
OSIRIS narrow-angle camera image taken at 00:22 UTC on 3 May 2016, when Rosetta was 18.8 km from Comet 67P/C-G. The scale is 0.33 m/pixel. Credits: ESA/Rosetta/MPS for OSIRIS Team MPS/UPD/LAM/IAA/SSO/INTA/UPM/DASP/IDA
The original NAVCAM image is provided below.
from Rosetta – ESA's comet chaser http://ift.tt/1WnfxJC
via IFTTT
No comments:
Post a Comment