thoughts none the less. If anyone else with more experience would like to chip in please feel free!
1) if it was Manually, how did you draw a line between each corresponding point in each surface?, or did you use Ln(line) component to connect them all?
I used the Ln component to join vertices between each surface. As I was working with two surfaces I meshed each surface with an equal number of U/V divisions (Vertices) so was able to draw lines between each matching vertex.
2) this sounds great, is it like retopologizing the 2nd mesh based on the 1st?, perhaps equalizing vertex numbers, positions and properties prior to SDivide and morphing?
Equalizing is correct. When you mesh an object it will create vertices, and you can use these to re-create a mesh between each set of sub-surfaces. You don’t need to Sdivide after meshing. If you check the definition in my second post you should get the idea.
2) is it possible to manually draw a few "key" Lines connecting points, that would then cause(influence) SDivide & Ln to create lines between points at their correct correspondence between surfaces?
This I am afraid I cannot provide concrete guidance on this. I am sure it is possible by drawing lines then matching vertices based on position relative to the ‘key lines’ however I don’t feel this would be a great solution. Better to create something that is more automatic.
My surface imports to Rhino as multiple sub-surfaces which are opened in Grasshopper using Srf > Set Multiple Surfaces. But in this case when i then use SDivide and Points on Surface the points are created at the intersections of each sub-surface and then across them instead of being Equally distributed as on a Single surface. 3) is there a way to import or join my sub-surfaces into a Single surface that SDivide will then distribute points evenly over?, perhaps Brep > Join?
Yes, you can use grasshopper Brep-join to join your sub-surfaces before you divide. See image below. Alternatively, if you are joining matching sets of sub-surfaces then you can morph each sub-surface with its corresponding sub-surface then join the whole object.
If you can upload an image of what you are trying to do I may be able to help more. My work evolved to some degree since I made these posts. I am now generating objects based on time stamped data from excel rather than objects in Rhino.
How many sets of surfaces are you trying to merge through? It is also possible to morph from 1 to 2, 2 to 3, 3 to 4 …… x-1 to x by using a slider which calculates the range and picks the correct two surfaces to morph. If you need more info let me know and I will write something.
I am planning to show some of my work and where my industry (civil engineering) is going with grasshopper based solutions. Will post a link shortly to some of my projects.
Cheers
Lyndon
…
and 7 floors) depending on the size of their areas of surfaces. I managed to do it. Then I tried to divide buildings into frames/staircases (more or less). Then, I wanted to assign appropriate numbers to the proper frame/staircase. Like I did it before with whole buildings. Here is a problem. I'm lost in the lists. Could somebody help me with it? Disscution about lines and boolean regions
Columns in Excel: A - year B - population number C - % of kids in 0-2 age D - % of kids in 3-6 age
…
more about book keeping inside a single document. For example: first tab would be UI, second would be formatting, others would be different modules of my script. I have to push stuff around all the time and even with groups or alt-drag it takes a while.
In Excel a sheet is a very large 2d array, but you can add a third dimension by adding sheets and access them with =Sheet2!A1 (3 coordinates : Sheet2 , A , 1)
So sheet are just 2d slices in a 3d array for visualization.
Processing is not such a good example, it's just pages in your code that are executed one after another, but still it's good for clarity : one tab with "setup", one with "draw", one with functions, one with classes etc
Since you're an architect, think of my tabs as the storeys of a building. there are horizontal as well as vertical wires.
I figured you could add a "vertical wire" that could eventually act as a cluster in/outputs for export etc
Just an idea anyway…
hope you'd a Merry one,. 1) I used the Ln component to join vertices between each surface. As I was working with two surfaces I meshed each surface with an equal number of U/V divisions (Vertices) so was able to draw lines between each matching vertex.- ..by "meshed" i assume that meant converting Surfaces with MeshUV\DeMesh?, and from your screenshots thats a substantial number of vertices and therefore lines to draw, well worth it though from the results!, i agree with your answer to 3) that a more automatic solution is required,. 2) Equalizing is correct. When you mesh an object it will create vertices, and you can use these to re-create a mesh between each set of sub-surfaces. You don’t need to Sdivide after meshing. If you check the definition in my second post you should get the idea.- ..thats great news, equalizing vertex numbers is exactly what i need to do since my Blend surface "keyframes" by nature will likely have unequal point counts. However, a) ..when using default Rhino surf's your intruiging def. starting to work for me only after i replaced you "custom" Domain(VB\Python?,let me know) with Deconstruct Domain. then it connected each surf's vertices but did Not produce an intermediate surface or points. b) ..when using my IDENTICAL Blend surf's in your def. with Deconstruct Domain and Merge comp's it then produced intermediate vertices,.see def. screenshots or i can send def's i you like,.I'll also produce the 2nd, Non-identical Blend surf keyframe to test in your def.- 5) please show me which actual Domain etc. components or substitutes to use and how to use them to run your def. successfully? 3) This I am afraid I cannot provide concrete guidance on this. I am sure it is possible by drawing lines then matching vertices based on position relative to the ‘key lines’ however I don’t feel this would be a great solution. Better to create something that is more automatic.- .. agreed, 6) does or will your latest def. contain more automated, vertex correspondence, Ln creation? 4) Yes, you can use grasshopper Brep-join to join your sub-surfaces before you divide. See image below. Alternatively, if you are joining matching sets of sub-surfaces then you can morph each sub-surface with its corresponding sub-surface then join the whole object.- ..perhaps i missed something, but after using Brep > Join on my polysurface SDivide still saw it as subsurfaces instead of a single surface,. If you can upload an image of what you are trying to do I may be able to help more. My work evolved to some degree since I made these posts. I am now generating objects based on time stamped data from excel rather than objects in Rhino.- ..see screenshot "2-Def_shot.JPG" showing my two surf's beside Blended Rhino surfs which i need to do with mine,. How many sets of surfaces are you trying to merge through? It is also possible to morph from 1 to 2, 2 to 3, 3 to 4 …… x-1 to x by using a slider which calculates the range and picks the correct two surfaces to morph. If you need more info let me know and I will write something.- ..that sounds perfect, esp. since the sets of surfaces will be as nearly unlimited as the feature film they're modeled from. Yes, i'd love to learn more info\def's on this subject, thanks,.. I am planning to show some of my work and where my industry (civil engineering) is going with grasshopper based solutions. Will post a link shortly to some of my projects.- ..look forward to that as well, please keep me informed,..
I should be available most of today and days following so really look forward to heard back soon as you've free moments.
Thanks again for the great work as well,
big fan, Jeff…
as the design table? I think this could be 'drawn' and constrained in Inventor in a lot less time. I know the GH model would have a lot of flexibility, but in this case, what can you do with it that wasn't provided by an Inventor model?
Only the 27 lines mentioned were modeled in Rhino, the rest is modeled with GH.
The 5 hrs involved thinking about the approach, defining vertical lines, tilts, elevations, pitch of the roof, intersections.
Once I had decided what my approach would be, and tested the logic with those first lines, points and data path arrangements, it only took one more hour to get to this:
Which is actually quite fast, compared to MCAD workflows.
If you already have components (columns, beams, etc.) modeled and ready to drop into a project, of course it is lightning fast to model simple projects like this example.
I am not as much interested in those situations, because improving efficiency is straightforward and obvious.
I'm more interested in situations where there are no pre-defined families of objects, in which case you need to start from scratch.
The GH model I'm showing is modeled from scratch, except for the 27 lines in Rhino.
Here's one obvious advantage to modeling with GH, once the definition is set-up, it's virtually effortless to change inputs and alter the overall design. Here's an example, lets say we wanted to extend the roof 3 more units, curling away from the original direction.
Plan view before:
And after:
An MCAD app will also allow you to do this, as long as the location of additional elements follows the existing geometric method of definition. What happens if you want completely change the way you locate columns, roof slope, intersection points?
In MCAD, you'll need to re-model the underlying geometry, which will take the same effort as the first round. In GH, this process is not only much faster, it's open to algorithmic approaches, galapagos, etc. and it just takes some simple re-wiring to have all down-stream elements associate themselves to this new geoemtric definition.
For instance, here's the same definition applied to two curves, which are divided in GH, the resulting points are used as a starting point for lines directed at normal from curves.
This is not so easy to do in MCAD.…
Added by Santiago Diaz at 7:55pm on February 24, 2011
ices" which i found very intresting , I have your thesis and it will be the base of my futur work, I'm a graduate student in bioclimatic architecture and environment in Constantine -Algeria , I will prepare a thesis for my master degree in the theme of " parametric design, the dynamic envelope and intelligent façade" and really I need your help, if you can send me your work in grasshopper in(.ghx) mentioned in the "APPENDIX D SOLAR CONTROL VISUAL DEFINITION "(GRASSHOPPER),because i can't download it from the web site , I'm juste a beginner in grasshopper so I want to master the link between all the elements ,for this reason I would like to master your exemple in grasshopper as beginning , and I'll work with daylighting + thermal comfort in my thesis which is the continuity of your work, can you share your exemple with me please ? and why did you choose a 200 btu/ft² as a limits for direct normal irradiance , what is the formula ? I'm waiting for your response because it's so importante for my work , and i promise you , i will put your name in my references . thank you karla. the files needed are: the part which contains: 1-Solar Irradiance / TMY3 Excel Data (in grasshopper) 2-:Surface Geometry Analysis / Grid Pattern Selection (in grasshopper) 3-: Solar Profile Angles (in grasshopper)
4- Shading Geometry Profile Angles (in grasshopper) …
Introduction to Grasshopper Videos by David Rutten.
Wondering how to get started with Grasshopper? Look no further. Spend an some time with the creator of Grasshopper, David Rutten, to learn the
th (60° max in Paris), but the problem stil arises for the angle theta (for the south but also for the others orientations). For the diffuse radiation, this difference should be 10% as you noticed.
2) I have done some simulations and tried to analyse the weather file used. You can find my results in the Excel File attached. Some simulations take into account the glazing and others just determine the "occultation factor" of the shading device, to which I apply then the solar factor of the window. I found there is a noticeable difference between "_shading_1" and "_Focc_1" for exemple, we should have found similar values ... ? It seems to happen something strange when the rays passe through the glass to reach the analysis points. Facing those results, I still have trouble to draw conclusions. I also determined the diffuse part of radiations for each day from the weather file used, it may help to understand ... If you have any suggestion to explain those results, please let me know.
3) Another point attracts my attention :
The horizontal infrared radiation intensity of the weather file is quite high and constant. I'm wondering if HB take into account this solar radiation's component which represent about 50% of the solar energy ?!
http://bigladdersoftware.com/epx/docs/8-3/auxiliary-programs/energyplus-weather-file-epw-data-dictionary.html#field-horizontal-infrared-radiation-intensity
I continue my research about what is going under the hood (reading documents on Radiance and Daysim calculations) and let you know about the progress of my searches.
Thank you again for your support !
Regards,
Severine
…
lues are of any use from a display perspective as some IES files tend to have upwards of a 1000 numbers. That is why the candela values are visualized in the Rhino viewport.
2. Did you check out the (relatively) new Honeybee_IES Project component? It does produce a Bill of Quantity and also allows an export to Excel. I have explained this here: http://www.grasshopper3d.com/xn/detail/2985220:Comment:1474434
3. Eulumdat to IES is an easy fix. I wasn't aware that anybody had tested this using Eulumdat files. I will add this feature when I update the code next time.
4. Can you describe this simulation? The time taken by the simulation itself should not be that long because Radiance ( the calculation engine) has optimization algorithms to tackle multiple sources. My comment about multiple sources had more to do with Rhino than HB itself.
5. What do you mean by material design ? As in textures for surfaces?
Now, with regards to future work, we don't have a road-map of sorts at present as personally I am not quite sure about what might be useful to people who work exclusively with electric lighting. Most of the (vocal) users of Honeybee tend to be interested in Daylighting and that is where our development efforts have centered over the past year. You can read more about it here and here.
If there is some sort of consensus-based opinion from lighting designers on what would be useful we will look into adding new features.…
he time to work with it.
the project is about facade strips which turns along height. the top angle is
parallel to the facade and the bottom is max. 90 degrees twisted, but the strips
should turn diffrently to achieve more dinamic look.
first i have tried to achieve this by calculating distance between the rotation angle from points of the grid and a single point.
then i have tried to ad some more effecting points and used the distance to the divided surface (the circles are just to control the area of effection):
i manually lofted it.
the result is a bit annoying becouse the points that effect the angle are always visible:
i have triend to solve this by drawing a line and divided it to recieve points along the bottom of the geometry. the result is not working properly:
Anyway,
there must be a better/smoother way to achieve this. i would like to effect the twist of the surfaces by distance to a spline, but im just lost. can you help me please?
the problems im encountering:
0- distance spline to grid to effect the angle
1- list of x/y coordinates and angle of rotation for each point of the grid
2- export points to excel
3- lofting lines in one direction only (x1, x2, x3...)
4- reduce the list data to 2 decimal (0,00)
5- maybe angle from radian to degrees
thx…