login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: all
Displaying 401-410 of 462 results found. ( prev | next )     page 1 ... 37 38 39 40 41 42 43 44 45 46 47
     Sort: id      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP1111 Bongard Problem requires solver to already be interpreting all examples in a specific way for the answer to seem simple vs. not so.
BP200
BP361
BP362
BP793
BP795
BP796
BP802
BP803
BP827
BP828
BP829
BP831
BP832
BP833
BP834
BP835
BP836
BP852
BP871
BP872
BP873
BP874
BP875
BP876
BP877
BP878
BP879
BP880
BP881
BP894
BP955
BP957
BP968
BP987
BP1024

. . .

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

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


Sometimes all the examples in a Bongard Problem need to be interpreted a certain way for the Bongard Problem to make sense. Only once the representation is understood, the idea seems simple.


For example, all meta Bongard Problems (Bongard Problems sorting other Bongard Problems) assume the solver interprets the examples as Bongard Problems.


TO DO: Maybe it is best to stop putting the label "assumesfamiliarity" on all meta-Bongard Problems. There are so many of them. It may be better to only use the "assumesfamiliarity" keyword on meta-BPs for a further assumption than just that all examples are interpreted as Bongard Problems. - Aaron David Fairbanks, Feb 11 2021

CROSSREFS

Many Bongard Problems in which all examples take the same format (keyword structure) assume the solver already knows how to read that format.

Some Bongard Problems assume the solver will be able to understand symbolism that is consistent between examples (keyword consistentsymbols).

Bongard Problems tagged math often assume the solver is familiar with a certain representation of a math idea.

Adjacent-numbered pages:
BP1106 BP1107 BP1108 BP1109 BP1110  *  BP1112 BP1113 BP1114 BP1115 BP1116

EXAMPLE

BP1032: The solution should really read "Assuming all images are Bongard Problems sorting each natural number left or right ..." This Bongard Problem makes sense to someone who has been solving a series of similar BPs, but otherwise there is no reason to automatically read a collection of numbers as standing for a larger collection of numbers.

KEYWORD

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

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP1112 "Stretch-dependent" Bongard Problems vs. Bongard Problems in which examples can be stretched (or compressed) along any axis without being sorted differently.
BP7
BP11
BP12
BP13
BP33
BP50
BP62
BP76
BP77
BP80
BP103
BP152
BP250
BP289
BP328
BP329
BP333
BP335
BP336
BP523
BP525
BP536
BP557
BP559
BP812
BP813
BP816
BP860
BP920
BP924
BP942
BP949
BP1011
BP1086
BP1145

. . .

BP1
BP5
BP15
BP31
BP45
BP98
BP157
BP240
BP322
BP327
BP330
BP331
BP332
BP348
BP363
BP367
BP368
BP369
BP389
BP809
BP810
BP851
BP853
BP911
BP966
BP977
BP992
BP1022
BP1094
BP1131
BP1135
BP1136
(edit; present; nest [left/right]; search; history)
COMMENTS

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


If applying a scaling along one particular axis to the whole of any example can change its sorting the BP fits on the left side here. (For BPs with bounding boxes this means scaling and cropping, but without cutting out any detail.)

CROSSREFS

Adjacent-numbered pages:
BP1107 BP1108 BP1109 BP1110 BP1111  *  BP1113 BP1114 BP1115 BP1116 BP1117

KEYWORD

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

WORLD

[smaller | same | bigger]

AUTHOR

Leo Crabbe

BP1113 Bongard Problems relating to the OEBP vs. Bongard Problems unrelated to the OEBP.
BP503
BP504
BP518
BP542
BP546
BP919
BP930
BP943
BP967
BP1113
BP1121
BP1125
BP1150
BP1174
BP1
BP2
BP3
BP4
BP5
BP6
BP7
BP8
BP9
BP10
BP11
BP12
BP13
BP14
BP15
BP16
BP17
BP18
BP19
BP20
BP21
BP22
BP23
BP24
BP25
BP26
BP27
BP28
BP29
BP30
BP31
BP32
BP33
BP34
BP35

. . .

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

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


Most Bongard Problems relating to the OEBP are meta.

CROSSREFS

Adjacent-numbered pages:
BP1108 BP1109 BP1110 BP1111 BP1112  *  BP1114 BP1115 BP1116 BP1117 BP1118

KEYWORD

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

AUTHOR

Leo Crabbe

BP1117 Bongard Problem with solution relating to concept: topological density vs. Bongard Problem unrelated to this concept.
BP1108
BP1116
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP1112 BP1113 BP1114 BP1115 BP1116  *  BP1118 BP1119 BP1120 BP1121 BP1122

KEYWORD

meta (see left/right), links, metaconcept

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

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP1121 Bongard Problems that were added to the OEBP to be used as examples in particular meta-BPs vs. other Bongard Problems,
BP570
BP868
BP915
BP1042
BP1043
BP1105
BP1141
BP1150
BP1163
BP1168
BP1227
(edit; present; nest [left/right]; search; history)
COMMENTS

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


Plea to the reader: We need a good counterexample for this Problem. Could you please make a good example of a Problem this meta BP would sort on its right? Don't forget to tag it appropriately. - Leo Crabbe, Dec 13 2021

CROSSREFS

Adjacent-numbered pages:
BP1116 BP1117 BP1118 BP1119 BP1120  *  BP1122 BP1123 BP1124 BP1125 BP1126

KEYWORD

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

AUTHOR

Aaron David Fairbanks

BP1124 Bongard Problems such that examples are always by default sorted left, until some unforeseen way of fitting right is noticed (a person is never "sure" something should fit left, but can be "sure" something fits right) vs. vice versa.
BP347
BP829
BP1127
BP801
BP1155
BP1163
(edit; present; nest [left/right]; search; history)
COMMENTS

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

Right-sorted Bongard Problems have the keyword "right-unknowable".


Think of searching for needles in endless haystacks. You can be sure a haystack has a needle by finding it, but you can never be sure a haystack does not have a needle.


When a Bongard Problem is "left-unknowable", individual examples cannot be determined for certain to fit left, by any means. The author of the Bongard Problem just chooses some examples that seem to fit left. (See also the noproofs keyword.)


It is very extreme for this to apply to all examples without exception. Often a Bongard Problem is close to being purely left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason.


It is natural for a person to guess the solution to an unknowable Bongard Problem before actually understanding all the knowable examples, taking some of them on faith.

As a prank, take a left- or right- unknowable Bongard Problem and put an example that actually belongs on the unknowable side on the knowable side. The solver will have to take it on faith there is some reason it fits there they are not seeing.

(The property of having this kind of sorting mistake is unknowable for left- or right- unknowable Bongard Problems.)



One interpretation of topology (a subject of mathematics -- see https://en.wikipedia.org/wiki/Topology ) is that a topology describes the observability of various properties. (The topological "neighborhoods" of a point are the subsets one could determine the point to be within using a finite number of measurements.) The analogue of a property that is nowhere directly observable is a "subset with empty interior". Furthermore, the fact that the negation of the property is observable corresponds to the subset being "closed".

CROSSREFS

Left- or right- unknowable Bongard Problems are generally notso Bongard Problems: an example fits on one side just in case it cannot be observed to fit on the other.


Although the descriptions of left-couldbe and right-couldbe sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and perpetual uncertainty about whether there is more information to be found. For any example sorted on a "could be" side, there is a clear (knowable) absence of information whose presence would justify the example being on the other side.

Sometimes an unknowable BP can be turned into a couldbe BP by explicitly restricting the amount of available information. For example, if there were a hypothetical Bongard Problem with infinitely detailed pictures, using a low resolution for all pictures could simplify the issue of detecting some properties that would be "unknowable". Many fractal-based BPs are this way (e.g. BP1122). See keyword infinitedetail.


Right-unknowable Bongard Problems are generally left-narrow (and left-unknowable Bongard Problems are generally right-narrow).


A Bongard Problem with examples on both sides cannot be tagged both proofsrequired and left- or right- unknowable.


Many Bongard Problems are about finding rules (keyword rules)--in each panel a rule is to be found, and there are no specified limits about what kind of rule it can be or how abstract it can be. (Just like a Bongard Problem.) "There is a rule vs. there isn't" (resp. vice versa) are right- (resp. left-) unknowable. (That is, disregarding cases that obviously do not define a rule because of some trivial disqualifying reason.)


Actually, I think there is something more to be said about this. It is possible to design examples that signal there is no rule to be found. See for example EX9138 in BP1127 and EX6829 in BP829. (Related: keyword help.) Each of these examples communicates a clear rule that "doesn't count". And there is so little information shown that a person can feel confident they've noticed all the relevant details. So, contrary to how they are currently tagged, these Bongard Problems aren't strictly "unknowable"; there are some exceptional knowable cases. But being too strict about the definition of "unknowable" makes it so there aren't any examples of unknowable Bongard Problems, so it's probably better to be a bit loose. - Aaron David Fairbanks, Apr 20 2022

Adjacent-numbered pages:
BP1119 BP1120 BP1121 BP1122 BP1123  *  BP1125 BP1126 BP1127 BP1128 BP1129

EXAMPLE

The perfect example is BP1163.


Interesting example of a Bongard Problem that is neither left-unknowable nor right unknowable in particular, but for which it is impossible to know whether any example fits on either side: BP1229 (translational symmetry vs. not) made with examples that can be expanded to any larger finite region the solver wants to look at. In this case, examples could only be sorted based on what they seem like (see seemslike), trusting they appear in a way that hints psychologically at what they actually are (see help).

KEYWORD

dual, meta (see left/right), links, keyword, side, viceversa

CONCEPT semidecidable (info | search)

AUTHOR

Aaron David Fairbanks

BP1125 BP pages on the OEBP (with a criterion for sorting examples that in some cases may be very difficult to work out) where users should be certain (i.e. know a proof) about how examples are sorted vs. users can include examples on a side as long as nobody has seen a reason it does not fit there.
BP335
BP344
BP532
BP850
BP1119
BP1137
BP1200
BP1245
(edit; present; nest [left/right]; search; history)
COMMENTS

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

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


For every "noproofs" Bongard Problem there could be made a stricter "proofsrequired" version. This stricter version will be hardsort.


Deciding to make a Bongard Problem noproofs adds subjectivity to the sorting of examples (keyword subjective).



One interpretation of topology (a subject of mathematics -- see https://en.wikipedia.org/wiki/Topology ) is that a topology describes the observability of various properties. (The topological "neighborhoods" of a point are the subsets one could determine the point to be within using a finite number of measurements.) The analogue of restricting to just the cases where a property is observably true (i.e. "proofsrequired") corresponds to taking the topological "interior" of that property.



TO DO: It may be better to split each of these keywords up into two: "left-proofsrequired", "right-proofsrequired", "left-noproofs", "right noproofs".


CROSSREFS

See keyword hardsort.


Bongard Problems that are left-unknowable or right-unknowable will have to be "noproofs".

Adjacent-numbered pages:
BP1120 BP1121 BP1122 BP1123 BP1124  *  BP1126 BP1127 BP1128 BP1129 BP1130

EXAMPLE

In "proofsrequired" BP335 (shape tessellates the plane vs. shape does not tessellate the plane), shapes are only put in the Bongard Problem if they are known to tessellate or not to tessellate the plane. A "noproofs" version of this Bongard Problem would instead allow a shape to be put on the right if it was just (subjectively) really hard to find a way of tessellating the plane with it.

KEYWORD

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

AUTHOR

Aaron David Fairbanks

BP1126 Meta Bongard Problems in which examples are pages on the OEBP vs. meta Bongard Problems in which examples are pictures of Bongard Problems.
BP501
BP503
BP504
BP506
BP507
BP508
BP509
BP510
BP511
BP512
BP513
BP514
BP515
BP516
BP517
BP518
BP519
BP520
BP521
BP522
BP526
BP534
BP535
BP537
BP539
BP541
BP542
BP544
BP546
BP547
BP549
BP550
BP552
BP553
BP554

. . .

BP200
BP793
BP795
BP796
BP802
BP803
BP827
BP828
BP829
BP830
BP831
BP832
BP833
BP834
BP835
BP836
BP868
BP871
BP872
BP873
BP874
BP875
BP876
BP877
BP878
BP879
BP880
BP881
BP894
BP948
BP952
BP953
BP954
BP955
BP957

. . .

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

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

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


The keyword "links" is automatically added to a Bongard Problem on the OEBP if a BP number is added as an example.


Meta Bongard problems that sort Bongard Problems purely based on their solutions (keyword presentationmatters) usually have two versions in the database: one that sorts images of Bongard Problems and one that sorts links to pages on the OEBP. If both versions exist, users should make them cross-reference one another.

CROSSREFS

All the examples of miniature Bongard Problems within any meta Bongard Problem tagged "miniproblems" would fit left on BP1080 (which is a showcase of the various formats for images of Bongard Problems).

Adjacent-numbered pages:
BP1121 BP1122 BP1123 BP1124 BP1125  *  BP1127 BP1128 BP1129 BP1130 BP1131

KEYWORD

meta (see left/right), links, keyword, world, left-self, metameta

WORLD

metabp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP1128 Bongard Problem with inductive definition of solution vs. other Bongard Problems.
BP956
BP1129
BP1200
(edit; present; nest [left/right]; search; history)
COMMENTS

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


An inductive definition is like, "Call certain basic objects 'blurps', and call combinations of blurps 'blurps' too."

CROSSREFS

Adjacent-numbered pages:
BP1123 BP1124 BP1125 BP1126 BP1127  *  BP1129 BP1130 BP1131 BP1132 BP1133

KEYWORD

meta (see left/right), links, keyword

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP1134 Bongard Problem with solution relating to concept: impossible vs. Bongard Problem unrelated to this concept.
BP252
BP821
BP868
BP1133
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP1129 BP1130 BP1131 BP1132 BP1133  *  BP1135 BP1136 BP1137 BP1138 BP1139

KEYWORD

meta (see left/right), links, metaconcept

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

WORLD

bp [smaller | same | bigger]

AUTHOR

Leo Crabbe

( prev | next )     page 1 ... 37 38 39 40 41 42 43 44 45 46 47

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