of memory and can thus create far larger images then when it has to share memory space with an application like Rhino.
Combining images is not difficult if you know a bit of VB/C#, so I can help you out if you tell me exactly what you'd ideally need. Whether as a grasshopper script component or stand-alone app.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
er ... but ... Autodesk has other plans in mind.
Given the opportunity the main reason to use a solid modeller is ... well .. the fact that when you arrive in a polysurface (in a surface modeller) this signals the end of the road whilst in the solid apps it's just the beginning.
That said the best solid thingy out there is Siemens NX closely followed by CATIA (SolidEdge and SolidWorks are both owned by these 2).
The best way to get the gist of these things is to find some friend who (hopefully) knows his onions and ask for a 5 minutes demo.…
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. …
ee. That said these things (masterminded by a certain David R) are not bad at all ... but if you write code that is "supposedly" transferable (kinda) to other CAD apps ... well ... I would strongly recommend the other classic nested C# collections.
2. The HLP method is one out of many: for instance for a better approximation of the required fitted plane we can use the divide Curve method etc etc.
3. GH components use (in most of cases) methods exposed in Rhino SDK > get the thingy and start digging into the rabbit hole. Of course David did some other components as well that use "less" classic SDK methods (if at all).
4. HLP is a classic approach to count the beans in nurbs curves. Of course I could use PolyCurves and recursive explosion blah, blah ... but here we are not after segments (at least at present time). On the other hand if that was a Faceted Dome (planar Polylines) ... well getting the nodes that way it could be an overkill (this means business for V2).
5. Mastermind some plane orientation policies in order to finish(?) the @$%@$ thing. For instance: Given Plane plane, define a Plane.WorldXY at plane.Origin and section these 2 > then get the cross product (sectionVector, plane.ZAxis) for the new orientedPlane Y axis etc etc (this presupposes that any plane Z axis points "outwards": use Dot Product and a center point as apex etc etc).…
lines, dedicated MCAD apps, BIM apps, team work AND elevators as well: if you design something "variable" and then attempt to service it via a "static way" (Revit) you'll discover that you are wasting your time. I can list you a lot of WOW towers that failed on that (elevator) matter ... but this wouldn't be polite for the designers: so let's continue.
2. The other critical thing is the system that does the skin: since "liquid" is the new WOW (it shouldn't) the task of "faceting" a facade and doing it with a system that doesn't leak (in the long term), doesn't pop the panels out of the frames and it doesn't cost the GNP of Nigeria ... well ... is not that simple.
3. It's a very common mistake for some future Architect to "skip" (even mentally) "trivial" matters like these ... but if you get used on this type of thinking you'll gonna pay a heavy price (as an Architect).
So my advise is: whilst you are after "form(s)" sketch frantically the nuts and bits of that form (not to mention ... er ... hmm... the elevators, he he).
best…
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=…
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…
formance issue.
Reasons why I don't want to change the Integer parameter:
1) what about Number, and String, and Boolean, and Point, and Vector, and Line... should they also display the value? Or is the integer parameter supposed to be different from all the others?
2) what if you have multiple values inside a parameter. Should it grow to display them all? Should it grow to display only the first ten? Should it automatically switch to Icon-display?
3) would value display be a fourth kind of display type (alongside Name, Icon and App-default)?
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 10:25am on December 17, 2009
i want to draw a line between them. The first point called FisrtPt is a fixed point from RHINO but the second point called SecondPt is the point which i want to be able to get its data from the UI.)…