e, this definition just measures the angle between the current angle and the previous one. Then it uses mass addition (the list of partial results) to give the current angle. So each angle is just the sum of all the angles before it. This allows them to go above 360 degrees (or below -360 degrees).
The method I use to tell whether or not an angle is negative is by using a plane input for the angle component. Without it, an angle at -30 degrees from 0 and an angle at +30 degrees from 0 will look the same (it will say 30 degrees). So with this plane input, instead of having +30 and -30 = 30, you get +30 = 30 and -30 = 330. So you can stipulate that any angle over 180 degrees is negative (I guess this is not always absolutely the case, but I wont go into that as it should work fine for you).
I don't think I explained that very well as it's late and I'm overdue for some sleep - but hopefully it will help.
P.S. the numbers in the screenshot are kind of jumbled, but the small numbers are the angle values of the current angle minus the previous one, and the large numbers are the sums of each previous angle.
-Brian
…
lconcepts in parametric design and exercises using Rhino, Grasshopper, andPython. Each of the 3 workshops corresponds to learning different software skillsthe softwares and applying those skills to a creative design challenge.…
trying to do.
i have a spiral that i divided in grasshopper into 360 points, that bit i managed to do, what i want is to connect point 1 to point 2 with a line, then connect point 1 to point 3 with a line and so on till point 1 is connected to all the other 359 points in that order, once i have done that i want to then connect point 2 to point 3 and so on, i want to repeat this till i have a connection all the way down the spiral, i'm pretty sure that once the first set of points are dealt with then it should be fairly easy to replicate the procedure to do the other point connections.
Michael…
one another by 1 value (255,0,0) and (255,0,1) so thats practically the same color.
Maybe input a minimal variation of 30 units?
Btw shouldnt hue go form 0 to 360? The component seems to just go to 255.…
ts of spheres, that are behind the camera, appear. This normally happens with weird lens length settings. The camera needs a 45° viewing angle and therefore might fall into this category. Maybe there is a good solution to get rid of this issue?
Issue #2: I have no clue how to run the screenshot calculation at the end of the solution. Normally I wanted to color the spheres in the video with the "Custom Preview" component, but they would not show up in the saved picture, since custom preview was calculated later than the screenshot component "Cubemap"
Issue #3: The calculation of an equirectangular image takes quite a while. ~4 seconds. Thats still good compared to the 9 seconds i had in the beginning. Multithreading through parallelizing could improve it even more, but it wouldn't work for me.
Especially ISSUE #2 is annoying and does not allow me to create a nice video. I would be glad if someone could assist me in this.
I actually tried already ExpirePreview or Solution, but maybe I used it the wrong way...
Best,
Martin…