Talk:Wave function collapse: Difference between revisions

m
m (Thundergnat moved page Talk:Wave Function Collapse to Talk:Wave function collapse: capitalization policy)
 
Line 18:
: And/or, instead of scanning the full list of unassigned grid locations, we could instead maintain a list of unassigned grid locations for each level of entropy. For the current task example, this would be four lists, corresponding to entropy 2, 3, 4 or 5. Here, we would want data structure support locating a list entry from a grid location, and vice versa, and it would be convenient to also be tracking the length of each list. But the extra storage and data movement weight per-item would tend to be countered by the need to inspect fewer grid locations in each iteration (adding a tile to the grid would change entropy for at most four grid locations).
 
: There's probably other possibilities (some which might have better performance on large examples due to memory cache structures). That said... for rosettacode, it's probably best to ignore optimizations which have introduce high code complexity. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 13:26, 12 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)
6,951

edits