Re: [Discuss-gnuradio] setup_env.sh equivalent when installing form source

[Marcus Müller]

Prior to pybombs, there was but 
https://gnuradio.org/redmine/projects/gnuradio/wiki/OldFAQ#The-problem-of-multiple-installs
 and the next FAQ entry.

Best regards,
Marcus

Am 22. Dezember 2015 01:10:16 MEZ, schrieb Richard Bell 
:
>Hi all,
>
>I would like to know if there is a way of creating the setup_env.sh
>file
>that pybombs creates for you automatically, when you are installing
>from
>source without pybombs at all. Currently, I cheat by copy and pasting
>the
>pybombs generated file from another computer that used pybombs. What is
>someone who does not have pybombs supposed to do to setup paths? Are
>they
>supposed to just know how, go to a website I haven't found that
>explains
>it, or something else?
>
>Thanks,
>Rich
>
>
>
>
>___
>Discuss-gnuradio mailing list
>Discuss-gnuradio@gnu.org
>https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] About decoding qpsk symbol

[Marcus Müller]

How are you including qpsk.py?
This does sound like your PYTHONPATH isn't set correctly, but I'd assume Python 
stumbles over that before you can even import qpsk.py 

Generally, for this kind of problem, a little background, maybe at least a code 
excerpt and a higher level view on what you're trying to do from the start 
would be very helpful.

Best regards,
Marcus

Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal 
:
>Hii marcus,
>
>I am trying to decode the symbols  and use the decoded symbols for
>further
>processing in the same python written module. I am not able to call the
>"constellation" related functions.
>How can i use them ? or is there any "decoder"  written in python ?
>
>Thanks !!
>
>
>
>On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller
>
>wrote:
>
>> qpsk.py can't be run.
>> It's just a python module containing functionality for QPSK, but no
>"main"
>> function or similar.
>>
>> What are you actually trying to do?
>>
>> Best regards,
>> Marcus
>>
>>
>> On 21.12.2015 21:09, monika bansal wrote:
>>
>> Hii,
>>
>> I am trying to decode qpsk symbols for channel estimation block in
>python
>> but there is error in importing digital_swig.
>> This also happens when i run "qpsk.py" as shown below:
>>
>> *Traceback (most recent call last):*
>> *  File "qpsk.py", line 32, in *
>> *import digital_swig as digital*
>> *ImportError: No module named digital_swig*
>>
>> Is there some other way or what should i do ?
>>
>>
>>
>>
>> ___
>> Discuss-gnuradio mailing
>listDiscuss-gnuradio@gnu.orghttps://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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] About decoding qpsk symbol

[monika bansal]

Hi Marcus,
I am creating a channel equalization block in python, trying some different
algorithms, and inside it I need to decode the modulated symbols(mapped
using qpsk). So I am looking for a python module, which can be called
inside the work function of my block, that can do this.

Thanks




On Tue, Dec 22, 2015 at 2:55 PM, Marcus Müller 
wrote:

> How are you including qpsk.py?
> This does sound like your PYTHONPATH isn't set correctly, but I'd assume
> Python stumbles over that before you can even import qpsk.py
>
> Generally, for this kind of problem, a little background, maybe at least a
> code excerpt and a higher level view on what you're trying to do from the
> start would be very helpful.
>
> Best regards,
> Marcus
>
>
> Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal <
> monika19...@gmail.com>:
>>
>> Hii marcus,
>>
>> I am trying to decode the symbols  and use the decoded symbols for
>> further processing in the same python written module. I am not able to call
>> the "constellation" related functions.
>> How can i use them ? or is there any "decoder"  written in python ?
>>
>> Thanks !!
>>
>>
>>
>> On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller 
>> wrote:
>>
>>> qpsk.py can't be run.
>>> It's just a python module containing functionality for QPSK, but no
>>> "main" function or similar.
>>>
>>> What are you actually trying to do?
>>>
>>> Best regards,
>>> Marcus
>>>
>>>
>>> On 21.12.2015 21:09, monika bansal wrote:
>>>
>>> Hii,
>>>
>>> I am trying to decode qpsk symbols for channel estimation block in
>>> python but there is error in importing digital_swig.
>>> This also happens when i run "qpsk.py" as shown below:
>>>
>>> *Traceback (most recent call last):*
>>> *  File "qpsk.py", line 32, in *
>>> *import digital_swig as digital*
>>> *ImportError: No module named digital_swig*
>>>
>>> Is there some other way or what should i do ?
>>>
>>>
>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing 
>>> listDiscuss-gnuradio@gnu.orghttps://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
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] About decoding qpsk symbol

[Marcus Müller]

To ask this more explcitely:
What *exactly* are you doing to produce the error?
We will need your code to understand what goes wrong.

On 22.12.2015 15:59, monika bansal wrote:
> Hi Marcus,
> I am creating a channel equalization block in python, trying some
> different algorithms, and inside it I need to decode the modulated
> symbols(mapped using qpsk). So I am looking for a python module, which
> can be called inside the work function of my block, that can do this. 
>
> Thanks 
>
>
>  
>
> On Tue, Dec 22, 2015 at 2:55 PM, Marcus Müller
> mailto:marcus.muel...@ettus.com>> wrote:
>
> How are you including qpsk.py ?
> This does sound like your PYTHONPATH isn't set correctly, but I'd
> assume Python stumbles over that before you can even import
> qpsk.py 
>
> Generally, for this kind of problem, a little background, maybe at
> least a code excerpt and a higher level view on what you're trying
> to do from the start would be very helpful.
>
> Best regards,
> Marcus
>
>
> Am 22. Dezember 2015 05:56:46 MEZ, schrieb monika bansal
> mailto:monika19...@gmail.com>>:
>
> Hii marcus,
>
> I am trying to decode the symbols  and use the decoded symbols
> for further processing in the same python written module. I am
> not able to call the "constellation" related functions.
> How can i use them ? or is there any "decoder"  written in
> python ?
>
> Thanks !!
>
>
>
> On Tue, Dec 22, 2015 at 3:48 AM, Marcus Müller
> mailto:marcus.muel...@ettus.com>>
> wrote:
>
> qpsk.py can't be run.
> It's just a python module containing functionality for
> QPSK, but no "main" function or similar.
>
> What are you actually trying to do?
>
> Best regards,
> Marcus
>
>
> On 21.12.2015 21:09, monika bansal wrote:
>> Hii,
>>
>> I am trying to decode qpsk symbols for channel estimation
>> block in python but there is error in importing digital_swig.
>> This also happens when i run "qpsk.py" as shown below:
>>
>> *Traceback (most recent call last):*
>> *  File "qpsk.py", line 32, in *
>> *import digital_swig as digital*
>> *ImportError: No module named digital_swig*
>>
>> Is there some other way or what should i do ?
>>
>>
>>
>>
>> ___
>> 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
>
>
> 
> 
>
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org 
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> -- Sent from my Android device with K-9 Mail. Please excuse my
> brevity.
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] FPGA compatibility number X310

[Lecoq Yann]

Hello,

I am setting up a new computer to talk to a x310 previously used on another 
system. I installed on this computer gnuradio and uhd on ubuntu 14.04 from the 
latest (yesterday) build-gnuradio script from Marcus Leech. All works fine with 
a N210.

However, with a usrp x310 on standard ethernet communication, uhd_usrp_probe 
--args addr=192.168.10.2 returns an error:

linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.git-101-g4a1cb1f2
Error: RuntimeError: Expected FPGA compatibility number 18, but got 17:
The FPGA image on your device is not compatible with this host code build.
Download the appropriate FPGA images for this version of UHD.

I therefore runned (successfuly), as instructed, uhd_images_dowloader.py and 
then /usr/local/bin/uhd_image_loader --args="type=x300,addr=192.168.10.2" which 
didn't show any error. I power cycled the x310 as I must after a fpga burn, but 
then the error of uhd_usrp_probe is still there.

Note than on the PC that was used previously with the x310 everything still 
works fine. On this one however, UHD_003.010.git-89-gb17b440d is reported for 
the uhd version... Is there a delay to be expected before the standard image 
fetched by uhd_images_dowloader is in agreement with the uhd version gitted by 
the build-gnuradio script ?

Thanks for your help.

Best,





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] FPGA compatibility number X310

[Derek Kozel]

Hello Lecoq,

A new set of images will be released soon resolving the current
compatibility version number difference, the pace of development on master
has a small offset for the moment. For now here is the most recent commit
which has compat 17 for both host and images.
https://github.com/EttusResearch/uhd/commit/b17b440d75a874b404f5493cc8ca9a1d6dbeb08c

Please let us know if you have any problems with this version.

Regards,
Derek

On Tue, Dec 22, 2015 at 5:52 PM, Lecoq Yann via USRP-users <
usrp-us...@lists.ettus.com> wrote:

> Hello,
>
> I am setting up a new computer to talk to a x310 previously used on
> another system. I installed on this computer gnuradio and uhd on ubuntu
> 14.04 from the latest (yesterday) build-gnuradio script from Marcus Leech.
> All works fine with a N210.
>
> However, with a usrp x310 on standard ethernet communication,
> uhd_usrp_probe --args addr=192.168.10.2 returns an error:
>
> linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.git-101-g4a1cb1f2
> Error: RuntimeError: Expected FPGA compatibility number 18, but got 17:
> The FPGA image on your device is not compatible with this host code build.
> Download the appropriate FPGA images for this version of UHD.
>
> I therefore runned (successfuly), as instructed, uhd_images_dowloader.py
> and then /usr/local/bin/uhd_image_loader
> --args="type=x300,addr=192.168.10.2" which didn't show any error. I power
> cycled the x310 as I must after a fpga burn, but then the error of
> uhd_usrp_probe is still there.
>
> Note than on the PC that was used previously with the x310 everything
> still works fine. On this one however, UHD_003.010.git-89-gb17b440d is
> reported for the uhd version... Is there a delay to be expected before the
> standard image fetched by uhd_images_dowloader is in agreement with the uhd
> version gitted by the build-gnuradio script ?
>
> Thanks for your help.
>
> Best,
>
>
>
>
>
> ___
> USRP-users mailing list
> usrp-us...@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Renaming PyBOMBS

[Martin Braun]

There's been some demand to rename PyBOMBS, and now that we're
re-releasing it, this is a good time to think about it. Complaints about
the name include:

- It may or may not be true that people have been detained by TSA for
working on PyBOMBS at the airport[1]
- The name suggests a Python-related packages (like Pylint, PyPI...)
rather than a GNU Radio-related tool
- People can't agree on a capitalization
- No one can remember what the acronym stands for

Sure, this is not a critical thing, but now's a good chance to bring it
up and also, this is not a joke :)

Here's how we're going to do this:

- Please suggest new names in this thread.
- I will choose from those names based on 'can I live with this name',
100% subjectively.
- New names will be put up for a vote. This will include an option to
keep the old name.
- Finally, the result of the vote will be used as a strong suggestion on
what the new name will be.

There already have been some suggestions:

- gromit -- the GNU Radio out-of-tree module installation tool
- the groot
- grpm -- the GNU Radio package manager


OK guys, bring up the ideas!

Cheers,
Martin

[1] It's not.

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Richard Bell]

GRAB = Gnu RAdio Basic installer

Then we can say things like "Go GRAB it" when referring to a needed module

On Tue, Dec 22, 2015 at 12:10 PM, Martin Braun 
wrote:

> There's been some demand to rename PyBOMBS, and now that we're
> re-releasing it, this is a good time to think about it. Complaints about
> the name include:
>
> - It may or may not be true that people have been detained by TSA for
> working on PyBOMBS at the airport[1]
> - The name suggests a Python-related packages (like Pylint, PyPI...)
> rather than a GNU Radio-related tool
> - People can't agree on a capitalization
> - No one can remember what the acronym stands for
>
> Sure, this is not a critical thing, but now's a good chance to bring it
> up and also, this is not a joke :)
>
> Here's how we're going to do this:
>
> - Please suggest new names in this thread.
> - I will choose from those names based on 'can I live with this name',
> 100% subjectively.
> - New names will be put up for a vote. This will include an option to
> keep the old name.
> - Finally, the result of the vote will be used as a strong suggestion on
> what the new name will be.
>
> There already have been some suggestions:
>
> - gromit -- the GNU Radio out-of-tree module installation tool
> - the groot
> - grpm -- the GNU Radio package manager
>
>
> OK guys, bring up the ideas!
>
> Cheers,
> Martin
>
> [1] It's not.
>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Tim]

Martin,
Excited to see pybombs2 emerging as stable !
A few thoughts on the naming below --
-Tim

On 12/22/2015 03:10 PM, Martin Braun wrote:
> There's been some demand to rename PyBOMBS, and now that we're
> re-releasing it, this is a good time to think about it. Complaints about
> the name include:
>
> - It may or may not be true that people have been detained by TSA for
> working on PyBOMBS at the airport[1]
> - The name suggests a Python-related packages (like Pylint, PyPI...)
> rather than a GNU Radio-related tool
it doesn’t really need to be gnu radio specific --
it was written to work with any such light weight recipes that follow
standard git/cmake or other common or custom format

> - People can't agree on a capitalization
> - No one can remember what the acronym stands for
>
> Sure, this is not a critical thing, but now's a good chance to bring it
> up and also, this is not a joke :)
>
> Here's how we're going to do this:
>
> - Please suggest new names in this thread.
> - I will choose from those names based on 'can I live with this name',
> 100% subjectively.
> - New names will be put up for a vote. This will include an option to
> keep the old name.
> - Finally, the result of the vote will be used as a strong suggestion on
> what the new name will be.
>
> There already have been some suggestions:
>
> - gromit -- the GNU Radio out-of-tree module installation tool
this name makes me cringe horribly
"installation tool" isn't really a fair characterization since it is
setting up a development environment
apt-get or standard binary installs are more "installation tool"

> - the groot
also - horrible cringe factor,

> - grpm -- the GNU Radio package manager
I like grpm --
other similar possibilities:

rmm - radio module manager
grmm - gnu radio module manager
gmm - gnuradio module manager
spm - SDR Packager Manager
spm - spm package manager

personally in favour of something short and functional vs cutesy and
contrived (we already have one of those names)
three letter package managers seem to be relatively common practice in FOSS

examples:apt, rpm, pip, gpm, npm, ...

>
>
> OK guys, bring up the ideas!
>
> Cheers,
> Martin
>
> [1] It's not.
>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Chris Kuethe]

The only strong opinion I have is an objection to the substring "rpm" due
to potential confusion with existing RPM installation utilities.

GRAB is nice. GRMM too.

Other possibilities are GRIP/GRIM: GnuRadio Installation and
Packages/Modules



On Tue, Dec 22, 2015 at 12:31 PM, Tim  wrote:

> Martin,
> Excited to see pybombs2 emerging as stable !
> A few thoughts on the naming below --
> -Tim
>
> On 12/22/2015 03:10 PM, Martin Braun wrote:
> > There's been some demand to rename PyBOMBS, and now that we're
> > re-releasing it, this is a good time to think about it. Complaints about
> > the name include:
> >
> > - It may or may not be true that people have been detained by TSA for
> > working on PyBOMBS at the airport[1]
> > - The name suggests a Python-related packages (like Pylint, PyPI...)
> > rather than a GNU Radio-related tool
> it doesn’t really need to be gnu radio specific --
> it was written to work with any such light weight recipes that follow
> standard git/cmake or other common or custom format
>
> > - People can't agree on a capitalization
> > - No one can remember what the acronym stands for
> >
> > Sure, this is not a critical thing, but now's a good chance to bring it
> > up and also, this is not a joke :)
> >
> > Here's how we're going to do this:
> >
> > - Please suggest new names in this thread.
> > - I will choose from those names based on 'can I live with this name',
> > 100% subjectively.
> > - New names will be put up for a vote. This will include an option to
> > keep the old name.
> > - Finally, the result of the vote will be used as a strong suggestion on
> > what the new name will be.
> >
> > There already have been some suggestions:
> >
> > - gromit -- the GNU Radio out-of-tree module installation tool
> this name makes me cringe horribly
> "installation tool" isn't really a fair characterization since it is
> setting up a development environment
> apt-get or standard binary installs are more "installation tool"
>
> > - the groot
> also - horrible cringe factor,
>
> > - grpm -- the GNU Radio package manager
> I like grpm --
> other similar possibilities:
>
> rmm - radio module manager
> grmm - gnu radio module manager
> gmm - gnuradio module manager
> spm - SDR Packager Manager
> spm - spm package manager
>
> personally in favour of something short and functional vs cutesy and
> contrived (we already have one of those names)
> three letter package managers seem to be relatively common practice in FOSS
>
> examples:apt, rpm, pip, gpm, npm, ...
>
> >
> >
> > OK guys, bring up the ideas!
> >
> > Cheers,
> > Martin
> >
> > [1] It's not.
> >
> > ___
> > 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
>



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Philip Balister]

YABS - Yet Another Build System

On 12/22/2015 03:37 PM, Chris Kuethe wrote:
> The only strong opinion I have is an objection to the substring "rpm" due
> to potential confusion with existing RPM installation utilities.
> 
> GRAB is nice. GRMM too.
> 
> Other possibilities are GRIP/GRIM: GnuRadio Installation and
> Packages/Modules
> 
> 
> 
> On Tue, Dec 22, 2015 at 12:31 PM, Tim  wrote:
> 
>> Martin,
>> Excited to see pybombs2 emerging as stable !
>> A few thoughts on the naming below --
>> -Tim
>>
>> On 12/22/2015 03:10 PM, Martin Braun wrote:
>>> There's been some demand to rename PyBOMBS, and now that we're
>>> re-releasing it, this is a good time to think about it. Complaints about
>>> the name include:
>>>
>>> - It may or may not be true that people have been detained by TSA for
>>> working on PyBOMBS at the airport[1]
>>> - The name suggests a Python-related packages (like Pylint, PyPI...)
>>> rather than a GNU Radio-related tool
>> it doesn’t really need to be gnu radio specific --
>> it was written to work with any such light weight recipes that follow
>> standard git/cmake or other common or custom format
>>
>>> - People can't agree on a capitalization
>>> - No one can remember what the acronym stands for
>>>
>>> Sure, this is not a critical thing, but now's a good chance to bring it
>>> up and also, this is not a joke :)
>>>
>>> Here's how we're going to do this:
>>>
>>> - Please suggest new names in this thread.
>>> - I will choose from those names based on 'can I live with this name',
>>> 100% subjectively.
>>> - New names will be put up for a vote. This will include an option to
>>> keep the old name.
>>> - Finally, the result of the vote will be used as a strong suggestion on
>>> what the new name will be.
>>>
>>> There already have been some suggestions:
>>>
>>> - gromit -- the GNU Radio out-of-tree module installation tool
>> this name makes me cringe horribly
>> "installation tool" isn't really a fair characterization since it is
>> setting up a development environment
>> apt-get or standard binary installs are more "installation tool"
>>
>>> - the groot
>> also - horrible cringe factor,
>>
>>> - grpm -- the GNU Radio package manager
>> I like grpm --
>> other similar possibilities:
>>
>> rmm - radio module manager
>> grmm - gnu radio module manager
>> gmm - gnuradio module manager
>> spm - SDR Packager Manager
>> spm - spm package manager
>>
>> personally in favour of something short and functional vs cutesy and
>> contrived (we already have one of those names)
>> three letter package managers seem to be relatively common practice in FOSS
>>
>> examples:apt, rpm, pip, gpm, npm, ...
>>
>>>
>>>
>>> OK guys, bring up the ideas!
>>>
>>> Cheers,
>>> Martin
>>>
>>> [1] It's not.
>>>
>>> ___
>>> 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
>>
> 
> 
> 
> 
> 
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Iluta V]

Dear all,

I would like to suggest the overall description in abbreviation:

GR.PY.SYS - GnuRadio Pyton System

Easy to Remember. Pronounce. One syllable. Name raises the level (of
already excellent content) ...

Sincerely,

Iluta

On Tue, Dec 22, 2015 at 8:37 PM, Chris Kuethe 
wrote:

> The only strong opinion I have is an objection to the substring "rpm" due
> to potential confusion with existing RPM installation utilities.
>
> GRAB is nice. GRMM too.
>
> Other possibilities are GRIP/GRIM: GnuRadio Installation and
> Packages/Modules
>
>
>
> On Tue, Dec 22, 2015 at 12:31 PM, Tim  wrote:
>
>> Martin,
>> Excited to see pybombs2 emerging as stable !
>> A few thoughts on the naming below --
>> -Tim
>>
>> On 12/22/2015 03:10 PM, Martin Braun wrote:
>> > There's been some demand to rename PyBOMBS, and now that we're
>> > re-releasing it, this is a good time to think about it. Complaints about
>> > the name include:
>> >
>> > - It may or may not be true that people have been detained by TSA for
>> > working on PyBOMBS at the airport[1]
>> > - The name suggests a Python-related packages (like Pylint, PyPI...)
>> > rather than a GNU Radio-related tool
>> it doesn’t really need to be gnu radio specific --
>> it was written to work with any such light weight recipes that follow
>> standard git/cmake or other common or custom format
>>
>> > - People can't agree on a capitalization
>> > - No one can remember what the acronym stands for
>> >
>> > Sure, this is not a critical thing, but now's a good chance to bring it
>> > up and also, this is not a joke :)
>> >
>> > Here's how we're going to do this:
>> >
>> > - Please suggest new names in this thread.
>> > - I will choose from those names based on 'can I live with this name',
>> > 100% subjectively.
>> > - New names will be put up for a vote. This will include an option to
>> > keep the old name.
>> > - Finally, the result of the vote will be used as a strong suggestion on
>> > what the new name will be.
>> >
>> > There already have been some suggestions:
>> >
>> > - gromit -- the GNU Radio out-of-tree module installation tool
>> this name makes me cringe horribly
>> "installation tool" isn't really a fair characterization since it is
>> setting up a development environment
>> apt-get or standard binary installs are more "installation tool"
>>
>> > - the groot
>> also - horrible cringe factor,
>>
>> > - grpm -- the GNU Radio package manager
>> I like grpm --
>> other similar possibilities:
>>
>> rmm - radio module manager
>> grmm - gnu radio module manager
>> gmm - gnuradio module manager
>> spm - SDR Packager Manager
>> spm - spm package manager
>>
>> personally in favour of something short and functional vs cutesy and
>> contrived (we already have one of those names)
>> three letter package managers seem to be relatively common practice in
>> FOSS
>>
>> examples:apt, rpm, pip, gpm, npm, ...
>>
>> >
>> >
>> > OK guys, bring up the ideas!
>> >
>> > Cheers,
>> > Martin
>> >
>> > [1] It's not.
>> >
>> > ___
>> > 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
>>
>
>
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?
>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Martin Braun]

On 22.12.2015 12:31, Tim wrote:
>> - The name suggests a Python-related packages (like Pylint, PyPI...)
>> rather than a GNU Radio-related tool
> it doesn’t really need to be gnu radio specific --
> it was written to work with any such light weight recipes that follow
> standard git/cmake or other common or custom format

This is a good point, actually. Already, it installs things like Boost,
gcc, git... etc. in case people didn't know.

> personally in favour of something short and functional vs cutesy and
> contrived (we already have one of those names)
> three letter package managers seem to be relatively common practice in FOSS

Having something that's easily typable on most keyboard layouts is also
a nice to have.

Cheers,
M


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Martin Braun]

On 22.12.2015 12:31, Tim wrote:
> personally in favour of something short and functional vs cutesy and
> contrived (we already have one of those names)
> three letter package managers seem to be relatively common practice in FOSS
> 
> examples:apt, rpm, pip, gpm, npm, ...

Also, it doesn't *have* to be an acronym.

M

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Sylvain Munaut]

> Also, it doesn't *have* to be an acronym.

Let's call it Bob.

Cheers,

   Sylvain

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Matt Ettus]

On Tue, Dec 22, 2015 at 12:31 PM, Richard Bell 
wrote:

> GRAB = Gnu RAdio Basic installer
>
> Then we can say things like "Go GRAB it" when referring to a needed module
>

+1.  Short, not used by any other project, pronounceable.

It could also stand for GNU Radio Application Bundles.   Or Bombs.

Matt
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Donald Pupecki]

I like GRPM - GnuRadio Package Manager.

Can never remember what pybombs stands for anyway.
On Dec 22, 2015 3:10 PM, "Martin Braun"  wrote:

> There's been some demand to rename PyBOMBS, and now that we're
> re-releasing it, this is a good time to think about it. Complaints about
> the name include:
>
> - It may or may not be true that people have been detained by TSA for
> working on PyBOMBS at the airport[1]
> - The name suggests a Python-related packages (like Pylint, PyPI...)
> rather than a GNU Radio-related tool
> - People can't agree on a capitalization
> - No one can remember what the acronym stands for
>
> Sure, this is not a critical thing, but now's a good chance to bring it
> up and also, this is not a joke :)
>
> Here's how we're going to do this:
>
> - Please suggest new names in this thread.
> - I will choose from those names based on 'can I live with this name',
> 100% subjectively.
> - New names will be put up for a vote. This will include an option to
> keep the old name.
> - Finally, the result of the vote will be used as a strong suggestion on
> what the new name will be.
>
> There already have been some suggestions:
>
> - gromit -- the GNU Radio out-of-tree module installation tool
> - the groot
> - grpm -- the GNU Radio package manager
>
>
> OK guys, bring up the ideas!
>
> Cheers,
> Martin
>
> [1] It's not.
>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Tim O'Shea]

Python build overlay managed bundle system


On Tue, Dec 22, 2015, 4:47 PM Donald Pupecki  wrote:

> I like GRPM - GnuRadio Package Manager.
>
> Can never remember what pybombs stands for anyway.
> On Dec 22, 2015 3:10 PM, "Martin Braun"  wrote:
>
>> There's been some demand to rename PyBOMBS, and now that we're
>> re-releasing it, this is a good time to think about it. Complaints about
>> the name include:
>>
>> - It may or may not be true that people have been detained by TSA for
>> working on PyBOMBS at the airport[1]
>> - The name suggests a Python-related packages (like Pylint, PyPI...)
>> rather than a GNU Radio-related tool
>> - People can't agree on a capitalization
>> - No one can remember what the acronym stands for
>>
>> Sure, this is not a critical thing, but now's a good chance to bring it
>> up and also, this is not a joke :)
>>
>> Here's how we're going to do this:
>>
>> - Please suggest new names in this thread.
>> - I will choose from those names based on 'can I live with this name',
>> 100% subjectively.
>> - New names will be put up for a vote. This will include an option to
>> keep the old name.
>> - Finally, the result of the vote will be used as a strong suggestion on
>> what the new name will be.
>>
>> There already have been some suggestions:
>>
>> - gromit -- the GNU Radio out-of-tree module installation tool
>> - the groot
>> - grpm -- the GNU Radio package manager
>>
>>
>> OK guys, bring up the ideas!
>>
>> Cheers,
>> Martin
>>
>> [1] It's not.
>>
>> ___
>> 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
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Limits of freq_hopping.py

[Richard Bell]

I'm using Ubuntu 14.04 LTS, GNU Radio 3.7.9rc1, UHD 3.9.1 with two USRP
N210s with WBX daughtercards.

I'm trying to determine what the fastest hopping rate is with the given
setup above. Using the provided gr-uhd/examples/python frequency hopping
script, it seems that 100 ms (10 Hz) is the fastest. What I haven't been
able to figure out yet, is if this is due to a limitation imposed by that
script, or if this is the fastest way (or right around the fastest way)
that any script could hope to approach.

What I did to arive at this 100 ms limit is the following:
1) The first N210 is used as a transmitter and I use the following command
to initiate hopping
./freq_hopping.py -a "addr=10.0.8.5" --antenna TX/RX --verbose --freq
915e6 --gain 20 --rate 5e6 --num-bursts 1 --freq-delta 0.1e6
--samp-per-burst 10 --hop-time 50

2) The second N210 is a spectrum analyzer using the following command and
the waterfall tab
uhd_fft -f 915M -s 0.5M -A TX/RX

3) I stop the waterfall plot, so it stops scrolling, and measure the
smallest length of time at one frequency I can achieve given any batch of
settings in step 1. The settings I linked in step one should have set a hop
time of 50 ms, but this measurements shows 100 ms.

I'm going to try writing my own custom script, but would like to know if
others have pushed this before and found ~100 ms (10 Hz) as the limit for
frequency hopping intervals using the N210+WBX combo.

Appreciated,
Rich
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Neel Pandeya]

My vote would be for one of these:

GRPM = GnuRadio Package Manager

GRAB = Gnu RAdio Basic installer

GRBI = Gnu Radio Basic Installer

I agree with Tim O'Shea, the name should be something short and functional,
and give an idea of what it does, instead of being cutesy and contrived.

--Neel




On 22 December 2015 at 12:10, Martin Braun  wrote:

> There's been some demand to rename PyBOMBS, and now that we're
> re-releasing it, this is a good time to think about it. Complaints about
> the name include:
>
> - It may or may not be true that people have been detained by TSA for
> working on PyBOMBS at the airport[1]
> - The name suggests a Python-related packages (like Pylint, PyPI...)
> rather than a GNU Radio-related tool
> - People can't agree on a capitalization
> - No one can remember what the acronym stands for
>
> Sure, this is not a critical thing, but now's a good chance to bring it
> up and also, this is not a joke :)
>
> Here's how we're going to do this:
>
> - Please suggest new names in this thread.
> - I will choose from those names based on 'can I live with this name',
> 100% subjectively.
> - New names will be put up for a vote. This will include an option to
> keep the old name.
> - Finally, the result of the vote will be used as a strong suggestion on
> what the new name will be.
>
> There already have been some suggestions:
>
> - gromit -- the GNU Radio out-of-tree module installation tool
> - the groot
> - grpm -- the GNU Radio package manager
>
>
> OK guys, bring up the ideas!
>
> Cheers,
> Martin
>
> [1] It's not.
>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Martin Braun]

Another suggestion from #gnuradio was 'grapple'.

M
On 22 Dec 2015 15:12, "Neel Pandeya"  wrote:

> My vote would be for one of these:
>
> GRPM = GnuRadio Package Manager
>
> GRAB = Gnu RAdio Basic installer
>
> GRBI = Gnu Radio Basic Installer
>
> I agree with Tim O'Shea, the name should be something short and
> functional, and give an idea of what it does, instead of being cutesy and
> contrived.
>
> --Neel
>
>
>
>
> On 22 December 2015 at 12:10, Martin Braun  wrote:
>
>> There's been some demand to rename PyBOMBS, and now that we're
>> re-releasing it, this is a good time to think about it. Complaints about
>> the name include:
>>
>> - It may or may not be true that people have been detained by TSA for
>> working on PyBOMBS at the airport[1]
>> - The name suggests a Python-related packages (like Pylint, PyPI...)
>> rather than a GNU Radio-related tool
>> - People can't agree on a capitalization
>> - No one can remember what the acronym stands for
>>
>> Sure, this is not a critical thing, but now's a good chance to bring it
>> up and also, this is not a joke :)
>>
>> Here's how we're going to do this:
>>
>> - Please suggest new names in this thread.
>> - I will choose from those names based on 'can I live with this name',
>> 100% subjectively.
>> - New names will be put up for a vote. This will include an option to
>> keep the old name.
>> - Finally, the result of the vote will be used as a strong suggestion on
>> what the new name will be.
>>
>> There already have been some suggestions:
>>
>> - gromit -- the GNU Radio out-of-tree module installation tool
>> - the groot
>> - grpm -- the GNU Radio package manager
>>
>>
>> OK guys, bring up the ideas!
>>
>> Cheers,
>> Martin
>>
>> [1] It's not.
>>
>> ___
>> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Neel Pandeya]

Also perhaps:

GRIN = Gnu Radio INstaller



On 22 December 2015 at 15:37, Martin Braun  wrote:

> Another suggestion from #gnuradio was 'grapple'.
>
> M
> On 22 Dec 2015 15:12, "Neel Pandeya"  wrote:
>
>> My vote would be for one of these:
>>
>> GRPM = GnuRadio Package Manager
>>
>> GRAB = Gnu RAdio Basic installer
>>
>> GRBI =
>> ​​
>> Gnu Radio Basic Installer
>>
>> I agree with Tim O'Shea, the name should be something short and
>> functional, and give an idea of what it does, instead of being cutesy and
>> contrived.
>>
>> --Neel
>>
>>
>>
>>
>> On 22 December 2015 at 12:10, Martin Braun 
>> wrote:
>>
>>> There's been some demand to rename PyBOMBS, and now that we're
>>> re-releasing it, this is a good time to think about it. Complaints about
>>> the name include:
>>>
>>> - It may or may not be true that people have been detained by TSA for
>>> working on PyBOMBS at the airport[1]
>>> - The name suggests a Python-related packages (like Pylint, PyPI...)
>>> rather than a GNU Radio-related tool
>>> - People can't agree on a capitalization
>>> - No one can remember what the acronym stands for
>>>
>>> Sure, this is not a critical thing, but now's a good chance to bring it
>>> up and also, this is not a joke :)
>>>
>>> Here's how we're going to do this:
>>>
>>> - Please suggest new names in this thread.
>>> - I will choose from those names based on 'can I live with this name',
>>> 100% subjectively.
>>> - New names will be put up for a vote. This will include an option to
>>> keep the old name.
>>> - Finally, the result of the vote will be used as a strong suggestion on
>>> what the new name will be.
>>>
>>> There already have been some suggestions:
>>>
>>> - gromit -- the GNU Radio out-of-tree module installation tool
>>> - the groot
>>> - grpm -- the GNU Radio package manager
>>>
>>>
>>> OK guys, bring up the ideas!
>>>
>>> Cheers,
>>> Martin
>>>
>>> [1] It's not.
>>>
>>> ___
>>> 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
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Tim O'Shea]

Cutesy acronym grumblings aside on this one, If all you wanted to do was
install gnu radio, apt, rpm, our emerge would do.   IMO pybombs seems more
about indexing, installing, setting up development environments, and
updating out of tree modules - "grin" implied scope is a small subset
thereof

On Tue, Dec 22, 2015, 10:02 PM Neel Pandeya  wrote:

> Also perhaps:
>
> GRIN = Gnu Radio INstaller
>
>
>
> On 22 December 2015 at 15:37, Martin Braun  wrote:
>
>> Another suggestion from #gnuradio was 'grapple'.
>>
>> M
>> On 22 Dec 2015 15:12, "Neel Pandeya"  wrote:
>>
>>> My vote would be for one of these:
>>>
>>> GRPM = GnuRadio Package Manager
>>>
>>> GRAB = Gnu RAdio Basic installer
>>>
>>> GRBI =
>>> ​​
>>> Gnu Radio Basic Installer
>>>
>>> I agree with Tim O'Shea, the name should be something short and
>>> functional, and give an idea of what it does, instead of being cutesy and
>>> contrived.
>>>
>>> --Neel
>>>
>>>
>>>
>>>
>>> On 22 December 2015 at 12:10, Martin Braun 
>>> wrote:
>>>
 There's been some demand to rename PyBOMBS, and now that we're
 re-releasing it, this is a good time to think about it. Complaints about
 the name include:

 - It may or may not be true that people have been detained by TSA for
 working on PyBOMBS at the airport[1]
 - The name suggests a Python-related packages (like Pylint, PyPI...)
 rather than a GNU Radio-related tool
 - People can't agree on a capitalization
 - No one can remember what the acronym stands for

 Sure, this is not a critical thing, but now's a good chance to bring it
 up and also, this is not a joke :)

 Here's how we're going to do this:

 - Please suggest new names in this thread.
 - I will choose from those names based on 'can I live with this name',
 100% subjectively.
 - New names will be put up for a vote. This will include an option to
 keep the old name.
 - Finally, the result of the vote will be used as a strong suggestion on
 what the new name will be.

 There already have been some suggestions:

 - gromit -- the GNU Radio out-of-tree module installation tool
 - the groot
 - grpm -- the GNU Radio package manager


 OK guys, bring up the ideas!

 Cheers,
 Martin

 [1] It's not.

 ___
 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
>>
>>
> ___
> 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

Re: [Discuss-gnuradio] Renaming PyBOMBS

[Murray Thomson]

On Dec 22, 2015 8:31 PM, "Tim" 
gmail.com > wrote:
>
> Martin,
> Excited to see pybombs2 emerging as stable !
> A few thoughts on the naming below --
> -Tim
>
> On 12/22/2015 03:10 PM, Martin Braun wrote:
> > There's been some demand to rename PyBOMBS, and now that we're
> > re-releasing it, this is a good time to think about it. Complaints about
> > the name include:
> >
> > - It may or may not be true that people have been detained by TSA for
> > working on PyBOMBS at the airport[1]
> > - The name suggests a Python-related packages (like Pylint, PyPI...)
> > rather than a GNU Radio-related tool
> it doesn’t really need to be gnu radio specific --
> it was written to work with any such light weight recipes that follow
> standard git/cmake or other common or custom format
>
> > - People can't agree on a capitalization
> > - No one can remember what the acronym stands for
> >
> > Sure, this is not a critical thing, but now's a good chance to bring it
> > up and also, this is not a joke :)
> >
> > Here's how we're going to do this:
> >
> > - Please suggest new names in this thread.
> > - I will choose from those names based on 'can I live with this name',
> > 100% subjectively.
> > - New names will be put up for a vote. This will include an option to
> > keep the old name.
> > - Finally, the result of the vote will be used as a strong suggestion on
> > what the new name will be.
> >
> > There already have been some suggestions:
> >
> > - gromit -- the GNU Radio out-of-tree module installation tool
> this name makes me cringe horribly
> "installation tool" isn't really a fair characterization since it is
> setting up a development environment
> apt-get or standard binary installs are more "installation tool"

What about

GRDEV : GnuRadio Development EnVironment

>
> > - the groot
> also - horrible cringe factor,
>
> > - grpm -- the GNU Radio package manager
> I like grpm --
> other similar possibilities:
>
> rmm - radio module manager
> grmm - gnu radio module manager
> gmm - gnuradio module manager
> spm - SDR Packager Manager
> spm - spm package manager
>
> personally in favour of something short and functional vs cutesy and
> contrived (we already have one of those names)
> three letter package managers seem to be relatively common practice in
FOSS
>
> examples:apt, rpm, pip, gpm, npm, ...
>
> >
> >
> > OK guys, bring up the ideas!
> >
> > Cheers,
> > Martin
> >
> > [1] It's not.
> >
> > ___
> > 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

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio