random points. UV coordinates of a sphere are kind of weird since they go from 0 to U in one direction but -v/2 to v/2 in the other?!
A standard 3D Voronoi of the surface points was used to create intersection curves with the rounded surface. This doubles the work of the slow marching cubes part, since each cell outline edge is duplicate of the adjacent face one, but so be it.
The layering effect and sticky flow would require more sophistication.
The Cocoon plugin is here:
http://www.bespokegeometry.com/2015/07/22/cocoon/
With a whopping 600 points, it takes some time, about a minute:
Or 1200 points:
The little bumps here and there are from using a fast crude marching cubes sample size of 0.02 instead of maybe half that which would take much longer.…
Added by Nik Willmore at 7:59am on August 17, 2015
... er ... AGAIN these @$@% fins [also baked in U and V] - wonder why I insist on them?
Why ? well ... man ... here's Greece > we can promise auto rotating fins (WOW *2 = rings on the floor + fins on the sky) and never make them > the Greek way, that is. But we can take the money (+ VAT) for making them > the Greek way.
If we make them (crisis of honesty: bad thing) there's people in Greece who can do it - barely believable but trust the Lord - by extruding poly carbonate (kinda like making custom alu extrusions) at a fraction of the planar glazing thingy cost. Panos T (excellent windsurfer, mind) can rotate them rather easily. Lord can do other "minor" things as well and supervise the construction with his known way (Merciless Perfectionism).
What if rains? Well ... Greeks do the ouzo option in this occasion (thus why bother?)
Added the happy bunny thingy on the demo surface to encourage you towards the girl + Monaco stuff.
…
r did you type paraFoam to call the OF integrated paraview, or did you maybe type paraFoam -builtin? The last one was a workaround for when paraview installation has issues. I think I remember an old bug where the version not connected to OF would give out this error. I will check it as soon as I can to make sure it's not smth in our case setup.
Concerning the boxes on the display that is the refinement of your mesh. The fastest way to get a more refined image is to go back to your blockMesh and change the number of cells in x and y directions (and thus the size of these squares) and go through the whole process of meshing and solving again. Bare in mind doubling the cell number makes a 4 times bigger mesh, which would also delay the simulation a bit (but really for such a small model it would still be fairly fast).
Another thing you can do in coarse or even medium quality meshes is to display the point values and not the cell values. You can do that in the dropdown menu where you select which fluid parameter to display (U, p, k, epsilon, etc.). In your screenshot I can see the cell value is currently selected. By selecting point values Parafoam should interpolate the display automatically and provide a more 'refined' image (but not a more accurate result). Should make a small difference in such a coarse mesh but this works quite nicely in medium to better meshes.
Kind regards,
Theodore.…
n an entire EnergyPlus model and we can get pretty close with some simpler assumptions. At the moment, there is actually a Ladybug component that I have put in WIP that calculates steady-state indoor surface temperatures given assumptions of U-Value, indoor temperature and outdoor temperature. I am currently thinking of extending this to give outdoor surface temperatures but the critical thing that I need to account for is the effect of direct sun shining on the outdoor surfaces. Because the sun moves across the sky so quickly, I am actually not sure if the steady-state assumption will hold in this case or what the minimum considerations of transient calculation would be in order to get something decently accurate. I plan to do some comparisons between steady state assumptions and transient E+ runs soon and I'll keep your comments in mind when I do so.
I should also say that, if you are ok with the assumption that surface temperatures are the same as the air temperature, you can build a comfort map using just the presence/absence of the sun as I do here:
http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Urban_Microclimate_-_Simple_Spatial_UTCI
It is probably in this type of Ladybug workflow that you will see a faster/simpler type of comfort map emerging in the next few months if I find that it is accurate/possible.
-Chris…
ility of possible (but also functional) plans in some simple module plan or better module volume (if it s could work for example also for duplex apartments or for privet houses with more than one floor). I could also image to split the module on the different parts (rooms) and let them and their position dictate the form of different modules.
And last but not the least i would like to create some generator to put those simple modules in clever and variable settlements.
as shorter conclusion.
1. floor generator in fixed form (in this case rooms should change there potions and proportions but follow some rules about for example lighting, visibility, connection between the rooms and mb min and max sizes for each function area.)
2. floor generator with fixed function areas (rooms) (in this case the plan contour or volume varieties have to be created from different arrangment from the rooms. I would lake to take care in this case of the space syntax but also lighting.
3. settlement generator which could organised different masterplans from those simple living modules.
I just started with it with research and reading of different PHd works and scripts about those themes. It s looks to be really hard.And i am kind of beginner in grasshopper and have only 3 months time. So i would be very happy for any advice, example definitions e t c.
…
that is beyond me, and with which i would really appreciate some help with !!
here s a quick explanantion ( but is probably best if u take a moment to
look at the jpeg that i have attached.
i basically have a polyline consisting of a given number of segments (
which vary), the points of which are extracted and then (apart from the
first one) moved down so that the a line of fixed length can be built
through them. the original polyline sits on the ground plane, as i have
the segments vary in lengh, this information is exrtracted using the
'length component' ....
basically for each segment you make a calculation using pythagoras'
theorem to work out the length of short edge('c')of the right angled
triangle, as you have the hypotenuse ( which is the fixed length) and
you have the length of the original line ( 'b'), ie, the amount the
point has to drop in the z-axis , but clearly each successicve vlaue
needs to added together.
so what i would really appreciate is if some could give me some
scripting asssitance ! as i feel that i need a way of adding the
successive values of 'c' together and then adding them to the new 'c'
value. i woudl count myself as a very proficient in general grasshopper
but my scripting is nt up to much ! so any help would be really
appreciated !
thanks in advance
louis
…
ives me the 'U' and 'V' to plug into my subdivide, allowing for non uniform evenly spaced tiling.
Here are two issues with my definition:
1) the polygons rotate incorrectly after the first two rows, how can a set a rotation value for this to control it? (Image below)
2) While this definition works great for surfaces that are mostly flat, unfortunately it struggles with vertical surfaces because it's only based on X Y dimensions. (Image shown below)
Unfortunately I can't use Divide Domain and IsoTrim because the domain extends past the boarder of my surfaces.
The Grasshopper file is attached to my post.
I'm extremely appreciative of any help rendered,
-Derek…
Added by Derek E Smith at 2:34pm on February 9, 2012
s because the geometry is too big for cuting in laser machine plotter, so I Want to separate this 5 segments, If you see the image 2.
I select the item number 3 that is in the midle and its all fine, but if u watch the image 3 when i select the Item 2 for example tooks segments for randomly :(.
Its like the curves are not in the same direction, i tried to flip them but no results, I tested the curve direction and it seems all ok. Look at this:
This is killing me T_T... any commentaries...…
sessment comes before design. My goal is to use both tools in their full capabilities and perhaps suggest (I would say create if I could code a line) new ones.
I was wondering about if there is already a capability of Heat Island Effect assessment in ladybug. Solar adjusted radiation modelling seems to approach something similar. I have seen variables such as material absorption. I realize that usually a CFD simulation is performed to assess Heat Island Effects but such a simulation could be enhanced with data provided from Ladybug or perhaps it could be done completely in the tool.
A simple checklist of the top of my mind, just as a brainstorming exercise, would be:
- percentages of softscape and hardscape materials in the area
- thermal properties of all materials (SRI, absorption, U-values, etc.)
- Leef Area Index of softscape (to account for shading from greenery)
- Water bodies and/or irrigation (to account for evapotranspiration)
- Open sky views, to account for reflections of light between surfaces that trap heat
- Roof and glazing reflectance of buildings (I'm guessing that is already somewhere there).
- Wind assessment to account for blockage, turbulence, etc. (this is essentially the CFD?)
- ...
I am quite new to the tools, and the scene, so I hope this topic makes a bit of sense (i.e. it can be in the least feasible or not already completely provided).
Kind regards,
Theodore.
…
s to load from file (from 0 to 1)
So this post is about masks.
Rhino Point Clouds can store information such as : location of a point, it's color and normal vector. It is common to store intensity values, but it is not supported in Rhino.
Mask characters :
x y z - location
u v w - normal
r g b - color
a - intensity
Let's say that your file is formatted such as :
10.000 ; 12.000 ; 20.053 ; 0.243
which means it stores location and intensity values.
A proper mask will inform Load Cloud component how to read those values
x;y;z;a
The first non-alphabetic character in the mask is automatically interpreted as the separator.
Same masks work with Save Cloud component. Note that it has D input which when set to True will make it surround all the values in double-quotes.
"10.000" ; "12.000" ; "20.053" ; "0.243"
Cloud Load doesn't care about those double-quotes, it just ignores them and proceeds to read the values without them.…