The most important here are the two components facilitating the insertion of custom numeric weight data into the MeshGraph. The tools in this category are in fact a sum of presset ways to add the weight information to the MeshGraph. All values are normalized to that interval. Any kind of geometrical/non geometrical property of any object residing in the Grasshopper environment that can be expressed as a number, can be used as a node or edge weight. The weights are added to the MeshGraph as floating point numbers between 0 and 1. A MeshGraph can have both node and edge weights specified for each of its nodes and/or edges. This is important for the tree making algorithms in the next sections. 2| Weight Graph houses a set of components for adding additional data to a MeshGraph.1| Mesh Graph contains components that deal with constructing and decomposing MeshGraphs.The tools packaged with Ivy are organized inside nine categories: The graph edges can be visualized as the mesh topological edges. The data containers that can be visualized as the mesh faces are the nodes of the graph and the links between them are the graph edges. In order to enable the use of graph theory specific algorithms, a new custom data type was created. The MeshGraph is an abstract construct that combines the geometric characteristics of the mesh with sets of linked data containers. Ivy uses notions and algorithms from Graph Theory and applies them towards mesh geometry exploration. This is the most recent release of my plug-in for mesh analysis, segmentation and unrolling inside the Grasshopper environment. Please consider citing them if ivy helps you in your research and up-vote the plug-in if it is helpful for your work. The manual and some examples can be found on my old repository.Īdditionally if you are interested in the research behind Ivy you can read these two papers. He'll get a copy of it for distribution.įoot.You can find a set of videos with examples and tutorials on Ivy on my Vimeo Chanel. As suspected, he doesn't have access to a Mac or Xcode. I've also talked to Thomas so that he knows about the port.

I'm slowly going to go through the information at hand and try to get the port built from there today.

They also don't provide direct support for the free GPL version (darnit). Trolltech (Qt) doesn't recommend using Xcode but instead building with the command line (Terminal).

I had to make sure to build a universal release build so that this will work on PPC or Intel Macs. The build of Qt took about three hours and consumes 50GB (yikers! - but that includes all of the examples). You can use bundles, frameworks, staticlib, or dynamic lib for the Qt support - they recommend staticlib for Qt applications as you don't have to provide the frameworks or dylibs. Still working on it - Qt is not exactly simple to set up on the Mac.

An ivy generator