<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SketchyGrid &#187; SketchyGrid</title>
	<atom:link href="http://www.sketchygrid.com/tag/organization/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sketchygrid.com/index</link>
	<description>Experiments in art, architecture, and urbanism.</description>
	<lastBuildDate>Wed, 28 Dec 2011 05:02:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Optimize Connections</title>
		<link>http://www.sketchygrid.com/index/architecture/optimize-connections/</link>
		<comments>http://www.sketchygrid.com/index/architecture/optimize-connections/#comments</comments>
		<pubDate>Sun, 30 May 2010 16:22:33 +0000</pubDate>
		<dc:creator>morrow.liam</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Attractor Point]]></category>
		<category><![CDATA[Connections]]></category>
		<category><![CDATA[Grasshopper]]></category>
		<category><![CDATA[Lists]]></category>
		<category><![CDATA[Optimize]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Parametric]]></category>
		<category><![CDATA[System]]></category>

		<guid isPermaLink="false">http://www.sketchygrid.com/?p=433</guid>
		<description><![CDATA[This definition is very simple, but incredibly useful.  It sorts a series of points based on distance and then creates connections based on that list.  The only slider in the definition is used to control the number of connections that are allowed.  The purpose of the definition being that it optimizes the placement of connections. Connecting Points Grasshopper File Note:Version [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;">This definition is very simple, but incredibly useful.  It sorts a series of points based on distance and then creates connections based on that list.  The only slider in the definition is used to control the number of connections that are allowed.  The purpose of the definition being that it optimizes the placement of connections.</p>
<pre><a href="/Files/connectingpoints.rar">Connecting Points Grasshopper File</a></pre>
<pre><a href="/Files/connectingpoints.rar"></a>Note:Version of Grasshopper Used-(Grasshopper 0.6.0059)</pre>
<pre style="text-align: center;"><span id="more-433"></span></pre>
<p style="text-align: center;">
<p style="text-align: center;">
<p style="text-align: center;"><img class="size-medium wp-image-565 aligncenter" title="pointside" src="http://www.sketchygrid.com/index/wp-content/uploads/2010/05/pointside-400x222.jpg" alt="" width="400" height="222" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.sketchygrid.com/index/architecture/optimize-connections//feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tutorial:Circle Panels</title>
		<link>http://www.sketchygrid.com/index/tutorials/tutorialcircle-panels/</link>
		<comments>http://www.sketchygrid.com/index/tutorials/tutorialcircle-panels/#comments</comments>
		<pubDate>Sun, 20 Dec 2009 04:34:07 +0000</pubDate>
		<dc:creator>morrow.liam</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Grasshopper]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Parametric]]></category>
		<category><![CDATA[Rhino]]></category>
		<category><![CDATA[System]]></category>

		<guid isPermaLink="false">http://www.sketchygrid.com/?p=292</guid>
		<description><![CDATA[This Grasshopper definition uses a grid of points to generate a series of curves that respond to an attractor point.  This definition is a great example of using really simple and basic concepts of parametrics to accomplish a more complicated goal.  Essentially, all this definition is composed of is an attractor point that adjusts the curvature of a plane [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;">This Grasshopper definition uses a grid of points to generate a series of curves that respond to an attractor point.  This definition is a great example of using really simple and basic concepts of parametrics to accomplish a more complicated goal.  Essentially, all this definition is composed of is an attractor point that adjusts the curvature of a plane and an attractor point that adjusts the radius of circles that are projected onto that surface.  The small bit of vbscript at the end is used to split the circles from the surface.</p>
<pre>Note:Version of Grasshopper Needed-(Grasshopper 0.6.0019)</pre>
<p><span id="more-292"></span></p>
<p>VBscript:</p>
<pre>a = rhutil.RhinoSplitBrepFace(y, 0, x.ToArray, doc.AbsoluteTolerance)</pre>
<p>As a bit of code, its actually not very necessary.  Does it really matter if you split the circles in grasshopper or rhino space?  In this case, not really, however its useful to know and more importantly it brings up the question of how integrated grasshopper can become with rhino.  As a tool, grasshopper can be great a modeling things really quickly and when you start to make relationships its really great at doing calculations for you.  These panels are a good example, they illustrate both a much easier way of modeling and an easier way of calculating the relationships between points.  Grasshopper presents a much clearer way for the designer to understand what the relationships are within a given project.  Given this diagrammatic way of seeing the logic behind an object, designers should begin to spend more time articulating these relationships and less time articulating the form.</p>
<p>The set of images at the top of the article represent an ethereal form of an object.  They show a logic, but in order for them to mean anything they need to be put within context.  The context would then generate a meaningful form.  Whether you design in grasshopper or rhino space is irrelevant as long as there is some context attached to the object.  An example with respect to this tutorial could be assigning the attractor points some sort of value, such as amount of light, pre-existing site constraints, or even something as simple as compositional logic.</p>
<p style="text-align: center;"><a href="http://www.sketchygrid.com/index/wp-content/uploads/2009/12/attractor-points.jpg"><img class="size-medium wp-image-621 aligncenter" title="attractor-points" src="http://www.sketchygrid.com/index/wp-content/uploads/2009/12/attractor-points-400x258.jpg" alt="" width="400" height="258" /></a></p>
<p style="text-align: center;">
<p style="text-align: center;">
<p>-Liam Morrow</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sketchygrid.com/index/tutorials/tutorialcircle-panels//feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

