This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Discuss a wide range of topics! Questions about the Alteryx Platform should be directed to the appropriate Product discussion forum.
General Discussions has some can't miss conversations going on right now! From conversations about automation to sharing your favorite Alteryx memes, there's something for everyone. Make it part of your community routine!
Three performance tips for me. 1) filter out "." values you don't need them. 2) Generate only your collisions, this follows from 1) 3) shift your plane to stay within byte data types.
Part 2 macro. This has 1 more generate rows than my part 1 macro for the extra w dimension. This could have its condition toggled and folded back into one macro.
My macro has a toggle for the number of iterations as I expected us to have to run 100 iterations in part 2 or something, I didn't need the toggle in the end and could have hard coded "6 iterations but I left it in anyway and made for a nice gif in the post below.
My macro steps. 1) Filter out "." from the initial data. This could in fact be done outside the macro as its not used after step 1. 2) generate collisions in each dimension, tripling rows at each step, looking at -1,self,+1. 3) tag the centre self collision. 4) keep only cubes with 2 or 3 collisions. 5) join back on against self colliders. 6) filter to only active cubes for next iteration. 7) repeat.