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
…
use an attractor curve to adjust curves that are being lofted to create a "wavey" surface. I've attached a picture to show the end result. Right now i create all the curves and then loft them together to create a surface which could then have a rib definition applied to it, and it works, my problem is that this project is for a 80' section of wall with ribs that would be a few inches apart, so that is a ton of curves i have to change everytime i want to adjust the overall shape. So is it possible to have an attractor curve that instead of adjusting the spacing of shapes in plane with the curve, would create high points or low points perpendicular to the curve? Hopefully that makes some sense, i'm having trouble finding the words to explain it, the attached pictures should help.
Any advice on how to do this would be great. I hate being that guy but this project came up last minute and it seemed like something the Grasshopper help save a ton of time in as far as adjustments go.
Thanks,
Kyle
…
h kangaroo and have found one project that illustrates my idea exactly...
https://vimeo.com/88002087
So far my best attempt has been to use a gridded surface in which the lines of the grid are springs, with a rest length at 80% of their initial length. (call this grid A) This is to simulate as if the material has been stretched 120% of its resting dimensions.
I have been trying to anchor the springs to a secondary grid (Grid B, curves that will be deposited onto the material) at the points of intersection with grid A.
I am not sure if this is the best approach, maybe soapfilm would be better? although i require the boundary (grid B) to adapt also...
Any advice or attempts to explain how Taichi Kuma has done this in his video would be greatly appreciated.
Thanks…
A: Who created it? / Copyright?
B: Anyone have a larger resolution copy of this image (or a vector so I can do a large resize).
Long and short - I'm an artist and I'd like to make a quilt out of that image. I need a decent resolution copy of it so I can do a huge resize and get a 76" x 80" crop out of it. I've tried resizing it in Photoshop, but by the time it's large enough, the quality has dropped below what is usable for my needs.
Thanks in advance! I totally understand I'm relying on the kindness of strangers here. (Also if this is inappropriate to post - please delete. Thank you)
Michael…
e some questions.
I want to loop with a foreach loop trough a list of points do i have to make a list before or is it possible to use them coming in from a noed i set the access to list?
Also i dont understand why no plane is created. How do i need to feed the points in?
And why is c# expecting open parens in line 88 and 86?
Hope its not to much at once, probably i should try a few less steps to get the problems solved one by one, just hoped it would be easier and sometimes just a parentesis is missing or some format stuff, so maybe it is not so much i really cant say.
If anybody has the time and feels he wants to help it would be nice on the other hand i understand cause of the amount of chaotic questions.
Regards!…
milar once its default data managment techniques are exceeded thus forcing a new address index to be inserted. Its all just so unnecessarily particular and finickity.
If addresses are added when forced to, why not just have that as the default behaviour in the first place? Its not so much 'one size fits all' as postulated previously, but more one size fits 80% of cases and in the remaining 20% of cases you're going to be a slave to your definition as constant manual management will be required just to control the thing.
My final point:
circle with points should have a list address of {0}
multiple circles with points should have list address of {0;0}
multiple circles in multiple locations with points should have list address of {0;0;0} etc
I really dont see how that is any less consistent for highly complex data strucutres. To any rational individual this is predicable and follows a logic. What advantage is there in fixing the address at {0;0} yet still allow for new address sequences to be added firther down stream? Logic is the key thing to keep in mind here, not peculiar nuances only the initiated can ever be aware of.…
cle
the 'Shape' is copied to all points
shapes are rotated randomly, plus or minus 'Angle' maximum
'Shape In Brep (ShapeIn)' is used to cull shapes that aren't within the circle
'Fast Loop' begins using 'MCX' (Multiple Curves Intersection)
first shape is added to 'D1' output and shapes intersecting it are culled
results minus first shape are passed to 'D0' of 'FastLoopEnd'
loop repeats until 'D0' list is empty
'D1' results are scaled down slightly (0.75) to leave more space around them
'Explode' results and return only the curved part, ignoring the base line that closes the shape
…
Added by Joseph Oster at 11:01pm on March 17, 2017
avid--this software is a pleasure to use, and David, you have done an amazing job. I also want to acknowledge it takes a lot of work to edit the software, and I understand that it can take a while before any changes are made.
Okay so here are some ideas:
Subcurve - just like subsurface, but based on 1-dimensional intervals
Map Values to Interval - a single component that could take a list of values, an interval, and would scale the list of values to match the input interval.
A Dispatch component that could dispatch according to a list of output indices. Instead of just True/False, you could output things based on a pattern using 0/1/2/3/4, etc. This component would be the inverse of Weave.
A text object parameter and data type, with some basic ways to edit it.
More string manipulation operations, allowing for easy editing with string subintervals, and character counts, and basic text formatting (line return, etc.).
I really really really wish the List Item component had a default index value of "0". That is what I input into it 80% of the time.
That's all for now. If any of these ideas are already adequately addressed, please let me know. Thanks.
…