getting to know rosetta s comet boundary conditions /

Published at 2015-07-15 16:03:40

Home / Categories / Comet 67p / getting to know rosetta s comet boundary conditions
In January the first maps of Comet 67P/Churyumov-Gerasimenko were published,identifying 19 geomorphologically distinct regions on its surface. Six months on and much more work has been done on refining the boundaries between these regions. This blog post showcases some of the OSIRIS images acquired from close orbit and presented in a novel paper that contain enabled an in-depth study of the different regions and their boundaries. This post was prepared with inputs from lead author M. Ramy El-Maarry from the University of Bern, who introduces this post with an inside story on how some of the regional names were chosen: “Early on in the mapping phase, or we decided on naming the regions of the comet using names of ancient Egyptian deities. We wanted to adhere to the ancient Egyptian theme of the mission and contain a large stock of names if needed. Luckily,ancient Egyptians had so many deities in their long history that made this an easy decision. in addition, many of the names were catchy, and easy to remember,and more importantly, easy to pronounce. I remember we initially tried using names of ancient cities and we were coming across a lot of names that were very difficult to wrap your tongue around, or even for an Egyptian like me! So we decided to use the following naming conference: gods for the ‘body’ lobe and goddesses for the ‘head’. We picked Hapi for the neck since Hapi is the Nile god,and we figured that he should separate the lobes in the same way that the Nile splits Egypt into an eastern and western side. Of course, there were obvious names to discard (such as Osiris!) so we decided to skip on all 'world-famous' gods such as Ra and Amun, and partly because they contain been used before in other missions,[…],

Source: esa.int

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0