mental studies and make it possible to run the analyses faster and more accurately.
Thanks to RADIANCE’s gendaymtx (and the awesomeness of Greg Ward, Ian Ashdown, and the help of Rob Guglielmetti) Ladybug is now using a brand new sky model which makes hourly and real time radiation analysis possible (Watch this video). SunPath is now improved and there are quite a few new components that work with SunPath including shadow mask, ray-tracing (short video), and view from sun (short video).
There are two new components for shading design and shadow studies that are not fully functional but are good enough to be released as a test version (This video shows the shadow study component).
I’m the most excited to introduce and welcome Chris Mackey as the new co-developer of the ‘bug who has developed the Humidity Ratio calculator for Ladybug which you can find under weather data analysis tab. People working with HVAC system design and thermal comfort may find it particularly useful and you can consider this component an initial step towards a Psychrometric chart for Ladybug.
There have also been a few enhancements to the analysis components. The parallel input is working properly now and the analyses are run much faster (here is the proof!). The orientation study is also modified so the legends are normalized and will stay at the same size and in the same location. And there’s much more to be explored when you install the components!
So far I couldn’t find a fast and accurate way to calculate the Vertical Sky Factor but both the viewRose (short video) and the shadow mask components calculate the values of VSF in 2d and 3d which can be used for your studies. I believe there should be a faster way to calculate the VSF based on view analysis.
You can download the new version from the same link and give it a try. I also updated the source code on GitHub and prepared some new examples to get you started. Don’t forget to update your GHPython to the latest release (Thanks Giulio) before updating the Ladybug.
Thanks again for all the support, great suggestions and the kind comments. Please keep the suggestions coming and stay critical to the ‘bug and the results of your studies.
Best,
Mostapha…
the daylighting and energy sim with Nat Vent create many complex questions.
Daylighting :
1. Adding shading to energy AND daylight simulation: Can I add HBconext to Honeybee_run daylight simulation HBobject input ?
Looking at the results it seems like daylight simulation doesn't recognize HBcontext, or maybe the difference is minute. Am I doing this correctly? Is there a possible error due to redundancy ? (meaning I am introducing the HBcontext twice, one time to the Honeybee_run daylight simulation AND energy simulation)
2. One of the component, Honeybee_Read annual result 1 keeps failing and says that ''1. Solution exception:index out of range: 0." I read here input needs to be internalize data but maybe there is a better solution?
Shading :
I want to study life cycle perspective of
A) Optimal ratio of fixed vs dynamic louvers for economic implementation,
B) Assess whether it makes more sense for the dynamic louvers to functions as light shelvs or the fixed ones for economic reasons
C) Simulate dynamic/fixed hybrid louver system schedule, and show it in a manner similiar to lighting schedule.
For this I would need to simulate the effect of dynamic and-or fixed shades in reducing annual lighting cost while reducing cumulative heat gain.
3_How to introduce Dynamic shading schedule for custom shades? Is this done with EPtranschedule input of the HB EP context component? I would like to keep the louvers branched so that it is possible to assign different modes i.e. fixed or dynamic
Light Shelf:
4_Is the lighting schedule effected by light shelves introduced in the annual daylighting simulation?
5_Does energy simulation take account of additional heat gain from light shelvs ?
6_When I use Honeybee_createHBSrfs with Honeybee_radiance Mirror material, it crashes rhino. The geometry input is not branched. Any report similar crashes?
Nat Vent:
I want to design to combine passivhaus principles with Natural ventilation.
My goal to simulate the energy performance of passivhaus house like building system with Bouyancy driven Nat Vent design which maximizing the percentage of the year Nat Vent takes care of ventilation and cooling, and in cloud days heat exchanger with fans kicks in.
using a trombe roof that heats air and using a vertical shaft that recirculate air, want to minimize the use of fans, Ducts, Heating etc. and I want to use the HB Set_Air flow component to evaluate such system if I can.
while I have heard that bouncy driven system may only be reserved for tall buildings, I still would to simulate the effectiveness for mid rizes and podium- types. I am skeptical whether there will be enough pressure difference for effective ventilation of 1.5ms so I would like to test.
How to set up models to evaluate bouyancy driven ventilation :
7 About HB Set_Air Flow, with Natural ventilation, If I use the HB Set_air the honeyzone output is null. I am not sure why, no error messages.
8_ When using the HB Set Air component to include Nat Vent with bouyancy,
does the result of reduced temperature to take effect into the cooling/equipment/ventilation schedule of the Honeybee_set Energy plus zone schedules?
Additionally I want to incorporate Nat vent analysis with the light shelf, since both would effect indoor temperature.
A wish list: as if it were all this has been not.
9_I wish there is something like a deconstruct honeybee zone component that basically breaks down all the options (mechanically ventilated or not) that is associated with the honeybee zones so that it is easy to document all the properties in text.…
nd linear/planar tectonics. Within this new field of investigation, the Stuttgart VS will be researching into novel techniques of material mixtures and grading, associative design and double curvature surface generation.
For the second cycle of this exploration we will be based at the Institute for Lightweight Structures and Conceptual Design (ILEK) at the University of Stuttgart. Drawing from the Institute’s long history of experimentation and research on tensile structures instigated by Frei Otto in the 1960s and conducted at present by Werner Sobek, this year we will be focusing on the design and fabrication of materially graded membranes, as well as the application of UHPC and FGC on fabric formworks. The workflow followed will be divided into two stages:
1. Computing Membranes: Computational form finding methods will be taught by professional engineers and architects from ILEK and str.ucture GmbH. The aim will be to utilise the latest software technologies to form find membranes for textile structures, or fabric formworks for complex concrete structures. The results will be evaluated against criteria such as internal air pressure, as well as asymmetric and wind loading. The outcome of this research will inform the material grading procedures (i.e. changing the stiffness, thickness or porosity of the membranes themselves, or the consistency of the concrete poured into the formworks) that will follow in stage two.
2. Fabricated Grading: The digitally computed membranes or formworks will eventually be fabricated physically, utilising the workshop and robotic fabrication facilities at ILEK. The objective will be to rethink conventional research on tensile and concrete structures as isotropic constructs, by customising attributes such as materiality, reinforcement, rigidity, translucency, patterning, and porosity among others. The final, graded prototypes will be made up of mixtures of materials, all accurately engineered to respond to variable environmental, structural and aesthetic criteria, in essence forming multi-material structures that have finally caught up with the latest material developments.
Prominent Features of the workshop/ skills developed:
Teaching team consisting of AA diploma tutors and ILEK and str.ucture GmbH engineers.
Access to the Institute of Lightweight Structures and Conceptual Design (ILEK), the Materials Testing Institute and Concrete Spraying Robotic facilities at the University of Stuttgart, as well as to the office of str.ucture GmbH Structural Design Engineering.
Computational skills tuition on Grasshopper, Rhino Membrane, and Karamba.
Lectures series by leading academics and practitioners in architecture and engineering.
Fabrication of functionally graded membrane and/or concrete structures.
Eligibility
The workshop is open to current architecture and design students, PhD candidates and young professionals. Software Requirements: Rhino (SR7 or later) and Grasshopper.
Fees
The AA Visiting School requires a student fee of £595 and a young professional fee of £895 per participant, which includes a £60 Visiting membership fee.
The deadline for applications is 10 July 2017.
For more information, please visit:
http://www.aaschool.ac.uk/STUDY/VISITING/stuttgart?name=stuttgart
For inquiries, please contact:
mixedmatters@aaschool.ac.uk…
to explain the ultimate goal in case it helps to clarify. I have all the elements i need now to pull this together thanks to your help, as you say most critical things are already implemented or not relevant to this particular thread. With your fret generator and equal spacing generator and my primitive convoluted solution for compound radius fretboard i have everything i need but need some time to cleanly implement and pull it together now.
as to your questions/coments:
1/ I don't care about Excel files in this context. The SIMPLE solution is to just copy/paste sets of string gauges into as many panels as you need and switch between them.
this was just to explain that ultimately there are a lot of different input patterns but all the data for them does already exist. for sure it is not necessary but in the end it's a feature i would like to implement since it will make the patch much more practical.
2/ What are "scale length low E string" and "scale length high e string"? Are they the actual string lengths of the bass and treble strings?
This is the initial decision taken by the luthier: which scale lengths to use for the multiscale build. While anything that makes sense goes here luthiers will probably want to choose some common values, say 24.75" (like most Gibson guitars) or 25.5" (like a Fender Stratocaster)
P.S. I did the rotations at the points where the treble string intersects the virtual bridge and nut (blue lines), so rotation has no effect on its length.
P.P.S. In case it isn't obvious, rotation has no effect on string spacing either.
This is the kind of things i don't know cause i'm zero in maths and i usually have to try out and measure to know for sure :-) as i said my initial instinct would have been to rotate around the 'zero frets' center point simply because everything is built aroun d the X axis. If you rotate around the treble string (the high e string) would the distance of the upper fretboard edge to the x-axis be the same than from the lower fretboard edge to the x-axis ?
for running data through panels, thanks for the tip, i do this mainly to visualize the values without having to hover over the outputs, good to know i shouldn't patch them onward from the panel.
PS: For the height of the strings above the fretboard (the 'action'), it's not as complicated as it sounds and most of the time an experienced luthier or guitar tech will have no problem achieving whatever low action desired if the neck is straight and built properly and the frets level and dressed properly. there's a german company who's built a machine to do the 'perfect setup': the PLEK machine
i'm sorry it takes me much longer to digest and implement all this, i will post back when i've merged everything together but i think i have evrything so far
…
hit Commit.
I'm wondering how hard it would be to have an edit box which shows the
number the user could click inside of then type in a new number, then
hit enter. :)
2) How would I go about using one line from a table and assign each
field to a variable? Then, move a slider or something and use the values
from the next row?
background: I'm recreating elbows, Tees, and other fittings using
paramatric scripts, then baking and exporting them. Here's one source
table, http://www.wardfittings.com/Assets/PDFs/0902CatalogColorOld.pdf
page 5, the uniform elbows.
Current Setup: the attached ghx file. Create a point at 0,5,0 in a blank
document with units set to inches, then assign that point to the top
left 'Center Pnt' in the ghx file.
Current workflow:
a) Modify variables A, B, H, and Nominal Dia to match one line from the
table in the linked PDF file, page 5, table of regular elbows.
b) Select the 'Nodes' and 'Surfaces' with a drag box
c) Click 'Bake'
d) Switch to Rhino window, do the 'sellast' command.
e) Drag baked objects along Y axis so the center point is at 0,0,0
f) Run 'Join'
g) Run 'Cap'
h) set the 'node' points to a layer called 'nodes'
i) set the surface to a layer called 'fit-3d'.
j) select the surfaces and nodes
k) export selected
This elbow that I'm doing only has 12 rows, so doing it the above method
doesn't take THAT long. I'm also going to be doing a couple with larger
tables like the Tee on page 8, and in other spec files. As you can
imagine, entering in EACH value into a slider is a bit tedious.
I'd love to take the pdf table, run it through an OCR program to convert
to excel, modify the headers so the ghx script knows what they are, then
paste it into grasshopper, or save it and have grasshopper read it, and
I be able to move a slider or something to to select one line at a time.
Has anyone done something similar? ie: assigned one row in a table to a
predefined set of variables, each variable coming from one field in the row?
Thanks for taking the time to read this message. :)
I'm making a rhino script to do steps d-k, so that part will be much faster.
-Suthern…
’s mid-point and whose direction is perpendicular to that edge. The following images are a summary of how I’m currently doing this. Keep in mind that the shared edge is not always parallel with the x, y or z axis… in fact it usually isn’t.
This is the vector I'm trying to get...
This is my workflow:
1- Find centroids of surfaces...
2- Find mid point of the edge. The for each surface, create vector from mid point to centroid and also reverse the direction. Place a point at the end of each vector...
3-Test to see which of the two points for each surface is contained within each surface's boundary and select that point (this parsing is necessary in some cases depending on the shape of the surfaces)...
4-Here is the kicker. In cases where one or both surfaces are skewed, the centroid of that surface is not necessarily "perpendicular" to the mid point of the edges as evident here with surface B. So I create a plane (technically its a "frame") that is perpendicular to the edge...
5-I then pull both points to that plane...
6-From there its pretty straight forward as far as getting the required vector...
So is this the best way to do this. In particular I'm curious if there is an alternative to step 4, but really any comments are welcome.
Thanks,
cbass…
is a tour through the different workshops we have organized in theTPceu from September 2010 when we started with this initiative.I take this opportunity to thank you all for your participation directly or indirectly to make all of this possible.
La exposición consiste en un recorrido por los diferentes talleres que hemos organizado en el TPceu desde septiembre de 2010 que arrancamos con ésta iniciativa.
Aprovecho para agradeceros a todos vuestra participación dirécta o indirecta para conseguir que todo ésto se haya hecho posible.
Organization: Pablo Delgado, Andrés Velasco Muro, Jaime Díaz Álvarez
more info at TP ceu…
urve. In this Curve I have defined the points, I exploded the segments and have added a Perp Frame on the ends of each segment.
Oriented on each Perp Frame I have created a Rectangle from which I have drawn a Box Rectangle.
Each 'other' (odd or even, or each 'second' rectangle in the list) of these rectangles needs to get a negative length value so it doesn't point outward of the curve, but instead so that it has it's length perpendicular to the segment.
So, eventually I want to make it so that each segment has a Box Rectangle placed on it's outermost point, pointing inwards. Half of these Box Rectangles is already oriented in the right direction, but I don't know how to single out half of them, or construct two lists with the 1st, 3rd, 5th, 7th, etc. and the 2nd, 4th, 6th, 8th etc.
I have added screenshots, I am making this as a personal project for a school project on the Art Academy and am really eager to learn to master this Grasshopper a bit more.
Before trying to do it this way, I tried to do it with Sweep1 Rail, but could not get the orientation along the segment, and also I didn't manage to find out how to limit the Sweep1 Rail to a certain distance (like 30mm for example).
I had imagined this should be done by projecting a second line of 30mm from a segment outer end inwards from both sides and using this second 30mm long line to put the Sweep 1 Rail on. Then I could close the ends, do a Union, Merge all Faces and be done.
However, I couldn't figure it out and the method I'm trying to solve now has gotten me further down the line of the process.
The next step in my process will be to be able to generate a structure on a point of a curve where I can project a certain shape on. Then I want to export this collection of shapes as an STL and 3D-print them. (I have built 2 3D-printer all by myself).
The parts are connectors to connect cheap aluminium extrusions together with minimal effort so I can start prototyping a shape for a small carriage I am designing.
If my explanation is unclear, please tell me, I am new to this, and my mother-language is Dutch, so mathematical terms are a bit difficult for me to understand, but please do use diffcult terms in an explanation where needed. I can only learn :)
Hi from a very happy new user of Grasshopper!
…
controlled by the brightness of the image and size of the diagrid panel is controlled by lunchbox). The frame surrounding each window is then extruded to shade the window within. The extrusion distance for the diamonds' 4 points are controlled by 4 sliders (one for each point).
My goal is to find the total radiation of the windows using Ladybug (or DIVA) and then use Galapagos to adjust the frame extrusions to optimize them to best shade the windows. However, in order to obtain an effective pattern for shading, I need to be able to move the 4 control points independently for each panel... So instead of adjusting all of the panels at once, I need to control each panel extrusion on its own.
First off, I'm not sure how to control each panel independently. Secondly, I'm afraid this will result in far too many sliders for Galapagos to handle (especially once it's applied to the scale of a facade). I tried using a random number generator for each point (which kept the slider count to only 4), but Galapagos was unable to identify any trends in this method (because it was entirely random) and thus could not optimize the extrusions. I think the most probable solution may be to limit the quantity of possible outcomes by making an index of pre-baked shapes (let's say 10 different frame types). Then, setting up a script that allows Galapagos to "plug-in" each different frame, at each different panel on a facade until it finds the ideal pattern. I'm not sure how to go about doing this either... specifically in a non-random way that will allow Galapagos to identify trends. Maybe by using hoopsnake?
I've attached my grasshopper definition. Any suggestions would be greatly appreciated!
…
Added by Caleb Wild at 12:20pm on February 14, 2015