@Stable Bongard Problems are generally @pixelperfect.

BPs tagged with the keyword @stable will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

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

All examples here are @perfect 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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with the keyword @continuous will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

BPs tagged with the keyword "continuous" (right-BP963) will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

BPs tagged with the keyword "continuous" (left-BP963) will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

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

All examples here are "perfect" (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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with the keyword "continuous" (left-BP963) be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

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

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

All examples here are "perfect" (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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "perfect" will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" will be pixelperfect automatically. (See e.g. BP62.) In that case, any image that is approximately pixel-perfect is actually pixel-perfect.

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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" will be pixelperfect. (See e.g. BP62.) Then, any image that is approximately pixel-perfect is actually pixel-perfect.

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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" will be pixelperfect. (See e.g. BP62.) Then, any image that is approximately pixel-perfect is actually pixel-perfect.

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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in the examples of BP335, which is about tessellation, the pixels interlock properly.

All BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" are pixelperfect. (See e.g. BP62.) This is because any image that is approximately pixel-perfect is automatically actually pixel-perfect. There is no need for users to ever worry about examples in such a Bongard Problem being pixel-perfect.

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. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.

For example, in BPs about tessellation (e.g. BP335) the solution is clearer when the pixels interlock properly, so the OEBP wants users to only upload pixel-perfect examples.

All BPs tagged with both the keyword "continuous" (left-BP963) and the keyword "imperfectionscanmatter" are pixelperfect. (See e.g. BP62.) This is because any image that is approximately pixel-perfect is automatically actually pixel-perfect. There is no need for users to ever worry about examples in such a Bongard Problem being pixel-perfect.

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. 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 "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.