Andrew Cooke | Contents | Latest | RSS | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

Surprise Paradox; [Books] Good Author List; [Computing] Efficient queries with grouping in Postgres; [Computing] Automatic Wake (Linux); [Computing] AWS CDK Aspects in Go; [Bike] Adidas Gravel Shoes; [Computing, Horror] Biological Chips; [Books] Weird Lit Recs; [Covid] Extended SIR Models; [Art] York-based Printmaker; [Physics] Quantum Transitions are not Instantaneous; [Computing] AI and Drum Machines; [Computing] Probabilities, Stopping Times, Martingales; bpftrace Intro Article; [Computing] Starlab Systems - Linux Laptops; [Computing] Extended Berkeley Packet Filter; [Green] Mainspring Linear Generator; Better Approach; Rummikub Solver; Chilean Poetry; Felicitations - Empowerment Grant; [Bike] Fixing Spyre Brakes (That Need Constant Adjustment); [Computing, Music] Raspberry Pi Media (Audio) Streamer; [Computing] Amazing Hack To Embed DSL In Python; [Bike] Ruta Del Condor (El Alfalfal); [Bike] Estimating Power On Climbs; [Computing] Applying Azure B2C Authentication To Function Apps; [Bike] Gearing On The Back Of An Envelope; [Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life

© 2006-2017 Andrew Cooke (site) / post authors (content).

Hyperloop, Waves, and Unexciting Reality

From: andrew cooke <andrew@...>

Date: Sun, 28 Jul 2013 20:18:55 -0400

There's been some discussion on HN and blogs about Hyperloop:

http://charlesalexander2013.wordpress.com/2013/07/18/hyperloop-riding-sounds-density-peak-to-exploit-the-drag-equation/
http://conscienceofanentrepreneur.blogspot.com/2013/07/hyperloop-lets-you-travel-on-resonant.html
https://news.ycombinator.com/item?id=6117114

However, people don't seem to be thinking the physics through.  It's not as
simple, obvious, or right, as it seems (as far as I can tell).  I may be
wrong, of course, but here's my take:


First, the general idea is that there is a closed loop, filled with air, and
that some kind of cabin "rides" a "wave" around the loop.  That's the vision,
which is certainly intuitively attractive.

However, it seems to be ignoring some practical details that typically come
out of the maths in problems like this (here's a good place for a disclaimer:
what follows is just "general knowledge" from studying simple physical systems
as a student - I have a degree in physics (more or less) - and it may be that
I am using too simple an approximation, or have forgotten something...)


First, lets consider a single, traveling wavefront.  Imagine standing in the
loop and shouting in one direction.  The sound wave travels round the loop and
eventually you hear it coming from behind you (assuming you shouted hard
enough).

That's cool, and it's what seems to be being discussed in the first link
above.  But it's not a steady state solution.  If you used that in a real
system then you'd need something making a huge shout for each journey.  And
the shout would die out as it traveled round the loop.  That doesn't sound
very efficient.


There's an obvious fix to this: generate a series of shouts that are timed so
that each shout coincides with a previous one.  In other words, there's an
exact number of "shout wavelengths" round the loop.  This gives a steady state
solution that's likely much more efficient: you've got a resonant system and
you need less energy to keep it going.

But it won't work.

This solution is called a "standing wave".  And it's called "standing" for a
reason.  The waves don't travel.  Or, if you like, there are two equal but
opposite sets of waves, traveling in opposite directions.  The two views are
equivalent.  And that means that there's no moving wavefront to "ride" (or,
equivalently, that there's an equal and opposite moving wavefront that screws
you up).


The second link recognises this and hopes that there is some other solution.
And it's likely that there is.  It's likely that you can simply add a constant
velocity to all the air particles.  So instead of them being, on average, in
one place (but vibrating backwards and forwards), they are also moving round
the loop.

If do that, then you rotate the high pressure nodes in the standing wave
pattern.  So there's a pressure wave to ride.  But you're not really gaining
much, because the "win" in the first link no longer exists.

The first link hoped to avoid the costs of moving at high speed relative to
the surrounding air.  But in our current solution the air is moving on average
too.  So you might as well not bother with the waves at all.  Just move the
air round the loop in a steady stream, at the same speed as the cabin.

And that works fine but (1) isn't as cool and (2) implies lots of losses from
the wind against the walls of the tunnel.


So I don't see a consistent, useful, efficient physically reasonable argument
for wave riding.

Andrew

Wrong!

From: andrew cooke <andrew@...>

Date: Mon, 29 Jul 2013 21:35:42 -0400

A comment on HN (link above) pretty much convinced me I'm wrong on this.  I
think I am biased by solving problems with fixed nodes.  There should be a
solution that has moving waves and stationary (on average) air.  Andrew

Comment on this post