onstrates the following:
1. The definition's functionality employing HumanUI for the custom user interface.
2. The evaluation of the definition's ability to handle different point cloud data sets.
3. Video reports with the definition's results, animating subsequent per deviation step frames.
This definition calculates best fitting plane deviations. The number of manual set parameters has been minimized to two the facade per World UCS axis selection and the search width. This defines a box, which is used to crop protruding architectural details, which do not contribute to the analysis, but also ensures that large deformations are included in the calculation.
For the automation of the vertical and horizontal sections creation, the analyzed cloud is clustered, according to user defined number of 2d grid cells. The deviations corresponding to each cell are averaged in mean and median mode.
The process is displayed mostly in real time, with some speed up in some parts. Too long calculations have been omitted during video edit. The setup is responsive and benchmarks show that changing between dense point cloud data sets and facades is pretty quick (6.5-7.5M points, 25-45 deviation steps, 44x22 clusters), updates are calculated in acceptable timings (3-6 minutes).
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=…
(probably during the course of installing some other apps)
Still Grasshopper is showing this error (I've installed the very latest build).
What do I do?…
rom this webpage (the first top download on that page):
https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-ma...
The issue is that downloaded 'pluto_20v2.csv' file is enormous - 290MB.
I tried to delete about 95% of it, and approximately use only the first 5%.
I hope the definition provides some insight.If not, let us know.I couldn't upload the files for some reason. They are here:https://www.dropbox.com/s/grxuta8v8x18u70/mapData.gh?dl=0https://www.dropbox.com/s/5igqsdnryz9df2q/pluto_20v2%20first%205perc.zip?dl=0…
Added by djordje to Gismo at 2:21pm on April 15, 2020
dro). The quality of the driver is also critical: hard to imagine NVidia working overnight to fix "some" driver bugs due to requests from gamers. Game cards are notoriously bad in dual monitor configurations.
3. A zillion of cores (triumph of marketing VS common sense) divided by the given clock rate ... gives you just ONE poor old core (Rhino/gh are single-threaded apps) that tries to do the job.
4. Single Xeon E5 2xxx V3 (the higher the clock the LESS the cores = better) would be my recommendation. ECC fast memory is also a must.
PS: Find a friend who operates a "loaded" H/P Z840 and test your defs.
…
is a exhibition building) generic outline (easy with GH), (b) real nested parametric part inclusion in the definition (hmm), (c) a GH ability to bake structured geometry to Rhino...and then Rhino (acting as a "companion" app to a given AEC app + FE analysis + cost analysis + ...) export properly structured data.
2. "Whole" and "Detail" here are tightly related : there's no meaning to promote an "idea" without solving the nuts and bolts of it. This is the so called "bottom-to-top" design mentality.
It's a mystery to me why GH doesn't include, say, some ways to control bake on a per block basis (actually on a per nested block basis).
…
a black hexagonal background. They are containers of parameters but parameters in themselves, like the "x" in a mathematical function. So, what I do is something like:
2) That depends exclusively on the panel, not the cluster. Then you can't. It is also not possible to assign access (item, list, tree) to the parameters.What you are trying to do, assigning components to the inputs directly, can only be done from code or using snippets. http://www.food4rhino.com/app/brick-box…
Get plenty of RAM. Windows 32-bit can assign 2MB of Ram per process, so if you have lots of RAM, you can run Rhino+Grasshopper in memory all the way. I'd say get at least 4GB, and preferably 8GB. If you have a 64-bit machine, then it pays off to go even higher than that.
2) Get fast RAM. Memory access is the main bottleneck in many applications, so the faster the RAM the faster most apps will work.
3) Get a fast processor, rather than lots of slow processors. Only a few apps out there can truly use Multi-Threading (Rhino and Grasshopper cannot). These days, CPU manufacturers try and dress up multi-core CPUs as the next best thing. It is not. It is a lie. Until software can truly run on multiple cores there is no benefit to this. If rendering is a big part of your job, then it does pay off to have a multi-core machine though.
4) Get a good graphics card. I've always preferred NVidia over ATI, but there are many good ATI cards as well. You can go for a gaming card (they're cheaper), but note that these are optimised for drawing triangles. If you get a professional card, it will draw lines and curves much faster.
--
David Rutten
david@mcneel.com
Robert McNeel & Associates…
ents instead of code ... it could yield a nightmare of components (and a myriad of parameters). For real-life designs I would never attempt to do this without code.
2. A certain experience with Kangaroo (or some min surf other thing since using K on these ... well may be the killing a mosquito with a bazooka thing). That said I'm a great admirer of Daniel's work. But on the other hand why not?
3. A "certain" experience with trusses/space frames.
4. A "certain" experience with instance definitions (that's not doable with GH components).
5. Years of experience with parametric feature driven MCAD apps - Image35 (NX/CATIA) for designing the real-life parts (that have NOTHING to do with "abstract" concepts).
In total I would say that a similar "app" with code (excluding the min surf/mesh thing) would require 6-10 full days of work (or even more).
BTW: https://www.google.com/url?q=http://www.grasshopper3d.com/forum/top...…
Please mail me the file that is causing problems so I can debug it.
Regarding your quad-core, Rhino and Grasshopper are not multi-threaded applications. (Very few apps actually are). Therefore I can only use 1 of your cores which equals about 25% of a quad-core machine.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 4:07am on November 10, 2009
th a graphic editor (GH) hosted in a CAD app that has primitive assembly/component capabilities and/or feature driven ops (Rhino). Did I've mentioned that Rhino is a surface modeler? (meaning the obvious).
3. Imagine a "seed" collection of assemblies related with various membrane components made in SW. Say: geometry (prior solid ops) and parameters (the feature driven part of the equation, in most of cases managed with some RDBMS). You should port these to GH (a variety of ways exist for that) and create the bare minimum of "solids" in GH as instance definitions. There's 2 main reasons to do that: (a) effectively communicating back on an assemply/component schema (via STEP) and ... (b) achieving manageable collections when in GH. These are critical for clash detection (when outlining some topology in GH, therefore NEVER work just with "curves") and "variation" control of some sort (up to a point). Of course for high class designs (where the devil hides in the details) this is NOT the best imaginable solution ... you'll need CATIA for such an integrated (all in one) procedure. On the other hand many could (wrongly) argue that CATIA is expensive (rather naive argument if a company has a certain turnover).
4. So, in general I would strongly suggest to use instance definitions of items in some sort of "intermediate state" of detail (an 100% undoable task without code) structured in such a way (classic assembly/component MCAD mentality blah, blah) that SW could take benefit of a possible modified "base topology" and proceed by finishing variations of the given assembly (feature driven stuff as usual).
5. Then export (STEP 214) back portions of the assemblies (and parameters used) to R/GH if and when this is required (for instance for BIM disciplines ... but Rhino is not a BIM app, nor it would ever be).
6. If you are familiar with code matters ... start thinking the whole puzzle that way, if not my advise is to find someone to design such a "procedure" (say an "app") using solely code, but this is not a task for the inexperienced by any means.
best, Peter…