Any solution to the problem of running out of date in one path?Tom On Thursday, October 12, 2023 at 11:02:06 AM CDT, discuss-gnuradio-requ...@gnu.org <discuss-gnuradio-requ...@gnu.org> wrote: Send Discuss-gnuradio mailing list submissions to discuss-gnuradio@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.gnu.org/mailman/listinfo/discuss-gnuradio or, via email, send a message with subject or body 'help' to discuss-gnuradio-requ...@gnu.org You can reach the person managing the list at discuss-gnuradio-ow...@gnu.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Discuss-gnuradio digest..." Today's Topics: 1. Some GRC files run with no errors but don't plot (tom sutherland) 2. Re: Some GRC files run with no errors but don't plot (Marcus Müller) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Oct 2023 11:36:24 +0000 (UTC) From: tom sutherland <alphatoz...@yahoo.com> To: "discuss-gnuradio@gnu.org" <discuss-gnuradio@gnu.org> Subject: Some GRC files run with no errors but don't plot Message-ID: <1055450876.6185365.1697110585...@mail.yahoo.com> Content-Type: text/plain; charset="utf-8" I have a simple grc file that shows the difference in Interpolation and Decimation using the Rational Re-sampler blocks. The program runs once, a "Time Sink" shows the signals(once) and then stops plotting and the Frequency Sink does not show a frequency plot at all. I've had other programs that do similar things, runs but nothing shows, once and freezes or for a few cycles and stops. Any thoughts on causes and /or how to solve/debug it would be appreciated. I am running GRC 3.10.5.0 on a Windows 10 Enterprise 12th Gen i7 machine with 32GB RAM. I've attached the grc/py and plot files. Thanks...Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20231012/233cf07a/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: RationalResamplerInterpAndDecimation.grc Type: application/octet-stream Size: 7734 bytes Desc: not available URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20231012/233cf07a/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: RationalResamplerInterpAndDecimation.png Type: image/png Size: 83107 bytes Desc: not available URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20231012/233cf07a/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: RationalResamplerInterpAndDecimation.py Type: application/octet-stream Size: 10462 bytes Desc: not available URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20231012/233cf07a/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1697110214110blob.jpg Type: image/png Size: 255699 bytes Desc: not available URL: <https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20231012/233cf07a/attachment-0001.png> ------------------------------ Message: 2 Date: Thu, 12 Oct 2023 13:59:07 +0200 From: Marcus Müller <marcus.muel...@ettus.com> To: discuss-gnuradio@gnu.org Subject: Re: Some GRC files run with no errors but don't plot Message-ID: <d126e12d-4b3d-4cfa-89a1-b04489a37...@ettus.com> Content-Type: text/plain; charset=UTF-8; format=flowed I think I can explain! Both sinks need to always consume the same number of input items from all their inputs. So, even if you disabled the time sink, the upper sink would quickly grind to a halt, because the "lowest rate" Rational Resampler (interp=1,decim=4) would not be able to produce the samples needed to keep up with the "highest rate" resample (interp=4, decim=1). Both resamplers work on the same input, just that the lowest-rate one takes 16× the amount of input to produce the same amount of output as the highest-rate one. Since both share the same input, and that input has a finite buffer, this can't work for long. So, your flow graph has an architectural shortcoming, either way. The time sink hits that bug you've built quicker, because it has no throttle in the way. Best, Marcus ------------------------------ Subject: Digest Footer _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ------------------------------ End of Discuss-gnuradio Digest, Vol 252, Issue 6 ************************************************