ALF frequency axis display is incorrect

Agreed. At one point the plot tool would observe the sampling frequency metadata tag and adjust accordingly, but before I checked it in I broke something so I had to revert it.

I think an axis of -Fs/2 to +Fs/2 would be fine for the moment (although because we're capturing complex short we can really go from -Fs to +Fs).

I would like -1 to 1 in 0.1's. Then I can easily do the math. I'd like to point to the 19kHz carrier in from the FM demod with some confidence :) Which I think is what Joe is saying ...

Use the metadata numbers if they are present, otherwise default to relative frequency.

I also did some reading on wikipedia,

http://en.wikipedia.org/wiki/Periodogram

http://en.wikipedia.org/wiki/Spectral_estimation

I think the real solution to the problem is to use one of the standard spectral estimation techniques to smooth the data.

Hmm... At some point we need to stop relying on wikipedia's descriptions of well-known mathematical terms, particularly when the articles have nearly no information on the subject.

While the periodogram is not the optimal spectrum estimate technique, it is extremely easy to calculate. For further reading, please see "statistical spectral analysis..." by Gardner. The book is sitting on my desk unless someone has borrowed it.

At this point, I do not care what you call it, as long as the plot tool does some averaging and the amount of averaging is controllable by the user.

Multiplying by two is not the right thing to do.

We're not multiplying by two, we are squaring. That's what you requested.

Don't worry, we're still looking into averaging.

Here is the proposed solution that jd and I have come up with:

User sets a "number of averages type" variable (num_avgs)

The plot tool will average the magnitude of the packets squared over num_avgs packets.

The plot display will refresh every num_avgs packets.

Complaints/comments so far?

Update based on clock time. We may want short averages without killing ALF. Most peoples brains can't process more than a few updates per second.

And just in case, the display rate and number of averages should be set from menu picks on the plot tool window, not by editing variables in the code.

I'm pretty sure it already does update by clock time:

def pushPacket(self, I_data, Q_data):

pushPacket_start_time = _time.time() if (pushPacket_start_time - self.last_plot_time) > self.plot_interval:

self.plotData(I_data, Q_data) self.last_plot_time = pushPacket_start_time

Is what we're really looking for a place to edit this on the GUI? That can be arranged...

Basically, yes. Take a look at the spectrum display on the Tektronix RSA, I believe you can adjust the averaging length and some other things.

Having to edit the plot tool to adjust display parameters is not very user friendly.

The frequency display has been normalized in revision 8004 for the 0.7.0 release. The additional functionality described in the comments is being delayed to a future release.

The additional behavior discussed in this ticket is needed to for the plot tool to be useful for debugging communication systems. This is also a key part of having the plot tool work with continuous data, for which there is another ticket. Sadly, with all the ticket shuffling going on, I cannnot find the ticket.

How about for the next release, fix some tickets from the last release, instead of moving them all to the next release?