Grasshopper

algorithmic modeling for Rhino

I'm Working on a Definition and i dont know why after a solid diference some of the geometry brep become a Invalid Brep

here i post the entire definition 

Views: 2062

Attachments:

Replies to This Discussion

Unable to get to data without the Rhino file.

UPS sorry here's the rhino file 

Attachments:

Hi Toussaint, I think you're overengineering things. I only looked at the disks boolean issue for now. Hope this helps.

Attachments:

Pieter i saw that you use a Kangaroo Component, i'm not available to use any componnent outside the native components. maybe its true i'm overengineering things. but now i need to complete de definition then at the end i will try to debug it. so let me see what can i do 

thanks for the answer 

Btw, I noticed I ended up with 6 disks missing, and I noticed some cuts missing... sorry about that. Well you got my point: simpler is better.

Considering the duplicate lines filter from Kangaroo: if a C# component is considered native enough, you could use Andrew Heumann's excellent script instead.

I tend to think that debugging along the way is crucial; no point in going on after unwanted results halfway the definition. I also think it might help to scale everything by a factor of 100 or so. Downside to that is that you'll have to adjust the numbers you use in your GH definition accordingly..

I'm curious about what you are making Toussaint, keep us informed.


Thanks Pieter, 

the definition its an exercise that me and a couple of classmates are developing in a Postgrade studies in Parametric design. the final goal is, to build a scultoric piece which will spiral around a Column that will be showed in an design exposition  here in Buenos Aires, so lets see at the end whats going on with it, i will post the process and the results when everything were done 

PS. sorry for my bad english i'm a native spanish speaker with a self-teaching of english  

I am not exactly sure what your goal is but I was able to get the Solid Difference to perform by bypassing the preceding Path mapper component immediately preceding the Solid Difference component.  The path mapper input data structure of the input was incorrect.  It was set as {a;b;c} and the actual data structure being output by the extrude component was {a;b}.  The data branch structure of the path mapper input should match the branch structure of the arriving data's branch structure.    However, I avoided the path mapper completely by simplifing the preceding Extrude component's output.  

By the way, I am using the latest Rhino 5 and the latest GH.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service