go and sulk in the corner, my C# is non existent, although i am making progress on python unfortunately slower than my grasshopper.
Attached is a typical relatively simple planar grillage model for a bridge form that is common in Australia/NZ/Asia. The analysis package has a good graphical interface, however i am looking at replicating the process ideally with GH. I am getting there.
There are a few constraints in the use of a super T, the precast mould is governed by two critical dimensions:
1. from the beams soffit to the underside of the precast flange, normally Depth -75 or 100mm. Depths that are common are 1200/1500/1800.
2.The real sweet spot dimension is the 1027mm dimension to the outside of the webs, this is a constraint
The actual shapes of the prestressed beams are governened by AS5100:5 Appendix H (from memory)
In my definition I included the super T cross section which is parametric.
The other definition is where I have got to with the grillage.
I am a little one dimensional: point-line-surface-volume. I think I am getting to grips with manageing data i lists.
My ulimate aim is to:
generate basic geometry in gh, the type of analysis will be a space frame or FE, these analysis types require different geometries imported to a structural analysis package
ideally utilise IFC, for materials, 2D, 3D drawings and project documentation
At the moment I am looking to generate all of my gemetry in GH, that seems to generate a lot of doubled up geometry. Deconstruct Brep may become my favourite.
A little excesive is the inclined members spilt into the same no. of points at the grillage length.
again thanks for you time, oh! took a a few minutes to work out how to plug your def's in.
kenyon
…
Added by Kenyon Graham at 7:57pm on December 3, 2015
ntended for an easier application of BF and not really for learning how to use BF, hope it was helpful. Not sure what this error is though as I can't reproduce it in my computer. Are you sure you have the latest Human components? I'll try and look it up when I can for you.
Concerning your results, they do look as expected. A heavy wake area behind the building has been created as you can see, with a quite clear pattern of wind deceleration and a recirculating vortex. This is a standard pattern in outdoor wind and something that generally we try to either minimize or plan activities around since these areas tend to have lower wind velocities and less recirculation, thus leading to debris/dust deposition and potentially higher pollutant concentration.
There are a lot of nice examples of urban wind patterns online you can check, it makes easier for you to help validate the results you get.
Finally, the k and epsilon values for outdoor studies are currently being calculated with (pretty) standard equations for the k-e family of turbulence models. I believe you can find these in the BF source code. Unfortunately I don't have access right now to check where exactly but I would look before the blockMesh component, since the case folder with all the values is created at that point.
Good luck in your CFD journey! Please keep posting results and issues!
P.S.: Btw if you are interested on the effect of your building geometry at a section parallel to the wind direction you could also try a 2D simulation. You can do that either by manually editing your blockMeshDict and setting 1 cell width on the direction perpendicular to your wind or by simply assigning a 1m wide windTunnel (centered at your geometry). This will allow you to refine your model much more than possible in a 3D case with lower run times as well. Ofc it's not as accurate as a 2D case but it's nice for experimentation.
Kind regards,
Theodore.…
ittle weave-ready ribbons appeared:
Though the Mesh+ plug-in has a few "weave" components, they only make local loops between adjacent mesh faces.
So I did the bookeeping required to create little construction ellipses and little stubby start and end lines offset in and out from each mesh edge to allow a curve blend and then rail sweep of locally rescaled ellipses along those curves, with lots of control.
There are occasional tube self overlaps due to kinks that would require fixing in other software to 3D print the output.
Interestingly, the result is sometimes a single knot curve, more often a mere handful.
…
cremental release is available for download. It fixes several bugs reported in the 0.9.0005 & 0.9.0006 versions. To wit:
Computer mice with smooth scrolling would not zoom well, this is fixed.
Previewable parameters with a lot of consecutive null items would crash, this is fixed.
Identical GHA files would collide during the loading process, this is handled.
GHA files with identical names would collide during the loading process, this is handled.
Solver Undo setting was not persistent, this is fixed.
Widget ZUI Zoom setting was not persistent, this is fixed.
Markov Widget Corner setting was not persistent, this is fixed.
Markov Widget Suggestion Count setting was not persistent, this is fixed.
Drag and Drop on Document and Template preview materials wasn't recorded, this is fixed.
AssignDataToParameter() COM-Access method was broken, this is fixed.
Geometry and Generic parameters with persistent data would not deserialize correctly, this is fixed.
Operator shortcuts via the Canvas popup instantiation menu no longer assigned data to the second parameter, this is fixed.
Cull Duplicates component did not always show the correct label upon deserialization, this is fixed.
Legacy VB/C# components would not correctly deserialize List access on input parameters, this is fixed.
Cloud Display component would still display old sprites on disconnect, this is fixed.
Minor changes to a document would trigger lengthy preview cache updates, slowing Grasshopper down. This is fixed.
Sphere 4Pt did not work correctly, this it fixed.
Failed data conversions in parameters would result in missing entries, this is fixed.
Text Tag components (2D & 3D) would not bake via the component menu, this is fixed.
There are also some new features:
Added Jump object for quickly navigating across a Canvas (Params.Util dropdown).
Added Relative Differences component which is basically the inverse of Mass Addition (Math.Operators dropdown).
Added tooltip wiggle controls to the Preferences window, Interface section.
'Draw Full Names' now also attempts to change the display of existing components, but only in the active document.
Drag+Dropping GHA, GHPY and GHUSER files onto the canvas now puts the original file into the bin.
Replaced Set Union component with a new one that has variable input parameters.
Replaced Set Intersection component with a new one that has variable input parameters.
Replaced And and Ternary And components with a single new one that has variable input parameters.
Replaced Or and Ternary Or components with a single new one that has variable input parameters.
Replaced Concatenate component with a new one that has variable input parameters.
Concatenate component now has a segment join option available via the component menu.
Added Digit options to the Transform Matrix Display object.
Integer parameters which represent options now have more informative context menus.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
…
Added by David Rutten at 11:06am on September 14, 2012
it seems that was this. Now all is working fine !
Glad that it worked! But I am still a bit worried. Gismo components only modify the gdal-data/osmconf.ini file and no other MapWinGIS file. So your MapWinGIS installation files should not be compromised. The fact that you did not get the "COM CLSID" error message when running the "Gismo Gismo" component suggests that MapWinGIS has been properly installed. So I wonder if the cause for the permanent "invalid shapes" warning has again something with the fact that your system is again not allowing the MapWinGIS to properly edit the osmconf.ini. Maybe this problem will appear again, and again, and reinstallation of MapWinGIS every time can be somewhat bothersome.
- About the terrain generation, is it possible to have the texture from google or other provider mapped onto the terrain surface from gismo component ? (Same as using the ladybug terrain generator in fact). I try to used the image extracted by ladybug component and then applied it to the gismo terrain but the texture is rotated by 90°.
The issue with the rotation can be solved by swapping/reversing the U,V directions of the terrain surface. A slightly more important issue is that terrain surface generated with Gismo "Terrain Generator" component might have a bit smaller radius than what the radius_ input required. This stems from the fact that the terrain data first needs to be downloaded in geographic coordinate system, and then projected. Some projecting issues may occur at the very edges of the projected terrain, so I had to slightly cut out the very edges of the terrain which results in the actual terrain diameters being slightly shorted in both directions. This means that if you apply the same satellite image from Ladybug "Terrain Generator" component to Gismo "Terrain Generator" component the results may not be the same.I attached below a python component which tries to solve this issue by extending the edges of Gismo "Terrain Generator" terrain, and then cutting them with the cuboid of the exact dimensions as the radius_ input. Have in mind that this extension of the original terrain at its edges is not a correct representation of the actual terrain in that location. But rather just an extension of the isoparameteric curve of the terrain surface. So basically: some 0 to 10% (0 to 10 percent of the width and length) of the terrain around all four edges is not the actual terrain for that location, but rather just its extension.The python component is located at the very right of the definition attached below.
Also, if you would like to use the satellite images from Ladybug "Terrain Generator" component along with "OSM shapes", sometimes you may find slight differences in position of the shapes. This is due to openstreetmap data not being based on Google Maps (that's what Ladybug "Terrain Generator" component is using), but rather on Bing, MapQuest and a few others.
- About the requiredKeys_ input of OSM shapes, I understand what you mean and your advice, but in most cases I use it, the component was working fine even without input. I think it's better to extract all tags, values and keys of the selected area, instead of searching for specific ones as I try to find all data related to what I want after, isn't it ? To check what keys are present on the area also.
Ineed, you are correct.I though you were trying to only create a terrain, 3d buildings and maybe find some school or similar 3d building, for these two locations. The recommendation I mentioned previously is due to shapefiles having a limit (2044) to how many keys it can contain. This requires further testing of some big cities locations with maybe larger radii, which I haven't performed due to my poor PC configuration. But in theory, I imagine that it may happen that a downloaded .osm file may have more than 2044 keys. In that case shapefile will only record 2044 of them, and disregard the others. That was my point.But again 2044 is a lot of keys, and I haven't been checking much this in practice. For example, when I set the radius_ to 1000 meters, and use your "3 Rue de Bretonvilliers Paris" location I get around 350 something keys, which is way below the 2044.Another reason why one should use the requiredKeys_ input is to make the Gismo OSM components run quicker: for example, the upper mentioned 350 something keys will result in 350 values for each branch of the "OSM shapes" component's "values" output.Which means if you have 10 000 shapes, the "OSM shapes" component will have 10 000 branches with 350 items on each branch (values). This can make all Gismo OSM components very heavy, and significantly elongate the calculation process.With requiredKeys_ input you may end up with only a couple of tens of items per each branch.Sorry for the long reply.…
Added by djordje to Gismo at 8:57am on June 11, 2017
(registrants will be able to re-watch it anytime) GOAL: understanding and managing surface continuity SOFTWARE: Rhinoceros, Grasshopper, Kangaroo 2 PREREQUISITES: basic experience of 3D modeling in Rhino LANGUAGE: English LENGTH: 160 minutes approximately TUTOR: Arturo Tedeschi
REGISTER HERE
One of the characteristics of contemporary design is a clear reduction of all visible connections, pursuing the idea of a seamless flow of curves and surfaces. From product design to automotive, from naval design to architecture’s envelope, understanding and managing surface continuity is an essential skill. The online webinar “Zebra” will introduce attendees to the notion of surface continuity in Rhino-Grasshopper. The lesson will cover mathematical aspect of curvature continuity, modeling strategies and practical examples. Contents are intended for users with basic knowledge of 3D modeling in Rhino. The webinar will be a fully interactive event hosted “live” but also available as a recorded video. Registrants will be able to re-watch it anytime. Zebra is part of our Parametric Vibrations webinar series. Tutor: Arturo Tedeschi. Language: English.
Main Topics:
NURBS representation
Notion of curvature for curves and surfaces
Curvature continuity for curves and surfaces: G0 – G3
Surface continuity in Rhino. Analysis tools: curvature analysis, Zebra, environmental map
Surface continuity in Rhino: tools, modeling strategies and tips for surface continuity.
Examples
Overview of continuity tools in Grasshopper
…
Diploma project from knagata on Vimeo.
Kinect hack on GRASSHOPPER 01 from knagata on Vimeo.
Kinect & Grasshopper from Elise Elsacker on Vimeo.
gHowl + Processing + Lazycutter Test from Atel
I'm assuming there will be some serious bugs. I'll upload a new installer friday-evening with all available fixes. Until then, you can get the pre-release here:
EXE installer
and a zipped version of the same installer:
ZIP installer
Known problems:
- Layout logic has been largely rewritten, which means that components and parameters will appear slightly shifted when loading old files. Panels, ParamViewers, Sketches etc should remain in place.
- Many core functions and classes have been changed. This will affect those VB and C# components that were calling directly into Grasshopper. Several of Giulio Piacento's components (TheEngine, BakingTools) will no longer work for example.
- Clusters have been removed entirely (trust me, there's a good reason for this), so any file you load that had clusters will give you IO warnings and the cluster contents will spill directly onto the canvas (functionality should remain the same).
New Features:
- Params.Special.ParamViewer now has scrollbars if the data description exceeds the visual rectangle.
- Params.Special.ParamViewer now has an alternative display mode which draws a graphic representation of the data tree.
- VB and C# component type hints are now much more robust.
- Zoom Selected button in View menu and Canvas Toolbar.
- Enable/Disable Solver switch which allows the user to completely switch off Grasshopper updates. This global switch replaces the RhinoEvents and Grasshopper events toggles, which were document bound.
- It is now possible to save and restore states ([Solution->Save State...] and [Solution->Restore State] menu). Sliders, Graphs, Boolean Toggles, Colour Swatches and Gradients can be included in a state record.
- ASSERTS can now all individually be discarded for the remainder of the runtime process.
- Discarded ASSERTS can be re-enabled via the [Solution->Clear Exception Ignore List] menu.
- Save operations are now echoed in the status bar, so there is feedback when using Ctrl+S.
- Deselect objects by pressing Escape in addition to Ctrl+D.
- Unknown shortcut combinations and unhandled keypresses are now relayed to the Rhino command line. So if you type "line" while Grasshopper is the active window, it will start the _Line command in Rhino.
- Objects can now instantiate themselves from IDs and Object Names, though there is still a problem with auto-updates.
- Variable parameter UI has been tuned up and all remaining (I hope) bugs have been fixed.
- Parameters and Components now have per-object display modes for icons, text or application default.
- Bakeable objects now feature a Bake... option in the menu which exposes more control over attributes.
- The Panel object now has an option for multiline input, which allows you to define a list of Strings simply by typing in multiple lines.
New Components:
- Params.Primitive.ID (represents a list of Rhino object IDs)
- Params.Special.Readfile (asynchronous text file parsing from disk with auto-update feature)
- Params.Special.ImageSampler (asynchronous image file parsing from disk with auto-update feature)
- Logic.Tree.ExplodeTree (extract all the branches from a data tree)
- Logic.Tree.PathCompare (compare a path to a search pattern)
- Logic.Tree.ReplaceBranches (a find/replace operation on the branches of data trees. Read the help topic of this component for information about how path mask work.)
- Vector.Vector.Display (preview anchored vectors in the Rhino viewport with an optional gradient)
- Curve.Util.Reduce (polyline reduction algorithm)
- Curve.Util.Rebuild (rebuild curves)
- Curve.Spline.CircleFit (fit circles between other circles)
- Surface.Primitive.SphereFit (create a least-squares fitting sphere for a set of 3D points)
- Mesh.Triangulation.ConvexHull (create a 2D convex hull for a set of points)
- Mesh.Triangulation.DelaunayEdges (create a 2D delaunay edge-graph for a set of points)
- Mesh.Triangulation.DelaunayMesh (create a 2D delaunay mesh triangulation for a set of points)
- Mesh.Triangulation.FacetDome (create a facetted dome for a set of points on a sphere)
- Mesh.Triangulation.OcTree (create a 3D Oc-Tree structure for a set of points)
- Mesh.Triangulation.QuadTree (create 2D Quad-Tree structure for a set of points)
- Mesh.Triangulation.Proximity2D (find the N closest points in a 2D set based on minimum and maximum search radii)
- Mesh.Triangulation.Proximity3D (find the N closest points in a 3D set based on minimum and maximum search radii)
- Mesh.Triangulation.Voronoi (create a 2D voronoi diagram for a set of points)
- Intersect.Boolean.TrimSolid (trim a Brep with any number of cutting objects)
- XForm.Morph.SpatialDeform (deform geometry based on a custom spatial definition)
If you're brave enough to test this, please post bugs as soon as possible on this forum since I only have 1 day left before I leave for Siggraph.
Enjoy!
David
--
David Rutten
david@mcneel.com
Robert McNeel & Associates…
, presso la sede Manens-Tifs, nei giorni 26,27 e 28 maggio 2016.
Il comfort visivo e la gestione dell’illuminazione naturale in relazione al risparmio energetico diventano sempre più rilevanti per una progettazione innovativa degli edifici. Ad esempio, il nuovo protocollo LEED 4 riconosce crediti per le simulazioni di daylighting e conferma l’importanza degli aspetti progettuali per “collegare gli occupanti con lo spazio esterno, rinforzare i ritmi circadiani, ridurre i consumi di energia elettrica per l’illuminazione artificiale con l’introduzione della luce naturale negli spazi”. Senza strumenti software per la simulazione della luce non è possibile ottenere risultati di qualità. Radiance è un software validato, utilizzato sia a livello di ricerca che dai progettisti ed è tra i più accurati per la simulazione professionale della luce naturale e artificiale. Non ha limiti di complessità geometrica ed è adatto a essere integrato in altri software di calcolo e interfacce grafiche. Queste ultime facilitano le procedure di programmazione. Le principali e più versatili saranno oggetto del corso (DIVA4Rhino e Ladybug+ Honeybee, plug-in per Grasshopper e Rhinoceros 3D).
Il corso è rivolto a progettisti e ricercatori che vogliano acquisire strumenti pratici per la simulazione con Radiance al fine di mettere a punto e verificare le soluzioni più adatte alle proprie esigenze. Sono previste lezioni di teoria e pratica con esempi ed esercitazioni volte a coprire in modo dimostrativo ed interattivo i concetti trattati.
Le domande di iscrizione devono essere presentate entro il 12 maggio 2016.
La brochure con i contenuti del corso e tutte le informazioni sono disponibili su questo link
Il corso è sponsorizzato da Pellinindustrie.…
eded to calculate many Waterplane Areas and the GH Area component was bogging things down. I looked to Basic Ship Theory and the use of Simpson’s Rule which in this case mirrors an intersection between a Half Hull and a waterline and then divides up the enclosed waterplane into an even number of equally spaced segments to calculate the area. The result of which is 99.997% of the Rhino and GH area and about a thousand times quicker (more actually). But when checking my method I lofted the simple section curves and fed this into an Area component and had a result a hundred times quicker than the original. This got me thinking that it was the complexity of the Surface that was a problem so I rebuilt the curve with the same number of points as used in the Simpson’s Rule calculation… This was even worse now taking 4 minutes as opposed to 2.8. Wondering why, I realised that the original surface and my Simpson’s surface where created 90º to each other. One lofted from one side of the vessel to the other whereas the quicker method lofted along the length. So I swapped the UV of the original and low and behold 4.3s….
The methods, results and images of the different area calculations are shown below with Simpson’s Rule at the top followed down by: Simpson’s Surface, Original, Swapped UV, and Simplified at the bottom. Also I attach the Definition AreaQuestion.gh
It’s also interesting to note that Rhino Itself does not take anywhere near as long to calculate.
All achieve as fast as I can select a surface and right click
I know the Area component does a lot more than what Simpson’s rule can achieve i.e. 3D surfaces with complex shapes but it would appear that some sort of evaluation of the surface regarding the UV direction might speed things up or if there was a check for planar surfaces to implement a numerically faster approach such as Simpson’s Rule.
I hope this was all of some use.
Slaynt vie!
Danny
…