postion i j k;
value, state:
1:get.grid3d.cell i, j, k, [index]);
index: Each 3D grid cell has up to 3 different slots for storing values.
state could be:
1 Visible and selected
0 Visible but not selected
-99 Disabled
-100 Hidden
-100 Hidden and selected
best to]…
contain a definition for 'PageWidth' and no extension method 'PageWidth' accepting a first argument of type 'Rhino.Display.RhinoPageView' could be found (are you missing a using directive or an assembly reference?) (line 99)
I've just been using the example rhino file and the example GH file from the Layout_Automation files you've kindly uploaded.
Is this an issue with my Rhino that doesn't make it compatible with the Layout widgets in Fabtools?
The other widgets (bake, tag etc.) all seem to work fine.…
combination is nearly 0 (of course with 1 try). You have about 100 (?) dimensions... its just impossible to do it well. Even with billions of random genotypes for 1st generation.
Its like 1:googol (10^100) to succeed. If youll try and run it on your pc, youll probably consume all the energy in universe, and it will take longer time than our universe will exist.
Sorry :(
EDIT : As David wrote in his post - every added dimension results with almost half of "success ratio". So as with one slider you have e.g. 1:2 ratio of success, with 100 sliders you have :
1:633825300114114700748351602688 (2^99)
To somebody more familiar with math -> correct me if Iam wrong :)…
ten, he he > meaning that they deliver a (stunning if things are going well) product that when it fails in some method it reports: "unable to do it".
2. NEVER take the short route when coding: try to "report" anything that's happening; it's a bit boring but you'll see the actual reason when later you'll do real-life complex things.
More patch freaky stuff soon (but given the opportunity: where's my goats? nothing arrived insofar).
May the Force (the pink option) be with you (I'll take the black option).…
all the other rules.
2. No Flattening! use path shift / trim tree instead of flattening.
3. No Path Mapper! I have never met a data operation with the path mapper that could not be achieved through relative means.
4. No Simplify! It makes things *look* nicer but believe it or not those zeros are meaningful and shouldn't just be eliminated. If you are OCD about the way your paths look, then Path shift after every operation that introduces a new branch level (a new "0" at the end) IF AND ONLY IF you are sure that in the case of your definition the component will always function "1 to 1" - that is, for every single input there is only one output.
5. If you absolutely must flatten (to take a global bounds, or generate random values for every item, or whatever) be sure to Unflatten before continuing.
6. Design for the worst case - start with primary inputs in the most complex data structure your definition is likely to need to be able to handle (a tree for instance) rather than a single item.
If you follow the above rules, 99% of the time your definitions will respond appropriately to any change in upstream data structure. If you want an example of how this works in practice, post your definition and I can help find "relative" approaches to the "absolute" things you are currently doing. …
ating. Here's a regex that answers this question though.
^(3[2-9])|([4-9][0-9])$
I say this hoping that you'll appreciate knowing that regexes can handle ranges such as this and can add really interesting functionality for number manipulation. I should add that it does certainly get trickier with larger numbers (e.g. 3-digits or more). I also know that this post is 5 years old, so I presume you may be aware of this by now... Anyways, thought it wouldn't hurt.…
ections, that is.
Since the WOW stuff it would been addressed solely via code and since it's actually the 99% of the whole puzzle ... I've used solely code for the 1% as well (does this make any sense? not much I guess, he he).
Note: Load R file first.
Moral: roll the bones (since it's the only mode currently working (dice == true)).
best, Peter
…
cided to expose the real-thing (something that is under construction these days, a "bit" bigger than the "demo" examples provided up to this point - around 25K m2). This means a more complex definition (a "bit"). The real thing is not made with GH.
4. Membranes are treated with 2 ways: Kangaroo (bad news: you receive a mesh that is anathema for shop-drawing level studies). MinSurf + trim (nurbs on hand but with the obvious disadvantages as regards "relaxing" the other components - more code, less time for windsurfing)
5. Puzzle: do you know that big "umbrella" thing made recently in Saudi Arabia? (colossally big membranes that ...er... hmm..."fold" - 1M times the size of an umbrella). Never heard about that? Shame I must say, he he.
best, Ron (actually I mean Stan).…