glangsto
commented
2 years ago Hi John,
Glad to hear you got the code working for the Raspberry Pi, but sorry about that initial hiccup, using Gnuradio Companion from the pull down menu.
I think the issue is that the command line code first runs a script (.bashrc or .profile) at login, that sets up the environment so the python code is found.
From the pull down menu, the system does not execute that script, so does not know where to find radio_astro.
I’ll try to figure out how to add that script to the default gnuradio startup.
Glen
Glen I Langston, Ph. D. Galactic Astronomy Program Director National Science Foundation 304-456-3032
On Dec 12, 2021, at 1:47 PM, johncneal @.***> wrote:
This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Following my recent MacBook build of GNU Radio and GR-Radio_Astro I also wanted to get one of my Rasperbby Pi's built for Radio Astronomy. So I installed the 'NsfSdr-21Jul13.img.xz' image from the Google Drive at - https://drive.google.com/drive/folders/1t2soWvGIgze7wg-7QGlVgB0m3Q-BR3C-
This appears to be the latest image on a new Raspi 4 Model B 4GB.
It mostly works 'out of the box' and is a great way of distributing the software. However there is a problem when running gnuradio-companion from the provided 'GNURadio Companion' desktop link or from the 'start menu item 'Programming->GNU Radio Companion'. Both these options launch GR-Companion fine but when you run a .grc file (eg) /home/pi/Research/gr-radio_astro-37/examples/vectordemo_c2.grc you get a Python import error -
Traceback (most recent call last): File "/home/pi/Research/gr-radio_astro-37/examples/vectordemo_c2.py", line 39, in import radio_astro ModuleNotFoundError: No module named 'radio_astro'
However if I start a Terminal session explicitly (from the Task bar or from 'Accessories->Terminal') and run GR-Companion, then the same .grc file will run quite happily in GR-Companion.
I note this is similar to the closed Issue 31 but I'm not sure if the cause is the same since the explicitly launched terminal session appears to work correctly.
The explicit start of the Terminal session is an effective workaround but thought it worth drawing your attention to this. ?
john
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Following my recent MacBook build of GNU Radio and GR-Radio_Astro I also wanted to get one of my Rasperbby Pi's built for Radio Astronomy. So I installed the 'NsfSdr-21Jul13.img.xz' image from the Google Drive at - https://drive.google.com/drive/folders/1t2soWvGIgze7wg-7QGlVgB0m3Q-BR3C-
This appears to be the latest image on a new Raspi 4 Model B 4GB.
It mostly works 'out of the box' and is a great way of distributing the software. However there is a problem when running gnuradio-companion from the provided 'GNURadio Companion' desktop link or from the 'start menu item 'Programming->GNU Radio Companion'. Both these options launch GR-Companion fine but when you run a .grc file (eg) /home/pi/Research/gr-radio_astro-37/examples/vectordemo_c2.grc you get a Python import error -
_Traceback (most recent call last): File "/home/pi/Research/gr-radio_astro-37/examples/vectordemo_c2.py", line 39, in
import radio_astro
ModuleNotFoundError: No module named 'radioastro'
However if I start a Terminal session explicitly (from the Task bar or from 'Accessories->Terminal') and run GR-Companion, then the same .grc file will run quite happily in GR-Companion.
I note this is similar to the closed Issue 31 but I'm not sure if the cause is the same since the explicitly launched terminal session appears to work correctly.
The explicit start of the Terminal session is an effective workaround but thought it worth drawing your attention to this. ?
john