login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)

Revision history for BP508

Displaying 326-350 of 384 results found. page 1 ... 10 11 12 13 14 15 16
     Edits shown per page: 25.
BP508 on 2020-08-01 06:51:38 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-08-01 06:38:17 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-08-01 04:02:26 by Aaron David Fairbanks                approved
-DATA

  

BP508 on 2020-08-01 03:56:13 by Aaron David Fairbanks                approved
-DATA

  

BP508 on 2020-07-30 21:49:29 by Leo Crabbe                approved
+DATA

  

BP508 on 2020-07-30 21:34:31 by Leo Crabbe                approved
+DATA

  

BP508 on 2020-07-30 06:19:18 by Aaron David Fairbanks                approved
COMMENTS

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

Right examples have the keyword "fuzzy" on the OEBP.

In exact Bongard Problems, it is always clear where each relevant example should be sorted. Ambiguity is allowed, but only if it is clear precisely which cases are ambiguous.

For quantity-based BPs, this sometimes means it is possible to calculate exactly the values of the examples (when the examples are themselves specified exactly enough).

Often a precise divide between values on a spectrum comes from intuitively "crossing a threshold." For example, there is an intuitive threshold between acute and obtuse angles. Two sides of a Bongard Problem on opposite ends of a threshold, coming close to it, are interpreted as having precise divide between sides, right up against that threshold.

IMPORTANT: For Bongard Problems based on images we assume the intended geometry represented by the image is understood before we sort. The case of a "poorly drawn square" is not here considered an ambiguous case for BP6 triangles vs. squares; a shape is either a square or it isn't.

However, for Bongard Problems specifically about approximation (e.g. BP10 approximately triangular outline vs. approximately convex quadrilateral outline) even in the pure geometry there is a spectrum of how closely a shape approximates something; there are ambiguous cases here.

For Bongard Problems in which fine subtleties of drawings, including small imperfections, are meant to be considered, use the keyword "literalgeometry" (BP913).

EXAMPLE

BP508 on 2020-07-30 06:18:51 by Aaron David Fairbanks                approved
COMMENTS

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

Right examples have the keyword "fuzzy" on the OEBP.

In exact Bongard Problems, it is always clear where each relevant example should be sorted. Ambiguity is allowed, but only if it is clear precisely which cases are ambiguous.

For quantity-based BPs, this sometimes means it is possible to calculate exactly the values of the examples (when the examples are themselves specified exactly enough).

Often a precise divide between values on a spectrum comes from intuitively "crossing a threshold." For example, there is an intuitive threshold between acute and obtuse angles. Two sides of a Bongard Problem on opposite ends of a threshold, coming close to it, are interpreted as having precise divide between sides, right up against that threshold..

IMPORTANT: For Bongard Problems based on images we assume the intended geometry represented by the image is understood before we sort. The case of a "poorly drawn square" is not here considered an ambiguous case for BP6 triangles vs. squares; a shape is either a square or it isn't.

However, for Bongard Problems specifically about approximation (e.g. BP10 approximately triangular outline vs. approximately convex quadrilateral outline) even in the pure geometry there is a spectrum of how closely a shape approximates something; there are ambiguous cases here.

For Bongard Problems in which fine subtleties of drawings, including small imperfections, are meant to be considered, use the keyword "literalgeometry" (BP913).

EXAMPLE

BP508 on 2020-07-30 05:51:47 by Aaron David Fairbanks                approved
CROSSREFS

See BP876 for the semi-meta version.

BP508 on 2020-07-29 21:58:06 by Leo Crabbe                approved
+DATA

  

BP508 on 2020-07-29 17:26:23 by Leo Crabbe                approved
REMOVE

  

BP508 on 2020-07-28 22:17:58 by Leo Crabbe                approved
+DATA

  

BP508 on 2020-07-28 00:37:21 by Leo Crabbe                approved
-DATA

  

BP508 on 2020-07-27 22:01:15 by Leo Crabbe                approved
-DATA

  

BP508 on 2020-07-27 21:41:55 by Leo Crabbe                approved
REMOVE

  

BP508 on 2020-07-27 17:57:28 by Leo Crabbe                approved
-DATA

  

BP508 on 2020-07-27 05:02:28 by Aaron David Fairbanks                approved
-DATA

  

BP508 on 2020-07-26 06:13:18 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-07-25 22:33:18 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-07-22 20:36:44 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-07-17 20:49:22 by Leo Crabbe                approved
+DATA

  

BP508 on 2020-07-08 02:19:04 by Aaron David Fairbanks                approved
+DATA

  

BP508 on 2020-07-08 02:18:39 by Aaron David Fairbanks                approved
-DATA

  

BP508 on 2020-07-08 02:07:51 by Aaron David Fairbanks                approved
-DATA

  

BP508 on 2020-07-08 02:07:42 by Aaron David Fairbanks                approved
+DATA

  


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