I am not knowledgeable about google maps nor google maps api, but from what I read the two components will definitely show a bit different results due to different topography sources.If it is judging by this 2010 article, your Terrain Generator component offers much higher precisions for USA. Precision goes up to a couple of meters, which is amazing!!On the global scale it offers either SRTM 1 or 3 arc-second data or 30 arc-second GLOBE data. Again this is from the mentioned article, I couldn't find this information by searching the Google Maps website.Terrain Generator 2 component always uses SRTM 1 arc-second data from opentopography.org, and it is limited to 60 degrees north and does not have data for Antarctica. It does not come with satellite image either which is another very convenient feature that you have!I couldn't find information about the allowed radius provided by the Google maps api free account. I limited the "radius_" input to 100 000 meters, even though opentopography.org provides more than that (I successfully downloaded 300 000, but Rhino 5 was not able to create a topography on my PC from such a large amount of data).Even though I couldn't compare the results from two components, by looking at your upper example_LB_terrain_generator.gh definition: set the "I" input of "Surface from points" component to True. In this way the surface will be interpolated through points, which is what we want.
Again thank you for the permission, and I look forward seeing those high precision topography that Google maps offers!!…
Here I use one which has been refined with a 5 level subdivision...does it appear ok to you or would you recommend going even smaller? Green nodes are the ones loads act upon.
2) 'Local To Mesh' vs 'Global' vs 'Projected Global'
I am applying a positive wind pressure (0,729 kN/m2) in the direction of global positive y axis.
The façade mesh is 1505 m2, of which 1056 m2 runs parallel to the XZ plane.The wind pressure is 0,729 kN/m2 acting in the positive y direction ---> expected resultant of +/- 1056 x 0,729 = 770 kN.
'Global' gives +1098 kN in positive y direction.
'Global Projected' gives a +770 kN resultant in the positive y direction.
'Local to mesh'...gives -770kN along x axis (parallel to the façade according to ModelView) & -215kN along y axis. This surprised me since 'Local to mesh' is indeed the option to chose according to the manual yet I can't see how a wind load perpendicular to the facade would result in the tower moving in a cross-wind direction. 'Global projected' appears to provide the most logical result.
In view of these results, do you think the mesh remains ill-defined, the tower's shape is the culprit...or my choice of coordinate system for the load? What would you recommend?
Thanks again for your feedback, which is greatly appreciated.
Nathan
…
cript that and I attempted tweaking it for several days but I'm having problems achieving the full idea i had.
Problem 1:
Once I Brep a frame of the original cube, and the hoopsnake starts, it does not always select the right face of the frame, sometimes chooses a face inside rather than the exterior one, therefore not always fitting pieces together nicely. I tried applying a bounding box to each frame and use the face of the bounding box as reference for the hoopsnake mirroring but I couldn't figure it out so i got rid of it. So I'm stuck...
Problem 2:
The other thing, is I'm wondering whether its possible to parametrize some sort of structural principle into the linear growth sequence in order for structure to retain realistic structural integrity. For example, when you start hoopsnake, the cube linearly grows (mirrors itself) towards the selected point(s); if the growth goes up and across, how would I make it reach a structural limit to make it go back down to the floor and back up again and continue? Could even be as simple as "after 5 frames/cubes vertically and across it goes back down and then up again towards the referenced point(s)" or something.
PS. "Reset All" in Hoopsnake before doing anything.
Hope someone can help.
Thanks in advance,
Cesco…
tle.
I use rhino with the nurbsrelaxation plugin. Recently we have had rhino do some work to come up with an automated drawing tool via grasshopper.
Since grasshopper has been added to rhino i have noticed that when drawing surfaces and then using the nurbs tool the tools behaviour has changed and is now including iterations at the end of its process doubling the amount of time it takes to draw/finalise the surface/shape.
Below i have included 2 screenshots, the first one shows the surface(yellow edges), and then the cursor showing the nurbs icons (toolbar) and the rest of the info is in the command boxes.
The 2nd one shows info in the command line, detailing what happens once the tool is run (this is where you can see the iterations occuring).
Having done a little research i get the impression that this may be grasshopper related but cannot find any confirmation of this nor of anyone experiencing the same issue.
I also know that nurbsrelaxation is a plug in so not everyone will use this.
Can anyone help me with this as i would like to know why the iterations are occurring and if we can eliminate or reduce them.
Many thanks in advance
Matt…
Added by Matt Fairley at 4:08am on November 10, 2015
j
1
c
e
h
k
2
f
-------------------------------------------------------------------------------------------------
To these...
0;0
0;1
0
a
i
------------------------------------------------------------
0;0
0;1
0;2
0
b
g
j
1
c
h
k
------------------------------------------------------------
0;0
0
d
1
e
2
f
------------------------------------------------------------
Thanx……
ooking for an efficient way to perform glazing of complex shapes.
I've only followed the Energy modelling workshops so far so i may have missed some essential components or workflows to achieve my needs. But i've made an attached definition with all my current attempts to get a proper HBzone with the numerous windows faces i will always have to deal with in this project.
I first thought that i was not using the HBObjWGZ correctly, then after some readings it was maybe an upgrading issue, then effectively i had my Therm 7.5 that needed to be reinstaled, but then ... I must be missing an essential HB tricks or workflow i guess ...
So I divided my attempt in two series :
- The Serie 1 : is a simplier version of the project step i'm working on but i'd be glad to achieve it first !
- The Serie 2 : is the real final direction of the project, which consist in sorting/dispatch faces to windowon one side and to an other material on the other, according to the winter sun and a pourcentage param.
Despite it is more complicated than the Serie one, it seems seems to create the same diversity of issues.
Until now, with the 5 different combinations of Serie 1, and the 3 of Serie 2, with and without using the different Glazing/window components, here are the logs i got from both HBZone component or OpenStudio component:
From OpenStudio - "1. The simulation has not run correctly because of this severe error: ** Severe ** BuildingSurface:Detailed="00073E23257843B6A948", invalid Construction Name="ETFE" - has Window materials.">> Has to deal with the way i'm trying to assign too early a customized EPConstruction material ? Done it wrong ? I tried to reload it in the library but doesn't change anything...
From OpenStudio - "1. The simulation has not run correctly because of this severe error: ** Severe ** BuildingSurface:Detailed="000579CD749E46DFA5EA", invalid Construction Name="EXTERIOR WINDOW" - has Window materials.">> Is it an issue in the way i define my surfs both as "WINDOW" (5) for srfType and Outdoors on the same component ?
From Create HBZone -"1. Solution exception:'EPZone' object has no attribute 'shdCntrlZoneInstructs'"
>> Happens when i try to introduce my ETFE EpMaterial after creating my first HBZone, with a Set EP Zone Construction, so this material seems to be not working either before and after trying to create an HB Zone
From Create HBZone- "1. Solution exception: 73df51a3b2144b1e858b has been moved, scaled or rotated."If you need to move or rotate a Honeybee object you should use Honeybee move, rotate or mirror components. You can find them under 12|WIP tab.
>> >> wich seems to exist in some on other thread Here and was a coding bug supposed to be fixed.
And last but not least ...
From OpenStudio - "1. The simulation has not run correctly because of this severe error: ** Severe ** checkSubSurfAzTiltNorm: Outward facing angle of subsurface differs more than 90.0 degrees from base surface.2. The simulation has failed because of this fatal error: ** Fatal ** GetSurfaceData: Errors discovered, program terminates" .
I'm attaching the file with each attempt in this post. The definitions are disabled and the log already copied separatly so there is no need to compute each of them to see what's wrong.
If someone from the beginner to one of the Kings of HoneyBee has any relevant answer/solution to this attempt with complex geometry Issue it will be really nice for me so i could to move forward !!
Thanks in advance guys and have a great day !
…
hopper no requiere de conocimientos de programación o scripting para permitir al diseñador trabajar de forma generativa y paramétrica. No son necesarios conocimientos previos de Grasshopper pero sí de Rhino a nivel básico.
Controlmad es Centro Formador Autorizado Rhinoceros y Rhino fab Studio.
Nuestros profesores son Instructores Autorizados Rhinoceros con experiencia universitaria, nacional e internacional.
El curso y los ejercicios a desarrollar están enfocados a diseñadores, arquitectos, ingenieros y estudiantes.
En este curso introductorio el alumno se familiarizará con términos básicos de la estructura de Grasshopper, como “listas de datos”, “dominios”, “estructuras en árbol”, etc.
Es un curso de 18 horas, con el que se pretende entrar en la lógica de trabajo de Grasshopper mediante diversos ejercicios, de forma que el alumno sea capaz posteriormente de desarrollar sus propias gramáticas, con la confianza que da comprender los términos básicos de programación sobre los que se apoya todo el sistema de trabajo de Grasshopper.Para este curso no son necesarios conocimientos previos de Grasshopper, pero sí de Rhino (a nivel básico).
También se vincula el programa con la impresión 3D aprendiendo a exportar archivos desde Grasshopper con los requisitos mínimos de impresión 3D. Se realizará una demo de impresión en el aula.
El primer día del curso se le facilita al alumno un manual-tutorial con los ejercicios a realizar, en PDF.
A la finalización del curso, y siempre que el alumno haya asistido al 80% de las clases, se le otorgará un diploma oficial acreditativo del curso.
Fechas: 5, 6, 12 y 13 de marzo
Horario: sábado y domingo 16 - 20,30h (Madrid, CET)
Lugar: Sesiones On-line en directo a través de nuestra plataforma online.controlmad.com
…
he picture (4).
Previously, I had a problem with generating intersections between the two directions of the beams, but a colleague helped me by extending beams, so there was no problem with lines of intersection. But this solution has generated curl (5) at the highest vertex geometry, which I ignored in order to repair it before printing, perhaps this mean my problem with my beam spread properly. Only when the beams is 19, does not jump no problem, but I still can not distribute them properly.
(1)
(2)
(3)
(4)
(5)
I tried to show as simply as possible by removing or signing my code in GHX file.
Thank you in advance for your help
…
which needs to go in the first line only.
Each value K is one element of the knot vector
XYZ is an individual control point. Each point gets its own line/string in the output list
R is the weight of the XYZ point defined in the same line
I can get all these data into separate lists easily enough using the buttons etc. But getting them into the proper order and moving stepwise down the data to generate the desired output string list is eluding me so far.
My thought is to make an array of columns.
Column one is a list of knot values.
Column two is a list of X values.
Column 3 = list of Y values
Column 4=z values
Column 5 is weight values
etc
The idea would be to read the first value in each list into a list of five elements, then make a string out of it. The second value of each column into a separate string on the next line, then the third value from each column into the third string in the output list and so on.The last few values in the output list will contain knot vector elements only, as there are more of these than there are control points. Some of these curves are very long, with many control points, like hundreds and hundreds.
It seems I should be able to pull the lists of interest and combine them into a tree somehow; so far all I have been able to manage is to get them into a single list by starting with control points, then weaving each list of interest successively into the growing list. I'm thinking I need to get the list for each parameter into an individual branch, then read a path across the branches at each index value. But I am missing something about the terminology. I have watched a few videos and it makes sense when people are pulling nested geometry out of models, but this is a little different. More of a data management issue. I'm sure if I wrestle with it I will get it, but it may not be pretty. Any pointers appreciated. A couple of approaches are attached. Not sure whether to loop a list subset through the data or do something else. Thanks,
Karl in LA…
I am starting to wonder if I have some sort of mismatch between my GHA file and my Diva version, though I'm not sure that would cause these kinds of problems.
Incidentally, I tried creating a brand new file and I get the same results. I cannot save anything with DIVA components in them, they disappear every time. :(
Speaking of 2.0, do you happen to know when that will be released?
Thanks,
Marc
info: Plugin version: 0.8.0066 info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read info: Plugin version: 0.8.0066 info: Object list read error: Component DIVA Daylight Analysis for GH {4ec4ef63-a2e3-4501-891c-dc1107bdd94d} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.
error: Component Material {842f969a-3d16-4b32-9aaf-d996bd25181a} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.
error: Component Construction Assembly {2f4beddf-fda7-4852-9820-c36101cd316d} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.
error: Component Fixed Shade {cc5c1712-3cb4-4e91-b322-ebc050a75c3f} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.
error: Component Read Saved Thermal Results {b71b827f-7e12-42a8-a44a-a9ebb1da1596} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.
error: Component Viper: Thermal Analysis for GH {8a8fd0f2-dcd8-4c3c-83dd-d74baf8dcaba} failed
…