From d9ed59dcd0f9eadf4d0999df0506cd42588c92b8 Mon Sep 17 00:00:00 2001 From: Ben Reynwar <ben@reynwar.net> Date: Tue, 14 May 2013 06:58:38 -0700 Subject: doxygen: Update pfb introduction. --- docs/doxygen/other/pfb_intro.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/doxygen/other') diff --git a/docs/doxygen/other/pfb_intro.dox b/docs/doxygen/other/pfb_intro.dox index 2d285f0027..4f77e7cf76 100644 --- a/docs/doxygen/other/pfb_intro.dox +++ b/docs/doxygen/other/pfb_intro.dox @@ -11,7 +11,7 @@ in all sorts of applications. See the documentation for the individual blocks for details about what they can do and how they should be used. Furthermore, there are -examples for these blocks in <b>gnuradio-examples/python/pfb</b>. +examples for these blocks in <b>gr-filter/examples</b>. The main issue when using the PFB blocks is defining the prototype filter, which is passed to all of the blocks as a vector of \p @@ -19,7 +19,7 @@ taps. The taps from the prototype filter which get partitioned among the \p N channels of the channelizer. An example of creating a set of filter taps for a PFB channelizer is -found on line 49 of <b>gnuradio-examples/python/pfb/channelizer.py</b> +found on line 49 of <b>gr-filter/examples/channelizer.py</b> and reproduced below. Notice that the sample rate is the sample rate at the input to the channelizer while the bandwidth and transition width are defined for the channel bandwidths. This makes a fairly long -- cgit v1.2.3