Adjacent-numbered pages:
BP756 BP757 BP758 BP759 BP760  *  BP762 BP763 BP764 BP765 BP766

meta (see left/right), links, metaconcept

bp [smaller | same | bigger]

Harry E. Foundalis

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

Right examples have the keyword "ignoreimperfections".

Consider the difference in style between BP344 and BP24.

Hand-drawn figures in BPs are typically imperfect. A "circles vs. squares" BP may only show what are approximately circles and approximately squares. A pedant might append to the solutions of all Bongard Problems the caveat "...when figures are interpreted as the most obvious shapes they approximate."

This is the meaning of the label "ignoreimperfections". On the other hand, the label "perfect" means even the pedant would drop this caveat; either all the images are precise, or precision doesn't matter (see also keyword stable).

Even in BPs tagged "perfect", the tiny rough edges caused by image pixelation are not expected to matter. If the OEBP would indeed prefer users only upload pixel-perfect examples, a BP can be tagged with the stricter keyword pixelperfect.

E.g., for BPs having to do with smooth curves and lines, "perfect" only requires images offer the best possible approximation of those intended shapes given the resolution.

Most Bongard Problems involving small details at all would be tagged "perfect". However, this is not always so; sometimes the small details are intended to be noticed, but certain imperfections are still intended to be overlooked.

BP119 ("small correction results in circle vs. not") is an interesting example: imperfections matter with respect to the outline being closed, but imperfections do not matter with respect to circular-ness.

If a Bongard Problem on the OEBP is tagged "ignoreimperfections" -- i.e., it has imperfect hand drawings -- then other keywords are generally applied relative to the intended idea, a corrected version sans imperfect hand drawings. (For example, this is how the keywords precise and stable are applied. Alternative versions of these keywords, which factor in imperfect hand drawings, could be made instead, but that would be less useful.)

It may be better to change the definition of "perfect" so it only applies to Bongard Problems such that small changes can potentially switch an example's side / remove it from the Bongard Problem. That would cut down on the number of Bongard Problems to label "perfect". There isn't currently a single keyword for "small changes can potentially switch an example's side / remove it from the Bongard Problem", but this is basically captured by unstable or unstableworld. There is also deformunstable which uses a different notion of "small change". - Aaron David Fairbanks, Jun 16 2023

See BP508 for discussion of this topic in relation to Bongard Problems tagged precise.

Stable Bongard Problems are generally "perfect".

Pixelperfect implies "perfect".

The keywords proofsrequired and noproofs (BP1125) have a similar relationship: "noproofs" indicates a lenience for a certain kind of imperfection.

Adjacent-numbered pages:
BP908 BP909 BP910 BP911 BP912  *  BP914 BP915 BP916 BP917 BP918

Many Bongard Problems involving properties of curves (e.g. BP62) really are about those wiggly, imperfect curves; they qualify as "perfect" problems. On the other hand, Bongard Problems involving polygons, (e.g. BP5) often show only approximately-straight lines; they are not "perfect" problems.

meta (see left/right), links, keyword, wellfounded

visualbp [smaller | same | bigger]
zoom in left (perfect_bp)

Aaron David Fairbanks

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

When this keyword is added to a Problem, OEBP users are advised to add a corresponding right example for every left example they add and vice versa.

It is common for Bongard Problems to present left examples on the left side and corresponding altered versions of those examples on the right side, tweaked only slightly, to highlight the difference and make the solution easier to see (see keyword help).

This is common in more abstract Bongard Problems that admit a wide range of examples, a variety of different styles or types (e.g. BP360). Showing two versions of the same thing, one on the left and one on the right, helps a person interpret what that thing is meant to be in the context of the Bongard Problem; whatever qualities vary between the two in the pair must be relevant.

If a person cannot sort an example according to the solution property without seeing its corresponding opposite example, the Bongard Problem is invalid (see https://www.oebp.org/invalid.php ). There is no one rule dividing the sides; the solution is not a method to determine whether an arbitrary example fits left or right. See also Bongard Problems with the keyword collective, which are similarly borderline-invalid.

A BP in which each left example corresponds to a right example and vice versa could be remade as a Bongard Problem in which the left examples are the pairs. For example BP360 would turn into "a pair consisting of the ordered version of something and the chaotic version of the same thing vs. a pair of things not satisfying this relationship." This process would turn a Bongard Problem that is invalid in the sense described above into a valid one.

(See keyword orderedpair.)

In some "contributepairs" Bongard Problems there really is a natural choice of left version for every right example and vice versa (see keyword dual); in others the choice is artificially imposed by the Bongard Problem creator.

When "contributepairs" Bongard Problems are laid out in the format with a grid of boxes on either side of a dividing line, the boxes may be arranged so as to highlight the correspondence: either

A B | A B

E F | E F

G H | G H

or

A B | B A

E F | F E

G H | H G.

Adjacent-numbered pages:
BP914 BP915 BP916 BP917 BP918  *  BP920 BP921 BP922 BP923 BP924

meta (see left/right), links, keyword, oebp, right-self, instruction

bppage [smaller | same | bigger]
zoom in left (correspondence_bp)

Aaron David Fairbanks

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.

Stable Bongard Problems are generally pixelperfect.

Adjacent-numbered pages:
BP942 BP943 BP944 BP945 BP946  *  BP948 BP949 BP950 BP951 BP952

meta (see left/right), links, keyword, instruction

perfect_bp [smaller | same | bigger]

Leo Crabbe