Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a22339c16c7e9de8

Jump to content

Talk:Oloid

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 day ago by ~2026-38138-31 in topic Any uses?

Erroneous statement

[edit]

The second sentence of the section Kinetics reads as follows:

"While rolling, it develops its entire surface: every point of the oloid touches the plane on which it is rolling, at some point during the rolling movement."

This is simply not true. This statement is footnoted as reference [1] (Dirnböck, Hans; Stachel, Hellmuth (1997), "The development of the oloid" (PDF), Journal for Geometry and Graphics 1 (2): 105–118, MR 1622664), but I cannot find any such statement in this paper.

It is completely clear in any case that points of the oloid lying near the centers of the two generating circles can never touch the plane on which it rolls.

Rather, only its points lying on the boundary of its convex hull can touch the plane.Daqu (talk) 19:04, 15 November 2015 (UTC)Reply

Fixed. Thanks. Next time please do it yourself. - üser:Altenmann >t 19:20, 15 November 2015 (UTC)Reply

Incorrect model in "related shapes" section

[edit]

The graphic with the rotatable oloid and sphericon contains an incorrect model of the oloid. It's not a convex figure.  Preceding unsigned comment added by 2602:306:3B1A:C6D0:42D:52B5:344E:90EB (talk) 10:25, 11 February 2018 (UTC)Reply

Any uses?

[edit]

is it just a mathematical curiosity or are there any practical applications of the oloid? ~2026-38138-31 (talk) 20:43, 26 July 2026 (UTC)Reply