[Commit-gnuradio] r9583 - gnuradio/trunk/gnuradio-examples/python/digital-bert

[jcorgan]

Author: jcorgan
Date: 2008-09-16 05:15:33 -0600 (Tue, 16 Sep 2008)
New Revision: 9583

Modified:
   gnuradio/trunk/gnuradio-examples/python/digital-bert/README
Log:
doc update

Modified: gnuradio/trunk/gnuradio-examples/python/digital-bert/README
===================================================================
--- gnuradio/trunk/gnuradio-examples/python/digital-bert/README 2008-09-16 
02:59:46 UTC (rev 9582)
+++ gnuradio/trunk/gnuradio-examples/python/digital-bert/README 2008-09-16 
11:15:33 UTC (rev 9583)
@@ -37,9 +37,9 @@
 
 The baseband signal from the USRP is first passed through an AGC to
 establish an average power of 1.0.  It is then passed through a matched
-filter (another RRC), a Costas phase-locked loop, and an M&M bit timing
-recovery loop.  The resulting constellation has an SNR estimation probe
-attached, and is then sliced into a bit stream.
+filter (another RRC), a Costas phase-locked loop, and a Mueller and
+Muller bit timing recovery loop.  The resulting constellation has an SNR
+estimation probe attached, and is then sliced into a bit stream.
 
 The recovered bits are then passed through a 7-bit descrambler.  If
 there are no channel errors, the all 1s sequence is recovered. In the 
@@ -52,8 +52,9 @@
 measurement is inaccurate at high BER rates (>10%) as the error 0s
 begin to overlap.
 
-The benchmark script will, once per second, output the mean symbol power,
-the average noise variance, the estimated SNR, and the average BER.
+The benchmark script will, once per second, output the Costas loop
+frequency offset, the recovered timing error, the estimated SNR, and the
+average BER.
 
 NOTE: The particular SNR estimator used is inaccurate below about 7dB,
 and will report erroneously high values even for random noise.