Hmm! I don't have any trouble saying/hearing that light interacts with the aperture! If it doesn't, then why does sticking in the aperture cause funny stuff to happen? (Google, "define: interact", To act together or affect each other. The shape of the wavefront is changed by size of the aperture, and the aperture -- or at least the stop that forms the aperture -- experiences a small force and even gets warm if the light is bright enough. Sure sounds like an interaction to me.)With water I suppose interact would not be so bad, as you might think of one wave lifting another but unless you believe in the ether that works less well for light. As I said, pedantry and certainly not as bad as saying the light interacts with the aperture.
The grid-cell simulation is in Java. Java has a reputation for slow execution, but in fact it runs almost as fast as C/C++ when programmed correctly. This simulation runs at over 150 megaflops on my 4 year old Pentium 4 home machine (2.8 GHz). I've clocked an eigensolver on my office laptop at over 250 megaflops. This is all on one cpu.Graham Stabler wrote:What are you programming in?
The animated image in my previous post is just a sketch, hacked together in Photoshop.
"Flavor" is exactly what I was going for in that sketch.
It's hard to know what to draw to get the message across.
I played around this morning with interfering waves. Most of the pictures ended up more confusing than helpful. (Remember Moiré patterns?)
Here's the best I could come up with. One wave perpendicular to the sensor, interfering with a second wave at varying angle.

I don't know what I think about these.
It's easy for me to imagine a newbie understanding that the distance between peaks and valleys in a single wave intersecting a plane will depend on angle. Maybe it's also easy for the newbie to understand that the distance between peaks and valleys in the interference pattern will depend on angle too, but it's not so easy to understand exactly how. Notice, for example, that the lines of nulls in the interference pattern do not have the same angle as either of the two interfering beams.
Of course (I say after considerable thought) there's a simple explanation using symmetry for why that has to be -- the axis of the interference pattern has to be midway between the axes of the beams. But then why is the distance between peaks and valleys of the interference pattern just the same as the distance between peaks and valleys of the slanted wave? (Yeah, I know, there's a simple explanation for that too. But these questions just keep coming...)
BTW, these latter illustrations are coming pretty much straight out of Java -- this time a code that just computes a bunch of phases and cosines and adds 'em up. The bottom part ("what the sensor sees") does come from a bit of Photoshop work so that I could manually choose the best y-location to pick up the interference pattern from. I could have done that computationally, but to start with it was easier to just do it visually.
--Rik