Left examples have the keyword "pixelperfect" on the OEBP.

All examples here are "imperfectionscanmatter" (left-BP913) Bongard Problems--that is, subtle imperfections in images are meant to be considered.

When a Problem is tagged with "pixelperfect", users are reminded to make sure they do not upload images such that taking the pixelation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images in these cases. For example, in BPs about tessellation (e.g. BP335) the solution is clearer when the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" are automatically pixelperfect. For example, in BP62, any image that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.

BPs where users are advised to only upload images in which the pixelation is not misleading vs. other "imperfectionscanmatter" Bongard Problems that use pixelated images to closely approximate the actual intended shapes.

BPs where users are advised to only upload pixel-perfect examples vs. other "imperfectionscanmatter" Bongard Problems that can use pixelated images to closely approximate the actual intended shapes.

Left examples have the keyword "pixelperfect" on the OEBP.

All examples here are "imperfectionscanmatter" (left-BP913) Bongard Problems--that is, subtle imperfections in images are meant to be considered.

When a Problem is tagged with "pixelperfect", users are reminded to make sure they do not upload images such that taking the pixellation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images in these cases. For example, in BPs about tessellation (e.g. BP335) the solution is clearer when the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" are automatically pixelperfect. For example, in BP62, any image that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.

Left examples have the keyword "pixelperfect" on the OEBP.

All examples here are "imperfectionsmatter" (left-BP913) Bongard Problems--that is, subtle imperfections in images are meant to be considered.

When a Problem is tagged with "pixelperfect", users are reminded to make sure they do not upload images such that taking the pixellation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images in these cases. For example, in BPs about tessellation (e.g. BP335) the solution is clearer when the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionsmatter" are automatically pixelperfect. For example, in BP62, any image that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.

BPs where users are advised to only upload pixel-perfect examples vs. other "imperfectionsmatter" Bongard Problems that can use pixelated images to closely approximate the actual intended shapes.

All examples here are "imperfectionsmatter" Problems. See BP913 for meaning of "imperfectionsmatter."

Left examples have the keyword "pixelperfect" on the OEBP.

When a Problem is tagged with this keyword, users are reminded to make sure they do not upload any image such that taking the pixellation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); in these Problems, it's natural to make the pixels interlock properly for tessellation.

Typically, imperfectionsmatter Problems tagged with the keyword "continuous" (left-BP963) are automatically pixelperfect. For example, in BP62, any image that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.

BPs where users are advised to only upload pixel-perfect examples vs. other "imperfectionsmatter" Bongard Problems that can use pixelated images to closely approximate the intended shapes.

BPs where users are advised to only upload pixel-perfect examples vs. other "imperfectionsmatter" Bongard Problems that can use pixelated images to closely approximate the actual intended shapes.

All examples here are "literalgeometry" Problems. See BP913 for meaning of "literalgeometry."

Left examples have the keyword "pixelperfect" on the OEBP.

When a Problem is tagged with this keyword, users are reminded to make sure they do not upload any image such that taking the pixellation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); in these Problems, it's natural to make the pixels interlock properly for tessellation.

Typically, literalgeometry Problems tagged with the keyword "continuous" (left-BP963) are automatically pixelperfect. For example, in BP62, any image that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.

All examples here are "literalgeometry" Problems. See BP913 for meaning of "literalgeometry."

Left examples have the keyword "pixelperfect" on the OEBP.

When a Problem is tagged with this keyword, users are reminded to make sure they do not upload any image such that taking the pixellation into account would affect the sorting of that example. The OEBP does not want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); in these Problems, it's natural to make the pixels interlock properly for tessellation.

Typically, literalgeometry Problems tagged with the keyword "continuous" (left-BP963) are automatically pixelperfect. For example, in BP62, any example that is approximately pixel-perfect is automatically actually pixel-perfect; there's no need for users to ever worry about examples in this Problem being pixel-perfect.