Talk:Wave function collapse: Difference between revisions
Content added Content deleted
m (→Vote for deletion: rescinded my vote, all too late now anyway...) |
|||
| Line 21: | Line 21: | ||
:One thing (which may stem from all the original stuff) I just don't get is why the task description has to redefine "Tiled" to mean "Overlapped[-by-one-matching-pixel]". It turned out very helpful to display things non-overlapping and hence in my mind they should co-exist. All the references are about making tiles from an image, and it should probably be clearer that's not done here, and/or stress those links are ''many times'' more complicated than this task requires. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 00:32, 15 July 2022 (UTC) |
:One thing (which may stem from all the original stuff) I just don't get is why the task description has to redefine "Tiled" to mean "Overlapped[-by-one-matching-pixel]". It turned out very helpful to display things non-overlapping and hence in my mind they should co-exist. All the references are about making tiles from an image, and it should probably be clearer that's not done here, and/or stress those links are ''many times'' more complicated than this task requires. --[[User:Petelomax|Pete Lomax]] ([[User talk:Petelomax|talk]]) 00:32, 15 July 2022 (UTC) |
||
:: I believe that that "one pixel overlap" constraint is necessary to satisfy ''(C1) The output should contain only those NxN patterns of pixels that are present in the input'' from https://github.com/mxgmn/WaveFunctionCollapse |
|||
:: If the tiles do not overlap, we are introducing a new bit pattern where the the edges lie side-by-side and thus some rows/columns would be duplicated where that never would have occurred in the original. |
|||
:: Though, granted, this assumes that there was an original. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 05:26, 15 July 2022 (UTC) |
|||
== Vote for deletion == |
== Vote for deletion == |
||