Skip to main content

Chain Rule Notes


Not too surprisingly, I suppose, a homework problem in EM recently asked us to find the Laplacian in a different coordinate system.  The system of choice this time was parabolic cylindrical coordinates.  At first, I was unconcerned, I had my handy example on how to do this using the line element for the coordinate system[1].  As it turned out, that trick was disallowed by the assignment itself.  We were required to use the chain rule.  The parabolic coordinate system was defined as the set of equations to the left, (picture 1).


The chain rule of calculus for some odd reason has always been my arch-nemesis.  This is particularly problematic for studying physics because we use it to exhaustion.  I'd hoped to provide a more coherent presentation, but more midterms are coming up.  For now I'll just capture the solution for finding the Laplacian with a few notes as to what can be learned, and the motivations for various steps.

Step one
Write down the u and v differentials in terms of x and y abstractly (picture 2):


The above is essentially the multi-variable chain rule.  If you're me, and you can get to this step, the rest is pretty easy.  One thing to notice here.  As physicists, we're often fond of 'cancelling' differentials like fractions, (as a memory aid if for not other reason).  Our mathematician buddies frequently caution us that this is just wrong.  If you 'cancel' the partial x or partial y differentials above and add, you'll see an example of why you have to be careful with this.

Step 2
Calculate the x and y differentials with respect to u and v, (the missing pieces above).  (picture 3)


Step 3
Since we're looking for the Laplacian which involves second derivatives, have faith, press on, and apply 'partial partial u' and 'partial partial v' to the above equations once more.  Next, add the results together (picture 4).


Step 4
I've done a horrible, horrible thing here, one of the things I hate the most.  I've skipped steps somewhat wholesale.  Do be fair, I did them in my head, so I know they can be done, but there you have it.  I did it. (picture 5)


Here's what we're up to.  We want a Laplacian that we can apply to scalar fields in the parabolic cylindrical coordinate system.  If you look at the last set of results above, you'll notice that all the u and v differentials are bound up behind other differential operators.  That won't do.  We need to be able in the end to be able to apply them directly to functions written in the u, v system.  So, we collect our blind faith again and apply 'partial partial u' and 'partial partial v' calculated in step two to the x and y differentials.  After that, all that remains is to collect like terms and make the whole mess look like a Laplacian.  The z term gets tacked on a the end since it was orthogonal to the other two coordinates in each system and had not u or v dependence.

Hopefully, there will be more on this later.

References:
1.  http://copaseticflow.blogspot.com/2012/09/an-intuitive-way-to-spherical-gradient.html

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. ...