discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] self.set_min_noutput_items() is not a valid pytho


From: Marcus Müller
Subject: Re: [Discuss-gnuradio] self.set_min_noutput_items() is not a valid python command in gnuradio ?
Date: Sat, 08 Mar 2014 14:08:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Activecat,

On 08.03.2014 13:54, Activecat wrote:
> Dear Marcus,
> 
> Thanks for pointing out, I've corrected it to std::max. It still
> doesn't seem to produce correct output when the d_iFactor changes 
> on the fly.
> 
> BTW this flow graph consists of other built-in blocks like Low Pass
> Filter, Signal Source etc, whose outputs also depends on the
> instantaneous Sample Rate (samp_rate). If one of these built-in
> blocks doesn't work well when samp_rate changes on the fly, then
> that could cause the flow graph to produce wrong result too.
> 
But, well, these blocks don't change output ratios based on sample_rate..

> My main concern is whether set_output_multiple() and 
> set_min_noutput_items() works on the fly in general. As your answer
> is yes to both, then I think that is good enough for this thread.
:)
> 
> The general_work() is called repeatedly and problematically only if
> it return 0 and consume 0.  With the set_min_noutput_items() works
> on the fly, this problem doesn't happen anymore.  Now the problem
> is the incorrect output when the d_iFactor changes on the fly.
> 
> Meanwhile, as you had advised, I had tried to see the parameters
> that forecast() and general_work() are called with. Refer below
> verbose message. When the flow chart started, the initial values
> are samp_rate=32k, change_rate=64; hence d_iFactor = 32k/64 = 500. 
> At line 24 the samp_rate is changed to 64k on the fly by the user.
> So now d_iFactor = 64k/64 = 1000. Every parameters and return
> values seem to be correct, but the flow graph output becomes wrong
> after line 24.
Wrong in which way?

Greetings,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTGxZlAAoJEBQ6EdjyzlHtzVkH/2yu6GyvUr2aevwric3ER7iS
kuZ0drhy9C1PweSqPeBBPSRdOxqX0nDsYD9O+f+k03bGLyfidwLQ8jlt0J9wX9Vv
82yvxGkEVf3OShAUB44uPFEUOvbAYef697jjP0YmDSrbGc/XQ7+FpngJmOqhqBpe
AsiqmKpLaYJ9rvKsButGaj6mnT98mnWQt2+GTk5bTzZ0w9O1NVKpo6odaFVMp+hM
+OjW7w+vV5YfyRw3OhhyrjoXCMOtw1oXz4aUbHuKqXfFF12GJYA3mrElKuELK7E+
fnC24SD8rrpytdjTTwj+sAoebJhxDymb8oCJ2UwR7f13CgmWrmat+p0J9KS6aUY=
=FeQj
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]