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…
installing or running.Here is the direct link to download the PanelingTools installer. Simply double click the downloaded file and follow the prompts to install:https://www.rhino3d.com/download/panelingtools/1/wip/rcImportant Note:You will need the latest Rhino 6 Beta to run the new PanelingTools. Download from here:https://www.rhino3d.com/download/rhino-for-windows/betaIf you own Rhino 5.0 License, then you can access Rhino 6 Beta now. Grasshopper installs and runs as part of Rhino 6 Beta.You can download older versions of PanelingTools and access documentation from one of the following:- PanelingTools Wiki: https://wiki.mcneel.com/labs/panelingtools- PanelingTools at Food4Rhino: http://www.food4rhino.com/app/panelingtools-rhinoA great place to post questions and suggestions is the McNeel Discourse Forum:https://discourse.mcneel.com/For those of you using PanelingTools in Rhino Mac, you can continue to access PT thought the commandline (type pt, and the commands will auto-complete). You can also access PT Grasshopper components by following the instructions here:http://www.grasshopper3d.com/group/panelingtools/forum/topics/pt-gh-for-the-rhinowip-for-the-macRelease Notes November 14, 2017:-------------------- PanelingTools is now compiled against the public Rhino 6 SDK. This will help with quick updates and improvements independent of the Rhino release cycle.- Paneling data is compatible between Rhino 6 Beta and earlier Rhino versions.- ptGridExtrude1 allows defining a rotation base point when you set a rotation axis (from point becomes the base).- Fixed the paneling output of partial patterns when the grid does not extend far enough to accommodate a full unit pattern.- ptWeaveGrids has now an option to weave by columns. It used to support weaving by row only.- Writing a reading managed patterns has been re-written.- Fixed a number of various bugs.Enjoy!Rajaa IssaRobert McNeel & Associates…
, 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.
…
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…
glass panel).
2. This actually means that the parts on duty they don't differ that much. Meaning that we can use an "average" size (and "local" topology) acting as the Jack for all trades.
3. Meaning that we can effectively solve the abstract topology with an abstract app the likes of GH and then place in properly defined coordinate systems all the real-life bits and nuts ... closely "emulating" a pro solution (that could "adjust" the parts as well).
4. This means that one particular C# needs more lines of code since as it is it defines cable axis on a per nod to node basis ... but in fact these are defined as the min segment between curves (circles to be exact).
5. Additionally the end part of each strut differs depending on how many pairs of stabilizing cables are used (either 2 or 1). Meaning some lines of code more for defining the proper coordinate systems for the instance definitions.
6. This is the reason that I've postponed mailing to you the 4 horsemen (because PRIOR finishing the whole you MUST define what parts to use: the classic bottom-top design approach).
But in order to receive the Salvation (aka: Apocalypse) you MUST answer correctly to a simple puzzle:
Provided that money is no object, pick your car:
1. Ferrari 245 (Less is more)
2. Lancia Stratos (Lethal).
3. Cobra 427 (Men only)
4. Ford GT40 (Mama mia)
5. Ariel Atom (Mental)
6. Aston Zagato GTB4 (Sweet Jesus)
7. Fulvia HF Fanalone (THE racer)
8. Lambo Miura (Enough said)
9. Lotus Elise (Just add lightness)
10. Alfa Romeo 8C Competizione (In red)…
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.…
and Grasshopper installed, or Rhino 6. 2-Install GHPython from here (Rhino 5 only). 3-Select and drag all the userObjects (downloaded here) onto your Grasshopper canvas. 4-Restart Rhino Grasshopper.
Check out our example files to get yourself familiar with typical SkinDesigner workflows. Also SkinDesigner Tutorials will be posted in this YouTube playlist as they become available.
You should also feel free to post any questions, feature requests, or bug reports to the SkinDesigner Grasshopper Group as discussions. Finally, SkinDesigner is an open source project and all of the project’s source code is visible on SkinDesigner’s Github site as well as within the Grasshopper components (by double-clicking on them).
…
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).
…