have a variable grid. sects 1 and 3 are a function of the width of the skewed slab crucially I require points aloneg the edge to the slab which means that U and V maust be equal. For sect 2 I will require to vary this dependent upn the length of the skewed slab.
I am trying to retain the data structue in the form of {0;0;0}(N) to allow what i see as a more simpler line/grillage generation.
I have seen other posts that have attempted to address it, I'm sure there are other ways of doing this. i have included two VB scripts that are close but do provide what I am after.
All help appreciated. this is drving me mental.
rgds kenyon
Hopefyully my sketch will whet someones whistle, the points weer drawn by hand
I should point out that once I have achievd the data tree challenge the plan is to exclude the points on outside of the skewed slab, which i have solved.
…
Added by Kenyon Graham at 6:19pm on January 30, 2016
doing generative design with grasshopper.
The idea was to do the spatial zoning and massing on a site based on some density calculations. but so far i could just achieved a basic volume(cuboid) which went beyond the plot boundary from the script attached with this post. The goals that i look to achieve are 1) massing according to the density calculation 2) division of plot and zoning of different programmes 3) environmental analysis (which might be achieved by gecko)
I cant figure a way to achieve the desirable output as i am newbie to this as well as i couldnt find any guidance around me from the people i know or over the internet. It would be nice if u could have a look and guide me to complete this script succesfully as this is something a lot of people have been talking about but couldnt find any1 who had successfully achieved this.
Regards,
Nirav Upadhyay
generative%20design.3dm
Generative%20design.gh…
image with shows some simple usage of the path mapper.
The points worth noting are the following:
1. The "Source" is comrised of a single line notation which EXACTLY matches the existing path structure. This means that if your parameter viewer shows you a path strcutrure which looks like {0;0;0;1;0} (N=4), your source input should look like {A;B;C;D;E}(i). Here, all the letters A-E and i are placeholders meaning that they can be any letters and are standing by for each digit in your path structure. This also means that they could be any letters: {Q;R;S;T;U}(V) would work as well as {A;X;T;B;S}(J). The important thing is that you are identifying each digit (including the value of 'N', the total items in each path).
2. The "Target" is (obviously) your desired path structure. If you want to simply get rid of the zeros while maintaining essentially the same path structure, it is as simple as dropping out those placeholders while writing the target notation. In the above example, if your source is {Q;R;S;T;U}(V), you can use a targe like {S;T}(V) to return a structure which will be {0;1}(N=4) or {T}(V) for {1}(N=4) and so on.
3. if you want to swap the path structure, i.e. if you have 5 paths with 10 items each and you want 10 paths with 5 items each, you switch the placeholders in the source and target notations. for example, {X;Y}(n) -> {n}(Y)... and so on.
I hope that the above is of some help. Please feel free to keep asking.…
Added by Sameer Kumar at 10:29am on December 7, 2009
in a "bigger" scale, he he). Divisions are proposed to suit variable area schedules (small airport with 3 divisions bigger wow stuff with more). My initial intension was to design this via insulated tensile membranes (THE engineering purity) bit client thinks that these are only suitable for some gypsy campus.
2. Goal is to outline a collection of "boundary" surfaces (so far the definition deals only with the exterior skin and an indicative WIP "base") that could define "in-between" them space trusses. See a primitive "generic" outside boundary in the Rhino file (second not shown). Of course ideally this type of forms is actually T-Spline territory, but never mind.
Back to GH thing:
3. See results with C# Surf rebuild and odd results with closed stuff as well.
4. It's obvious that mess relaxation (Geo Gym stuff) methods are required here - working solely with nurbs is a clear dead end (unless applying "weaving" in dense U/V areas) .
Stupid questions section:
(a) how we can trim surfaces in GH? - help in components...er...hmm...is this help?
(b) by what means can we fillet, variable fillet and/or blend surfaces in GH? Of course given an infinitive amount of time one could do that by defining a myriad of suitable curves - but this is CAT not CAD (T=torture).
Best, Peter (one step before Plan A, no actually there's no Plan A since Microstation/Gen Comp can't blend/fillet correctly a thing (or two), he he)…
make quad mesh usable with Kangaroo and with limited inputs parameters in order to simulate funicular structures like "Vaulted Willow" or "Pleated Inflation" from Marc Fornes and the Verymany.
Here is a first attempt script.
As inputs there are :
Lines_in, just lines, no duplicates, on XY plane could have Z values, but the algorithm works on a , on XY plane could have Z values, but the algorithm works on a flat representation.
Tolerance is used to glue lines when points are closer than tolerance
Width is the half width of the “roads” going through the network
Angle is the shape of the ends of the roads, 0° means flat end, 180° a totally rounded end
Deviation is the shift generating spikes or enabling to generate pleated geometry
N_u is the number of subdivision along the “roads”, image above with 3 subdivisions on the roads
N_u is the number of subdivision across the “roads”
Zbool if false everything is flat, if true the mesh is in 3d, best with angle = 180° or -180°
For the outputs there is the topology of the network (like Sandbox)
As outputs geometry are put on datatree, each branch represent a path on the road, above 3 paths, which are brep output.
Adding a diagonal there are now 4 paths so 4 branches
The mesh M goes with F which are fixed points, anchor in Kangaroo.
U and V are lines in datatree, there will be used as spring in Kangaroo, U above
This script could be used to draw sort of roads, like in here https://codequotidien.wordpress.com/2013/03/22/hemfunction/
But the primary purpose is to do that.
…
t the maximum potential with the bridge BIM+PARAMETRIC DESIGN ;D
During this Intense Week, we will learn about the power of Rhino + Grasshopper + ArchiCAD with Professional and Useful examples for our Normal Working day :D
You will get Advanced Library Files + Personal Web + Knowledge and Skills to start using this incredible Methodology ;D
Also, the week is having Lectures from different Experts sharing their Computational Working Experiences ;D And Jam Sessions! opening the door to 5 interesting topics to research, learn and experiment together :D
2020 is your YEAR ;D !!!
Complete details and registration……
n be obtained for curved NURBS surfaces as well as unconventional window configurations".
And I also noticed the following information form the optional input in the runEnergySimulation component.
"meshSettings_: Optional mesh settings for your geometry from any one of the native Grasshopper mesh setting components. These will be used to change the meshing of curved surfaces before they are run through EnergyPlus (note that meshing of curved surfaces is done since Energyplus is not able to calculate heat flow through non-planar surfaces). Default Grasshopper meshing is used if nothing is input here but you may want to decrease your calculation time by changing it to Coarse or increase your curvature definition (and calculation time) by making it finer".
1) My case is an one-story, rectangular-plan large hall (40m*70m*25m) with a curved roof. The roof surface is a part of a standard sphere and the walls and floor are all planar (the each wall has one curved edge as showed in the image).
For testing, I threw the original curved roof surface into daylight and energy simulations without making customized meshings, because I assumed that it might be automatically converted to meshs by Honeybee - Am I right? As showed in the image, how can I reduce the number of meshs in a proper way? Must two connected surfaces (i.e. wall and roof) be STRICTLY/SEAMLESSLY connected or not (considering different divisions of meshs in the respective surface)? - Is a connection tolerance allowed?
2) But, when I run the annual daylight simulation for this case, it gave me a lot of warnings "oconv: warning - zero area for polygon".- is that normal? and how to avoid this? Does the daylight simulation allow "curved NURBS surfaces"?
3) Moreover, when I run an energy simulation for this case, it costed extremely long time. It was just so long that I did not even have results out of one simulation. - I guessed it might be the problem caused by the curved roof surface (or automatic meshing?), but I don't have experience of converting a curved NURBS/spheral surface into correct meshs that can be recognized by Honeybee simulations (Daylight and Energy) in a proper way.
4) The large window on the wall was generated by the "_glzRatio". But the automatically generated wall meshs around this window are just too "fine", which might largely increase simulation time. Is there a proper way to get rid of it? (Considering that the size, shape and position of the window will have large influence on the daylight distribution in the building, it is worthy to keep the size, shape and position of the window as it should be in reality).
In sum, considering all above, could your please provide me some suggestions/tutorials/links that might be helpful for dealing with "curved NURBS surfaces" in Honeybee simulations.
Thank you all in advance!
Best,
Ding
…
or rhino like terrain, terrain in 3DS max etc, but I the result isn't enough for precision request mine, and I've also try with patch surface directly on the level curves.. terrible!!!
I have found an Italian video tutorial (you can download at the following page http://www.treddi.com/forum/topic/4543-modellare-un-terreno-con-rhino/ ) basically the main steps are the following:
1) create multiple section of the level curves in U direction (using contour command)
2) create poly line trough these points
3) create multiple section of the previous poly line in V direction
4) create poly line trough the last points
5) create network surface.
I'm trying with GH because I've an huge area (around 350x500 m) and a large number of level curves, at the end I've a crazy number of poly "self made draw". I'm newbie of GH (just few months), but I've done the step n. 1, the my problem is that the result points are unorganized (or not organized like I want ;-)) and GH cannot correctly do all the line.
Enclosed you will find the 3dm and ghx file, any suggestion?
I hope I made myself clear!
Best
Andrea
In Italiano
Ciao Ragazzi vi riassumo in italiano il mio problema scritto veramente male e di fretta in inglese.
Devo costruirmi il modello digitale di un area collinare di dimensioni circa 350x500 m, con una discreta precisione (necessità di controllare sterri e riporti a seguito di una edificazione). Ho provato varie soluzioni e plug-in tipo terrain o altro, ma i risultati sono scarsi per il mio livello di definizione e aumentando i parametri il computer (non proprio da buttar via) si impalla.
Il grande philix su treddi ha postato questo tutorial che sembra fare al caso mio (http://www.treddi.com/forum/topic/4543-modellare-un-terreno-con-rhino/) il problema è che, dato l'area e il numero di curve di livello, alla fine potrei passarci una settimana e perderci la vista per disegnare a mano tutte le polilinee, vi riassumo in breve i passaggi di philix:
1) creo delle sezioni a passo costante delle curve di livello in una direzione U
2) mi faccio delle polilinee semplicemente unendo i punti appena trovati (continuando riga per riga)
3) creo delle sezioni a passo costante in direzione V delle polilinee appena disegnate in direzione U
4) punti come al punto 2
5) network surface
Ho provato con GH (sono un neofita) e sono riuscito a fare il punto 1 del tutorial (beh non è molto difficile) ora il problema è che se chiedo a GH di provare a disegnare polilinee, di qualsiasi grado, mi restituisce un errore, poichè i punti non sono "organizzati" (o meglio non come vorrei io hihihihi), e pertanto non mi disegna nessuna polilinea. Le ho provate tutte, cercare di riunire le liste, provare a ordinarle, ma niente proprio non riesco, vi prego aiutatemi.
Vi posto sia il modello 3dm che il ghx.
Grazie
Andrea…
ial-by-nao-box-morphing/), but there are several reasons as to why it wasn't suitable for what I'm trying to do;
1. I'm interested in using a 2D pattern rather than a 3D form, which will then be repeated within a Paneling point grid which is assigned to a surface. The repeated patterns are then pulled onto the surface, which are then used to trim the surface.
2. The surface I'm using has high curvature, and using box morphing intersects the surface, so it doesn't conform to the surface as closely as I'd like it to unless the number of repeats along U and V are increased.
3. The surface I'd like to use has various trimmed regions on it. Paneling Tools is great for me, because the 2D pattern is repeated on a Surface Domain point grid, so it is initially repeated over the the trimmed regions, but once since the Pull setting is used, only the repeated pattern curves that lie over the kept surface remain (see Paneling tools jpeg).
The surface I've used in the images isn't the surface I need to use, but hopefully it shows what I'm trying to do. Also, I've managed to get the patterning that I need on the paneling tool example, but the reason why I want to use Grasshopper is that it allows me to scale up/down the UV ratio of the paneling points by using a slider tool, so the user can change the pattern density. The only trouble with this is that I can't bake the points out of Grasshopper into Rhino so I can use paneling tools.
Also...I'd quite like to know how the VB module works, because I'm curious, and I'd like to learn more!
Sorry if this is a bit wordy, but I can't think of a better way of explaining what I need.
Cheers, Abs…
olling layers and potential condensing surfaces may occur in a design assembly by graphing the temperature gradient through the assembly and calculating the dew point (internal). By studying a proposed roof and wall in isolation, it can inform the process of detailing the juncture between those two assemblies.
Here's how the script looks with the algorithm doing all the calculation and drawing on the right and the control panel for material and design parameters on the left.
Here you can see the organization of the file with the notations and group labels. The script uses two different dew point calculations for comparison. This is an example wall assembly with a total R value in US units of 22. Material thickness (mm) and thermal resistance (u value) parameters are inputted to calculate R value in SI units which is then converted to US units. Design parameters are set to study a particular interior/exterior temperature relationship and a desired interior relative humidity. The tool then graphs the temperature gradient through the assembly and located the dew point as a coloured point (the yellow and orange Xs).
Give it a go and feel free to comment or ask questions. A 2D typical assembly dew point calculator like this is of limited value, but can be a useful step towards developing well understood details at assembly junctures.…
Added by Naryn Davar at 8:10pm on February 1, 2016