Skip to main content

Electric Fields, Charge Distributions, and the GRE

Reviewing for the GRE physics subject test, I've frequently come across questions like:

Given a distribution of discrete charges, (as shown in the diagram), determine the electric field at a given point r, (also shown in the diagram).



Formula for the Electric Field from a Distribution of Charges
The distribution of charges I've seen in sample questions have, so far, involved only finite numbers of point charges, so the electric field equation can be written as a sum:

where

is the distance from a charge contributing to the sum to the location where the electric field is being measured, q is the value of the particular charge, and u is the unit vector pointing from the contributing charge to the field measurement point.

This can be separated into x and y components:

where theta is the angle between the particular charge and the point where the field is being measured with respect to the x axis. Using these formulas, it's just a matter of summing up the contribution of each point charge to the electric field at the location defined by the problem.

So, the standard method is to determine the x and y contribution from each charge at the location specified by the problem, and then simply sum up all the contributions. Let's try one out:

Example

First, we'll try the example from the diagram above:
The contributions from each charge are shown in the table below:



Here's one more example with three equal charges space equally around the unit circle:

The angles used to calculate the x and y contributions of each field are also shown.

The contributions from each charge are shown in the table below:



The Trick
Both of these examples also point out a type of 'trick' question that appears in the samples. When a set of equal charges is evenly spaced around a circle surrounding the field measurement point, the total field is 0. Watch for this pattern.

Handy Stuff
GRE Physics Sample Test [pdf]
Other links to GRE sample questions


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