Boxes intersection and adjacent count

Replies to This Discussion

Permalink Reply by Abdulaziz Afandi on August 4, 2017 at 4:34am

I tried to work with cluster that you made you used include as an input and the output was a vector.

Why you made it as a cluster?

and why when I open it it dose not have include it has exclude only?

Thank you for your help

Permalink Reply by Julian Buhagiar on August 4, 2017 at 5:16am

Sorry for the confusion...that label might be a relic from when the logic was the opposite way around in an earlier solution.
Originally it was exclude items rather than include, just ignore this label, it is include.

Permalink Reply by Julian Buhagiar on August 4, 2017 at 5:28am

To cut a long story short I was originally thinking to exclude self because you don't want to count yourself. I then realised its better to classify all other possibilities and make it inclusive with a checklist.... You could of course create other classifications such as above, below, behind, in front, 2 away, 3 away etc

Permalink Reply by Julian Buhagiar on July 31, 2017 at 11:54am

I meant to put this control on the outside of the cluster.

Attachments:

• Boxesforadjacentandintersectioncounttestversion3.gh, 48 KB

Permalink Reply by Joseph Oster on July 31, 2017 at 12:52pm

Nicely done!  But... but... his original boxes were overlapped horizontally and/or vertically, eh?  Didn't make much sense so I gave up quickly, but was thinking along similar lines - as you say in your code:

you can tell whether its adjacent to another by the indices rather than doing any geometric functions which is always more processor intense.

Permalink Reply by Abdulaziz Afandi on August 4, 2017 at 3:38am

Sorry, I am still learning and I did not know that I have to divide the dimension by 2. That is why I made version 2 of the file.

I have to learn more I am really excited to learn more. any suggestion ... Reading, videos that explain the idea of indices in GH.

Thank you

Permalink Reply by Julian Buhagiar on August 4, 2017 at 5:03am

I put together a storyboard, scratch the surface tutorial on paths here...http://www.grasshopper3d.com/xn/detail/2985220:Comment:1792378

Permalink Reply by Abdulaziz Afandi on August 4, 2017 at 3:26am

But I dont understand how you built the checklist I mean it is my first time to see this node. how it works?

Permalink Reply by Julian Buhagiar on August 4, 2017 at 4:21am

Its on the params input ribbon....drop down component....you can change its type by right click.


Also another tip... Any component you don't know....hold Ctrl + alt and click and hold on the component....it will display arrows to where in the ribbon you'll find it. (Unless its a cluster which won't be in the ribbon and then you'll know to double click it instead)

To build a list, on this component you double click it and make entries in a text panel
Each entry is a new line
Each entry is display name followed by = followed by output value

In this case the output values are a series of : separated vectors which are internally parsed using the split text component.

Permalink Reply by Abdulaziz Afandi on August 4, 2017 at 4:44am

'hold Ctrl + alt and click and hold on the component'  this is very useful

I don't understand "Each entry is display name followed by = followed by output value". And how you pick those values?

Permalink Reply by Julian Buhagiar on August 4, 2017 at 4:50am

OK... If you think of the perspective of a random box, you have potentially 26 boxes adjacent to you in all directions. {0,0,0} is you, and all the others are relative to you.

-1,0,0 is the box next to you in the x direction and 1,0,0 is the other side of you in the x direction, if you do this for all possibilities you end up with the list defined.
All the faces are when there are two 0s in the vector (6 of these exist) all the edges when there is one 0s in the vector (12 exist) and all the corners when there are no 0s in the vector. (8 exist) giving 26 relative position to the centre in total

These relative positions are than applied to the absolute coordinates, (remember we are using paths as a quasi coordinate system.)
If a path is not found it means it doesn't exist and therefore is not adjacent. If one is found it is returned, ...if a path has been found 6 times it will appear in its own list 6 times. So all we need to do is measure the list length at each path

Permalink Reply by Julian Buhagiar on August 4, 2017 at 5:10am

Using paths as a secondary coordinate system is good for this example where the boxes themselves have there own xyz coordinates, but generally its not typically the way paths are used.

There are many ways you can achieve auxiliary coordinate systems, paths is a discrete coordinate system whereas xyz, uvw etc are continuous coordinate systems. Youre project is a regular 3d voxel grid so a discrete coordinate system works well.

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page