<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>QuantumHeat.org</title>
		<description>Discuss QuantumHeat.org</description>
		<link>http://www.quantumheat.org</link>
		<lastBuildDate>Thu, 30 Apr 2026 16:49:37 +0000</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://www.quantumheat.org/index.php/it/component/jcomments/feed/com_content/135" rel="self" type="application/rss+xml" />
		<item>
			<title>Ecco says:</title>
			<link>http://www.quantumheat.org#comment-441</link>
			<description><![CDATA[The new "Toggle" button should probably be called "Invert channel selection", as that's what it does.]]></description>
			<dc:creator>Ecco</dc:creator>
			<pubDate>Fri, 16 Nov 2012 12:21:34 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-441</guid>
		</item>
		<item>
			<title>Ecco says:</title>
			<link>http://www.quantumheat.org#comment-412</link>
			<description><![CDATA[Another suggestion which however might not be very easy to implement: data caching. Currently much bandwidth is wasted, especially if the "update with new data" option used, because at every "tick" the entire chosen slice of data is re-downloaded (default: 30 minutes). If only actually new data were added, bandwidth usage would be reduced enormously. Data would be able to be loaded faster and more frequently (currently there's a "tick" every 12 seconds or so) as a benefit, in addition to the bandwidth savings.]]></description>
			<dc:creator>Ecco</dc:creator>
			<pubDate>Thu, 15 Nov 2012 23:14:32 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-412</guid>
		</item>
		<item>
			<title>Robert Greenyer says:</title>
			<link>http://www.quantumheat.org#comment-404</link>
			<description><![CDATA[@Ecco Good suggestions - Mine were - Nothing selected means all on - select one and auto scales graph - select two and it auto scales and puts first on LHS axis and second on RHS axis for instant relative comparison - select 3 or more and it represents normalised with chosen sample start at 100%, 1 or zero - can set axis min/max and also log/lin]]></description>
			<dc:creator>Robert Greenyer</dc:creator>
			<pubDate>Thu, 15 Nov 2012 21:03:06 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-404</guid>
		</item>
		<item>
			<title>Ryan Hunt says:</title>
			<link>http://www.quantumheat.org#comment-403</link>
			<description><![CDATA[Problem fixed. It was a problem with the computation interpreter not handling scientific notation. The problem occurred while the power was very close to zero. We are beginning the steps again.]]></description>
			<dc:creator>Ryan Hunt</dc:creator>
			<pubDate>Thu, 15 Nov 2012 20:44:52 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-403</guid>
		</item>
		<item>
			<title>Ryan Hunt says:</title>
			<link>http://www.quantumheat.org#comment-400</link>
			<description><![CDATA[Currently data is flowing. We are troubleshooting what appears to be a power metering and calculation problem, though, that is making the P_in look negative and the resistance of the Celani look like it is at 21 ohms.]]></description>
			<dc:creator>Ryan Hunt</dc:creator>
			<pubDate>Thu, 15 Nov 2012 20:31:07 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-400</guid>
		</item>
		<item>
			<title>Ryan Hunt says:</title>
			<link>http://www.quantumheat.org#comment-397</link>
			<description><![CDATA[Sorry, problem with the link. There was a space at the end of the address that was throwing it off. Please share all the new features you can think of here. We plan to open source this software and the programming interface for the data so anyone can make a viewer for it. More details next week.]]></description>
			<dc:creator>Ryan Hunt</dc:creator>
			<pubDate>Thu, 15 Nov 2012 20:04:39 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-397</guid>
		</item>
		<item>
			<title>Ecco says:</title>
			<link>http://www.quantumheat.org#comment-395</link>
			<description><![CDATA[I'm glad you left an option to see the raw data ("History"). I find a 30 seconds average to be too harsh for the 30 minutes live data. That means that roughly only 60 data points are fit in the 750 pixel wide chart. It makes perfectly sense for the 4 and 12 hours options, instead. (4 hours @ 1 datapoint/30 seconds = 480 datapoints). Perhaps a more sensible option would be making the chart performing the average dynamically so that in the end only 750 datapoints at most are downloaded at once (thus fitting exactly 1 data point for each pixel in the chart's x axis).]]></description>
			<dc:creator>Ecco</dc:creator>
			<pubDate>Thu, 15 Nov 2012 19:37:13 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-395</guid>
		</item>
	</channel>
</rss>
