<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Rosetta&#8217;s final descent to Comet 67P/C-G	</title>
	<atom:link href="https://behindtheblack.com/behind-the-black/points-of-information/rosettas-final-descent-to-comet-67pc-g/feed/" rel="self" type="application/rss+xml" />
	<link>https://behindtheblack.com/behind-the-black/points-of-information/rosettas-final-descent-to-comet-67pc-g/</link>
	<description></description>
	<lastBuildDate>Wed, 09 Nov 2016 00:15:24 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Levi Nelson		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/rosettas-final-descent-to-comet-67pc-g/#comment-944552</link>

		<dc:creator><![CDATA[Levi Nelson]]></dc:creator>
		<pubDate>Wed, 09 Nov 2016 00:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=41552#comment-944552</guid>

					<description><![CDATA[Hello Mr. Zimmerman, I have a interview request for you. Do you have a email that I can forward that request to? Thanks so much]]></description>
			<content:encoded><![CDATA[<p>Hello Mr. Zimmerman, I have a interview request for you. Do you have a email that I can forward that request to? Thanks so much</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Gealon		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/rosettas-final-descent-to-comet-67pc-g/#comment-927332</link>

		<dc:creator><![CDATA[Gealon]]></dc:creator>
		<pubDate>Fri, 09 Sep 2016 19:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=41552#comment-927332</guid>

					<description><![CDATA[Update: It appears the reasoning behind the crash/shutdown of Rosetta&#039;s systems is apparent to comply with, you guessed it, government regulations. Not too far off from my supposition that the motivation is political. The probe is evidently being shut down on impact to prevent it from transmitting accidently and interfering with communications channels on the DSN. Frankly this does not change my thinking on the matter.

If they can instruct the spacecraft to shut it&#039;s self down, they can instruct it to disable it&#039;s transmitter After a computer restart. This would ensure that if Rosetta survives the landing, it could continue to transmit data for as long as it&#039;s batteries permit. Once the batteries die, the computer shut&#039;s down. Then if in the future the solar panels recharge the batteries enough for the computer to restart, it would simply sit there waiting for instructions, NOT using it&#039;s transmitter. This should satisfy everyone from explorers to the government toads that come up with these ridiculous rules, and I&#039;m sure must have been an option proposed. But it&#039;s not being acted upon and this chance to explore the surface of the comet, going boldly to coin a phrase, is instead being turned into nothing more then a stunt. True some information will be acquired during the descent, but what about what could be learned on the surface?

Link, the answer I&#039;m quoting above is about half way down the page: http://www.esa.int/Our_Activities/Space_Science/Rosetta/Rosetta_s_grand_finale_frequently_asked_questions]]></description>
			<content:encoded><![CDATA[<p>Update: It appears the reasoning behind the crash/shutdown of Rosetta&#8217;s systems is apparent to comply with, you guessed it, government regulations. Not too far off from my supposition that the motivation is political. The probe is evidently being shut down on impact to prevent it from transmitting accidently and interfering with communications channels on the DSN. Frankly this does not change my thinking on the matter.</p>
<p>If they can instruct the spacecraft to shut it&#8217;s self down, they can instruct it to disable it&#8217;s transmitter After a computer restart. This would ensure that if Rosetta survives the landing, it could continue to transmit data for as long as it&#8217;s batteries permit. Once the batteries die, the computer shut&#8217;s down. Then if in the future the solar panels recharge the batteries enough for the computer to restart, it would simply sit there waiting for instructions, NOT using it&#8217;s transmitter. This should satisfy everyone from explorers to the government toads that come up with these ridiculous rules, and I&#8217;m sure must have been an option proposed. But it&#8217;s not being acted upon and this chance to explore the surface of the comet, going boldly to coin a phrase, is instead being turned into nothing more then a stunt. True some information will be acquired during the descent, but what about what could be learned on the surface?</p>
<p>Link, the answer I&#8217;m quoting above is about half way down the page: <a href="http://www.esa.int/Our_Activities/Space_Science/Rosetta/Rosetta_s_grand_finale_frequently_asked_questions" rel="nofollow ugc">http://www.esa.int/Our_Activities/Space_Science/Rosetta/Rosetta_s_grand_finale_frequently_asked_questions</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Gealon		</title>
		<link>https://behindtheblack.com/behind-the-black/points-of-information/rosettas-final-descent-to-comet-67pc-g/#comment-927326</link>

		<dc:creator><![CDATA[Gealon]]></dc:creator>
		<pubDate>Fri, 09 Sep 2016 18:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://behindtheblack.com/?p=41552#comment-927326</guid>

					<description><![CDATA[Again I see them going on about how it will be impossible to get any data from the spacecraft after it touches down. And now I&#039;m noting most pointedly in the first link, that they are no longer calling it a landing, but an &quot;impact.&quot; I could take hours to go back to see when this trend started but commenting on the lack of a proper landing attempt is the main reason for my posting and I&#039;d like to stay on point. So the question is, why the &quot;impact?&quot; When Near landed on Eros it too was running out of fuel, but they still managed to make a controlled landing, leaning on it&#039;s solar panels no less.

Why can&#039;t Rosetta descend in a similar fashion, and land on it&#039;s instrumented side? Literally push them into the soil, and if any survive, keep taking readings. Even if they can&#039;t point the high gain antenna any more, they still have the lower power transmitters. And again even if the solar panels are no longer pointed directly at the sun, the spacecraft has a battery power reserve. USE IT. Fire the RCS jets again a few minutes before expected &quot;impact&quot; to kill the velocity and let it drift down nice and slow. True, it will probably bounce just like Philae did, but at least you&#039;ll make something resembling a controlled landing and who knows, the vehicle might still be functional when it stops. Don&#039;t just crash it into the surface and be done with it. Heck, if they wanted to ensure it doesn&#039;t bounce, it wouldn&#039;t be that hard to feed in another parameter into the programing so that when the vehicle&#039;s IMU&#039;s sense the initial collision, it fire&#039;s it&#039;s jets in a downward direction and hold&#039;s it&#039;s self against the surface. But I&#039;m expecting too much.

Everything I&#039;m proposing here could be accomplished without jeopardizing ESA&#039;s current plan to Crash Rosetta into the pit. The additions to the programming would take effect only in the last minutes of the descent and given that ESA&#039;s already given up on the craft at that point, and to paraphrase Mr. Trump, What do they have to lose? The probe is already written off after this point anyway. Why not invest a few extra minutes in updating a line of code and see what you can learn from it? 

This to me illustrates the difference between the Near team and the Rosetta team. Near descended and landed in the hope of the craft still functioning after touch down, so that we might learn something from it. Rosetta will be crashed into the comet just so ESA can say, &quot;We did it too.&quot; I&#039;m of the mind that the choice to &quot;land&quot; here is purely political. Nothing can be learned if you intentionally destroy the spacecraft.]]></description>
			<content:encoded><![CDATA[<p>Again I see them going on about how it will be impossible to get any data from the spacecraft after it touches down. And now I&#8217;m noting most pointedly in the first link, that they are no longer calling it a landing, but an &#8220;impact.&#8221; I could take hours to go back to see when this trend started but commenting on the lack of a proper landing attempt is the main reason for my posting and I&#8217;d like to stay on point. So the question is, why the &#8220;impact?&#8221; When Near landed on Eros it too was running out of fuel, but they still managed to make a controlled landing, leaning on it&#8217;s solar panels no less.</p>
<p>Why can&#8217;t Rosetta descend in a similar fashion, and land on it&#8217;s instrumented side? Literally push them into the soil, and if any survive, keep taking readings. Even if they can&#8217;t point the high gain antenna any more, they still have the lower power transmitters. And again even if the solar panels are no longer pointed directly at the sun, the spacecraft has a battery power reserve. USE IT. Fire the RCS jets again a few minutes before expected &#8220;impact&#8221; to kill the velocity and let it drift down nice and slow. True, it will probably bounce just like Philae did, but at least you&#8217;ll make something resembling a controlled landing and who knows, the vehicle might still be functional when it stops. Don&#8217;t just crash it into the surface and be done with it. Heck, if they wanted to ensure it doesn&#8217;t bounce, it wouldn&#8217;t be that hard to feed in another parameter into the programing so that when the vehicle&#8217;s IMU&#8217;s sense the initial collision, it fire&#8217;s it&#8217;s jets in a downward direction and hold&#8217;s it&#8217;s self against the surface. But I&#8217;m expecting too much.</p>
<p>Everything I&#8217;m proposing here could be accomplished without jeopardizing ESA&#8217;s current plan to Crash Rosetta into the pit. The additions to the programming would take effect only in the last minutes of the descent and given that ESA&#8217;s already given up on the craft at that point, and to paraphrase Mr. Trump, What do they have to lose? The probe is already written off after this point anyway. Why not invest a few extra minutes in updating a line of code and see what you can learn from it? </p>
<p>This to me illustrates the difference between the Near team and the Rosetta team. Near descended and landed in the hope of the craft still functioning after touch down, so that we might learn something from it. Rosetta will be crashed into the comet just so ESA can say, &#8220;We did it too.&#8221; I&#8217;m of the mind that the choice to &#8220;land&#8221; here is purely political. Nothing can be learned if you intentionally destroy the spacecraft.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
