Grasshopper

algorithmic modeling for Rhino

Hello everyone, First I thank for its magnificent gulio component GH Python.
In addition, this post comes from this discussion:



So thank you also a systemic.
And for his help, Charles De Ville d'Avray!

Here is my project:
An arch dam from a spiral of equations with polynomials of the second and third degrees.

The definition is broken down into five steps:
1.Definition the axis of the dam
2.Definition the cut in the key
3.Definitions thickness of the peak
4.Extraction parameters for facing upstream and downstream
5.Modélisation with native components of GH.

 

1.Mean Fiber

GH definition

 

Rhino

 

 

2.Crown cantilever

 

GH Definition

 

Rhino

 

 

3.Widening (Crest)

 

GH Definition

 

Rhino

 

 

4.Final Downstream face & upstream face

 

GH Definition

 

 

Rhino

 

 

Modeling with compoment GH:

 

 

 

Result 3D Solid

Views: 1983

Replies to This Discussion

Very nice! It would help to hear if you, after this project, have wishes or maybe encountered bottlenecks? Also, in final_GH there are also some other vb components. Do you need any help to convert them?

Again, cool project.

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Giulio thank you for your answer. I have not encountered any problems in using GH python,
In fact everything is in reading the file out of python, the format does not match that of a grasshopper.
He forged a meter component in place to get to read the data.
GH Python lists me spring 3 xy and z format [x1, x2, x3,...] [y1, y2, y3,...] and [z1, z2, z3,...]

The VB code is simple: (A = CDbl (x))

I am not sure I understand every aspect of this, but maybe the Python float function will help.

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Attachments:

Thanks giulio, but the code for float function it's ok.

Just to say that the format of points from GH_Python is not compatible with GH, the format is a bit special.

 

GH Python lists points xy and z format [x1, x2, x3,...] [y1, y2, y3,...] and [z1, z2, z3,...]

not [x1,y1,z1]...

 

 


See you soon

 

It seems that you are already quite familiar with the topic, yet this is one convention that is useful to control properly:

[x, y, z] is a Python list
(x, y, z) is a Python tuple

You can use both of these to mean RhinoScriptSyntax points, and Rhino.Python will pretend that they are "normal" points. Yet they are still lists or tuples. Grasshopper has no knowledge of them, and cannot understand whether for example this is just a list of three numbers, a 3d vector or a 3d point. So if you want to obtain a point in a with RhinoScriptSyntax, do so:

import rhinoscriptsyntax as rs
a = rs.AddPoint(1, 2, 3)

---

or in RhinoCommon:

from Rhino.Geometry import *
a = Point3d(1, 2, 3)

These two methods yield the same result. a will be a Guid in the first example and a Rhino.Geometry.Point3d in the second. If you have "Automatically marshal Guids" in the first example, the output will not be the random Guid, but the point itself.

I hope this is useful,

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Giulio,

I have no outcome on the small python code.

It seems to be working here.

Last week's Rhino 5 had a bug. It needs to have EditPythonScript running before using the Python component in Grasshopper. I think this is fixed in the 2011 October 12 version.

Thanks,

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Sorry it's not problem.

When I write list of points, the format is special;

[x1;x2;x3;...] [y1:y2:y3;...] et [z1;z2;z3;...]

It's not normaly, but list of point [x1,y1,z1;x2,y2,z2;...]

Do you understand why?

Here some methods to work with points.
Please feel free to post any further question!

Cheers,

- Giulio
_______________
giulio@mcneel.com
McNeel Europe

Attachments:

thanks, verry thanks

Hi Remy,

It's a very nice job !

I just discover GS and the possibilities to create complex 3D model are infinite.
I try to do my first development by designed an archdam too.
I use the "Guide for preliminary design of Arch dams" by the US Bureau of Reclamation, but this kind of literature is very poor especially for the explanation of the design.
I understand that we use a part of a spiral definition, but I have no idea concerning the evolution of the section from the crest to the fundation.
What is your reference documents to do this job ?
Many thanks for your help.

Losbos,

I can not communicate on the geometry of the structure, it is confidential !


I can help you understand the generation mechanism of the points of the structure:
Here to GH_Python component was used to create points using a recursive function.
For each level:
Depending on the axis (1.Mean Fiber), the key (2.Crown cantilever) and the thickness (3.Widening) calculating   upstream or downstream face of the dam .

The mathematical function used takes into account a part of the logarithmic spiral.

Best,

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service