Re: difference between linux distro for running gnuradio
Hi Robin, I am using several virtual machines on Linux (Debian Bookworm / x64) with different gnuradio versions. I failed using different versions of gnuradio on the same machine when an update arrives. VMware ist working well. For older versions 3.7 and 3.8 I keep VMs in my archive. BTW: I compile gnuradio from source. Everything workes beside the filter tool :-( Tom Am 27.05.2024 um 00:10 schrieb robin ivetic: Hello, I don't know if this proper place to ask such question, or to whom ask about that, but I notice that is much difference between GNURADIO speed running on different distro, for example I choose couple of distros with already compiled package, just to avoid buidling from source. I'm still using LimeSDR USB, and like to used older version of gnuradio which supports gr-limesdr, although can use with soapy wrapper under gr-osmosdr. Basically, I'm using osmosdr block, and I notice that Arch linux with gnuradio 3.10.10 running slower than Fedora 39 with 3.10.6. Arch was tested with SSD drive, Fedora with mechanical, although tests made with sysbench shows better r/w paramters made on Arch, can confirm that python scripts run faster on Fedora 39 Workstation Server, so where is the catch. Arch is known for speed and "clean" package build, tested version is not from AUR think 3.11, and can confirm that I made volk_profile before start using gnuardio. Where can I learn more about that topic, ask distros developer builder, can you give me advice about that matter Robin
Re: difference between linux distro for running gnuradio
Hi Robin On 2024-05-27 12:10 AM, robin ivetic wrote: Hello, I don't know if this proper place to ask such question, or to whom ask about that, but I notice that is much difference between GNURADIO speed running on different distro, for example I choose couple of distros with already compiled package, just to avoid buidling from source. and that's *exactly* what we recommend! Make your life as easy as possible. I'm still using LimeSDR USB, and like to used older version of gnuradio which supports gr-limesdr, although can use with soapy wrapper under gr-osmosdr. You should be using the wrapper for SoapySDR instead, because that would be supported directly by the gr-soapy that's part of GNU Radio :) Basically, I'm using osmosdr block, and I notice that Arch linux with gnuradio 3.10.10 running slower than Fedora 39 with 3.10.6. Arch was tested with SSD drive, Fedora with mechanical, although tests made with sysbench shows better r/w paramters made on Arch, can confirm that python scripts run faster on Fedora 39 Workstation Server, so where is the catch. Sounds like arch uses different build options. You can compare `gnuradio-config-info --cflags` between the two platforms to see what they're doing differently, if anything. Historically, Fedora did have stronger stack protection flags than arch, if I remember correctly, but I have positively no idea whether that's still the case. And, maybe you ran `volk_profile -b` on one machine and not the other? Arch is known for speed and "clean" package build, Reasonable people can disagree about that. I personally agree with "arch package scripts are very easy", but imho that comes at the price of not always being adequate. Again, let's not get into the weeds of discussing distros in general; that would just lead to disagreement without benefit to your problem :) I've never heard arch being known for being especially fast. Maybe in the "rolling release" sense, but not in the software optimization sense. tested version is not from AUR think 3.11, There's no GNU Radio 3.11; we just label our git development versions from the main branch "3.11-gHASH", but seriously, these are *not* for public consumption but development versions, so you'd probably be better off with a non-AUR source that gives you GNU Radio 3.10.x.x. SO: I think you're doing everything right if you say you have GR 3.10.10.0. and can confirm that I made volk_profile before start using gnuardio. Ah, there goes my theory. Best regards, Marcus
Selector Block GNU radio
Hello, GNU Radio version 3.10 My requirement is to switch between multiple waveforms. For this purpose, I think I should use the Selector Block. However, my issue is that each waveform chain has a different sampling rate: Waveform1 has 1 MSPS and Waveform2 has 2 MSPS, for example. Can the Selector Block support inputs with different sampling rates like Waveform1, Waveform2, etc.? I plan to switch the runtime sampling rate of the Source block connected to the output of Selector Block. If this setup is not the right approach, please suggest how to achieve this.
Re: Selector Block GNU radio
Hello! In order to grant good performance, using selector is not a good choice. The best way to achieve reconfiguration is to change modulator (as well as sample rate) at runtime dynamically handling the flowgraph (lock/unlock and stop/start). Have a look to https://wiki.gnuradio.org/index.php/Handling_Flowgraphs. Regards. Ivan > Il giorno 28 mag 2024, alle ore 06:00, Rakesh M ha > scritto: > > > Hello, > > GNU Radio version 3.10 > > My requirement is to switch between multiple waveforms. For this purpose, I > think I should use the Selector Block. However, my issue is that each > waveform chain has a different sampling rate: Waveform1 has 1 MSPS and > Waveform2 has 2 MSPS, for example. > > Can the Selector Block support inputs with different sampling rates like > Waveform1, Waveform2, etc.? > > I plan to switch the runtime sampling rate of the Source block connected to > the output of Selector Block. > > If this setup is not the right approach, please suggest how to achieve this. >
