<?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"
	>
<channel>
	<title>Comments on: Summer of Synapse</title>
	<atom:link href="http://blog.peltarion.com/2008/07/02/summer-drive/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.peltarion.com/2008/07/02/summer-drive/</link>
	<description>The Peltarion Blog</description>
	<pubDate>Fri, 21 Nov 2008 07:17:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Luka (Peltarion)</title>
		<link>http://blog.peltarion.com/2008/07/02/summer-drive/#comment-20819</link>
		<dc:creator>Luka (Peltarion)</dc:creator>
		<pubDate>Fri, 08 Aug 2008 03:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.peltarion.com/?p=71#comment-20819</guid>
		<description>Synapse uses a component based approach which for a NN means that the weights and the non-linear function are separated into two blocks, the weight layer and the function layer. Bias weights are on the function layer. The weight layer is a simple inputs x outputs matrix.

For more information see:
http://www.peltarion.com/doc/index.php?title=Synapse:Function_layer_block

http://www.peltarion.com/doc/index.php?title=Synapse:Weight_layer_block

If you have any more questions, please email us at info(AT)peltarion.com</description>
		<content:encoded><![CDATA[<p>Synapse uses a component based approach which for a NN means that the weights and the non-linear function are separated into two blocks, the weight layer and the function layer. Bias weights are on the function layer. The weight layer is a simple inputs x outputs matrix.</p>
<p>For more information see:<br />
<a href="http://www.peltarion.com/doc/index.php?title=Synapse:Function_layer_block" rel="nofollow">http://www.peltarion.com/doc/index.php?title=Synapse:Function_layer_block</a></p>
<p><a href="http://www.peltarion.com/doc/index.php?title=Synapse:Weight_layer_block" rel="nofollow">http://www.peltarion.com/doc/index.php?title=Synapse:Weight_layer_block</a></p>
<p>If you have any more questions, please email us at info(AT)peltarion.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandhya Samarasinghe</title>
		<link>http://blog.peltarion.com/2008/07/02/summer-drive/#comment-20756</link>
		<dc:creator>Sandhya Samarasinghe</dc:creator>
		<pubDate>Thu, 07 Aug 2008 02:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.peltarion.com/?p=71#comment-20756</guid>
		<description>Hi
I am using Peltarion for my NN postgraduate class.  I wanted my students to do a small 2-d classfication using a linear neuron and extract the weights from Synapse and then draw classification boundary on the data.  It seems that Synapse does not use bias weights carrying an input of +1 that allows intercept.  In Synapse, weights seems to be associated with only the disignated inputs.  When I extract these and draw the classification boundary on the data, it does not produce the correct bundary that should divide the data into two regions.  Other NN software that I use have bias weight and I get the correct classification boundary from it.  Can you please tell me the structure of weights in Synapse?</description>
		<content:encoded><![CDATA[<p>Hi<br />
I am using Peltarion for my NN postgraduate class.  I wanted my students to do a small 2-d classfication using a linear neuron and extract the weights from Synapse and then draw classification boundary on the data.  It seems that Synapse does not use bias weights carrying an input of +1 that allows intercept.  In Synapse, weights seems to be associated with only the disignated inputs.  When I extract these and draw the classification boundary on the data, it does not produce the correct bundary that should divide the data into two regions.  Other NN software that I use have bias weight and I get the correct classification boundary from it.  Can you please tell me the structure of weights in Synapse?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
