Hello Marcus,
During my testing, I think, I set the time.sleep function by try and error.
I didn't check for different PC. I will update it after testing it on my
too slow AWS may be.
Also, this resize issue is because Bokeh stopped the support of resize
feature. If you can, use Bokeh V0.12.6, an
On 02/27/2018 01:25 AM, Marcus D. Leech wrote:
On 02/27/2018 12:15 AM, Kartik Patel wrote:
Hello Marcus,
Just for starters, make sure you have v3.7.12 of GNU Radio. In
particular, your GR should contain the commit `/3c989f9`./ Also, make
sure you select Bokeh GUI instead of QT GUI in /Generat
On 02/27/2018 12:15 AM, Kartik Patel wrote:
Hello Marcus,
Just for starters, make sure you have v3.7.12 of GNU Radio. In
particular, your GR should contain the commit `/3c989f9`./ Also, make
sure you select Bokeh GUI instead of QT GUI in /Generate Options/
field in /Options/ block. For Bokeh
Hello Marcus,
Just for starters, make sure you have v3.7.12 of GNU Radio. In particular,
your GR should contain the commit `*3c989f9`.* Also, make sure you select
Bokeh GUI instead of QT GUI in *Generate Options* field in *Options* block.
For Bokeh GUI we have a different `main()` function templat
Just started playing with gr-bokehgui. Seems like a good start, but I
think I'm missing something.
Tried a simple application built in GRC, with a source, and a bokeh
Frequency Sink.
Genned up just fine, but when I run it
Traceback (most recent call last):
File "./top_block.py", line 108,
Yes, I wished I had a definite number at this point; we'll probably
actually will orient on the release cycles of the more popular Linux
distros, but, to be honest, I don't think it'd be 100% appropriate to
promise that "we will _fully_ support 3.7 till 2023, because it's what
Ubuntu 18.04 LTS ship
Hello Marcus,
All I wanted to know was the typical time frame of the maint-X.Y branch
(not 3.7 in specific). I believe the answer is (from your reply), it will
depend on the particular version. Maybe maint-3.7 will have a long life and
other maint-X.Y may not.
With the Debian and QT4 example, it'
Hello Kartik,
there will not be a "maint-3.7.12", there will only be a "maint-3.7";
that's enough fragmentation for me :)
Yes, it will be actively maintained for a finite time, just like
anything in this world :) That timeframe probably will be a bit longer
than for future maint-X.Y branches, as
Hello Marcus,
I believe this workflow is an excellent improvement and stepping stone to
acknowledge that GNU Radio is now a "medium-to-large" size projects.
Only thing I did not understand was the connection with Linux Distros. I
think you want to say that suppose 3.7.12 version is released, then
Hello everyone,
as the last days have been pretty heavy on discussion between the new
GNU Radio lead team, it’s now become clearer how we’ll actually deal
with the day-to-day maintenance work as well with the release
management.
So, as you might have noticed, we’ve been crunching through the Pull
Hi there!
We are very glad that you find interest in contributing to GNU Radio and
GSoC! You are definitely on the right road by getting familiarized with the
software and its perks by installing it and following the guided tutorials.
If you have any question regarding functionality that you want
Hi,
I am Swapnil Negi, an Electronics and Communication undergraduate at Indian
Institute of Technology Roorkee, India. I am highly interested in
contributing towards GNU Radio as my GSoC project.
I am done with setting up the project and have gone through the guided
tutorial on gnuradio-companion.
12 matches
Mail list logo
