use for some typical reasons why solar access can be important:
Solar Access for Passive Solar Heating - The conditional statement should request sun vectors for any hours below the balance point of the building (the temperature at which the building starts requiring additional heating). For residences, this can be as high as 18C and for commercial/retail buildings with high internal heat gains, this can be as low as 10C. 16C is around what you might find for some residences with better insulation and is probably the reason why that is chosen in the file.
Solar Access for Outdoor Thermal Comfort - The conditional statement should request sun vectors for any hours below the lower limit of outdoor comfort (UTCI uses 9C for this lower limit).
Solar Access for Health of Plants/Trees in a Park/Garden - This is a bit of the opposite of the other metrics since you want hours of the warmer season. In this case, I usually use solar radiation as the annualHourlyData with the conditional statement and I request hours that are above a certain radiation level (where the plants are benefiting the most). I then use an analysisPeriod to get rid of any months of the year when the trees don't have leaves on them.
Hope this helps,
-Chris…
remain the same.
Although Grasshopper is a powerful tool designed to allow non-coders access to programming-like capabilities, being able to programm allows for new possibilities along with added power and flexibility. Combine the power of Code with the accessibility of Grasshopper and the possibilites for exploration become even greater. Grasshopper|DotNet scripting training focuses specifically on the scripting capabilities and challenges of using Rhino’s DotNET SDK, as well as the DotNET framework within Grasshopper. Trainees will be given the tools to understand how to approach coding with Rhino’s DotNET SDK and perform a variety of tasks which will be the building blocks for Grasshopper scripts.
Topics for the training will include the general structure of the Rhino DotNET SDK, Object Oriented Programming, the Grasshopper scripting environment, data trees, as well as creating, manipulating, and evaluating points, curves, surfaces, and B-Reps.
The training is aimed at people with some experience writing code who are looking to try and begin scripting within Grasshopper. Although the course does presume some previous coding experience, it does not assume a specific language or application, and syntax issues will be covered.
Training will be given in VB.NET, although training material will have both VB.NET and C# examples. Trainees interested in coding in C# are encouraged to register.
Trainees are required to bring their own laptops with Rhino and Grasshopper installed. Installing Visual Studio Express is recommended. Arrangements can be made for Trainees without laptops at an additional cost. Space is limited to 10 trainees.
More Info…
e intention of the workshop is to create a light structure that can support your own weight with the condition of using only one sheet of plywood. The workshop is addressed to architects, interior designers and designers.
The first part of the course, students will learn Rhinoceros 4.0 and RhinoCAM while they learn how to design inside Rhino. Students will take basic training in Rhino (and an overview of Grasshopper) and basic training in RhinoCAM. All the design process will be guided and assisted by the tutors.
The second part of the course will be completely practical, we will fabricate all the designs using a CNC Milling Machine. The students will learn how to program the machine and all machine-related stuff needed to get things done.
More info can be found on Medio Design Website…
n excuse. Participants will design their own texture and will mill it according to their own intuitions on how to represent that geometry. The workshop is addressed to architects, interior designers and designers.
During the first day, students will design with digital tools (and parametrical tools if they have basic knowledge) a set of interesting (kind of) textures. Later on, paricipants will learn how to program machine toolpaths in 3D, using the three axis simultaneously . All the design process will be guided by the tutors.
The second day is going to be a bit more practical, we are going to fabricate the selected textures using a CNC Milling Machine. The files we are going to use for machining will be the ones that students had been working on the day before.
More info can be found on: Medio Design Website…
ceros. Parametrización, panelización y análisis en Grasshopper, así como el proceso de manufactura digital para maquinaria de corte Láser y CNC.
UN solo pago anticipado $4,000.00
Pagos diferidos $4,500.00*
*reserva tu lugar con el 50%
Martes y Jueves de 7 a 10 PM
Del 15 de Mayo al 14 de junio
DURACION: 30 HORAS
SESIONES: 10 DE 3 HORAS
o info@dimensiontallerdigital.com
informes al 55 (50 16 0634) con Mayri Gallegos (o al cel. 55 28 85 24 73)
$4,000.00…
ete" AEC things ... the others could be several steps ahead either by virtue or by momentum.
But Hannes (and others - the pissed-off ones, he he) misunderstood my intentions: I'm not here to measure our ego(s), our @$@% nor to dispute/debate for the obvious. I'm not here for the money (that could be ridiculous) the glory (preposterous), or to perform some cheapo show-off (what for?).
I'm here in case that people can distinguish (and are willing to talk and suggest ways/methods/you name it) the difference between up hauling a windsurf sail and attempting a single forward (that's a loop, he he - the double one is another animal).
By that I mean: ways/methods/whatever that could yield a GH/R combo that could seriously be part of the System as above.
Forget geodomes ... get this (reduced by 95%, every 5th floor combo is shown) and think: what we can do for that matter?
best, Peter …
he new ones start like this:
Imports RhinoImports Rhino.GeometryImports Rhino.Collections
So when I try to run my old code:
Dim vertexList As New List(Of On3dPoint) Dim ribList As New list(Of OnLine) Dim spineList As New list(Of OnLine)
I get these errors:
Error: Type 'On3dPoint' is not defined. (line 93)Error: Type 'OnLine' is not defined. (line 94)Error: Type 'OnLine' is not defined. (line 95)
So this is probably a really easy question. Can I still use the OpenNURBS library or do I need to rewrite using Rhino.Geometry? If so, where is best reference for that?…
Added by Chris Wilkins at 3:32pm on October 15, 2012
ther math and logic. i can usually conceptualise what i want to do and cobble some semi working thing together but don't know which components to use and how to patch it. so i'm super happy to have someone who knows what he's doing to find this interesting.
and i'm glad you mention the fanned frets again, there is one input parameter that's still missing for the multiscale frets to be fully parametric, it's the angle of the nut or which fret should be straight. it depends a bit on personal preferences and playing posture what is more comfortable. so being able to adjust this easily would be cool. again i have no idea how the maths for that work or if you can just rotate each fret the same amount around it's middle point. The input either as fret number (for the straight fret) or as a simple slider from bridge to nut should do as input setting.
Here are the two extremes and the middle ground:
i've been thinkin today while analysing your patches and cleaning up my mess what exactly the monster should do.
Here are the input parameters needed, i think it's the complete list
scale length low E string
scale length high e string
fret angle/straight fret
string width at nut
string width at bridge
number of frets
fretboard overhang at nut (distance from string to fretboard bounds)
fretboard overhang at last fret
string gauges
string tensions
fretboard radius at nut (for compound radius fretboard radius at bridge is calculated with the stewmac formula)
fretwire crown width
fretwire crown height
action height at nut (distance between bottom of string and fretwire crown top)
action height at last fret
pickup 1 neck position
pickup 2 middle position
pickup 3 bridge position
nut width
the pickup positions should be used to draw circles for the magnet poles on each string so they are perfectly aligned and can be used for the pickup flatwork construction. ideally they would need a rotation control aligning the center line of the pickup so it's somewher between the last fret angle and bridge angle. personally i do this visually depending on the design i'm looking for, some people have huge theories on pickup positioning but personally i don't believe in it.
that should result in everything needed to quickly generate all the necessary construction curves or geometry for nut/fingerboard/frets/pickups. this is the core of what makes a guitar work, the more precise this dynamic system is the better the guitar plays and sounds.
i posted another thread trying to understand how i could use datasets form spreadsheets,databse, csv to organize the input parameters. What would make sense for the strings for example is hook into a spreadsheet with the different string sets, i attached one for the d'Addario NYXL string line which basically covers all combos that make sense.
The string tension is an interesting one, and implmenting it would sure be overkill albeit super interesting to try. it should be possible to extrapolate from the scale length of each string what the tension for a given string gauge of that string would be so that you could say 'i want a fully balanced set' or 'heavy top light bottom) and it would calculate which SKU from d'addario would best match the required tension. All the strings listed in the spreadsheet are available as single strings to buy.
i'm trying to reorganize everything which helps me understand it. i just discovered the 'hidden wires' feature which is great since once i understood what a certain block does or have finished one of my own, i can get the wires out of the way to carry on undistracted. a bit risky to hide so many wires but it makes it so much easier not to get completely lost :-)
btw, the 'fanned fret' term is trademarked, some guy tried to patent it in the 80's which is a bit silly since it has been done for centuries. there is a level of sophistication above this as well, check out http://www.truetemperament.com/ and that really is something else. it really is astounding how superior the tuning is on those wigglefrets, the problem is that it's rather awkward for string bending and also you can't easily recrown or level the frets when they are used. …
e matching with a dedicated component which creates combinations of items. You can find the [Cross Reference] component in the Sets.List panel.
When Grasshopper iterates over lists of items, it will match the first item in list A with the first item in list B. Then the second item in list A with the second item in list B and so on and so forth. Sometimes however you want all items in list A to combine with all items in list B, the [Cross Reference] component allows you to do this.
Here we have two input lists {A,B,C} and {X,Y,Z}. Normally Grasshopper would iterate over these lists and only consider the combinations {A,X}, {B,Y} and {C,Z}. There are however six more combinations that are not typically considered, to wit: {A,Y}, {A,Z}, {B,X}, {B,Z}, {C,X} and {C,Y}. As you can see the output of the [Cross Reference] component is such that all nine permutations are indeed present.
We can denote the behaviour of data cross referencing using a table. The rows represent the first list of items, the columns the second. If we create all possible permutations, the table will have a dot in every single cell, as every cell represents a unique combination of two source list indices:
Sometimes however you don't want all possible permutations. Sometimes you wish to exclude certain areas because they would result in meaningless or invalid computations. A common exclusion principle is to ignore all cells that are on the diagonal of the table. The image above shows a 'holistic' matching, whereas the 'diagonal' option (available from the [Cross Reference] component menu) has gaps for {0,0}, {1,1}, {2,2} and {3,3}:
If we apply this to our {A,B,C}, {X,Y,Z} example, we should expect to not see the combinations for {A,X}, {B,Y} and {C,Z}:
The rule that is applied to 'diagonal' matching is: "Skip all permutations where all items have the same list index". 'Coincident' matching is the same as 'diagonal' matching in the case of two input lists which is why I won't show an example of it here (since we are only dealing with 2-list examples), but the rule is subtly different: "Skip all permutations where any two items have the same list index".
The four remaining matching algorithms are all variations on the same theme. 'Lower triangle' matching applies the rule: "Skip all permutations where the index of an item is less than the index of the item in the next list", resulting in an empty triangle but with items on the diagonal.
'Lower triangle (strict)' matching goes one step further and also eliminates the items on the diagonal:
'Upper Triangle' and 'Upper Triangle (strict)' are mirror images of the previous two algorithms, resulting in empty triangles on the other side of the diagonal line:
…
go As New MRhinoGetObject()
go.SetCommandPrompt("Sélectionnez les deux arrêtes sur les pièces à serrer pour placer la Boulonnerie...")
go.SetGeometryFilter(IRhinoGetObject.GEOMETRY_TYPE_FILTER.edge_object)
go.AcceptNothing()
go.GetObjects(2, 2)
If (go.CommandResult() <> IRhinoCommand.result.success) Then
C1 = go.CommandResult()
End If
Dim object_ref1 As MRhinoObjRef = go.Object(0)
Dim obj1 As IRhinoObject = object_ref1.Object()
Dim curve1 As OnCurve = object_ref1.Curve()
Dim object_ref2 As MRhinoObjRef = go.Object(1)
Dim obj2 As IRhinoObject = object_ref2.Object()
Dim curve2 As OnCurve = object_ref2.Curve()
C1 = curve1.NurbsCurve
C2 = curve2.NurbsCurve…