Grasshopper

algorithmic modeling for Rhino

Hi Guys,

 

Trying to make this pattern using Grasshopper:

http://en.wikipedia.org/wiki/Snub_square_tiling

 

Could i use the 43433 properties using a basic grid ?

http://www.uwgb.edu/dutchs/symmetry/archtil.htm

 

Or should I try to make it from a square grid  and apply the UV onto the new surface?

 

I could even use the formula directly?
http://www.wolframalpha.com/entities/calculators/snub_square_tiling...

 

Any advice would be precious,

 

Many thanks,

 

Arthur

Views: 1245

Replies to This Discussion

Hi Arthur -

I gave it a try myself; the strategy that worked best for me involved laying out the pattern in 2D and then mapping it as curves to the surface, and building surfaces from those curves.


There may well be a more elegant approach possible with a little bit deeper investigation into the mathematical properties of the tiling, but a brute force approach seems to do the trick. I have two versions; one that builds all the surfaces at once and one that separates them into five sets for specific treatment (colored differently in the image).
Attachments:
Thanks Andrew!
Can i ask you on which GH you did the definition, i am getting lots of error messages...?
Here is with GH 0.7.60:

GH.0.7.60???
he, he... maybe this weeks update has already been leaked.
goodness, how does one get on the pre-pre-release list!? I am using 0.7.30.
and weirdly enough, I am getting errors opening my own definition, even in the same version:


Persistent data deserialization failed.

Component Modulus {431bc610-8ae1-4090-b217-1a9d9c519fe2} failed to deserialize itself.

I think it has something to do with having used an expression somewhere? Try these files - I just updated them with function components to replace the x%2 expression I was using.
Attachments:
Thanks a lot Andrew!
I ll try as soon as i get to work, i was getting this problem too actualy.
I meant 7.30 not 7.60 :) just getting confused with all the versions, sorry...
It's a common bug for many components in 0.7.0030. I think David needs to double check all the older pre-existing components to update them.

I don't really know what "XX failed to deserialize itself" means but the reality is multiple instances of a component aren't retained/operational in a definition and they're lost after saving and reopening.

Them's the breaks.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service