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

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

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

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

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

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 all examples they upload are pixel-perfect. 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.

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

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 all examples they upload are pixel-perfect. 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.

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 all examples they upload are pixel-perfect. 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.

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 all examples they upload are pixel-perfect. 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 think about this Problem being pixel-perfect.

"Literalgeometry" Bongard Problems in which taking pixelation into account is not allowed to affect sorting of examples vs. "literalgeometry" Bongard Problems that use pixelated images to only closely approximate the actual examples.

"Literalgeometry" Bongard Problems in which taking pixellation into account is not allowed to affect sorting of examples vs. "literalgeometry" Bongard Problems that use pixellated images to closely approximate the actual examples.

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 all examples they upload are pixel-perfect. We don't want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); it's very natural to make the pixels interlock properly to tessellate the plane.

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 think about this Problem being pixel-perfect.

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 all examples they upload are pixel-perfect. We don't want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); it's very natural to make the pixels interlock properly to tessellate the plane.

Typically, literalgeometry Problems tagged with the keyword "continuous" 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 think about this Problem being pixel-perfect.

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 all examples they upload are pixel-perfect. We don't want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); it's very natural to make the pixels interlock properly to tessellate the plane.

Typically, literalgeometry Problems tagged with the keyword "continuous" 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 think about this Problem being pixel-perfect.

Contrast "exact" (left-BP508).

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 all examples they upload are pixel-perfect. We don't want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); it's very natural to make the pixels interlock properly to tessellate the plane.

Typically, literalgeometry Problems tagged with the keyword "continuous" 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 think about this Problem being pixel-perfect.

"Literalgeometry" Bongard Problems where taking pixellation into account should not change sorting of examples vs. "literalgeometry" Bongard Problems that use pixellated images to approximate the examples.

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 all examples they upload are pixel-perfect. We don't want approximate pixellated images as examples in these Problems. Examples are Problems about tessellation (e.g. BP335); it's very natural to make the pixels interlock properly to tessellate the plane.

"Literalgeometry" Bongard Problems where taking pixellation into account would not change sorting of examples vs. "literalgeometry" Bongard Problems that use pixellated images to approximate the examples.

See BP913.