Skip to main content

Understanding Cylindrical Gradients

We’ve previously looked at how to derive divergence for cylindrical coordinates. If you’re like me though, knowing the rather lengthy derivation won’t help you understand or memorize the resulting formula. So, let’s take a look at why the result makes sense.

The formula for the gradient of a function in cylindrical coordinates is:



Why is the factor of 1/r in the phi term? Remember what question the divergence is asking. We want to find out the amount the function changes vs. a small change in distance along each coordinate’s direction. For coordinates that actually correspond to distances, like x, y, and z of Cartesian coordinates, or r and z of cylindrical coordinates, this is straightforward. The change in the coordinate corresponds to the change in distance along the coordinate.


For coordinates that correspond to angles in the cylindrical coordinate system, there’s an extra twist. The direction of phi always points tangent to a circle centered on the z axis. The small change in distance along the phi or theta coordinate direction is actually a distance measured along the circumference of a circle. The figure below helps me see the issue more clearly. A small change in phi at a radius of 1 means a change of distance of phi times the radius, or 1 phi. At a radius of 2, the same small change in phi results in a change along the circumference of 2 phi.



The distance used in finding the amount the function changes per small change in distance along the phi or theta coordinate is equal to the change in phi times the radius where the change in phi or theta occurs.

So, to properly account for the distance along the phi direction, the divergence has to be written as:

Comments

Popular posts from this blog

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

When Codex CLI Met Port 9 (Debugging WinError 10061 in a Whisper Pipeline)

When Port 9 Ate My Transcript When Port 9 Ate My Transcript A small debugging story about proxies, Codex CLI, and why localhost isn’t always your friend. CopaseticFlow field notes WinError 10061 Codex CLI + Whisper Environment gremlins There’s a particular kind of bug that feels like someone's been messing with your network stack again. You run a script from cmd.exe . It works. You run the exact same script from Codex CLI. It stops with: [WinError 10061] No connection could be made because the target machine actively refused it FFmpeg happily splits the audio. The Whisper API call dies immediately. No 401. No timeout. Just an instant refusal. Translation: that’s not an API error. That’s a socket being rejected. ...