login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: ex:BP1088
Displaying 1-2 of 2 results found.     page 1
     Sort: id      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP913 Bongard Problems in which fine subtleties of images may be considered with respect to the solution (no slightly wrong hand-drawings!) vs. other visual Bongard Problems.
BP1
BP160
BP199
BP210
BP211
BP213
BP216
BP217
BP223
BP312
BP321
BP324
BP325
BP335
BP341
BP344
BP348
BP367
BP368
BP386
BP523
BP529
BP530
BP531
BP532
BP533
BP551
BP557
BP559
BP564
BP816
BP852
BP859
BP860
BP861

. . .

BP5
BP6
BP72
BP91
BP136
BP148
?
BP119
(edit; present; nest [left/right]; search; history)
COMMENTS

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

CROSSREFS

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

EXAMPLE

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.

KEYWORD

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

WORLD

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

AUTHOR

Aaron David Fairbanks

BP947 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.
BP1
BP31
BP210
BP211
BP217
BP279
BP321
BP324
BP325
BP335
BP341
BP367
BP386
BP523
BP548
BP859
BP860
BP861
BP892
BP920
BP934
BP935
BP966
BP1008
BP1088
BP1089
BP1090
BP1093
BP1104
BP1131
BP1156
BP1161
BP1168
BP1183
BP344
BP559
BP564
BP912
BP937
BP949
BP965
(edit; present; nest [left/right]; search; history)
COMMENTS

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.

CROSSREFS

Stable Bongard Problems are generally pixelperfect.

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

KEYWORD

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

WORLD

perfect_bp [smaller | same | bigger]

AUTHOR

Leo Crabbe

    page 1

Welcome | Solve | Browse | Lookup | Recent | Links | Register | Contact
Contribute | Keywords | Concepts | Worlds | Ambiguities | Transformations | Invalid Problems | Style Guide | Goals | Glossary