blinds be (B1,B2..B5). Then the geometry for the five iterations will be ((A+B1), (A+B2)...(A+B5)).
And assume that you are measuring illuminance at four points inside the room (x1,x2,x3,x4) and one point outside the room(y1).
The way Daysim works ( and should work as per the best of my understanding) is that for each setting of the blind (ie. B1,B2,..B5), a separate value of (x1,x2,x3,x4) gets calculated through the Daylight Coefficient Method. So let's say you have illuminance thresholds of (p,q,r,s,t) corresponding to (B1,B2,..B5). What the shade-control algorithm does is that it compares the illuminance at y1 with your threshold of (p,q,..t) and then chooses a value of (x1,x,2,x3,x4) on basis of that. So, when we repeat this process for (365x24=)8760 hours , we end up with a value of a shade setting for each hour which was set on basis of your threshold illuminance values.
I would have gladly answered your question on HB itself, however, I usually work with Daysim directly through commandline.
(BTW, if you are interested in reading more about Daysim google Christoph Reinhart's dissertation on the subject, along with some papers by Zack Rogers).…
nts but as there are polylines and surfaces in it, they are conflicting as the geometries are overlapping and intersecting.
The input for the model is a centre point and four connecting points: we can call them CNT, A, B, C and D. The model works for these points - it's quite complicated with lots of polylines, vector geometry, surfaces, rotations, etc. - but it still works and has an output of two breps.
If I had a compilation of N sets of CNT, A, B, C and D's, is there a way of feeding each of these into the grasshopper in individual sets rather than just plugging in the huge set of numbers - e.g. feeding in CNT1, A1, B1, C1 and D1 and getting a result before moving on to CNT2, A2, B2, C2 and D2?
I've tried looking through tree structures, but it seems to be failing when the size of the set isn't known - e.g. how to extract all the information from trees when N isn't know using list item (i=0, i=1, i=2..., i=N).
I hope I've managed to explain the problem adequately, I can make up an easier to understand Grasshopper model later if I haven't explained well...
Thanks in advance for any comments, pointers, etc.…
raw a single line that intersects them all. I'm also not certain what the metric for "closest" would be if you have more than three lines all intersecting each other. What groups of three can you find here:
This is not just splitting hairs, when designing a new algorithm it is important to always figure out whether:
There is ever a case with more than one possible solution.
There is ever a case with no possible solutions.
Does the algorithm change the state of the problem while it runs, i.e. whether run order matters.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
basis" problem ... all of a sudden - quite recently - a girl posted the MITESIGF (Most Important Thread Even Seen In Grasshopper Forums). She doesn't even realized that: she's novice:
http://www.grasshopper3d.com/forum/topics/array-1
4. Why this MITESIGF is MITESIGF? For 2 reasons:
4.a: Wooden pairs (Beams) Profile Curves (belonging in some tree) MUST allow individual control on a per "item basis" (OK, that's obvious) - see Images posted in the thread. No attractor (or any other "global" policy) can cut the mustard here (to tell you the truth this happens in 99% of pure engineering cases, but they appear very rarely in GH Forums - if at all, mind). If the profile curves are defined with 5 points (or 9 for the double thing) we need "on-the-fly" control over this Array (like the radii in your Sphere Manipulator) :
4.b: Critical Bottom-to-Top issues arise: Create a "global" topology (call it "parent") - the beams - and then place real-life "components" (call them "childs") that affect (most probably) the "parent". OK, that's impossible to do with GH/Rhino (peace of cake with CATIA/Microstation) but you can "approximate" things up to a point. Alternatively: you can "trigger" some interest from GH/Rhino developers if they have any AEC market(s) in mind.
Topic 4.a requires the master-to-slave slider thingy (iterate over branches (index slider:master) > reset the 5 values (value slider:slave) > modify them on the fly > save > increase/decrease branch > ...).
Other than that my definitions are far more challenging than this simple case ... but ... anyway ... long is the path (and hilly).
more soon.
best, The Troll
…