Grasshopper

algorithmic modeling for Rhino

Hi All!

I have been testing different grasshopper paneling tools to try to apply box panels to  a surface. In the definition, I have the boxes move towards a center point which I have chosen. The boxes are moving according to (firefly and millipede) components that analyzes sound and outputs a list of numbers which I assigned to the moving vector amplitude. However, when the boxes move, they are intersecting with each other. Is there a way to populate the boxes on the grid in a way that they do not intersect when they move?

I was also wondering if there is a way to reduce the size of the definition..it is running very slow due to the rapidly changing numbers from the sound components.

Thank you!

Views: 975

Attachments:

Replies to This Discussion

I haven't downloaded the additional plugins necessary to run the full script yet, so I can't speak to how millipede and firefly are impacting the script at the moment.  However, I have a couple of suggestions in the meantime:

1. Profiler which is located under Display -> Canvas Widgets will help you to identify which components are taking the most resources.  From what I can see the Area Moments component is taking the most time at 1.5 seconds to run on my machine.  Enabling it will help you to better identify the slow points while working.

2. With the curvature of this wall, your boxes should move outwards normal to the brep face to avoid intersection.  I can't tell if this is the case until the additional components are installed.

I'll take another look after I have the time to get a proper look at it, but wanted to give you some things to investigate in the meantime. 

Hi Barrak
Why are you generating boxes early in the definition?
You should work with points as far as possible distorting your grid to respond to sound, etc., before creating curves or surfaces. This will help you make faster more elegant definition.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service