<?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 for Dot Physics</title>
	<atom:link href="http://blog.dotphys.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dotphys.net</link>
	<description>Physics and Stuff</description>
	<pubDate>Wed, 07 Jan 2009 14:11:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on I&#8217;m Iron Man.  (no, I&#8217;m not) by jacob swink</title>
		<link>http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/comment-page-1/#comment-1757</link>
		<dc:creator>jacob swink</dc:creator>
		<pubDate>Wed, 07 Jan 2009 05:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/#comment-1757</guid>
		<description>&lt;p&gt;your just ruining the movie so shut your freakin mouth&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>your just ruining the movie so shut your freakin mouth</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on WALL-E Gravity and Air by Rhett</title>
		<link>http://blog.dotphys.net/2009/01/wall-e-gravity-and-air/comment-page-1/#comment-1752</link>
		<dc:creator>Rhett</dc:creator>
		<pubDate>Tue, 06 Jan 2009 18:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/wall-e-gravity-and-air/#comment-1752</guid>
		<description>&lt;p&gt;@meichnel&lt;/p&gt;

&lt;p&gt;Thanks for the insightful comment.&lt;/p&gt;

&lt;p&gt;Rhett&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@meichnel</p>

<p>Thanks for the insightful comment.</p>

<p>Rhett</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Basics: Vectors and Vector Addition by Alek</title>
		<link>http://blog.dotphys.net/2008/09/basics-vectors-and-vector-addition/comment-page-1/#comment-1751</link>
		<dc:creator>Alek</dc:creator>
		<pubDate>Tue, 06 Jan 2009 18:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2008/09/basics-vectors-and-vector-addition/#comment-1751</guid>
		<description>&lt;p&gt;Hi. Good site.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi. Good site.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physics of Fantastic Contraption I by Gfunk</title>
		<link>http://blog.dotphys.net/2008/10/physics-of-fantastic-contraption-i/comment-page-1/#comment-1744</link>
		<dc:creator>Gfunk</dc:creator>
		<pubDate>Tue, 06 Jan 2009 00:08:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2008/10/physics-of-fantastic-contraption-i/#comment-1744</guid>
		<description>&lt;p&gt;"This shows that it does indeed acceleration."&lt;/p&gt;

&lt;p&gt;Maybe you should spend time brushing up on your English instead of wasting your obvious Physics talent with blogs like this...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;This shows that it does indeed acceleration.&#8221;</p>

<p>Maybe you should spend time brushing up on your English instead of wasting your obvious Physics talent with blogs like this&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on WALL-E Gravity and Air by meichenl</title>
		<link>http://blog.dotphys.net/2009/01/wall-e-gravity-and-air/comment-page-1/#comment-1743</link>
		<dc:creator>meichenl</dc:creator>
		<pubDate>Mon, 05 Jan 2009 23:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/wall-e-gravity-and-air/#comment-1743</guid>
		<description>&lt;p&gt;I'll try to give an argument that does not answer your final question directly, but could at least serve as the beginning of a discussion.&lt;/p&gt;

&lt;p&gt;Suppose you have a certain amount of information which you want to remember exactly, so you make a digital record of it with &lt;i&gt;n&lt;/i&gt; bits.  However, every minute, each bit of information has some small chance &lt;i&gt;p&lt;/i&gt; of being flipped randomly.  Over a long time, you accumulate errors and your record evolves into completely random mush.&lt;/p&gt;

&lt;p&gt;Now imagine you foresaw the previous disaster, so you decided to build three records of information.  They begin identically.  Again, every minute, each bit has some small probability &lt;i&gt;p&lt;/i&gt; of being flipped.  So, at the end of each minute, you compare all three records.  If a bit flipped, you'll have one record that disagrees with the other two.  That way, you catch the mistake, and can manually flip it back.&lt;/p&gt;

&lt;p&gt;Unfortunately, after some extremely long period of time, you will have a case where the very same bit flips in two different records in the same minute.  When you do the comparison at the end of the minute, the record with the correct bit will be outvoted, and you'll lose some of your information for the first time.  But if this happens once, give it long enough, and it will happen again and again.  So after many ages, you'll again have mush for data.&lt;/p&gt;

&lt;p&gt;Assuming the rate of random errors is fixed, you can slow the degradation of your data by
1) making more copies
2) checking more frequently
Say you make &lt;i&gt;c&lt;/i&gt; copies of your data and check on it with a frequency &lt;i&gt;f&lt;/i&gt;.  The sad news is that for any given probability P that no degradations have taken place, we can find some function t(c,f,n,p,P) that gives a time &lt;i&gt;t&lt;/i&gt; such that if you wait for &lt;i&gt;t&lt;/i&gt; minutes, the probability that you will lose some of your data exceeds P.&lt;/p&gt;

&lt;p&gt;In other words, if you want things to remain &lt;i&gt;exactly&lt;/i&gt; the same for infinitely long, even an infinite supply of free energy won't save you.  Eventually, you'll have to forget.&lt;/p&gt;

&lt;p&gt;However, there could be a way around this.  What you need to do is continually increase the number of copies of data you have as a function of time (or continually increase the frequency of your checks as a function of time).  If you continually make more copies of your data as time goes on, you may be able to get your probability of an error to converge to some value less than one as &lt;i&gt;t&lt;/i&gt; -&#62; infinity.  However, to implement this strategy, the number of copies of the data you're capable of storing would have to be unbounded (or the frequency with which you conduct checks on your data would have to be likewise unbounded.)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ll try to give an argument that does not answer your final question directly, but could at least serve as the beginning of a discussion.</p>

<p>Suppose you have a certain amount of information which you want to remember exactly, so you make a digital record of it with <i>n</i> bits.  However, every minute, each bit of information has some small chance <i>p</i> of being flipped randomly.  Over a long time, you accumulate errors and your record evolves into completely random mush.</p>

<p>Now imagine you foresaw the previous disaster, so you decided to build three records of information.  They begin identically.  Again, every minute, each bit has some small probability <i>p</i> of being flipped.  So, at the end of each minute, you compare all three records.  If a bit flipped, you&#8217;ll have one record that disagrees with the other two.  That way, you catch the mistake, and can manually flip it back.</p>

<p>Unfortunately, after some extremely long period of time, you will have a case where the very same bit flips in two different records in the same minute.  When you do the comparison at the end of the minute, the record with the correct bit will be outvoted, and you&#8217;ll lose some of your information for the first time.  But if this happens once, give it long enough, and it will happen again and again.  So after many ages, you&#8217;ll again have mush for data.</p>

<p>Assuming the rate of random errors is fixed, you can slow the degradation of your data by
1) making more copies
2) checking more frequently
Say you make <i>c</i> copies of your data and check on it with a frequency <i>f</i>.  The sad news is that for any given probability P that no degradations have taken place, we can find some function t(c,f,n,p,P) that gives a time <i>t</i> such that if you wait for <i>t</i> minutes, the probability that you will lose some of your data exceeds P.</p>

<p>In other words, if you want things to remain <i>exactly</i> the same for infinitely long, even an infinite supply of free energy won&#8217;t save you.  Eventually, you&#8217;ll have to forget.</p>

<p>However, there could be a way around this.  What you need to do is continually increase the number of copies of data you have as a function of time (or continually increase the frequency of your checks as a function of time).  If you continually make more copies of your data as time goes on, you may be able to get your probability of an error to converge to some value less than one as <i>t</i> -&gt; infinity.  However, to implement this strategy, the number of copies of the data you&#8217;re capable of storing would have to be unbounded (or the frequency with which you conduct checks on your data would have to be likewise unbounded.)</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on I&#8217;m Iron Man.  (no, I&#8217;m not) by Anonymous Coward</title>
		<link>http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/comment-page-1/#comment-1741</link>
		<dc:creator>Anonymous Coward</dc:creator>
		<pubDate>Mon, 05 Jan 2009 01:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/#comment-1741</guid>
		<description>&lt;p&gt;I liked your analysis, but I question the assumptions that went into your value for "d".  Given typical impact crater formation, I think it would be safe to assume the local sand height was significantly higher pre-impact than it is post-impact.&lt;/p&gt;

&lt;p&gt;I think Professor Jones's trip in the refrigerator (in Indiana Jones 4) is a more egregious example of that kind of bad movie physics.  Or maybe I'm just saying that because I liked Iron Man more.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I liked your analysis, but I question the assumptions that went into your value for &#8220;d&#8221;.  Given typical impact crater formation, I think it would be safe to assume the local sand height was significantly higher pre-impact than it is post-impact.</p>

<p>I think Professor Jones&#8217;s trip in the refrigerator (in Indiana Jones 4) is a more egregious example of that kind of bad movie physics.  Or maybe I&#8217;m just saying that because I liked Iron Man more.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on I&#8217;m Iron Man.  (no, I&#8217;m not) by beth</title>
		<link>http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/comment-page-1/#comment-1740</link>
		<dc:creator>beth</dc:creator>
		<pubDate>Sun, 04 Jan 2009 17:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/#comment-1740</guid>
		<description>&lt;p&gt;While we watch the film my brother and I wondered why he didn't look for more uses for the anti-momentum device he had also invented.  I figure it was in his pocket or something.  It is clearly also in use when he is testing his suit and he slams into the ceiling and back again.  Tony was just too modest to mention it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>While we watch the film my brother and I wondered why he didn&#8217;t look for more uses for the anti-momentum device he had also invented.  I figure it was in his pocket or something.  It is clearly also in use when he is testing his suit and he slams into the ceiling and back again.  Tony was just too modest to mention it.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physics and directly downwind faster than the wind (DWFTTW) vehicles by Tad Hurst</title>
		<link>http://blog.dotphys.net/2008/12/physics-and-directly-downwind-faster-than-the-wind-dwfttw-vehicles/comment-page-1/#comment-1738</link>
		<dc:creator>Tad Hurst</dc:creator>
		<pubDate>Sat, 03 Jan 2009 18:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2008/12/physics-and-directly-downwind-faster-than-the-wind-dwfttw-vehicles/#comment-1738</guid>
		<description>&lt;p&gt;Roadrunner changed their setup.  My  page is now at:&lt;/p&gt;

&lt;p&gt;http://home.roadrunner.com/~tadhurst/DWFTTW.htm&lt;/p&gt;

&lt;p&gt;-tad&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Roadrunner changed their setup.  My  page is now at:</p>

<p><a href="http://home.roadrunner.com/~tadhurst/DWFTTW.htm" rel="nofollow">http://home.roadrunner.com/~tadhurst/DWFTTW.htm</a></p>

<p>-tad</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on I&#8217;m Iron Man.  (no, I&#8217;m not) by Frank Stallone</title>
		<link>http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/comment-page-1/#comment-1737</link>
		<dc:creator>Frank Stallone</dc:creator>
		<pubDate>Sat, 03 Jan 2009 17:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/#comment-1737</guid>
		<description>&lt;p&gt;Since his repulsor hand shooter things are powered by the arc reactor thing which would have a gradual power output falloff curve and not some liquid fuel source that would have an abrupt boundary between "on" and "off", it's plausible (within the movie's rule set) that they were able to act as retro-rockets, retarding his fall, even if they couldn't prevent it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Since his repulsor hand shooter things are powered by the arc reactor thing which would have a gradual power output falloff curve and not some liquid fuel source that would have an abrupt boundary between &#8220;on&#8221; and &#8220;off&#8221;, it&#8217;s plausible (within the movie&#8217;s rule set) that they were able to act as retro-rockets, retarding his fall, even if they couldn&#8217;t prevent it.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on I&#8217;m Iron Man.  (no, I&#8217;m not) by Uncle Al</title>
		<link>http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/comment-page-1/#comment-1736</link>
		<dc:creator>Uncle Al</dc:creator>
		<pubDate>Sat, 03 Jan 2009 17:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dotphys.net/2009/01/im-iron-man-no-im-not/#comment-1736</guid>
		<description>&lt;p&gt;The energy source - the necessary palladium ring - is cold fusion.  Respect the film for its delicate handling of the absurd.  A repulsar field's push is anchored against Heisenberg uncertainty vacuum fluctuations, 10^90 g/cm^2 equivalent.  It's the stuff that covariantly sources the Casimir effect, Lamb shift, Purcell effect, Rabi vacuum oscillation, electron anomalous g-factor...&lt;/p&gt;

&lt;p&gt;If you can believe string theory has 10^(10^5) acceptable vacuum solutions you can hardly criticize a mere 126 minutes of gadget porn.  Ask yourself, "how did Iron Man take a whiz?"  Now we shall see if the movie is true to itself - "They say the best weapon is one you never have to fire.  I prefer the weapon you only need to fire once."&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The energy source - the necessary palladium ring - is cold fusion.  Respect the film for its delicate handling of the absurd.  A repulsar field&#8217;s push is anchored against Heisenberg uncertainty vacuum fluctuations, 10^90 g/cm^2 equivalent.  It&#8217;s the stuff that covariantly sources the Casimir effect, Lamb shift, Purcell effect, Rabi vacuum oscillation, electron anomalous g-factor&#8230;</p>

<p>If you can believe string theory has 10^(10^5) acceptable vacuum solutions you can hardly criticize a mere 126 minutes of gadget porn.  Ask yourself, &#8220;how did Iron Man take a whiz?&#8221;  Now we shall see if the movie is true to itself - &#8220;They say the best weapon is one you never have to fire.  I prefer the weapon you only need to fire once.&#8221;</p>]]></content:encoded>
	</item>
</channel>
</rss>
