Archimedian Snub Square Tiling

Replies to This Discussion

Permalink Reply by Andrew Heumann on July 12, 2010 at 2:01am

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:

• Snub-square_tiling.ghx, 807 KB
• Snub-square_tiling_separate.ghx, 1.1 MB

Permalink Reply by Arthur Mamou-Mani on July 12, 2010 at 11:59am

Thanks Andrew!
Can i ask you on which GH you did the definition, i am getting lots of error messages...?

Permalink Reply by Arthur Mamou-Mani on July 12, 2010 at 12:23pm

Here is with GH 0.7.60:

Permalink Reply by to] on July 12, 2010 at 12:32pm

GH.0.7.60???

Permalink Reply by taz on July 12, 2010 at 4:08pm

he, he... maybe this weeks update has already been leaked.

Permalink Reply by Andrew Heumann on July 12, 2010 at 6:16pm

goodness, how does one get on the pre-pre-release list!? I am using 0.7.30.

Permalink Reply by Andrew Heumann on July 12, 2010 at 6:26pm

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:

• Snub-square_tiling_separate.ghx, 1.1 MB
• Snub-square_tiling.ghx, 810 KB

Permalink Reply by Arthur Mamou-Mani on July 12, 2010 at 6:31pm

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...

Permalink Reply by taz on July 13, 2010 at 2:05pm

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.