algorithmic modeling for Rhino



PhylloMachine is a set of scripts/UserObject for Grasshopper to model plants using some properties of phyllotaxis.

The basic idea is that a mesh with phyllotaxis proportions has a topology described by two Fibonacci numbers, and its topology (indices of vertices of faces, parastichies spirals, cycles and topological neighbors) is described by simple number sequences without geometric calculation.
Thanks to these, it can be modeled parametrically plant organs such as branches, leaves or petals, with very nature-like results.

PhylloMachine continues to be a work in progress, it's written in VisualBasic and it is open source. Released under the GNU 3.0 license.

Enjoy it! ツ

Location: Inside a seed
Members: 51
Latest Activity: Sep 2, 2019

Group organization


Feel free to consult your doubts about PhylloMachine components, about its use, its code or the implementation of the phyllotaxis. Consider adding a discussion instead of a comment.


If you find an error or something strange, please let me know.


Are you missing some functionality? Let's see what we can do.

Next season

I encourage all those interested in continuing the development of PhylloMachine to contact me via There is room for many improvements: new components; the same phyllo-wrap over several curves; somehow overlap organs like petals to the stem; branching; growth or L-System used for modeling. I am especially interested in implementing parametric L-System because the result would be just wonderful.

Discussion Forum

Comment Wall


You need to be a member of PhylloMachine to add comments!

Comment by spiral on August 5, 2015 at 12:39am

ivy to grow on any surface, it is the right tool for landscaping projects of houses, help, thank you for your work

Comment by Daniel González Abalde on June 15, 2015 at 4:47am

Hi Nik,

thanks for your interesting comment and apology late response.

The use of low poly mesh is very comparable to EditablePoly + turbosmooth in 3DMax, the difference is that from gh we can only manipulate points, and using weaverbird can easily model organic forms. It is not a new concept but little used.

Yes, to add a popup to provide assistance in each input can be a very useful and interesting solution, but I think that we should not always give everything thoroughly chewed. Learning is more inportant than the result.

About branching... I tried a couple of recursive solutions with hoopsnake, but were dirty solutions and have decided not to share. It's something you can do, though perhaps not as elegant as we would like. Also for this I'm so interested in the implementing of L-Systems.

The images that are placed in food4rhino, it really is just baked geometry in rhino, nothing more. Well yes, the "shaded" view is set to take that aspect, and simply use the captureScreen function of Rhino.


Members (51)






  • Add Photos
  • View All

© 2020   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service