Re: Are there firls and kaiser filter methods for C++ OOT?

[GNU Radio, the Free & Open-Source Toolkit for Software Radio]

Hello George,
Yes, there is. Check this out:
https://www.gnuradio.org/doc/doxygen/firdes_8h_source.html
https://www.gnuradio.org/doc/doxygen/pm__remez_8h.html
BR,
Marcin

pon., 14 lut 2022 o 00:07 George Edwards 
napisał(a):

> Hello GNURadio Community,
>
> I am designing a Gnuradio OOT block in C++. Are there firls and kaiser
> filter methods (analogous to the scipy package methods that one would use
> in Python OOT) that I can call to generate coefficients.
>
> Thank you!
>
> Regards,
> George
>

Are there firls and kaiser filter methods for C++ OOT?

[George Edwards]

Hello GNURadio Community,

I am designing a Gnuradio OOT block in C++. Are there firls and kaiser
filter methods (analogous to the scipy package methods that one would use
in Python OOT) that I can call to generate coefficients.

Thank you!

Regards,
George

Re: segfault in 3.10.1.1

[Franco VENTURI]

Steve,
I am glad to hear that you are now able to run GNU Radio Companion there.
I am not familiar with the internals of GTK and GObjects and I can't really 
help you there.

However this morning I ran GRC on a simple FM receiver example I have, and I 
used strace to track the calls to 'execve':

strace -f -e execve -o /tmp/grc.trc gnuradio-companion FM-Receiver-RSPdx.grc

The output from 'strace' here shows only these processes being launched 
directly by GRC:

6439 execve("/usr/local/bin/gnuradio-companion", ["gnuradio-companion", 
"FM-Receiver-RSPdx.grc"], 0x7ffc04bea340 /* 75 vars */) = 0
6450 execve("/bin/gsettings", ["gsettings", "get", 
"org.gnome.desktop.interface", "gtk-theme"], 0x55652906a3d0 /* 75 vars */) = 0
6456 execve("/usr/bin/python3", ["/usr/bin/python3", "-uc", "import runpy; 
runpy.run_path('/u"...], 0x55652906a3d0 /* 75 vars */) = 0
6529 execve("/usr/bin/python3", ["/usr/bin/python3", "-u", 
"/home/franco/SDR/gr-sdrplay3/exa"...], 0x55652906a3d0 /* 75 vars */) = 0

I don't see GRC launching other additional processes directly; in my case some 
of processes you show in your message are part of the OS common services (for 
instance here I see a service called 'dbus-broker').

Franco



> On 02/12/2022 10:25 PM Steven Barbo  wrote:
> 
> 
> Hello patient and helpful folks, hope this day finds you well.
> Have had some "success", gui runs appears work fine, not calling the 
> offending functions  g_free and ffi_closure_free in
> gobject-introspection-1.70.0/girepository/girffi.c
> 
> guessing these are the parameter linkages and walking trail for circuit 
> path for each block etc.?
> no idea where this is even called from, wow there is a lot going on...
> 
> **
>  * g_callable_info_free_closure:
>  * @callable_info: a callable info from a typelib
>  * @closure: ffi closure
>  *
>  * Frees a ffi_closure returned from g_callable_info_prepare_closure()
>  */
> void
> g_callable_info_free_closure (GICallableInfo *callable_info,
>   ffi_closure*closure)
> {
>   GIClosureWrapper *wrapper = (GIClosureWrapper *)closure;
> 
>   //g_free (wrapper->ffi_closure.cif->arg_types);
>   //ffi_closure_free (wrapper->writable_self);
> 
>   printf("%s ( [callable_info-> dummy1=%d, dummy2=%d, dummy3=%x, 
> dummy4=%x, dummy5=%x, dummy6=%d, dummy7=%d, 
> padding[0]=%x,padding[1]=%x,padding[2]=%x,padding[3]=%x], [closure-> ... ] 
> )\n",__func__,callable_info->dummy1,callable_info->dummy2,callable_info->dummy3,callable_info->dummy4,callable_info->dummy3,callable_info->dummy6,callable_info->dummy7,callable_info->padding[0],callable_info->padding[1],callable_info->padding[2],callable_info->padding[3]);
> }
> 
> 
> typedef struct _GIBaseInfoStub {
>   /*  */
>   gint32 dummy1;
>   gint32 dummy2;
>   gpointer dummy3;
>   gpointer dummy4;
>   gpointer dummy5;
>   guint32  dummy6;
>   guint32  dummy7;
>   gpointer padding[4];
> } GIBaseInfo;
> 
> /**
>  * GICallableInfo:
>  *
>  * Represents a callable, either #GIFunctionInfo, #GICallbackInfo or
>  * #GIVFuncInfo.
>  */
> 
> 5.1# gnuradio-companion --log debug
> 
> [DEBUG] Starting GNU Radio Companion (3.10.2) (main.py:70)
> [DEBUG] Loading platform (main.py:76)
> [DEBUG] Loading application (main.py:86)
> [DEBUG] Running (main.py:88)
> <<< Welcome to GNU Radio Companion 3.10.1.1 >>>
> 
> Block paths:
> /usr/share/gnuradio/grc/blocks
> 
> Loading: "/UNUSED/testing123.grc"
> >>> Done
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=6, 
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=529188, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=6, 
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=529188, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> 
> Generating: '/UNUSED/testing123.py'
> 
> Executing_callable_info_free_closure ( [callable_info-> dummy1=2, 
> dummy2=3, dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=52, 
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=76, 
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> g_callable_info_free_closure ( [callable_info-> dummy1=2, dummy2=75, 
> dummy3=1d0b030, dummy4=0, dummy5=1d0b030, dummy6=86468, dummy7=0, 
> padding[0]=0,padding[1]=0,padding[2]=0,padding[3]=0], [closure-> ... ] )
> 

Re: Tutorial on Hier Block and Parameters

[Volker Schroer]

I think, the PYTHONPATH should not start with :
and it is not required that the PYTHONPATH contains the location of your
grc files.
~/.grc_gnuradio is not a file but a directory. If this diretocry does
not exist, just create it.

Copy your generated *.yml and *.py from your working directory to
~/.grc_gnuradio


What's the output of grc when you start it?

On my system it looks like:

grc
<<< Welcome to GNU Radio Companion v3.10.0.0-22-g7712360d >>>

Block paths:
/home/schroer/.grc_gnuradio
/usr/local/gnuradio/share/gnuradio/grc/blocks

The second path points to the gnuradio blocks and depends on your
installation., probably
/usr/share/gnuradio/grc/blocks/

If grc references your .grc_gnuradio directory , you should find your
created blocks in grc.

If the reference is missing have a look at
~/.gnuradio/config.conf

There should be a section like

[grc]
canvas_default_size = 1280, 1024
canvas_font_size = 8
default_flow_graph =
enabled_components =
testing-support;python-support;man-pages;gnuradio-runtime;gr-ctrlport;gnuradio-companion;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;*
alsa;* oss;gr-channels;gr-pdu;gr-iio;*
libad9361;gr-qtgui;gr-trellis;gr-utils;gr_modtool;gr_blocktool;gr-vocoder;gr-network
global_blocks_path = /usr/local/gnuradio/share/gnuradio/grc/blocks
local_blocks_path =
xterm_executable = /usr/bin/xterm

Here you can specify your local_blocks_path


I hope this helps.

-- Volker


The output is

echo $PYTHONPATH
:/home/grctut/the folder where I am saving working grc files.
However, I am able to use GRC for other purposes normally. I notice that
GRC blocks (.yaml files) are in /usr/share/gnuradio/grc/blocks/ folder.
Also there is no .grc_gnuradio file in my home directory. However, there
is a .gnuradio folder with a prefs folder and config.conf and grc.conf
files. prefs folder has a vmcircbuf_default_factory file.



--

Message: 3
Date: Sat, 12 Feb 2022 12:07:37 +0100
From: Volker Schroer mailto:dl1...@gmx.de>>
To: discuss-gnuradio@gnu.org 
Subject: Re: Tutorial on Hier Block and Parameters
Message-ID: mailto:a21da2e7-fea7-ecce-9de3-4b1567795...@gmx.de>>
Content-Type: text/plain; charset=UTF-8; format=flowed

Yes, that the generated hier block files go to the working directory of
~/.grc_gnuradio is a known bug.

See:
https://github.com/gnuradio/gnuradio/pull/5547


What is the result of

echo $PYTHONPATH


-- Volker
 > Hi,
 > I am facing a problem  using the tutorial. My installation is from
 > repository.
 > I am using GRC3.10.1.1(Python3.8.10) on OS Ubuntu 20.04.3LTS.
 > When I generate the flow graph, output files are going to the working
 > directory and not .grc_gnuradio as mentioned in tutorial. Probably
 > because of this, they are not appearing in the block tree of GRC.
Also,
 > I get these messages on the terminal.
 > Warning: vocoder_codec2_decode_ps - option_attributes are for enums
 > only, ignoring
 >  >>> Warning: vocoder_codec2_encode_sp - option_attributes are
for enums
 > only, ignoring
 > May not be relevant, but I observe whenever I open the terminal, the
 > following line appears before the command prompt.
 > PYTHONPATH: command not found
 > Please help me in configuring GRC properly. Or do i have to install
 > gnuradio in home directory instead of system installation?
 >
 > --
 > Best Regards,
 > vsrk sarma

--
Best Regards,
vsrk sarma

Re: [VOLK] Release 2.5.1

[Jeff Long]

Fons - filesystem is used for the volk_profile utility.

Chris - do not assume ABI compatibility. A number of small things have
changed in ".h" files.

On Sat, Feb 12, 2022 at 6:19 PM Chris Vine  wrote:

> On Sat, 12 Feb 2022 11:40:26 +0100
> Johannes Demel  wrote:
> > Hi everyone!
> >
> > You can find the news at https://www.libvolk.org/release-v251.html as
> well.
> >
> > We have a new VOLK release! We are happy to announce VOLK v2.5.1! We
> > want to thank all contributors. This release wouldn't have been possible
> > without them.
>
> Hi,
>
> Is this ABI compatible with volk-2.5.0 (or put another way, if I
> upgrade from volk-2.5.0 will I need to recompile gnuradio)?
>
> Chris
>
>