Revision history for BP1124
|
Displaying 1-25 of 97 results found.
|
page 1 2 3 4
|
|
Edits shown per page: 25.
|
|
|
|
|
| |
| |
|
|
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). |
|
|
|
|
| |
| |
|
|
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). |
|
|
|
|
| |
| |
|
|
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 |
|
|
|
|
| |
| |
|
|
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.
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.)
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.
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 (left-BP958).
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 |
|
|
|
|
| |
| |
|
|
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 right-BP1125.)
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.
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.)
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.
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 (left-BP867): 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" (BP1159) 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" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding rules (keyword "rules" left-BP1158)--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" left-BP930.) 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 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) 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" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding rules (keyword "rules" left-BP1158)--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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) 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" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding rules (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) 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" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule in each panel (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) 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" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
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.
If a Bongard Problem is "left-unknowable", then any individual example 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 right-BP1125.)
Sometimes a Bongard Problems is almost left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason.
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.)
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.
One interpretation of the axioms 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 (left-BP867): 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" (BP1159) 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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and 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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and 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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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" left-BP930.) Each of these examples communicates a clear "rule that doesn't count". And there is so little information shown in these examples 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. Perhaps the definition of "unknowable" needs some slight reworking. - Aaron David Fairbanks, Apr 20 2022 |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and 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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are generally "left-narrow", left-BP514 (and left-unknowable Bongard Problems are generally "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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.) |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and 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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are often "left-narrow", left-BP514 (and left-unknowable Bongard Problems are often "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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.) |
|
|
|
|
| |
| |
|
|
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.
If a Bongard Problem is "left-unknowable", then any individual example 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 right-BP1125.)
Sometimes a Bongard Problems is almost left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason. It may make for a cleaner Bongard Problem to exclude these exceptional disqualified cases.
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.)
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.
One interpretation of the axioms 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 (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and uncertainty about whether there is more information to be found. For any example sorted on the "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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122). See keyword "infinitedetail" (left-BP958).
Right-unknowable Bongard Problems are often "left-narrow", left-BP514 (and left-unknowable Bongard Problems are often "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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.) |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and uncertainty about whether there is more information to be found. For any example sorted on the "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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122).
Right-unknowable Bongard Problems are often "left-narrow", left-BP514 (and left-unknowable Bongard Problems are often "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "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.) |
|
|
|
|
| |
| |
|
|
CROSSREFS
|
Left- or right- unknowable Bongard Problems are generally "notso" Bongard Problems (left-BP867): 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" (BP1159) sound similar to "left-unknowable" and "right-unknowable", they are not the same. It is the difference between a clear absence of information and uncertainty about whether there is more information to be found. For any example sorted on the "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, using a low resolution for all pictures can simplify the issue of detecting some properties that would be "unknowable" for hypothetical infinitely detailed pictures. Many fractal-based BPs are this way (e.g. BP1122).
Right-unknowable Bongard Problems are often "left-narrow", left-BP514 (and left-unknowable Bongard Problems are often "right-narrow", left-BP513).
A Bongard Problem with examples on both sides cannot be both "proofsrequired" (left-BP1125) and left- or right- unknowable.
Many Bongard Problems are about finding a rule that a structure satisfies (keyword "rules" left-BP1158)--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.) Bongard Problems about rules like this with solution "There is a rule vs. there isn't" (resp. vice versa) are right- (resp. left-) unknowable (disregarding cases that obviously do not define a rule because of some trivial disqualifying reason). |
|
|
|
|
| |
| |
|
|
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.
If a Bongard Problem is "left-unknowable", then any individual example 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 right-BP1125.)
Sometimes a Bongard Problems is almost left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason. It may make for a cleaner Bongard Problem to exclude these exceptional disqualified cases.
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.)
Because of this, 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.
One interpretation of the axioms 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". |
|
|
|
|
| |
| |
|
|
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.
If a Bongard Problem is "left-unknowable", then any individual example 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 right-BP1125.)
Sometimes a Bongard Problems is almost left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason. It may make for a cleaner Bongard Problem to exclude these exceptional disqualified cases.
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.)
Because of this, 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.
One interpretation of the axioms 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 negation of the property being observable corresponds to the subset being "closed". |
|
|
|
|
| |
| |
|
|
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.
If a Bongard Problem is "left-unknowable", then any individual example 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 right-BP1125.)
Sometimes a Bongard Problems is almost left-unknowable, but a few examples spoil it by being obviously disqualified from the right side for some reason. It may make for a cleaner Bongard Problem to exclude these exceptional disqualified cases.
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.)
Because of this, 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.
One interpretation of the axioms 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". |
|
|
|