ere are ways to remap the data (PathMapper etc) and there's an excellent tutorial by David Rutten about path mapper on this forum somewhere.
And always look at whether you simply need to flatten your data to ba able to work with it.
For point lists I often use the PointNumber component to help visualise the data and the good old Panel component helps too!
When you see some of the elegant, compact definitions on here, there often seems to be some mystical foresight needed right from the first component but hopefully this jedi skill comes with practice!…
Added by martyn hogg at 12:24pm on January 13, 2014
"Z" elevation and get their heights.
As this will be used by people in my office, the letter tagging vs numbered indices might get confusing.
I can't really leave them as numbers as the points are separated into various groups, ie. Pt Aa, Ab, Ac...
Pt Ba, Bb. Bc... and so forth.
With that being said, is it possible to rename indices and/or paths to strings other than their default numbering?…
o be less from a tool-centric perspective, and more often geared toward general platforms (like BIM, or "computational" design).
For papers, I would search Cumincad first, as it captures a great deal of history as well as more current research from the proceedings of the eCAADe and ACADIA family of conferences. There are thousands of articles there.
Robert Woodbury's "Elements of Parametric Design" is considered pretty foundational. Sean Ahlquist and Achim Menges also put together a good anthology a few years back called "Computational Design Thinking" that collects several texts that are in line with the ICD's interests in biomimesis and emergence. "Inside Smartgeometry" is a good combination of theory, historical reflection, and state-of-the-art and edited by Brady and Terri Peters.
But really there is so much out there! One of my favorite short papers is Tom Maver's "CAAD's Seven Deadly Sins" which was basically a keynote mic-drop at the 1995 CAAD Futures conference. I'll spoil the end for you:
"7 Failure to criticise: Above all we have failed to exercise our critical faculties in relation to almost all of the research and development carried out by ourselves and by our peers in recent years. There has been a cosy conspiracy in the community to condone, even encourage, selfindulgent speculation and solipsism - a thoroughly bad example to set for young people in the academic community.
Conclusion: Perhaps these criticism are unjustly hard. Hopefully CAAD Futures 95 will prove me wrong or at least provide the opportunity for discussion."
…
Added by David Stasiuk at 11:10am on August 25, 2015
tween them)
However its not possible (Well its very tricky) for me to go back to the original geometry and merge the perimeter and the core into one zone.
As a result I thought that adding internal glazing would do the trick. However apart from using the addGlazing component I couldn't see any other way of adding internal glazing to the core zone without exploding it and putting it back together. So I modified the Glazing based on Ratio component so that the internal walls of the core would automatically be 95% glazing.
After passing the core zone through the modified Glazing based on Ratio component and then passing all the HB zones through the Solve Adjacency component I ran the daylight simulation. However the result is not what you would expect it appears as though there are no internal windows. (See the picture).
So two questions.
1. Is there a better way to merge these zones for a daylight study without going back to the original geometry?
2. From the illuminance map it appears that no light is passing through the internal windows. Why is this the case? Should I create a material that is like air so that the light can effectively pass through and then use this material instead?
…
ple I have to drag it through a panel before I can use it as an input to my python script. The supports comes as a list of strings (see figure) and I want to extract some of that information (e.g. what nodes are fixed) and write that to my txt file.
I extract the info with these lines:
for row in Support: node = row[8:row.find(' DOF')] file.write(" %s,\n" % node)
print node
>> 95
If I however don't drag it via a panel i get the following output:
for row in Support: node = row[8:row.find(' DOF')] file.write(" %s,\n" % node)
print node
>> Supports.Suppor
It's like the script doesn't get that each row is a string.
I have the input set to "list access" and type hint to "str" and I've tried to simplifying and flatten the list.
Greatful for help…
obably only using Rhino4, but three people who bought Rhino2, Rhino3 and Rhino4 respectively are three people using one version each.
We certainly don't know how many Grasshopper users there are. Grasshopper installers are not always downloaded via our website or -once downloaded- used multiple times (think class-rooms and company IT). We have no way of knowing whether someone who once downloaded Grasshopper is still using it. That being said, Grasshopper is downloaded ~100 times a day from our website and this number has been fairly constant since 2009 (though slightly on the increase, I'd say ~80 a day in early 2009). There are nearly 96,000 unique email addresses in the Grasshopper mailing list, more than 455,000 in the Rhino4 mailing list.
The size of this community (>17,000 registered users) is a much better indicator of user-base magnitude, but even here we have no idea how many people registered but are now no longer using GH as we do not collect use statistics (yet).
--
David Rutten
david@mcneel.com
Poprad, Slovakia
…
What I figured yesterday is that the increase in radiation because of the reflective facade for the 'worst' month is only about 2-3 kWh/m2 as your looking at a value of 80 without and 82-83 kWh/m2 with reflection.
So my assumption is that the glare factor will play a much bigger role instead of intensity of the sun, looking at comfortable levels. So I'm looking in this as well. It's very cool to play around with these plugins and see the outcome. I'll keep you guys posted.
@ Claudio, that was exactly my problem as well. I presented a direct sunlight hour analysis, to show the increase in direct sunlight hours because of the mirrored facade and at what times of the day the reflections occurred. But it is hard to asses if this is 'bad' or 'good'. The restaurant in question receives more or less 130 direct sunlight hours 'naturally' in the worst month and because of the reflection the result was 161 direct sunlight hours, but the client was like okay..... and is this a problem? So we decided to look at sun intensity but I didn't want to fall into the trap of in the end presenting kWh/m2 and having the same problem not knowing if this is 'comfortable' or 'annoying' etc. Good luck with your study, I'll post my findings
Thanks again guys…
nitions prior to Karamba are to allow the genes to manipulate the form of the shell and then kangaroo to relax the form to its "equilibrium" state.
The definition, as attached, runs fine over one iteration. However, when I run the Galapagos solver, rhino slowly uses up my computers memory and then ultimately crashes (around 80 Galapagos iterations). I don't think that the surface patch, or kangaroo are the issue, as I have run other iterative definitions through them without issue.
I believe Karamba may be occupying memory each iteration that is not released when a new iteration begins. This problem is exasperated by the fact that I am running 11 load cases, 9 of which are point loads defined over each vertex of the mesh. I ran a definition with only one load case, and it reached 170 generations (with a population of 50 for each generation). However, at this point it had occupied 90% of my computer's available memory.
Do you know of a way to ensure that Karamba purges its memory after an iteration, or is this a possible memory leak bug?
Thanks again, any help you can provide is much appreciated.
Sean
…
.
I think i'm about 80% there. It may not be the most elegant procedure, but it appears to be working. I am having some slight problems.
1. I'm having trouble extracting the edge curve on one side of my mesh
a. I used a mesh plane intersection to trim my site mesh, and the resultant curve extends beyond the limit of my mesh
b. I identified the intersection point, but GH is not shattering on that intersection point. instead it happens at a point further down the polyline
2. I'm can't join my curves. If i bake them, they join into a closed curve.... GH join curves is not behaving. i've had some success joining two segments, but i can seem to get all 4 side wall curves to join.
if anybody could offer some advice, i'd be very appreciative. also, i'd like some recommendations for ways to streamline this definition. I'm sure that there are more creative ways to manage this data, and i'd love to about them. thanks - CSDG
…