algorithmic modeling for Rhino



Wasp is a set of Grasshopper components, developed in Python, directed at representing and designing with discrete repetitive elements.

Download it here: Food4Rhino

Source Code: Github

Example Files: Wasp Examples

Facebook: GhWasp

Instagram: Gh_Wasp

Location: Frankfurt, DE
Members: 48
Latest Activity: yesterday

Discussion Forum

Do not repeat parts? 4 Replies

Hello! Thanks for making this great plugin!Is it possible to ensure that parts are not repeated in the aggregation?I.e - I have a large number of unique parts that correspondent to real world objects…Continue

Started by Matt. Last reply by Andrea Rossi yesterday.

Field driven modeling 5 Replies

When I tried to model a field driven structure,1) it takes so long time when I connected a "wasp field component" to a "wasp filed driven aggregation."2) Once connected, error messages were popped…Continue

Started by Yujin Kim. Last reply by Andrea Rossi May 27.

A Solid Difference component does not work for WASP. 2 Replies

When I tried to make a void in the center of WASP geometry, a "Solid Difference" component did not work. I understand WASP does not work as BREP but work as Mesh. So, a transform component was…Continue

Started by Yujin Kim. Last reply by Yujin Kim May 22.

Collision check between two Field Aggregations 4 Replies

Hello,I am creating a field aggregation with one part and another one with a different part but they are overlapping. Is there a way to check for collisions between 2 different aggregations and…Continue

Started by theotses. Last reply by theotses May 13.

Comment Wall


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

Comment by Andrea Rossi on December 7, 2017 at 7:10am

Hi Henrik,

the PREV input is there to allow you to add a previous aggregation as a base on top of which to aggregate new modules. However, as these modules are still computed in the aggregation process, using it will not make your code faster.

Currently, the best way to achieve aggregations made of large groups is to split the aggregation in smaller sub-areas with small overlaps, and aggregate them independently, always providing the last parts as starting points for the next aggregation. I can send you a file, if you are interested.

In the new version of Wasp (will release it hopefully this weekend) there is the possibility of setting a threshold on the Field component, which allows, depending on your field, to speed up calculations, of couse sacrificing the precision of the field approximation.
If you want to take a look, you can download the work in progess components on the Github page:

I am working on a "probabilistic" field aggregation, which should be much faster, but I am not sure of when I will have something usable. If you send me a PM with your email, I can keep you in the loop and let you know as soon as I have something.

Comment by Henrik Yang on December 7, 2017 at 4:03am

Hello Andrea,

Currently im working on a project using muqarnas as element to aggregate. As you can see it needs a very high iteration number. Then I saw this PREV input that i wonder if it would help my work to become more smooth? Can u show me an example where u set up the PREV? Does it save the old parts somehow? What does it do?




Members (48)






  • Add Photos
  • View All

© 2019   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service