<?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: Solar Mission</title>
	<atom:link href="http://jpaerospace.com/blog/?feed=rss2&#038;p=1351" rel="self" type="application/rss+xml" />
	<link>http://jpaerospace.com/blog/?p=1351</link>
	<description>Our Journey to Space</description>
	<lastBuildDate>Sun, 11 Dec 2022 19:44:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Administrator</title>
		<link>http://jpaerospace.com/blog/?p=1351#comment-57354</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Mon, 16 Aug 2010 19:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://jpaerospace.com/blog/?p=1351#comment-57354</guid>
		<description>We originally were going to track the sun, however we couldn&#039;t  verify the accuracy of the pointing in flight. We only wanted to do 2D tracking with the vertical angle preset so the cell would be pointed at the sun at time of peak altitude.  This created a problem that small pitches in the platform would though off the data and it would be hard to tell in the data if we had a low performance in the cell or the tracker was just playing chase from the pitching. We could have really worked with the data afterwords, but I hate noisy data.  By scanning the sun we can see in the data exactly when we&#039;re pointing at the sun (we took data five times a second). We could extract just those point and start with a much cleaner data set.  

I would have to dig out the numbers to get  percentage of performance increase. I remember it was pretty impressive.</description>
		<content:encoded><![CDATA[<p>We originally were going to track the sun, however we couldn&#8217;t  verify the accuracy of the pointing in flight. We only wanted to do 2D tracking with the vertical angle preset so the cell would be pointed at the sun at time of peak altitude.  This created a problem that small pitches in the platform would though off the data and it would be hard to tell in the data if we had a low performance in the cell or the tracker was just playing chase from the pitching. We could have really worked with the data afterwords, but I hate noisy data.  By scanning the sun we can see in the data exactly when we&#8217;re pointing at the sun (we took data five times a second). We could extract just those point and start with a much cleaner data set.  </p>
<p>I would have to dig out the numbers to get  percentage of performance increase. I remember it was pretty impressive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron</title>
		<link>http://jpaerospace.com/blog/?p=1351#comment-57294</link>
		<dc:creator>Cameron</dc:creator>
		<pubDate>Wed, 11 Aug 2010 05:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://jpaerospace.com/blog/?p=1351#comment-57294</guid>
		<description>Did the platform track the sun, or was it just spinning about?
(I appologize for commenting on every posting; however I am very excited about your program and want to be open about that excitement)</description>
		<content:encoded><![CDATA[<p>Did the platform track the sun, or was it just spinning about?<br />
(I appologize for commenting on every posting; however I am very excited about your program and want to be open about that excitement)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lbparker</title>
		<link>http://jpaerospace.com/blog/?p=1351#comment-57291</link>
		<dc:creator>lbparker</dc:creator>
		<pubDate>Tue, 10 Aug 2010 22:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://jpaerospace.com/blog/?p=1351#comment-57291</guid>
		<description>How was their performance?</description>
		<content:encoded><![CDATA[<p>How was their performance?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
