Grasshopper

algorithmic modeling for Rhino

I know that this is not a "how to" forum. I just want to have your opinion or your advice in this topic.

What i'm trying to do is to nest some rectangular areas, slightly variables, inside another bigger. I want to control the bigger one in width and height and having the inner rectangles changing in dimensions but not in area.

Also, if the bigger rectangle reaches certain area, add another area.

I think that i have to get into looping and recursive, but I would like to know from any of you about this topic and, if you've already dealed with this kind of problems, share some knowledge.

Thank you all.

Views: 184

Reply to This

Replies to This Discussion

A "better" picture of the diagram

Well

I have stuff for attempting that kind of thing but is carried over solely via code (C#) and thus if you are not familiar with ... it could be totally useless for you. Impossible to explain here the logic used ... not to mention that most of these things are strictly internal.

BUT ... the main problem here is (since obviously we are talking on spatial matters) the constrains applied/required for any "valid" spatial solution (or for any valid spatial variant):

For instance:

  • A bedroom is pointless when sizes are outside a valid domain (for hosting the objects required for the scope).
  • A dry wall (a must from what I hear, he he) may comply "as much as possible" to some standardization (say 60 cm: the standard on gypsum boards width).
  • A floor/false ceiling may also comply to raised floor/false ceiling module(s) standards (60*60 cm).
  • A facade may also comply to standard tile dimensions.
  • Lot's of other type of constrains must taken into account (fire rates for instance).
  • ...

All these make the whole thingy a bit more complex than you can imagine. If some real-life results (of some sort, anyway) are required ... I would strongly advise to abandon ship without "some" coding experience.

BTW: Imagine a red thin line.

  • On the right are the requirements/wishes/client demands/floor schedules that (hopefully) require a spatial solution (of some sort).
  • On the left are a myriad of constrains that ... well ... "filter" the results (variants).

In real life the left part always wins ... meaning that theory and reality differ vastly (unless you deliberately departure from rationalism and/or you brake the Law and/or you are a liar).

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

© 2019   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service