Admittedly, I could change the “Deconstruct Matrix” component to output a full 3D matrix for cases like this but it will increase the runtime and I am not sure that a 3D matrix is really desirable here as it will mean that certain operations with the data will not be do-able (like writing the data to a CSV).
So, before I consider making any changes to the behavior of the component, what do you think about the following possible solutions:
- If you are only going to have a small number of surfaces (like the 2 surfaces you have here), you could just explode the tree of matrices (you have one matrix for each surface) and pass each through their own “deconstruct matrix” component:
- If you really want to have a single data tree representing the 3D matrix, you could partition the output of the “deconstruct matrix” component using the length of the list of sun vectors:
You can even use the native Grasshopper Path Mapper component to put the index of the surface first in the path before the index of the point:
LBT1.0_SunIsVisible_Forum_CWM.gh (64.2 KB)
Are either of these alternative solutions going to be suitable for your case here?