On 03/12/2019 07:00 PM, Wayne Hilliard wrote:
Sure it's not much but it proves the concept.
One thing I think I'm going to try is to instead of using a vector
probe I want to use a single probe then rotate the vector to the left
sand concatenate the new value onto the end. But this will get you going.
The "trick" to the desired goodness is that you make some "helper code"
(via the Python Module block--very powerful way to achieve
procedural "stuff" without actually writing python blocks).
So, imagine, in your flow graph, that your 'fprobe' is actually for a
scalar value
(like, say, the heavily-filtered-and-decimated result of
complex-to-mag**2).
You then have a your "vec1" variable be the output of some function you
call in your helper code:
helper_code.my_funky_function(fprobe)
Then, "my_funky_function" can actually return a vector of some desirable
size (perhaps passed as a function argument).
That vector can be your "shift register" strip-chart type thingy.
This strategy is something I use quite a bit. Some might (probably
rightly) argue that some of what I do is a "substitute" for writing an
actual signal-processing block. But my code generally operates on
the output of "probe" blocks, generally sampled at *vastly* lower rates
than the input sample rate--like 1Hz, maybe more, depending on what
I'm doing.
Once you get really comfortable with this idiom, it becomes really quite
powerful...
On Tue, Mar 12, 2019 at 10:38 PM Joe Martin <k...@k5so.com
<mailto:k...@k5so.com>> wrote:
Congratulations Wayne. I’ve been trying to implement it but I am
having difficulty getting it to work. Would you mind sharing your
test GRC program with me so I can see how you accomplished it please?
I would much appreciate it,
Joe
On Mar 12, 2019, at 4:29 AM, Wayne Hilliard <woody...@gmail.com
<mailto:woody...@gmail.com>> wrote:
Thanks everyone for the replies. Huge help.
Kudos to Marcus Leech for the suggestion. Seems to work
wonderfully. At least in my test GRC file. Now to implement into
my own program.
Cheers!
Wayne Hilliard
On Sun, Mar 10, 2019 at 10:26 PM Marcus Müller
<mmuel...@gnuradio.org <mailto:mmuel...@gnuradio.org>> wrote:
Hi Wayne, Hi Joe,
you're right – we've been urging people to switch away from
WX since at
least 2014, and now we're finally removing it; with a bit of
a heavy
heart, to be honest: Without feature equality, removing an
alternative
feels bad, but we simply couldn't maintain the WX code
anymore, and had
to find the resources to maintain QT stuff first.
So, no, we don't have that specific visualization in Qt,
sorry. Joe,
this means we've long stopped supporting your widget – it
works on most
machines, on others it doesn't, and we can't really help you
in the
latter case.
Now, would one get started with developing a strip chart for
Qt? Either
one cheats a bit and just implements something that hands
n_points
sized chunks of data to the Qt GUI time sink, which always are
basically the last chunk, with old samples "shifted out" and new
samples "shifted in", or one would actually go and do a deep
C++/Qt
dive and write a proper stripchart widget.
Best regards,
Marcus
On Sun, 2019-03-10 at 16:12 -0600, Joe Martin wrote:
> Hi Wayne,
>
> I am using the strip-chart option of the WX GUI Scope Sink
block in
> GRC to perform drift scans in my radio astronomy project.
Works like
> a champ!
>
> Select “Stripchart” in the Trigger option.
>
> Regards,
>
> Joe
>
> > On Mar 10, 2019, at 3:24 PM, Wayne Hilliard
<woody...@gmail.com <mailto:woody...@gmail.com>>
> > wrote:
> >
> > Hello,
> > Question. Has there been any movement on adding a strip chart
> > option to this gui?
> >
> > I know WX_gui usage is discouraged and i have a radio
astronomy app
> > I've been working on that uses QT_Gui.
> >
> > I've looked around some on github and don't have a clue
on where I
> > would start to try something on my own.
> >
> > Any help would be appreciated .
> > Thanks in advance!!
> >
> > Wayne Hilliard
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
