The cycloid is the locus of a point on the rim of a circle of radius a rolling along a straight line. It was studied and named by Galileo in 1599.
There are many ways to write this. The attached GH is only one way to get the basics (a rolling wheel). I didn’t attempt to plot the curve that a point on the rim would produce.
The cycloid has a long and interesting math history. And it brings back memories from 25 years ago when I was artist-in-residence at the Science Museum of Minnesota. As part of an NSF grant to make Calculus-themed exhibits, I built a brachistochrone, and needed a cycloidal tool path for my home-brew CNC router.
Hi Joseph,
This reminds me of my naval architecture graduation thesis. The subject was a design methodology for the trochoidal Whale Tail Wheel ship propulsion system.
This was a horizontal axis propeller, contrary to the famous Voith Schneider vertical axis epi-cycloidal propeller.
Due to its large span of the blades the efficiency was fundamentally higher than conventional propellers. It was discovered by the late Prof Dr. van Manen.
How about using an arbitrary 3D curve instead of a straight line? The top cyan group creates one by modifying three points of an ellipse (still an ellipse from top view).
Funny what is discovered by accident or error… In the lower purple group there is a Value List(blue group) connected to a Stream Filter offering three choices. “Three” is the one I had in mind, “One” and “Two” were discovered along the way.
I’ve seen the Voith Schneider vertical axis propellers (very cool) but not the “Whale Tail” system. Will have to think about that… (P.S. I get it now!)
I just tacked on the four components to the end of your script: grab a spoke, create a point on it, record the points as it moves, and draw a pline through them. Used your radius slider to shrink the wheel so it rotated more times as it rolled on fixed track.
Since it was so few added components I thought the screen shot was unambiguous – but you’re right, it’s almost always better to post the .gh.
P.S. Puzzled that you used PLine and that IntCrv doesn’t work instead?
Just habit, I guess. I’m an old dog, trained in the early AutoCAD days. And since most my work connects geometry to digital motors via linear moves between points in machine-space, PLines are my bread and butter.
Strictly speaking, I’m not sure yesterday’s efforts using PFrames(plural) were accurate, but it had advantages - primarily the ‘precision’ slider and the fact that the “arbitrary” curve was divided evenly. But I tried adapted today’s effort to use the rolling wheel with the arbitrary curve and found problems.
no ‘precision’ slider
using IntCrv(instead of PLine) rounds the peaks of the cycloid curve, perhaps because of the scale? Or maybe I’ve just made mistakes?
No :“rolling wheel” and I’m not sure how to adapt this to an arbitrary curve? But this way of creating a peaked cycloid curve by joining fragments works well.
Curious stuff - I tried to rearrange for t in different ways (which was a little naïve), so that I could plug in grids of points and some weird stuff fell out - I don’t think it’s useful (or correct), but it is moreish