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

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

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (keyword @ignoreimperfections), the keyword "discontinuous" can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged "ignoreimperfections" in the first place if the underlying idea were such that several small changes could switch an example's side or could make it unsortable.)

Continuous implies @perfect.

Continuous implies @pixelperfect.

@Gap implies continuous.

Discontinuous Bongard Problems are often @exact.

Continuous Bongard Problems tend to either be @fuzzy or otherwise either have a @gap or be not @allsorted.

See BP1140, which is about any (perhaps large) additions of detail instead of small changes.

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

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

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (keyword @ignoreimperfections), the keyword "discontinuous" can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged "ignoreimperfections" in the first place if the underlying idea were not "continuous": small changes could switch an example's side (the keyword "discontinuous") or could make it unsortable.)

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

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

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (keyword @ignoreimperfections), the keyword "discontinuous" can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged "ignoreimperfections" in the first place if the underlying idea were such that small changes could switch an example's side (keyword "discontinuous") or could make it unsortable.)

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

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

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (keyword @ignoreimperfections), the keyword "discontinuous" can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged @ignoreimperfections in the first place if the underlying idea were such that small changes could switch an example's side (keyword "discontinuous") or could make it unsortable.)

Left examples have the keyword @discontinuous on the OEBP.

Right examples have the keyword @continuous on the OEBP.

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (keyword @ignoreimperfections), the keyword @discontinuous can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged @ignoreimperfections in the first place if the underlying idea were such that small changes could switch an example's side (keyword @discontinuous) or could make it unsortable.)

Left examples have the keyword @discontinuous on the OEBP.

Right examples have the keyword @continuous on the OEBP.

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (@ignoreimperfections), the keyword @discontinuous can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged @ignoreimperfections in the first place if the underlying idea were such that small changes could switch an example's side (keyword @discontinuous) or could make it unsortable.)

@Continuous implies @perfect.

@Continuous implies @pixelperfect.

@Gap implies @continuous.

Discontinuous Bongard Problems are often @exact.

Continuous Bongard Problems tend to either be @fuzzy or otherwise either have a @gap or be not @allsorted.

See BP1140, which is about any (perhaps large) additions of detail instead of small changes.

@Continuous implies @perfect.

@Continuous implies @pixelperfect.

@Gap implies @continuous.

Discontinuous Bongard Problems are often @exact.

Continuous Bongard Problems tend to either be @fuzzy (right-BP508) or otherwise either have a @gap (right-BP964) or be not @allsorted.

See BP1140, which is about any (perhaps large) additions of detail instead of small changes.

Left examples have the keyword @discontinuous on the OEBP.

Right examples have the keyword @continuous on the OEBP.

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings (@ignoreimperfections), the keyword @discontinuous can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged @ignoreimperfections in the first place if the underlying idea were such that small changes could switch an example's side (keyword @discontinuous@) or could make it unsortable.)

@Continuous" implies @perfect.

@Continuous" implies @pixelperfect.

@Gap implies @continuous.

Discontinuous Bongard Problems are often "exact" (left-BP508).

Continuous Bongard Problems tend to either be "fuzzy" (right-BP508) or otherwise either have a "gap" (right-BP964) or be not "allsorted" (right-BP509).

See BP1140, which is about any (perhaps large) additions of detail instead of small changes.

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

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

In a "continuous" Bongard Problem, no small change should outright flip an example's sorting. It IS allowed for a small change to make an example sorted slightly more ambiguously.

If a Bongard Problem is shown with imperfect hand drawings ("ignoreimperfections" right-BP913), the keyword "discontinuous" can be applied ignoring this. For instance, a hand-drawn version of BP344 would still be tagged "discontinuous", even though it would show examples wrong by small amounts.

(Note: a BP would only be tagged "ignoreimperfections" in the first place if the underlying idea were such that small changes could switch an example's side (keyword "discontinuous") or could make it unsortable.)