login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
BP963 Bongard Problems in which small changes to examples can switch their sorting vs. Bongard Problems in which examples changed slightly enough remain sorted the same way.
BP1
BP4
BP15
BP72
BP211
BP324
BP325
BP335
BP344
BP348
BP367
BP368
BP523
BP816
BP860
BP861
BP920
BP935
BP937
BP2
BP9
BP11
BP14
BP34
BP62
(edit; present; nest [left/right]; search; history)
COMMENTS

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

Right examples have the keyword "stable" on the OEBP.


For the purposes of this Bongard Problem, "small change" means adding to or removing from an arbitrarily small portion of the image. Other kinds of small change could be explored, such as making changes in multiple small places, translating, rotating, scaling, or deforming the whole image slightly (see also keywords deformunstable vs. deformstable), or even context-dependent small changes (e.g., changing the shadings slightly in BP196, or making small 3d changes to the represented 3d objects in BP333), but they are not considered here.


In a "stable" Bongard Problem, no small change should outright flip an example's sorting. It is allowed for a small change to make an example sorted slightly more ambiguously.


Small changes that make an example no longer even fit in with the format of a Bongard Problem are not considered. (Otherwise, far fewer Bongard Problems would be called "stable".)


For whether small changes make an example no longer fit in with the Bongard Problem, see unstableworld vs. stableworld.


If a Bongard Problem is shown with imperfect hand drawings (keyword ignoreimperfections), it is fine to apply the keyword "unstable" ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "unstable", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged "ignoreimperfections" in the first place if the underlying idea were such that several small changes could make an example switch sides, no longer fit in with the format of the Bongard Problem, or otherwise be ambiguously sorted.)

CROSSREFS

Stable Bongard Problems are generally perfect and pixelperfect.

Gap (technically) implies stable. (However, in practice it has seemed unnatural to tag BPs "stable" when ALL small changes render certain examples unsortable, as is sometimes the case in "gap" BPs.)


Unstable Bongard Problems are often precise.

Stable Bongard Problems tend to either be fuzzy or otherwise either have a gap or be not allsorted.


See BP1144, which is about all small changes making all examples unsortable rather than some small change making some example switch sides.


See BP1140, which is about any (perhaps large) additions of detail instead of small changes.

Adjacent-numbered pages:
BP958 BP959 BP960 BP961 BP962  *  BP964 BP965 BP966 BP967 BP968

EXAMPLE

BP1 is unstable because it's possible to change nothing slightly by adding a pixel to end up with something.

KEYWORD

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

AUTHOR

Aaron David Fairbanks

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