[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] gmsk error
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] gmsk error |
Date: |
Tue, 6 Dec 2005 14:24:43 -0800 |
User-agent: |
Mutt/1.5.6i |
On Tue, Dec 06, 2005 at 03:57:26PM -0500, address@hidden wrote:
> What are the parameters/arguments (omega, gain_omega, me, gain_mu...) used
> in gr_clock_recovery_mm_xx and how do you determine what they should be?
Quick answer:
use the defaults.
Involved answer:
It's a Mueller and Müller (M&M) discrete-time error-tracking synchronizer.
See "Digital Communication Receivers: Synchronization, Channel
Estimation and Signal Processing" by Heinrich Meyr, Marc Moeneclaey, & Stefan
Fechtel.
ISBN 0-471-50275-8.
> I have been trying to find in the Python literature what the follow syntac
> represent.
>
> """
> ...
> @param omega: nominal relative freq (defaults to spb)
> @type omega: float
> @param gain_mu: controls rate of mu adjustment
> @type gain_mu: float
> @param mu: fractional delay [0.0, 1.0]
> @type mu: float
> @param omega_relative_limit: sets max variation in omega
> @type omega_relative_limit: float, typically 0.000200 (200 ppm)
> @param freq_error: bit rate error as a fraction
> @param float
> """
>
> Is this some type of preprocessro directive?
This is "epydoc" format. http://epydoc.sf.net
Eric
- RE: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/01
- RE: [Discuss-gnuradio] gmsk error, Robitaille, Michael, 2005/12/02
- Re: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/05
- Re: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/05
- Re: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/06
- Re: [Discuss-gnuradio] gmsk error,
Eric Blossom <=
- Re: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/06
- Re: [Discuss-gnuradio] gmsk error, address@hidden, 2005/12/06