login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: BP1144
Displaying 1-5 of 5 results found.     page 1
     Sort: relevance      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP1144 Bongard Problems where making any small change to any sorted example renders the example unsortable vs. other Bongard Problems.
BP859
BP962
BP1104
(edit; present; nest [left/right]; search; history)
COMMENTS

Left-sorted Problems usually have a very specific collection of examples, where the only images sorted all show the same type of object.

CROSSREFS

See unstable vs. stable, which is about examples switching sides upon small changes instead of being rendered unsortable.

See unstableworld vs. stableworld, which is about SOME small change to SOME example making it no longer fit in.

See BP1142 for the version only about additions of detail (no erasures), and with no restriction on them being slight additions.

Adjacent-numbered pages:
BP1139 BP1140 BP1141 BP1142 BP1143  *  BP1145 BP1146 BP1147 BP1148 BP1149

KEYWORD

meta (see left/right), links, problemkiller

AUTHOR

Aaron David Fairbanks

BP1142 Bongard Problems where there is no way to turn an example into any other sorted example by adding black OR white (not both) vs. Bongard Problems where some example can be altered in this way and remain sorted.
BP285
BP304
BP328
BP329
BP342
BP801
BP934
BP1017
BP1056
BP1104
BP1145
BP1155
BP1156
BP1223
BP1269
BP859
BP962
(edit; present; nest [left/right]; search; history)
COMMENTS

Left-sorted problems have the keyword "finishedexamples" on the OEBP.


The addition does not have to be slight.


Left-sorted Problems usually have a very specific collection of examples, where the only images sorted all show the same type of object.


Any Bongard Problem where all examples are one shape outline will be sorted left, and (almost) any Bongard Problem where all examples are one fill shape will be sorted right.

CROSSREFS

See BP1144 for the version about both additions and erasures, and only slight changes are considered.


See BP1167 for a stricter version, the condition that all examples have the same amount of black and white.

Adjacent-numbered pages:
BP1137 BP1138 BP1139 BP1140 BP1141  *  BP1143 BP1144 BP1145 BP1146 BP1147

KEYWORD

unwordable, notso, meta (see left/right), links, keyword, sideless, problemkiller

AUTHOR

Leo Crabbe

BP964 Bongard Problems such that making repeated small changes can switch an example's sorting vs. Bongard Problems in which the two sides are so different that it is impossible to cross the gap by making successive small changes to examples while staying within the class of examples sorted by the Bongard Problem (there is no middle-ground between the sides; there is no obvious choice of shared ambient context both sides are part of).
BP2
BP4
BP8
BP9
BP3
BP16
BP23
BP363
BP962
BP1219
BP1253
(edit; present; nest [left/right]; search; history)
COMMENTS

Right-sorted BPs have the keyword "gap" on the OEBP.


A Bongard Problem with a gap showcases two completely separate classes of objects.


For example, the Bongard Problem "white vs. black" (BP962) has a gap; there is no obvious choice of shared context between the two sides. One could imagine there is a spectrum of grays between them, or that there is a space of partially filled black-and-white images between them, or any number of other ambient contexts.


Bongard Problems about comparing quantities on a spectrum should not usually be considered "gap" BPs. (Discrete spectra perhaps.) A spectrum establishes a shared context, with examples on both sides of the BP landing somewhere on it. (However, if it is reasonable to imagine getting the solution without noticing a spectrum in between, it could be a gap, since the ambient context is unclear.)


Bongard Problems with gaps may seem particularly arbitrary when the two classes of objects are particularly unrelated.

CROSSREFS

If a Bongard Problem has a "gap" it is likely precise: it will likely be clear on which side any potential example fits.


"Gap" implies stable. (This technically includes cases in which ALL small changes make certain examples no longer fit in with the Bongard Problem, as is sometimes the case in "gap" BPs. See also BP1144.)


See also preciseworld. "Gap" Bongard Problems would be tagged "preciseworld" when the two classes of objects are each clear; it is then apparent that there is no larger shared context and that no other types of objects besides the two types would be sorted by the Bongard Problem.


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

Adjacent-numbered pages:
BP959 BP960 BP961 BP962 BP963  *  BP965 BP966 BP967 BP968 BP969

KEYWORD

unwordable, meta (see left/right), links, keyword, sideless, invariance

AUTHOR

Aaron David Fairbanks

BP1203 Bongard Problems where making a small change to some example makes it no longer fit in vs. Bongard Problems in which sufficiently small changes to examples keep them fitting in.
BP859
BP962
BP1104
BP1219
BP1
BP1220
(edit; present; nest [left/right]; search; history)
COMMENTS

Left-sorted Bongard Problems have the keyword "unstableworld" on the OEBP.

Right-sorted Bongard Problems have the keyword "stableworld" on the OEBP.


In a "stableworld" Bongard Problem, no small change should outright make an example outright no longer fit in with the others in the Bongard Problem. It is allowed for a small change to make an example slightly less like all the others.


The meaning of "stableworld" is close to "examples have no particular format at all", but not quite the same.

CROSSREFS

See unstable vs. stable, which is about examples switching sides upon small changes instead of being rendered unsortable.

See BP1144, which is about ALL small changes to ALL examples making them unsortable.

Adjacent-numbered pages:
BP1198 BP1199 BP1200 BP1201 BP1202  *  BP1204 BP1205 BP1206 BP1207 BP1208

KEYWORD

meta (see left/right), links, keyword

AUTHOR

Aaron David Fairbanks

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

    page 1

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