@misc{reichinger_kinect_2011,

title = {Kinect {Pattern} {Uncovered}},

author={A. Reichinger},

url = {https://azttm.wordpress.com/2011/04/03/kinect-pattern-uncovered/},

urldate = {2017-07-09},

journal = {azt.tm’s Blog},

day = 3,

month = apr,

year = {2011}

} ]]>

Please cite it along the way others did. I’d suggest it should contain:

Andreas Reichinger, “Kinect Pattern Uncovered”, online, 3. April 2011, https://azttm.wordpress.com/2011/04/03/kinect-pattern-uncovered/

Please come back and post a link to your thesis!

Thanks for your interest. All the best for your thesis. ]]>

Thus I would say, the 211×165 subpattern had been designed in the following way:

Take a 35×55 matrix of 3×3 blocks, set randomly exactly one pixel per block such that the following constraints are met:

1. no two set pixels of adjacent blocks are horizontal, vertical or diagonal neighbours

2. Every 9×9 pixel configuration is unique and its 180 degree rotated version is also unique (since this is used for the right half of the 211×165 subpattern).

Note, that there are enough possibilities for ensuring these constraints.

Then rotate the pattern and use these two patterns to fill the left and the right half of the 211×165 subpattern.

Finally, fill the center column of the subpattern (since it is 211×165 and not 210×165) with pixels such that the constraints 1 and 2 are fulfilled for the whole subpattern

Thus, the generated pattern is an incomplete DeBruijn-Torus with window size 3×3, an alphabet size 9 and some further constraints.

]]>Of course it depends on the printer you plan to use. I used a uPrint Plus, so I was able to use the definition for a Fortus 200mc (if I am remembering correctly) since they share the same build envelope dimensions. If you don’t match the build envelope definition, you’ll get errors with the coordinates falling outside of the bounding box. What are you trying to do?

]]>