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.…
dy stuck.
The basic concept is to create a 3D boundary(a box),
by generating random differnt values(length) and vectors(xyz),
such as (0,0,2), (-3,0,0), (0,1,0), then connect these points in order,
so there will be a snake(polyline) running in the boundary and
keeps growing longer through looping.
However, I can't quite understand how to use hoopsnake to achieve such action.I tried many times but all of them doesn't work.
About the 2 gh files below,
Gourmet Snake 3D.gh is before I use Hoopsnake,I tried to run it without boundary.
Test snake.gh is that I tried to generate a random number for every loop, then save them all and sum them up every loop, so I can check if the result is out of boundary,
if true, then I can mutiply -1 to let it decrease till it's in the boundary.But I can't achieve it through Hoopsnake.
Sorry for the poor english expression,if you understand my problem,any suggestion will be appreciated.
Tien
Gourmet_Snake_3D.gh
test_snake.gh…
ude a solid with sharp edges, and then I try to fillet the edges.
The problem is that the process is very time consuming because there's a lot of guess work as to what radius you can apply. Also the result isn't very good.
I'm looking for a fast way to do this, and I was wondering if there isn't a simpler and faster way to do this with Grasshopper.
Here below are 2 images to illustrate and I attach a file if anyone would be kind enough to give it a try with Grasshopper.
Thanks in advance for your advice
Seb
1. This is what I have when I open the Illustrator file:
2. This is what I'm trying to get, even thought the result isn't great, and it takes way too long to do with Rhino's fillet edge function
Thank you,
Seb…
ning the simulation looks great(see figure 1). However, I find some question(see figure 2), the red wire frame on the right should be symmetry like the physical lamp, but it has a extend distance now.
I should like to keep the wire frame structure with same length after simulation.
maybe I miss some setting in Kangaroo, can any one fix it? thanks in advance.
I put this ghx file under the attach.
…
n elements in grasshopper.
So, I found myself rather blocked, not being able to do certain operations which I need:
1. I can't close the tubes, leaving the center circle open, when I try to input the cap holes, it takes all the tree and it closes, and I am still confused about how to edit trees and items. It would be rectangular shaped holes, rather small (it is intended for bicycle wheels, thus rather thin and long). I wish to be able to change the amount of these holes, since I am not certain yet.
2.In the same time, I have no idea how I would create a slope joining the 2 vertical boards ( floors).
Here is a small drawing explaining what I am looking to draw
In the same time, is there a way to create a slope, joining the same floors, but build on a different principle.
A slope revolving around the long vertical tubes ( trees). As in the image below
Thank you beforehand for your help, if halfway, you see the there is a faster way, or that would be more of a grasshopper way, of creating or changing an object, please do tell me, it would help me understand GH better.
I wouldn't have asked, if I wasn't this tight in terms of time, and if I had the slighest idea on how to do it. So pls help, and thank you.
…
Added by Archiheart at 1:51pm on November 13, 2015
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
eroberfläche des Grasshopper Programms
Funktionsprinzip eines grafischen Algorithmus-Editors (Datenfluss)
Unterscheidung von Parametern (Datentypen) und Komponenten (Datenverarbeitung)
Erzeugung, Bearbeitung und Analyse von Geometrie-Typen: Punkte, Vektoren, Linien, Kurven, Flächen (surfaces, brep) und Netze (meshes)
Strukturierung der Daten anhand von Listen und Bäumen
unterschiedliche Verknüpfungsmöglichkeiten von Parametern (data matching)
praxisnahe Grundlagen der Geometrie und Vektorrechnung für generatives Design
effizienter Aufbau von parametrischen Modellen anhand Übungsaufgaben
Auszug von Daten aus Modellen für die Fertigung; Daten aus Tabellen (Excel, CSV) importieren, exportieren
Einsatz von benutzerdefinierten Komponenten (custom components)
Vorkenntnisse: Rhinoceros3d Benutzeroberfläche der Software: Englisch Unterrichtssprache: Deutsch
Details und Anmeldung:
www.vhs-sha.de
click: SUCHE
Kurstitel: GRASSHOPPER
oder direkt:
http://www.vhs-sha.de/index.php?id=90&kathaupt=11&knr=3151053&kursname=Grasshopper+I
Trainer: Peter Mehrtens
Kursdauer: 3 Tage / 8 Stunden pro Tag
Freitag, 19.07.2013, 08:00-17:00 Uhr Samstag, 20.07.2013, 08:00-17:00 Uhr Sonntag, 21.07.2013, 08:00-17:00 Uhr Ort: Volkshochschule Schwäbisch Hall, im Haus der Bildung
Teilnahmegebühr: 349,00 € Teilnehmerzahl: 4-10 Personen
…
berfläche des Grasshopper Programms
Funktionsprinzip eines grafischen Algorithmus-Editors (Datenfluss)
Unterscheidung von Parametern (Datentypen) und Komponenten (Datenverarbeitung)
Erzeugung, Bearbeitung und Analyse von Geometrie-Typen: Punkte, Vektoren, Linien, Kurven, Flächen (surfaces, brep) und Netze (meshes)
Strukturierung der Daten anhand von Listen und Bäumen
unterschiedliche Verknüpfungsmöglichkeiten von Parametern (data matching)
praxisnahe Grundlagen der Geometrie und Vektorrechnung für generatives Design
effizienter Aufbau von parametrischen Modellen anhand Übungsaufgaben
Auszug von Daten aus Modellen für die Fertigung; Daten aus Tabellen (Excel, CSV) importieren, exportieren
Einsatz von benutzerdefinierten Komponenten (custom components)
Vorkenntnisse: Rhinoceros3d Benutzeroberfläche der Software: Englisch Unterrichtssprache: Deutsch, auf Wunsch auch Englisch
Details und Anmeldung:
www.vhs-stuttgart.de
Dieser Kurs wird in Kooperation mit ifBau gGmbH und VHS Stuttgart angeboten, und wird von ifBau als Fortbildung für Mitglieder der Architektenkammer BW anerkannt.
Trainer: Peter Mehrtens
Kursdauer: 3 Tage / 8 Stunden pro Tag
Freitag, 24.01.2014, 09:00-17:00 Uhr Samstag, 25.01.2014, 09:00-17:00 Uhr Sonntag, 26.01.2014, 09:00-17:00 Uhr Ort: VHS Stuttgart, Fritz-Elsas-Str. 46/48
Teilnahmegebühr: 510,00 € Teilnehmerzahl: 4-10 Personen
…
to do once I figured out how you use only a small portion of each of my generated curves to make the 360 degree Loft surface. I had a huge AHA! moment when I realized the complete Loft surface really only needs a small portion of the generated curves rotated around to form a closed (except for top & bottom) surface. That is a major new insight for me and I appreciate you pointing it out.
I also tweaked the Twist angle parameter a bit so the resulting positive and negative Twist surfaces, when combined, yielded a result that was closer to my original shape. This is when I discovered something very interesting.
When I baked/exported the result using just one of the 2 twisted surfaces I got an STL file that had no errors, that 3D Builder was able to simplify from a 37 MB file to a 3 MB file, and that sliced A-OK. But, when I combined the left and right twisted surfaces, I was back with my same set of problems: the exported STL file had many errors, could not be fixed, and did not slice properly.
I went back to my original layout that uses the complete set of generated curves to create the Loft surface and found I got exactly the same results - using only one twisted surface worked fine, but nothing worked when the left and right twisted surfaces were combined. By nothing I mean I tried all the standard methods (GH Join and Sunion, Rhino Solid/Union, Join, etc.) What I think this means is that the Loft surface behaves the same, and apparently is the same, regardless if it is generated by rotating strips or by using complete closed curves.
Furthermore, I am guessing the problems with the combined/exported STL file made from both left and right twisted surfaces has to do with overlapping/coincident parts of each one - like the top & bottom planar surfaces and some of the wiggly parts.
If I am correct about this then it suggests to me that there is some sort of glitch in Rhino's STL Export function. This is surprising to me since I though an STL file only paid attention to the external shape of thngs,and did not know or care about any inside stuff. Of course this is all conjecture on my part, but at least for now seems it will be impossible for me to actually print the double-twisted geometry.…
Added by Birk Binnard at 3:52pm on September 23, 2016