login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: +ex:BP67
Displaying 1-10 of 13 results found. ( next )     page 1 2
     Sort: id      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP507 Bongard Problems about comparison of quantity vs. other Bongard Problems.
BP2
BP11
BP12
BP28
BP29
BP34
BP36
BP37
BP38
BP53
BP62
BP65
BP67
BP79
BP173
BP176
BP196
BP211
BP292
BP338
BP501
BP565
BP869
BP882
BP915
BP971
BP972
BP978
BP1044
BP1046
BP1208
BP1
?
BP6
(edit; present; nest [left/right]; search; history)
COMMENTS

Bongard Problems sorted left have the keyword "spectrum" on the OEBP.


In a "spectrum" Bongard Problem, there is an evident way to assign each object a value (e.g. "size" or "number of holes"). Then, to determine whether an object fits left or right in the Bongard Problem, its value is compared with a fixed threshold value.


Spectra can be continuous or discrete.


A "spectrum" Bongard Problem is usually arbitrary, since there could be made many different versions of it with different choices of threshold value. However, sometimes a certain choice of threshold is particularly natural. For example, the threshold of 90 degrees in "acute vs. obtuse angles" does not come across as arbitrary. And in BP2, the spectrum of values ("size") is vague, so much that the fuzzy threshold, of about half the size of the bounding box, does not seem arbitrary.


A spectrum Bongard Problem may or may not have the following properties:

1) The values assigned to objects are precise.

2) The threshold value between the two sides is precise.

3) The threshold value is itself sorted on one of the two sides.

Each of the latter two typically only makes sense when the condition before it is true.


If a spectrum Bongard Problem obeys 1) and 2), then it will usually be precise.

For example:

"Angles less than 90° vs. angles greater than 90°" is "precise".


If a spectrum Bongard Problem obeys 1), 2), and 3), then it will usually be allsorted.

For example:

"Angles less than or equal to 90° vs. angles greater than 90°" is "allsorted".


Discrete spectra usually satisfy 1) but do not satisfy 2). In a discrete spectrum Bongard Problem, there isn't one unambiguous threshold value. Consider "2 or fewer holes vs. 3 or more holes". (Is the threshold 2? 3? 2.5?)


In an especially extreme kind of spectrum Bongard Problem, one side represents just a single value, just the threshold value. For example, "right angles vs. obtuse angles." In certain cases like this the threshold is an extreme value at the very boundary of the spectrum of possible values. For example, consider "no holes vs. one or more holes." Cases like this might not even be understood as two sides of a spectrum, but rather the absence versus presence of a property. (See the keyword notso.)


Even more extreme, in some Bongard Problems, each of the sides is a single value on a spectrum. For example, BP6 is "3 sides vs. 4 sides". We have not been labeling Bongard Problems like this with the keyword "spectrum".


After all, any Bongard Problem can be re-interpreted as a spectrum Bongard Problem, where the spectrum ranges from the extreme fitting left to the extreme of fitting right.

REFERENCE

https://en.wikipedia.org/wiki/Total_order

CROSSREFS

See BP874 for the version sorting pictures of Bongard Problems (miniproblems) instead of links to pages on the OEBP.

Adjacent-numbered pages:
BP502 BP503 BP504 BP505 BP506  *  BP508 BP509 BP510 BP511 BP512

KEYWORD

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

WORLD

bp [smaller | same | bigger]
zoom in left (spectrum_bp)

AUTHOR

Aaron David Fairbanks

BP508 Bongard Problems with precise definitions vs. Bongard Problems with vague definitions.
BP1
BP3
BP4
BP6
BP13
BP23
BP31
BP67
BP72
BP103
BP104
BP210
BP292
BP312
BP321
BP322
BP324
BP325
BP329
BP334
BP344
BP348
BP367
BP368
BP376
BP384
BP386
BP389
BP390
BP391
BP523
BP527
BP557
BP558
BP559

. . .

BP2
BP9
BP10
BP11
BP12
BP14
BP62
BP119
BP148
BP364
BP393
BP505
BP508
BP509
BP511
BP524
BP571
BP813
BP847
BP865
BP894
BP895
BP939
BP1002
BP1111
BP1158
(edit; present; nest [left/right]; search; history)
COMMENTS

Bongard Problems sorted left have the keyword "precise" on the OEBP.

Bongard Problems sorted right have the keyword "fuzzy" on the OEBP.


In an precise Bongard Problem, any relevant example is either clearly sorted left, clearly sorted right, or clearly not sorted.

(All relevant examples clearly sorted either left or right is the keyword allsorted.)


How can it be decided whether or not a rule is precise? How can it be decided whether or not a rule classifies all "examples that are relevant"? There needs to be another rule to determine which examples the original rule intends to sort. Bongard Problems by design communicate ideas without fixing that context ahead of time. The label "precise" can only mean a Bongard Problem's rule seems precise to people who see it. (This "precise vs. fuzzy" Bongard Problem is fuzzy.)


In an precise "less than ___ vs. greater than ___" Bongard Problem (keyword spectrum), the division between the sides is usually an apparent threshold. For example, there is an intuitive threshold between acute and obtuse angles (see e.g. BP292).


As a rule of thumb, do not consider imperfections of hand drawn images (keyword ignoreimperfections) when deciding whether a Bongard Problem is precise or fuzzy. Just because one can draw a square badly does not mean "triangle vs. quadrilateral" (BP6) should be labelled fuzzy; similar vagueness arises in all hand-drawn Bongard Problems. (For Bongard Problems in which fine subtleties of drawings, including small imperfections, are meant to be considered, use the keyword perfect.)


Sometimes the way a Bongard Problem would sort certain examples is an unsolved problem in mathematics. (See e.g. BP820.) There is a precise criterion that has been used to verify each sorted example fits where it fits (some kind of mathematical proof); however, where some examples fit is still unknown. Whether or not such a Bongard Problem should be labelled "precise" might be debated.

(Technical note: some properties are known to be undecidable, and sometimes the decidability itself is unknown. See https://en.wikipedia.org/wiki/Decision_problem .)

(See the keyword proofsrequired.)

One way to resolve this ambiguity is to define "precise" as meaning that once people decide where an example belongs for a reason, they will all agree about it.


Sometimes the class of all examples in a Bongard Problem is imprecise, but, despite that, the rule sorting those examples is precise. Say, for some potential new example, it is unclear whether it should be included in the Bongard Problem at all, but, if it were included, it would be clear where it should be sorted (or that it should be left unsorted). A Bongard Problem like this can still be tagged "precise".

(If all examples are clearly sorted except for some example for which it is unclear whether it belongs to the class of relevant examples, the situation becomes ambiguous.)

On the other hand, sometimes the class of all examples is very clear, with an obvious boundary. (Keyword preciseworld.)


There is a subtle distinction to draw between Bongard Problems that are precise to the people making them and Bongard Problems that are precise to the people solving them. A Bongard Problem (particularly a non-allsorted one) might be labeled "precise" on the OEBP because the description and the listed ambiguous examples explicitly forbid sorting certain border cases; however, someone looking at the Bongard Problem without access to the OEBP page containing the definition would not be aware of this. It may or may not be obvious that certain examples were intentionally left out of the Bongard Problem. A larger collection of examples may make it more clear that a particularly blatant potential border case was left out intentionally.

CROSSREFS

See BP876 for the version with pictures of Bongard Problems instead of links to pages on the OEBP.

See both and neither for specific ways an example can be classified as unsorted in an "precise" Bongard Problem.

Adjacent-numbered pages:
BP503 BP504 BP505 BP506 BP507  *  BP509 BP510 BP511 BP512 BP513

KEYWORD

fuzzy, meta (see left/right), links, keyword, right-self, sideless

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP534 Bongard Problems such that potential left examples can intuitively be put in bijection with potential right examples vs. other Bongard Problems.
BP7
BP8
BP19
BP36
BP43
BP45
BP54
BP55
BP63
BP64
BP67
BP95
BP106
BP109
BP157
BP158
BP180
BP196
BP197
BP211
BP234
BP278
BP279
BP286
BP313
BP337
BP357
BP363
BP372
BP513
BP514
BP515
BP516
BP517
BP793

. . .

(edit; present; nest [left/right]; search; history)
COMMENTS

This is the keyword "dual" on the OEBP.

Given an example there is some way to "flip sides" by altering it. The left-to-right and right-to-left transformations should be inverses.


It is not required that there only be one such transformation. For example, for many handed Bongard Problem, flipping an example over any axis will reliably switch its sorting.


It is not required that every left example must have its corresponding right example uploaded on the OEBP nor vice versa. See the keyword contributepairs for the BPs the OEBP advises users upload left and right examples for in pairs.

CROSSREFS

Adjacent-numbered pages:
BP529 BP530 BP531 BP532 BP533  *  BP535 BP536 BP537 BP538 BP539

KEYWORD

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

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP535 Visual Bongard Problems such that flipping over the vertical axis (left/right) can switch an example's side vs. visual Bongard Problems whose examples' sorting doesn't change under such a transformation.
BP8
BP43
BP67
BP109
BP207
BP234
BP278
BP279
BP313
BP337
BP357
BP363
BP372
BP793
BP795
BP796
BP805
BP830
BP881
BP931
BP955
BP961
BP971
BP1008
BP1014
BP1024
BP1025
BP1027
BP1028
BP1029
BP1030
BP1031
BP1032
BP1033
BP1034

. . .

BP199
BP839
BP896
BP972
BP986
BP1122
(edit; present; nest [left/right]; search; history)
COMMENTS

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

CROSSREFS

See updown.

All "leftright" Bongard Problems are handed.

Adjacent-numbered pages:
BP530 BP531 BP532 BP533 BP534  *  BP536 BP537 BP538 BP539 BP540

KEYWORD

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

WORLD

handed_visualbp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP552 Orientation-dependent Bongard Problems vs. orientation-independent visual Bongard Problems.
BP7
BP8
BP16
BP36
BP43
BP54
BP55
BP63
BP67
BP106
BP109
BP199
BP207
BP234
BP278
BP279
BP286
BP313
BP337
BP363
BP372
BP793
BP795
BP796
BP805
BP830
BP881
BP896
BP931
BP955
BP961
BP971
BP972
BP1008
BP1014

. . .

BP1
BP2
BP3
BP4
BP5
BP6
BP986
BP1197
BP1199
BP1200
(edit; present; nest [left/right]; search; history)
COMMENTS

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


If mirroring any example along the any axis can change its sorting the BP is "handed."


Note that BPs about comparing orientation between multiple things in one example fit on the right side.

CROSSREFS

See BP871 for the version with pictures of Bongard Problems (miniproblems) instead of links to pages on the OEBP.


The keyword leftright is specifically about flipping over the vertical axis, while the keyword updown is specifically about flipping over the horizontal axis.


Bongard Problems tagged rotate are usually "handed", since any rotation can be created by two reflections. Not necessarily, however, since the reflected step in between might not be sorted on either side by the Bongard Problem.

Adjacent-numbered pages:
BP547 BP548 BP549 BP550 BP551  *  BP553 BP554 BP555 BP556 BP557

KEYWORD

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

WORLD

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

AUTHOR

Aaron David Fairbanks

BP578 Bongard Problem with solution relating to concept: above / below vs. Bongard Problem unrelated to this concept.
BP36
BP37
BP48
BP67
BP68
BP337
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP573 BP574 BP575 BP576 BP577  *  BP579 BP580 BP581 BP582 BP583

KEYWORD

meta (see left/right), links, metaconcept

CONCEPT This MBP is about BPs that feature concept: "above_below"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP597 Bongard Problem with solution relating to concept: branching point on linear structure vs. Bongard Problem unrelated to this concept.
BP67
BP68
BP86
BP92
BP93
BP113
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP592 BP593 BP594 BP595 BP596  *  BP598 BP599 BP600 BP601 BP602

KEYWORD

meta (see left/right), links, metaconcept

CONCEPT This MBP is about BPs that feature concept: "branch_point"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP657 Bongard Problem with solution relating to concept: left / right vs. Bongard Problem unrelated to this concept.
BP8
BP63
BP67
BP68
BP191
BP234
BP279
BP280
BP339
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP652 BP653 BP654 BP655 BP656  *  BP658 BP659 BP660 BP661 BP662

KEYWORD

meta (see left/right), links, metaconcept, primitive

CONCEPT This MBP is about BPs that feature concept: "left_right"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP689 Bongard Problem with solution relating to concept: separated on two sides of a curve vs. Bongard Problem unrelated to this concept.
BP67
BP75
BP135
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP684 BP685 BP686 BP687 BP688  *  BP690 BP691 BP692 BP693 BP694

KEYWORD

meta (see left/right), links, metaconcept, primitive

CONCEPT This MBP is about BPs that feature concept: "on_sides_of_curve"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP708 Bongard Problem with solution relating to concept: tracing along a line or curve vs. Bongard Problem unrelated to this concept.
BP16
BP43
BP52
BP55
BP67
BP68
BP69
BP70
BP72
BP74
BP102
BP105
BP115
BP120
BP179
BP180
BP198
BP208
BP278
BP336
BP340
BP341
BP350
BP351
BP352
BP353
BP354
BP355
BP356
BP357
BP363
BP365
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP703 BP704 BP705 BP706 BP707  *  BP709 BP710 BP711 BP712 BP713

KEYWORD

meta (see left/right), links, metaconcept, primitive

CONCEPT This MBP is about BPs that feature concept: "tracing_line_or_curve"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

( next )     page 1 2

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