j. to rhino for architectural scenes.
(unispiring ... I admit)
On recent iOS the app doesn´t work any more, so I figured out, if I should think about making a "light" version of that plant growing thing, with a definition on GH,...
I try to imagine any kind of simple setup to start with,
since I am a middle / low skilled GH user celebrating allways the taste of succes ...running an ordinary GH definition.
Angelos
…
, HVAC, blah blah).
BIM is NOT a parametric process at least having in mind graphical editors the likes of GH (or stuff the likes of Generative Components): it's a holistic data management approach. Some concepts used in BIM apps (for instance in AECOSim etc) the likes of "walls"/"openings" etc are "parametric" in the sense that allow auto perforation of this with that. On the other hand AECOSim is feature driven (since Microstation works in that "mode" as well) ... a thing that complex things even more with regard what is actually "parametric" and what not.
BIM is as good as the meta data structure is (especially the spec related aspect - Goggle MasterFormat and the likes). BIM AEC apps are notoriously incapable to work (without a lot of lines of code) with proper RDBMS. On the other hand Bentley Systems ProjectWise ... well ... but that's another animal (by no means a topic for the inexperienced).
In descending order or importance a contemporary AEC practice should use:
1. A general information "controller" like ProjectWise (who said/did what/when/why).
2. A Specs (say CSI - not the TV soap opera) management app.
3. Several Meta data RDBMS.
4. A BIM suite of apps.
5. Optionally some parametric thingy.
PS: For AEC ... when inviting the parametric thingy to the party you have only 2 options:
ProjectWise + AECOSim + Generative Ciomponents (my choice).
?? + Revit + Dynamo.
…
Or if this doesn't work the the lines who's end points Y value doesn't match
5) join all remaining curves. this gives you polylines for each row.
6) From these you can extract control points that will be on differrent branches
i would demonstrate this but i'm stuck watching the wedding at a friend's and until mcneel makes a rhinoid with gh app you'll have to wait 'til later…
omponents and Revit means Dynamo.
Both are masterminded by the very same fella (Robert Aish: an ex Bentley R&D head, then Autodesk paid more [life sucks]).
AECOSim eats Revit for breakfast but has a far steeper learning curve ... meaning that the masses would opt for Revit.…
onstrates the following:
1. The definition's functionality employing HumanUI for the custom user interface.
2. Color based segmentation in manual and auto modes.
3. The evaluation of the definition's ability to handle different point cloud data sets.
This definition performs color based segmentation in two modes.
A manual mode, that implements the Delta-E CIE 2000 color difference formula, for targeted feature detection. An auto mode, that employs a simple RGB Color Range algorithm for quicker preliminary results.
RGB to XYZ to CIELab conversion and Delta-E scripts were based on Colormine's project code from github. Results have been compared and verified with the results of http://colormine.org/color-converter and http://colormine.org/delta-e-calculator/Cie2000.
Each stored class is charted and can be accessed through the UI, as shown at 2:30, where Delta-E CIE 2000, in CieLab color space, output results were found to be in perceptive conformity with human eyes, far superior to the preliminary RGB implementation.
Initial definition versions could process highly subsampled clouds in acceptable timings. Further research showed that employing the multithread processing of Volvox components, bundling the Delta E formula with the RGB to CIE lab color conversion script, per color segmentation calculations for a one million points point cloud would go down from 23 (c# script component) and 8 (vb script component) seconds to approx. 1 second (volvox script cloud component), thus allowing the segmentation of less subsampled point clouds.
I would like to thank Heumann A. and Zwierzycki M. who provided direct support with HumanUI and Volvox. Also Grasshopper3d forum users Maher S. and Segeren P., who contributed with Rhino viewport manipulation scripts.
More on Volvox:
http://papers.cumincad.org/cgi-bin/works/Show?_id=ecaade2016_171&sort=DEFAULT&search=ecaade%20volvox&hits=2629
http://www.food4rhino.com/app/volvox
http://duraark.eu/
HumanUI:
http://www.food4rhino.com/app/human-ui?page=1&ufh=&etx=
ColorMine:
https://github.com/THEjoezack/ColorMine…
sites the likes of Code Project etc etc) that may fit to your workflow/goals. Also the available literature/printed manuals/e-manuals/books etc etc.
3. Take into account the quality of the available editors (like VS etc etc). That said the "build-in" GH editor is a bit of a crap (but it's OK for smallish/not complex coding).
4. Most importantly: // computing is the holly grail these days (and it would become the standard in the years to come: either via trad CPU cores or via CUDA/Tesla type of stuff)... thus take into account ... well ... the obvious.
BTW: If 1 is true and there's some workflow around that involves many apps ... try to write code that is as "GH neutral" as possible.…
tructures)
Bad news: real-life AEC trusses are far and away from lines.
Ugly news: Rhino is NOT an AEC app by any means nor it would ever be. For AEC app I mean the known 3 (Allplan, Revit and my favorite: AECOSim) and/or proper MCAD apps (like CATIA/NX). In plain English : without exporting (meaning (a) bake in nested blocks + (b) export via STEP) proper structured data (assembly/component) this WIP case is absolutely useless.
why may you ask.
well ... trusses are made with numerous shop drawings like this, that's why:
more soon.
best, Peter…
some weird engine, you know, he he) IS NOT like designing plain vanilla AEC things.
Therefore features/calculation methods/capabilities as found in MCAD apps (considered off topic by many in our trade) are mandatory for certain types of designs.
Anyway and if we forget FEA stuff, currently I have 3 C# goals:
(1) master the art of controlling the placement of existed blocks in GH defined topology(done),
(2) master the art of baking blocks(done) and
(3) master the art of baking heavily nested blocks that NX/Catia can understand (progress is slow).
…
nite a zillion of "solids" (closed polysurfaces in Rhino speech) you need a decent solid CAD app. Rhino is a surface modeller ... meaning that you should narrow your search towards the right girl.
3. Personally I work with Microstation (same 3d core engine as Siemens/NX [ParaSolids]) and CATIA/NX. The difference in speed for doing things like these ... well ... find a friend who works with any of these and experience it first hand. …