s, each made from two Nurbs curves, each with different surface properties.
Curves A1 and A2 have 2 control points:
startpoint and endpoint
Curves B1 and B2 on the other hand were drawn with 6 control points each.
What's more, those point's aren't equally distanced from one another.
The lofts inherit the position of control points of the profile curves.
The distribution of control points in the loft direction is uniform.
So no suprise here:
You can think of Nurbs curves as rubber bands and of Nurbs surfaces as rubber sheets. The areas with less control points would correspond to streched rubber.
Now lets imagine you take an A4 piece of rubber, lay in on a table and draw equally distanced lines on it. When you strech it ununiformally - the distances won't stay equal anymore.
Returning to your first post:
The Divide Surface component operates on u,v values which you can imagine as dimensions of the rubber sheet in relaxed state.
So the result you got was indeed an equaly divided surface, only in the so called "parameter space" of the surface, which doesn't always correspond to the xyz space.
There are methods to divide curves and surfaces in equal distances in the way you want it. For starters check out the Evaluate Lenght component.
I think that's enough teory for today. Have fun!
JJ…
r (top left) is connected with the list which contains the centroids of every triangle of my mesh (my canopy, that I turned into a series of triangular surfaces). In this part of the definition I evaluate the Z coordinates (extracted form the points).
I execute some operations in order to have my values from 0 to 1 (parametrization). Then I sutracted the lower value of the list to all the data. So I obtained a new list of numbers, which stay from 0 to 1 and I can use in order to determine a gradient in the arch openings.
The result? If you look carefully to the rendering I posted you'll see that the arches are less opened near the ground and more opened near the top. It's a structural way of design the canopy. The more loads you must support, the more closed your arches will be (and the more stronger you should be).
Anyway consider this part as not important, because this parameter is just a my interpretation, it's not essential in order to obtain the canopy I posted. If you want you can just substitute that emitter with a simple number, from 0 to 1. Don't know, try to put 0.4 as an imput and let's see what happens. The result will be more similar. ;-)
Nice to meet you Morgan.…
tecture: Realtime Physics for Space Planning
http://vimeo.com/15563685
"This is a preview of a parametric conceptual design tool for architectural
practice that I have been developing at NBBJ. I wanted to develop a
system that allows designers to quickly organize and understand complex
architectural programmes in three dimensions.
It is an advancement of the traditional bubble diagram; it solves
adjacency requirements automatically and suggests planimetric and
sectional relationships. The resulting diagrams are not formal
solutions; they are simply organizational diagrams with solved
adjacencies and accurate required areas. The diagrams are raw
materials, meant to be manipulated sculpturally, or even squeezed into a
formal container.
Technical Information
The tool was created in the Grasshopper plug-in for Rhino. Custom components, written in VB.NET,
read programme data directly from Excel into Grasshopper. The tool
uses the Kangaroo engine for realtime spring dynamics simulation."
…
green & B in red. These surfaces are at the centerlines of thicker beams in the model (not shown).
I have a list of "Intersections", the yellow vertical lines, usually four at each point the beams intersect (85 points or 340 intersections expected, though there are only 335).
What I'm trying to do is "get" the list of yellow vertical lines for each beam and keep them "associated", so that I can re-orient them with the thick beams in a flat, "nested" layout.
These intersections will appear in two sets of lists, one for beams "A" and another for beams "B".
I found and hacked a bit of C# script to partition the sorted list of indexes but not the related list of intersections ("Line-like Curves").
In this case, the data trees aren't working for me. I want "beam objects" with arbitrary properties, such as lists of intersections. Are there ways to do this "easily" in GH without resorting to C#, VB or Python?…
the various digital design methods and technologies that they employ in their design workflow, highlighted at various scales through their recent work. Organizers and Moderators: Andrew Haas, Program Co-Director, Architectural Association Visiting School New York Alfonso Oliva, Associate/Director, LERA Consulting Structural Engineers Speakers: Luc Wilson, Senior Associate Principal and Director, KPF Urban Interface Dan Levine, Associate Director, Solutions Engineering – United Technologies (UTC) Jan Leenknegt, Architect and BIM Manager, Bjarke Ingels Group (BIG) Introductions by AIANY Technology Committee Co-Chairs: Michael Brotherton, AIA, VP of Operations, Situ Fabrication LLC Alexandra Pollock, AIA, LEED AP BD+C, Director of Design Technology, Senior Associate, FX Collaborative – Due to building security requirements, a state-issued photo ID or valid passport is required to obtain building entry. Advanced registration is required. This event is free and open to the public. Refreshments and pizza will be served.
Register: https://www.facebook.com/events/1019498534923019…
Added by Andrew Haas at 10:42am on October 30, 2018
angel but when it comes to material behavior, stresses, surface tension i think that "our" tools are still no complex and powerful enough - and like i said i didn't really see the benefit in the work of my friend form the digital experiment.
so i think the question is is there a benefit from your digital experiment or do you rather stick to the physical experiment.
…
of 400 interlocked rings in a 20 X 20 grid.
V1 - A single 'suLoop' component doing 400 'SUnion' operations (20 X 20): 11.6 minutes
V2 - Two phases: 5 X 10 in phase one and 2 X 4 in phase 2, 58 'SUnions' total: ~88 seconds combined
V3 - Two phases: 4 X 5 in phase one and 4 X 5 in phase 2, 40 'SUnions' total: ~104 seconds combined
Again, these Profiler benchmarks don't reflect the whole picture, and might be affected by other things I was doing on the laptop while the code was running.…
Added by Joseph Oster at 12:29pm on March 23, 2017
,
and then I saw under Application that resources are managed by 'Icon and manifest'.
That can also be set as 'Resource file', but then a file path is required.
Is 'Icon and manifest' OK, or have I to set thing differently ?
Also, in the class code I inserted the following:
( I saw it mentioned here in the forum )
protected override Bitmap Icon { get { return Resources.colour; } }
( colour.png is the image file's name )
but VS gives me an error, saying:
Error 1 The name 'Resources' does not exist in the current context C:\Program Files\Rhinoceros 5 Evaluation\gh\plug-ins\ColourRhOb\Class1.cs 88 26 ColourRhOb
Did I miss a reference in the code ? Here they are:
using System;using System.Drawing;using System.Collections.Generic;using Grasshopper.Kernel;using Grasshopper.Kernel.Types;using Rhino;using Rhino.DocObjects;using Rhino.Geometry;
What am I doing wrong ?
Thanks
emilio
…
he Cordyceps. Maybe some of you find this helpful/useful.
So basically, the Cordyceps is a physical module with 4 knobs and 1 slider. The knobs give an output between 1 and 1000, while the physical slider outputs 0-359. And of course, for this physical module I wrote a plugin to communicate with it. The knobs are intended to be the variables that modifies the design, while the physical slider is intended to be connected to the camera component.
Here I will put up "the recipe" for all to make their own module. You will be able to download the plugin as well.
Please send me a message if you want the 3D-files for the knobs, the box and slider knob. They've been made to directly 3D-print.
Plugin:
https://github.com/zakadjeb/Cordyceps/blob/master/Cordyceps/Cordyce...
Code for Arduino IDE:
https://github.com/zakadjeb/Cordyceps/blob/master/Arduino/_Arduino_...
What you need:
1x - Arduino (Leonardo, UNO or whatever)
4x - Potentiometers
1x - Sliding potentiometer
1x - Breadboard
Bundle of jump wires.
1. So, a potentiometer is a variable resistor, which is basically a component that changes the resistance between the voltage and the ground.
If A is supplied with 5V then B must be connected to Ground. The W will give "read" the resistance, and thus should be placed in Analog input (A0-A5) on the Arduino. The slider potentiometer works the same way.
2. Now connect the 4 pots to each their Analog input. The slider is supposed to be in A4. So to make sure:
A0: Knob1
A1: Knob2
A2: Knob3
A3: Knob4
A4: Slider
3. Now it's time to connect the voltage! Using the breadboard, the voltage can be sent through 1 line, the Ground as well. It should be quite easy to connect them.
4. Now, download the Arduino IDE and copy-paste the code I supplied above. In the IDE, you need to let it know which Arduino you're working with, and which port is should send the script.
5. Almost there. Download the plugin. Open the port you're using through the plugin. Set Start to True and the Cordyceps should be within you.
This recipe will be updated!
Let me know if there are any issues.
// Zakaria Djebbara…
he Cordyceps. Maybe some of you find this helpful/useful.
So basically, the Cordyceps is a physical module with 4 knobs and 1 slider. The knobs give an output between 1 and 1000, while the physical slider outputs 0-359. And of course, for this physical module I wrote a plugin to communicate with it. The knobs are intended to be the variables that modifies the design, while the physical slider is intended to be connected to the camera component.
Here I will put up "the recipe" for all to make their own module. You will be able to download the plugin as well.
Please send me a message if you want the 3D-files for the knobs, the box and slider knob. They've been made to directly 3D-print.
Plugin:
https://github.com/zakadjeb/Cordyceps/blob/master/Cordyceps/Cordyce...
Code for Arduino IDE:
https://github.com/zakadjeb/Cordyceps/blob/master/Arduino/_Arduino_...
What you need:
1x - Arduino (Leonardo, UNO or whatever)
4x - Potentiometers
1x - Sliding potentiometer
1x - Breadboard
Bundle of jump wires.
1. So, a potentiometer is a variable resistor, which is basically a component that changes the resistance between the voltage and the ground.
If A is supplied with 5V then B must be connected to Ground. The W will give "read" the resistance, and thus should be placed in Analog input (A0-A5) on the Arduino. The slider potentiometer works the same way.
2. Now connect the 4 pots to each their Analog input. The slider is supposed to be in A4. So to make sure:
A0: Knob1
A1: Knob2
A2: Knob3
A3: Knob4
A4: Slider
3. Now it's time to connect the voltage! Using the breadboard, the voltage can be sent through 1 line, the Ground as well. It should be quite easy to connect them.
4. Now, download the Arduino IDE and copy-paste the code I supplied above. In the IDE, you need to let it know which Arduino you're working with, and which port is should send the script.
5. Almost there. Download the plugin. Open the port you're using through the plugin. Set Start to True and the Cordyceps should be within you.
This recipe will be updated!
Let me know if there are any issues.
// Zakaria Djebbara…