Update on Radio Mapping Baylor Peak

I'm hoping to do a few more ham radio POTA activations of New Mexico parks today. In prep, here's a bit more data on the Organ Mountains-Desert Peaks activation.

In documenting the 'add your own QSO' feature on the RBN tracker, I created a few interesting pictures I thought I'd add as an update to my earlier ocmments on radio optics and mountains. The following picture shows the spots, (blue lines), and QSOs, (green lines), made during a few days worth of activations. From the perpective of the entire countyr, a rough pattern becomes apparent:

Zooming into the peak, we can see why:

(Basically, the neighboring mountain is affecting propagation.)

Of particular interest to me though: notice the pattern of the QSOs when the radio was located further up Baylor Peak. There are fewer QSOs headed out to the North. I think (but don't have enough data to support) this might have been caused by the antenna's angle of radiation being reduced due to the steeper slopes on either side of it from that location..

I had gone up the mountain hoping to get a better line of sight around the peak, but I think I may have also lowered the angle of radiation (check out the nice long QSO to Florida, although the QSO to near DC was from furhter down the slope; I need more data) with those two slopes to such an extent that the radio was transmitting straight into the peak to the north.

For simplicity, first consider an antenna on the top of a hill with a constant slope downward. The general effect is to lower the effective elevation angle by an amount equal to the downslope of the hill. For example, if the downslope is −3° for a long distance away from the tower and the flat-ground peak elevation angle is 10° (due to the height of the antenna), then the net result will be 10° − 3° = 7° peak angle.

--from the very fb "Antenna Height and Communications Effectiveness" by By R. Dean Straw, N6BV, and Gerald L. Hall, K1TD.

References:

POTA is Parks on the Air, an organization of ham radio operators who operate from parks all over the world. It's a fun way to get outdoors with a radio.

Comments

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

Copasetic Flow

Search This Blog