Search: subworld:handed_visualbp
|
| |
|
| BP947 |
| BPs where users are advised to only upload images in which the pixelation is not misleading vs. other "perfect" Bongard Problems that use pixelated images to closely approximate the actual intended shapes. |
|
| |
|
|
|
|
COMMENTS
|
Left examples have the keyword "pixelperfect" on the OEBP.
All examples here are perfect Bongard Problems. That is, subtle imperfections in images are meant to be considered.
When a Problem is tagged with "pixelperfect", users are reminded to make sure they do not upload images such that taking the pixelation into account would affect the sorting of that example. That is, the zoomed-in jagged blocky version of the picture should still fit the solution.
For example, in the examples of BP335, which is about tessellation, the pixels interlock properly. |
|
|
CROSSREFS
|
Stable Bongard Problems are generally pixelperfect.
Adjacent-numbered pages:
BP942 BP943 BP944 BP945 BP946 * BP948 BP949 BP950 BP951 BP952
|
|
|
KEYWORD
|
meta (see left/right), links, keyword, instruction
|
|
|
WORLD
|
perfect_bp [smaller | same | bigger]
|
|
|
AUTHOR
|
Leo Crabbe
|
| |
|
|
| |
|
| BP958 |
| Visual Bongard Problems about examples being read with infinite detail vs. other visual Bongard Problems. |
|
| |
|
|
|
|
COMMENTS
|
Left examples have the keyword "infinitedetail" on the OEBP.
Image files on the OEBP do not really have infinite detail. For a panel to be intuitively read as having infinite detail, there usually needs to be some apparent self-similarity, or perhaps a sequence of objects following an easy to read pattern getting smaller and smaller with increasing pixelation.
Usually in "infinitedetail" Bongard Problems, not only is it a puzzle to figure out the solution, but it is another puzzle to find self-similarities and understand the intended infinite detail in each example. |
|
|
CROSSREFS
|
BPs tagged with the keyword "infinitedetail" usually feature pixelated images that give the closest approximation of the intended infinite structure up to pixelation. This means they should be tagged with the keyword perfect, but should not be tagged with the keyword pixelperfect.
Just because a Bongard Problem has "infinitedetail" does not necessarily make it infodense. Some fractal images might be encoded by a small amount of information (just the information about which places within itself it includes smaller copies of itself) and may be recognized quickly.
Adjacent-numbered pages:
BP953 BP954 BP955 BP956 BP957 * BP959 BP960 BP961 BP962 BP963
|
|
|
KEYWORD
|
notso, meta (see left/right), links, keyword, wellfounded
|
|
|
WORLD
|
visualbp [smaller | same | bigger]
|
|
|
AUTHOR
|
Aaron David Fairbanks
|
| |
|
|
| |
|
| BP976 |
| Bongard Problems that use color in their examples vs. black and white Bongard Problems. |
|
| |
|
| |
| |
|
|
| |
|
| BP995 |
| Animated visual Bongard Problems vs. static visual Bongard Problems. |
|
| |
|
| |
| |
|
|
| |
|
| BP1009 |
| Visual Bongard Problems such that flipping over horizontal axis (up/down) can switch an example's side vs. visual Bongard Problems whose examples' sorting does not change under such a transformation. |
|
| |
|
| |
| |
|
|
| |
|
| BP1079 |
| A left example can be verified to fit left by checking only finitely many layers deep vs. not so. |
|
| |
|
| |
| |
|
|
| |
|
| BP1112 |
| "Stretch-dependent" Bongard Problems vs. Bongard Problems in which examples can be stretched (or compressed) along any axis without being sorted differently. |
|
| |
|
| |
| |
|
|
| |
|
| BP1143 |
| Bongard Problems where a visual addition (not erasing) can be made to any example such that it would still fit in the Bongard Problem vs. Bongard Problems where some example(s) are "maximal" (cannot be added to). |
|
| |
|
| |
| |
| |
|
|
|
|
|
|
|
|
