rested in specializing in the field of Computational design.
The workshop will help understand how Grasshopper facilitates during the design process allowing one to Generate, Automate and Manipulate data.
To Register:
Mail us at intofablab@gmail.com
Workshop Structure:
Day 01: 11 February 2019
Introduction to Computational Processes in Architecture
Understanding Grasshopper and its relation to Rhino3D
Working with fields and Grids (Supplementary readings for Architectural theory)
Spatial Concepts using Data
Day 02: 12 February 2019
Understanding Data in Grasshopper - LISTS
Managing Data in Grasshopper (Supplementary reading)
Experimentation on Massing and Architectural Forms
Day 03: 13 February 2019
Understanding Data in Grasshopper – Trees
Surface Logics (Supplementary reading)
Design Exercise and Prototyping
Day 04: 14 February 2019
Architectural Skins
Day 05: 15 February 2019
MasterClass Project
Introduction to various types of Digital Fabrications
Prototyping of works during the Workshops
Basic knowledge of Rhino 5 is required to be able to take this training.
CERTIFICATION: All participants will receive a Workshop certificate from Authorized Rhino Trainer.
3D Printing: Prototyping of works during the Workshops
Workshop Tutor:
Kavitha M, an Architect and Computational Designer, 3D Printing Specialist is also the co-founder of INTO Design Research, will head the Computational Process in Architecture using Grasshopper workshop. Graduated from Stadelschule Architecture class with Masters in Advanced Architecture Design, has been researching on teaching methodologies on digital tools and their influence on Design thinking.…
ocessed once Grasshopper is done with whatever it's doing now.
3) Grasshopper tells the Slider object that the mouse moved and the slider works out the new value as implied by the new cursor position.
4) The slider then expires itself and its dependencies ([VB Step 1] in this case, but there can be any number of dependent objects).
5) When [VB Step 1] is expired by the slider, it will in turn expire its dependencies (VB Step 2), and so on, recursively until all indirect dependencies of the slider have been expired.
6) When the expiration shockwave has subsided, runtime control is returned to the slider object, which tells the parent document that stuff has changed and that a new solution is much sought after.
7) The Document class then iterates over all its objects (they are stored in View order, not from left to right), solving each one in turn. (Assuming the object needs solving, but since in your example ALL objects will be expired by a slider change, I shall assume that here).
8) It's hard to tell which object will get triggered first. You'd have to superimpose them in order to see which one is visually the bottom-most object, but let's assume for purposes of completeness that it's the [VB Step 1] object which is solved first.
9) [VB Step 1] is triggered by the document, which causes it to collect all the input data.
10) The input parameter [x] is asked to collect all its data, which in turn will trigger the Slider to solve itself (it got expired in step 4 remember?). This is not a tricky operation, it merely copies the slider value into the slider data structure and shouts "DONE!".
11) [x] then collects the number, stores it into its own data structure and returns priority to the [VB Step 1] object.
12) [VB Step 1] now has sufficient data to get started, so it will trigger the script inside of it. When the script completes, the component is all ready and it will tell the parent document it can move on to the next object (the iteration loop from step 7).
13) Let us assume that the slider object is next on the list, but since it has already been solved (it was solved because [VB Step 1] needed the value) it can be skipped right away, which leaves us with the last object in the document which is still unsolved.
14) [VB Step 2] will be triggered by the document in very much the same way as [VB Step 1] was triggered in step 9. It will also start by collecting all input data.
15) Since all the input data for [VB Step 2] is either defined locally or provided by an object which has already been solved, this process is now swift and simple.
16) Upon collecting all data and running the user script, the component will surrender priority and the document becomes active again.
17) The document triggers a redraw of the Grasshopper Canvas and the Rhino viewports and then surrenders priority again and so on and so forth all the way up the hierarchy until Grasshopper becomes idle again.
[end boring]
Pretty involved for a small 3-component setup, but there you have it.
To answer somewhat more directly your questions:
- The order in which objects are solved is the same as the order in which they are drawn. This is only the case at present, this behaviour may change in the future.
- Adding a delay will not solve anything, since the execution of all components is serial, not parallel. Adding a delay simply means putting everything on hold for N milliseconds.
- [VB Step 1] MUST be solved prior to [VB Step 2] because otherwise there'd be no data to travel from [GO] to [Activate]. The only tricky part here is that sometimes [VB Step 1] will be solved as part of the process of [VB Step 2], while at other times it may be solved purely on its own merits. This should not make a difference to you as it does not affect the order in which your scripts are called.
--
The Man from Scene 24…
Added by David Rutten at 4:43pm on December 10, 2009
our own, understand third-party tutorials and process to the advanced sessions.
register for 29€/3hrs
GMT: SAT, 13 DEC 2014 @ 3:00PM / 29€
Introduction to vectors, vectors vs. points, vector addition, cross product, dot product, vector operations, vector display, practical use, planes/frames, normals.
Introduction to domains, t parameter, evaluate curve, boundaries, remap, reparametrize, UV coordinates, evaluate surface.
GMT: SUN, 14 DEC 2014 @ 3:00PM / 29€
Introduction to data trees, graft, flatten, unflatten, tree statistics, cherry picker, simplify, shift path, path mapper, tree item, tree items.
WEBINARS
The webinars are series of on-line live courses for people all over the world. The tutor broadcasts the screen of his computer along with his voice to the connected spectators who can ask questions and comment in real time. This makes webinars similar to live workshops and superior to tutorials. The rese arch Grasshopper® sessions are unique for their thorough explanation of all the features, which creates a sound foundation for your further individual development or direct use in the practice. All sessions are held entirely in English.
PAST EVENTS
…
Added by Jan Pernecky at 2:27am on December 11, 2014
returned to GSA, it is solving. You might have to reset result scales using the GSA button.
Cheers,
Jon
Checking Input Data - this may take some time.
________________________________________
Data checks commenced at 23/08/2017 4:59:18 PM.
Checking input data for static analysis by GSS.
Shortest element (element 9) is 5 m long.Longest element (element 1) is 6 m long.
Data checks completed at 23/08/2017 4:59:18 PM. No errors or warnings found.
Analysis commenced at 23/08/2017 4:59:18 PM.
Analysis by Gss Static analysis
Initialising results modulesSolving for displacementsSolution statisticsSparse Parallel Direct 12 active nodes 14 active elements 2 analysis cases 24 degrees of freedom Minimum degree ordering 90 terms in stiffness matrix Maximum stiffness is 4.804e+009 at node 4 in direction z Minimum stiffness is 3.132e+008 at node 2 in direction yy Condition number of the stiffness matrix is ~ 5328. Maximum relative error in displacements will be 2.4e-10 percent. Factorization in 109 msSolving for element forces and reactionsCalculation completeAnalysis completed with no errors
Analysis completed at 23/08/2017 4:59:18 PM.Analysis time: 0.172 seconds
…
.Besides these two output, it calculates the solar position (elevation angle and azimut) considering the atmospheric refraction.I saw the difference between solInitOutput (based on Radiance) and the script that I wrote (based on NOAA). Some formulas are the same, while others are different. for example "Julian day", "solar altitude"..Anyway, they are two different models.At the moment the imputs are:1) location2) analysis period3) yearand the outputs are:1) civil twilight2) official sunrise/sunset3) solar elevation angle4) solar azimutThis is an example where I used data of a real place.
and these are two photos that I took in this place.
SUNRISE (Civil Twilight) 06:44 AM
SUNRISE (Official) 07:14 AMNote that in the first photo the street lights are on, while in the second are off because of the good level of luminous energy.I hope that it could be useful.
BestsAntonello…
tions and that will be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I will continue to ask the aforementioned set of questions. Good luck.
___________________________________________________________________
Question 1: How do I go about measuring the arc length of a parabola in Rhino? In a nutshell, I'm looking to accurately measure curve length in Rhino in this case using a parabola.
Question 2: Once I can measure the arc length of a parabola, how do I go about manually changing it to a specified length (Ex: If my arc length is 14, but I need it to be 24)? Followup question, is there a way to use a slider in Grasshopper to do this?
Question 3: Once I eventually am able to create a parabola of a specific arc length/curve length the next thing I'll be doing is to create a parabolic cylinder comprised of 6 inch squares (view image below for visual cue). Is there a way to change the scale of a parabolic cylinder while still maintaining the 6x6" grid/panels? I plan on using a 3D printer to print out 6x6" interlocking tiles that when glued will form a parabola, and would like to be able to do it for a variety of parabola sizes.
…
Added by Chris Beffa at 4:21pm on November 30, 2015
e forces which are used with Kangaroo. I would like a model which is build according to it's geometrical relations. I started to make the base pattern, this worked out. The base pattern is constructed with the rectangular square in the middle, these points stay on the same position. Than 4 points (Points 1,7,8 and 14 in the GH-file) are created by taking a point on a circle with the corner points from the rectangle as center and the lines of the rectangle as normal. The remaining 4 points are created with knowledge of the distance of those points to it's connected points. Each point has a known distance between itself and 3 other points. So the intersection point with the correct angle (because the line has to be a mountain-fold) is taken. This makes the base pattern. But now I'm struggling to make this base pattern into a larger tessellation. The goal is to create a parametric model which can controlled over the following parameters:
- Size- Number of tessellations
- Controlling the folding angles of degrees of freedom of the model
Attached to this post I have the Grasshopper file of the base pattern which is described in this post and a pictures of the tessellation (first the base pattern and a 2x2 pattern).
Has anybody a suggestion how to model a folding pattern like this with the Kangaroo plug-in?…
ment.
This course will help architects and designers in their practice and development of forms using generative algorithms.
Curriculum
Introduction to parametric design
Understanding the user interface of Grasshopper and visual programming theory
Understand the components and types of networking
Linking and importing and exporting geometry from Rhino Rhino geometry results back
Knowledge of the main data types (numbers, fields, vectors, points, curves, surfaces, brep)
Manage lists and trees of data: simple tasks lists, extracting data in lists and trees
Operations with vectors and points
Using colored gradient according to the parameters
Strategies of planar space subdivision: Voronoi
Working with curves and create surfaces : loft, surface from points, attractors
Surface subdivision with Lunchbox: triangular, hex, diagrid
Schedule:
Module Grasshopper beginners (24 h)
10 May – 24 May 2014
Sat:
9 - 13
14 - 18
Language: Romanian
Trainers:
Ionuț Anton, idz arhitectura (ART-Authorised Rhino Trainer)
Dana Tănase, idz arhitectura (ART-Authorised Rhino Trainer)
https://www.facebook.com/cursurigrasshopperrhinoceros
https://www.facebook.com/idzarhitectura
http://www.idz.ro/training/…
Added by Dana Tanase at 2:21am on February 2, 2014