depends on that data.
So, for instance, if my component is receiving 3 strings and at some point that data changes (structurally or "physically") I have to know it to wipe the old data in my third app and send the new one.
I know that with my clunky method I'm counting more events than necessary but at least I'm on the safe side, avoiding data collision on the third app. If you have any suggestion to improve the performance and the general behaviour of the event listening system I'll appreciate it.
Thanks.
Ángel.…
the distance between the points so the triangles it creates don't have very long sides.All my attempts were very far from the goal so I'm only uploading the population. Pictures 2 and 3 demonstrate how the software works and changes which dots to connect. The software can be found here: https://www.behance.net/gallery/10543937/Image-Triangulator-AppThank you very much!…
ood4rhino.com/app/wasp
Wasp Newsletter: https://mailchi.mp/e0ccee5c4e32/wasp_newsletter
Source Code: https://github.com/ar0551/Wasp
---
In this bonus tutorial, we will explore how to use the new SubD tools available in Rhino 7 to simplify the workflow of creating organic geometries from Wasp aggregations. We will use a set of lines as attributes, and convert them to SubD using the MultiPipe component. We will then see how to convert seamlessly between Control Mesh and SubD object.
Download the tutorial files: https://bit.ly/organic_wasp_05
Full Series Playlist: https://www.youtube.com/playlist?list=PLCn3-_9Z4-E6dfKDLUjQUG3w8rxrPrTHN…
, 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.
…
ions - essentially Shape Changing. Pufferfish mainly uses parameters and factors for inputs for more custom control over operations like tweens and grids as opposed to grasshoppers usual division count inputs. These components are accompanied by support components which are useful methods for tween / blend / morph / lattice operations such as making curves compatible, a custom curve graph mapper, and a multi-threaded morph to twisted box. In addition, there are extra components which simplify some common grasshopper operations such as testing for equality within a tolerance and rounding to nearest numbers. Please email me if you find any bugs. Works with Grasshopper for Rhino 5, Rhino 6, Rhino 7 WIP, and Rhino Mac.
Instagrams: @ekimroyrp & @designmorphine
Download:www.food4rhino.com/app/pufferfish…
Added by Michael Pryor at 2:23am on October 17, 2017
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).
…
Rhino, similar to Attribute User Text tab in Rhino 6 but with some enhanced features. Any bug or error report would be appreciated.
http://www.food4rhino.com/app/elefront…