See the other thread. By Matrix page, I think you mean the mapping page. Which is NOT where you’d do hsv() anything. It’s purely a real JavaScript (unlike PB) program that either generates an array of coordinates OR is literally an array of coordinates.
If you mean in an actual pattern, yes, that could might work, but it’s what I consider “brittle” requiring someone to add height and width variables that are hard coded. So you put in 12 and 22 and it works for you, but then you share the pattern and someone with a cylinder that is 15x30, it doesn’t work for them, until they adjust the height and width.
Ideally your code shouldn’t require those, and work regardless of the actual dimensions, and thus work on any map, any size, any number of pixels, etc.
But we have “brittle” patterns in the collection now, and I’ve even written some of them, but the goal is to avoid that going forward. The transformation API (which has scaling and rotating) really helps with this too.