GSoC 2023 Qt Widgets Improvement Week-7 Blog

[Rohit Bisht]

Dear GNU Radio Community,

I hope this email finds you well. I am excited to announce that my latest
blog post covering "GSoC 2023 Qt Widgets Improvement - Week 7" is now live
and accessible to everyone.

In this blog post, I discuss the successful integration of the gr-qtgui
flowgraph’s Qt GUI widget component with popular tools such as QT Creator
and Qt Designer. This integration empowers users with enhanced
customization options for their GUIs, including easy widget placement,
alignment, custom labels, and formatting.

Read the full blog post here:
https://www.gnuradio.org/blog/2023-07-23-GSoC-2023-Qt-Widgets-Improvement-Week-7/

Your feedback and engagement with the GNU Radio community are valuable to
me. I hope you enjoy the blog and find it useful!

Best regards,
Rohit Bisht

Re: update for gr-radar to gnuradio 3.10

[Chris Gorman]

Hello Again,


I have finally finished porting and testing (that I can) of my port of
gr-radar from kit-cel sources.  Unfortunately, I didn't notice that
this had already been done by Ryan Volz.  Thanks to Ryan's sources, I
debugged my qa python scripts and all but one runs properly now.

I plan on leaving this tree and only using it as reference and doing
my development if any on Ryan's tree.  No point on duplicating
efforts.  I am not sure if it is possible, but I would like to try
building an echotimer for the pluto sdr and then adding this to the
gr-radar tree.  (This may be beyond my programming capabilities.)
Anyone with pointers on how to best do this, please email me.

Best regards,

Chris






On Sun, Jul 30, 2023 at 2:52 PM Chris Gorman  wrote:
>
> Hello Again,
>
> Folks might want to consider this port alpha quality.  I have already
> found a few bugs.  (I've done something wrong with pybind11.)  I will
> repost when I have a quasi working port.
>
> Sorry for the distraction.
>
> Chris
>
> On Sun, Jul 30, 2023 at 1:47 PM Chris Gorman  wrote:
> >
> > Hello All,
> >
> > I have just finished a port of https://github.com/kit-cel/gr-radar
> > from gnuradio 3.8 to gnuradio 3.10.  It is available on my github page
> > https://github.com/chrisjohgorman/gr-radar .  I have only done the
> > bare minimum to update it, that is getting it to build.  I followed
> > the 
> > https://wiki.gnuradio.org/index.php/GNU_Radio_3.9_OOT_Module_Porting_Guide
> > , but it is quite possible I've made mistakes.  I welcome patches/pull
> > requests to fix the warning messages, as well as fixes for
> > functionality for those who are interested.  I want to thank the
> > original authors for making this package and all those who have
> > contributed to it.
> >
> > In the event that I have duplicated someone else's efforts in porting
> > this to 3.10, (ie. it has already been done), please let me know.
> >
> > Best regards,
> >
> > Chris

Re: update for gr-radar to gnuradio 3.10

[Ryan Volz]

Hi Chris,

There are a couple pull requests on the kit-cel gr-radar github already. Check 
out https://github.com/kit-cel/gr-radar/pull/57. Or you can find this built as 
a conda package already or in radioconda.

Cheers,
Ryan

On July 30, 2023 2:52:23 PM EDT, Chris Gorman  wrote:
>Hello Again,
>
>Folks might want to consider this port alpha quality.  I have already
>found a few bugs.  (I've done something wrong with pybind11.)  I will
>repost when I have a quasi working port.
>
>Sorry for the distraction.
>
>Chris
>
>On Sun, Jul 30, 2023 at 1:47 PM Chris Gorman  wrote:
>>
>> Hello All,
>>
>> I have just finished a port of https://github.com/kit-cel/gr-radar
>> from gnuradio 3.8 to gnuradio 3.10.  It is available on my github page
>> https://github.com/chrisjohgorman/gr-radar .  I have only done the
>> bare minimum to update it, that is getting it to build.  I followed
>> the 
>> https://wiki.gnuradio.org/index.php/GNU_Radio_3.9_OOT_Module_Porting_Guide
>> , but it is quite possible I've made mistakes.  I welcome patches/pull
>> requests to fix the warning messages, as well as fixes for
>> functionality for those who are interested.  I want to thank the
>> original authors for making this package and all those who have
>> contributed to it.
>>
>> In the event that I have duplicated someone else's efforts in porting
>> this to 3.10, (ie. it has already been done), please let me know.
>>
>> Best regards,
>>
>> Chris
>

Re: Incompatible function arguments

[Marcus Müller]

Hi Jim,

that reads as if `Receive.blocks.head` is not an instance of Head block, but the *type* 
(think as in "blueprint")!


Could you share your hier block's Python source code with us?

Best regards,
Marcus

On 31.07.23 15:40, Elmore's wrote:
I have created a flowgraph which has a hierarchical block called Receive. In the Receive 
block is a Head block.
The primary block has an OOT containing a callback in which I wish to call the reset() 
function in the Head block as follows:

    Receive.blocks.head.reset()
This call results in the following error:
    TypeError: reset(): incompatible function arguments. The following argument 
types are supported:

    1. (self: gnuradio.blocks_python.head) –> None
I’m confused since reset takes no arguments and I don’t understand the meaning of the 
argument types shown.

Jim

 
	Virus-free.www.avg.com 
 



<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Incompatible function arguments

[Elmore's]

I have created a flowgraph which has a hierarchical block called Receive. In 
the Receive block is a Head block.

The primary block has an OOT containing a callback in which I wish to call the 
reset() function in the Head block as follows:

Receive.blocks.head.reset()

This call results in the following error:
TypeError: reset(): incompatible function arguments. The following 
argument types are supported:
1. (self: gnuradio.blocks_python.head) –> None

I’m confused since reset takes no arguments and I don’t understand the meaning 
of the argument types shown.

Jim

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: Time difference between between different GUI Instruments.

[Marcus Müller]

Hi Igor,

well you set the sampling rate in your QT GUI Sink to twice the value of what you use in 
your QT GUI Time Sink.


So, this is correct!

Best regards,
Marcus

On 31.07.23 14:40, Igor wrote:

Hi community,

I noticed the double time difference between two different time  related QT GUI 
Instruments:
Inline image

My graph is:
Inline image

Is it a bug or feature or my mistake ;)?

Regards
Igor