Installation difficulty

[dave290]

I'm having difficulty installing the gr-radio_astro package. I have Windows 10, and already successfully installed and used the Gnuradio suite, including GNUCompanion, python, etc. I have 2 questions (bear with me, since I am sort of new to this.) 1) Does the "build" folder go into the general folder, GNURadio-3.7 ? If so, do I put the downloaded contents of the gr-radio package into this build folder after I create it? (by downloaded contents, I mean the folders named "apps," "cmake," "data," etc.) 2) I followed the instructions in the install guide, but get stuck at the following commands: sudo make, sudo make install, and sudo ldconfig. When I type these in the powershell, I get error messages saying these are not recognized commands. I tried using the commands at different folder levels, but still no luck. I attempted the troubleshooting instructions, but cannot find the .bashrc file that is described. Hopefully, it's not a big problem that I'm using Windows. It seems like all that is needed is a way to point GNUradio to the correct subfolders. Any help would be greatly appreciated!

[glangsto]

Hi Dave,

I’m not an expert on installing on Windows.

I’m cc’ing Grad student at WVU, who has lots of software experience.

Perhaps he can advise?

Thanks

Glen

On Jun 4, 2020, at 4:28 PM, dave290 notifications@github.com wrote:

I'm having difficulty installing the gr-radio_astro package. I have Windows 10, and already successfully installed and used the Gnuradio suite, including GNUCompanion, python, etc. I have 2 questions (bear with me, since I am sort of new to this.)

• Does the "build" folder go into the general folder, GNURadio-3.7 ? If so, do I put the downloaded contents of the gr-radio package into this build folder after I create it? (by downloaded contents, I mean the folders named "apps," "cmake," "data," etc.) • I followed the instructions in the install guide, but get stuck at the following commands: sudo make, sudo make install, and sudo ldconfig. When I type these in the powershell, I get error messages saying these are not recognized commands. I tried using the commands at different folder levels, but still no luck. I attempted the troubleshooting instructions, but cannot find the .bashrc file that is described. Hopefully, it's not a big problem that I'm using Windows. It seems like all that is needed is a way to point GNUradio to the correct subfolders. Any help would be greatly appreciated! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Okay. Thank you, Glen.

Dave

On Thu, Jun 4, 2020 at 3:37 PM Glen Langston notifications@github.com wrote:

Hi Dave,

I’m not an expert on installing on Windows.

I’m cc’ing Grad student at WVU, who has lots of software experience.

Perhaps he can advise?

Thanks

Glen

On Jun 4, 2020, at 4:28 PM, dave290 notifications@github.com wrote:

I'm having difficulty installing the gr-radio_astro package. I have Windows 10, and already successfully installed and used the Gnuradio suite, including GNUCompanion, python, etc. I have 2 questions (bear with me, since I am sort of new to this.)

• Does the "build" folder go into the general folder, GNURadio-3.7 ? If so, do I put the downloaded contents of the gr-radio package into this build folder after I create it? (by downloaded contents, I mean the folders named "apps," "cmake," "data," etc.) • I followed the instructions in the install guide, but get stuck at the following commands: sudo make, sudo make install, and sudo ldconfig. When I type these in the powershell, I get error messages saying these are not recognized commands. I tried using the commands at different folder levels, but still no luck. I attempted the troubleshooting instructions, but cannot find the .bashrc file that is described. Hopefully, it's not a big problem that I'm using Windows. It seems like all that is needed is a way to point GNUradio to the correct subfolders. Any help would be greatly appreciated! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639103087, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ5NNPO3MGLGHIKOXMDRVAAZFANCNFSM4NS6UUEQ .

[PranavSanghavi]

Hi Dave,

I am sorry that you have been facing trouble with the package. Installing Out Of Tree modules on Windows is non trivial by the very nature of the way software environments behave in Windows. One would have to manually move individual source and xml files from the repository to the GNURadio “environment” and that leaves a lot of room for mismatches and errors. The only way to truly incorporate custom out of tree modules is to build GNURadio from source with the package included in the initial build to obtain a binary that can be installed on Windows.

The current releases of gr-radio_astro have been tested to work on Linux distributions only. That being said it is on our project priorities to have a Windows compatible release in the coming couple of weeks or explore some workarounds.

I’ll keep you posted

• Pranav .

[glangsto]

Thanks Pranav!

On Jun 5, 2020, at 4:38 AM, Pranav Sanghavi notifications@github.com wrote:

Hi Dave,

I am sorry that you have been facing trouble with the package. Installing Out Of Tree modules on Windows is non trivial by the very nature of the way software environments behave in Windows. One would have to manually move individual source and xml files from the repository to the GNURadio “environment” and that leaves a lot of room for mismatches and errors. The only way to truly incorporate custom out of tree modules is to build GNURadio from source with the package included in the initial build to obtain a binary that can be installed on Windows.

The current releases of gr-radio_astro have been tested to work on Linux distributions only. That being said it is on our project priorities to have a Windows compatible release in the coming couple of weeks or explore some workarounds.

I’ll keep you posted

• Pranav . — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639341865", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639341865", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Pranav,

Thanks for your response. I was afraid that might be the case. I would very eagerly await any Windows-compatible package or work-around, as you suggested. I'm a high school physics teacher, and was hoping to test this project out this summer so that I can involve my students in the Fall. I've been in touch with Eric Trumbauer, who recommended your software and who has done a similar project with a HS student. Any chance of a "fix" in the near future would be awesome!

I did try moving some of the XML files into the GNU environment, but couldn't get them to be recognized. It seems like three blocks are missing (ascii_sink, integrate, and v_median) but I suspect it may be more complicated. As you said, it is not such a simple matter to incorporate these in an ad hoc way.

Thanks again for your time, and please let me know if and when you update the installation package.

Best, David

On Fri, Jun 5, 2020 at 6:56 AM Glen Langston notifications@github.com wrote:

Thanks Pranav!

On Jun 5, 2020, at 4:38 AM, Pranav Sanghavi notifications@github.com wrote:

Hi Dave,

I am sorry that you have been facing trouble with the package. Installing Out Of Tree modules on Windows is non trivial by the very nature of the way software environments behave in Windows. One would have to manually move individual source and xml files from the repository to the GNURadio “environment” and that leaves a lot of room for mismatches and errors. The only way to truly incorporate custom out of tree modules is to build GNURadio from source with the package included in the initial build to obtain a binary that can be installed on Windows.

The current releases of gr-radio_astro have been tested to work on Linux distributions only. That being said it is on our project priorities to have a Windows compatible release in the coming couple of weeks or explore some workarounds.

I’ll keep you posted

• Pranav . — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639341865", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639341865", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639436014, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ4J6O6BVMAFC4RA52TRVDMOJANCNFSM4NS6UUEQ .

[PranavSanghavi]

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

[dave290]

Pranav,

To clarify, can Ubuntu be installed on Windows? If so, I'm still a little reluctant to go that route because my expertise level is not so high. However, I see your point. Maybe in the future, I should do this on a raspberry pi, with Linux (but again, I'd have to learn this first!)

David

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi notifications@github.com wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ .

[glangsto]

Hi David,

I do recommend the Raspberry pi 4 route, if possible, as the entire setup can be downloaded, along with the OS at

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes.

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

This is the whole operating system, so needs to be downloaded, and written to an SDCard with “Balena Etcher”

Then plug it into your Pi and reboot. It will automatically start a VNC session, but also allows login if you have a monitor and keyboard.

User is Pi

I think no password is needed. Certainly none is needed if you use VNC. I never actually login.

Glen

On Jun 5, 2020, at 10:54 AM, dave290 notifications@github.com wrote:

Pranav,

To clarify, can Ubuntu be installed on Windows? If so, I'm still a little reluctant to go that route because my expertise level is not so high. However, I see your point. Maybe in the future, I should do this on a raspberry pi, with Linux (but again, I'd have to learn this first!)

David

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi notifications@github.com wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639545317", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639545317", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Glenn,

Okay, thanks very much for this info. I will also start looking into this for the future.

Dave

On Fri, Jun 5, 2020 at 11:05 AM Glen Langston notifications@github.com wrote:

Hi David,

I do recommend the Raspberry pi 4 route, if possible, as the entire setup can be downloaded, along with the OS at

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes.

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

This is the whole operating system, so needs to be downloaded, and written to an SDCard with “Balena Etcher”

Then plug it into your Pi and reboot. It will automatically start a VNC session, but also allows login if you have a monitor and keyboard.

User is Pi

I think no password is needed. Certainly none is needed if you use VNC. I never actually login.

Glen

On Jun 5, 2020, at 10:54 AM, dave290 notifications@github.com wrote:

Pranav,

To clarify, can Ubuntu be installed on Windows? If so, I'm still a little reluctant to go that route because my expertise level is not so high. However, I see your point. Maybe in the future, I should do this on a raspberry pi, with Linux (but again, I'd have to learn this first!)

David

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi <notifications@github.com

wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639545317", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639545317", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639597856, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZZ4MQB7XHP6JPQCAJ3RVEJTDANCNFSM4NS6UUEQ .

[dave290]

Glen,

I just wanted to clarify how to use the Raspberry Pi SDR OS download you shared:

1) Will this OS overwrite the Raspbian (or Ubuntu) OS that may have been previously installed? 2) After it is installed, do I install GNU radio (and Companion) first, and then separately install the gr-radio_astro program, according to the instructions in GitHub?

(For now, I'm still working on Windows, but am looking ahead to maybe trying a Pi4.)

Thanks again, Dave

[glangsto]

Hi Dave,

Great hearing from you again.

Our goal was to make it easy to get started with home radio astronomy.

Yes the download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NooElec, AIRSPY mini (6 MHz), SDRplay dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

You can “sudo su” to change the password. I will be changing the password to H1!drogen in the future, so that we’ll all know the same password.

(passwd pi)

Glen

PS Most of the work was done by the SDRPlay folks, and the the VNC session starts up running their diagnostic tools. They have have installed many many programs.

I do like using the SDRPlay RSP1A, except that the bias tee it has installed can not run the NooElec H1 amplifier, as the amplifier uses just a little too much current.

On Jun 9, 2020, at 12:00 PM, dave290 notifications@github.com wrote:

Glen,

I just wanted to clarify how to use the Raspberry Pi SDR OS download you shared:

• Will this OS overwrite the Raspbian (or Ubuntu) OS that may have been previously installed? • After it is installed, do I install GNU radio (and Companion) first, and then separately install the gr-radio_astro program, according to the instructions in GitHub? (For now, I'm still working on Windows, but am looking ahead to maybe trying a Pi4.)

Thanks again, Dave

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Glen,

Thank you, again. Final (?) silly questions:

Will this operating system still allow me to do other, non-SDR related things, or would I have to switch back to one of the systems that comes with the Pi ?

I have a 2.4 MHz RTL-SDR dongle which I know is capable of detecting 1.4 GHz. I'm assuming the software will still work with this lower bandwidth SDR.

Dave

On Tue, Jun 9, 2020 at 12:31 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Great hearing from you again.

Our goal was to make it easy to get started with home radio astronomy.

Yes the download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NooElec, AIRSPY mini (6 MHz), SDRplay dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

You can “sudo su” to change the password. I will be changing the password to H1!drogen in the future, so that we’ll all know the same password.

(passwd pi)

Glen

PS Most of the work was done by the SDRPlay folks, and the the VNC session starts up running their diagnostic tools. They have have installed many many programs.

I do like using the SDRPlay RSP1A, except that the bias tee it has installed can not run the NooElec H1 amplifier, as the amplifier uses just a little too much current.

On Jun 9, 2020, at 12:00 PM, dave290 notifications@github.com wrote:

Glen,

I just wanted to clarify how to use the Raspberry Pi SDR OS download you shared:

• Will this OS overwrite the Raspbian (or Ubuntu) OS that may have been previously installed? • After it is installed, do I install GNU radio (and Companion) first, and then separately install the gr-radio_astro program, according to the instructions in GitHub? (For now, I'm still working on Windows, but am looking ahead to maybe trying a Pi4.)

Thanks again, Dave

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641464422, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ3P35TSO32SMVLGU73RVZWYVANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

The download OS is a complete system. There are many non-SDR programs in the operating system. There is a web browser and document editing tools.

You can also use the “sudo apt-get ” command to install that

you want to install. Regards Glen I need to update the documentation a bit more, but you can use the 2.4 MHz dongle to take spectra and/or detect transient events. The two commands you need to know (and should be documented) are: 1: cd examples either: 2a: python NsfIntegrate30.py or 2b: gnuradio-companion NsfIntegrate30.grc Then change the bandwidth from 3.0 MHz to 2.4 MHz, in either one. Regards Glen > On Jun 9, 2020, at 6:23 PM, dave290 wrote: > > > Glen, > > Thank you, again. Final (?) silly questions: > > Will this operating system still allow me to do other, non-SDR related > things, or would I have to switch back to one of the systems that comes > with the Pi ? > > I have a 2.4 MHz RTL-SDR dongle which I know is capable of detecting 1.4 > GHz. I'm assuming the software will still work with this lower bandwidth > SDR. > > Dave > > > > > On Tue, Jun 9, 2020 at 12:31 PM Glen Langston > wrote: > >> Hi Dave, >> >> Great hearing from you again. >> >> Our goal was to make it easy to get started with home radio astronomy. >> >> Yes the download completely overwrites the previous contends of the SDcard. >> You can start with a new blank card (8, 16 or 32 GB). >> >> The OS has absolutely all the code you need to observe, except your >> horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NooElec, >> AIRSPY mini (6 MHz), SDRplay dongles. >> >> The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also >> installed. >> >> You have to login via VNC (Virtual Network Connection) on your PC. >> The PI address is 192.168.1.110 for the Raspberry Pi. >> >> You can “sudo su” to change the password. I will be changing >> the password to H1!drogen in the future, so that we’ll all know >> the same password. >> >> (passwd pi) >> >> Glen >> >> PS Most of the work was done by the SDRPlay folks, and the the VNC >> session starts up running their diagnostic tools. They have >> have installed many many programs. >> >> I do like using the SDRPlay RSP1A, except that the bias tee it has >> installed can not run the NooElec H1 amplifier, as the amplifier uses >> just a little too much current. >> >>> On Jun 9, 2020, at 12:00 PM, dave290 wrote: >>> >>> >>> Glen, >>> >>> I just wanted to clarify how to use the Raspberry Pi SDR OS download you >> shared: >>> >>> • Will this OS overwrite the Raspbian (or Ubuntu) OS that may have been >> previously installed? >>> • After it is installed, do I install GNU radio (and Companion) first, >> and then separately install the gr-radio_astro program, according to the >> instructions in GitHub? >>> (For now, I'm still working on Windows, but am looking ahead to maybe >> trying a Pi4.) >>> >>> Thanks again, >>> Dave >>> >>> — >>> You are receiving this because you commented. >>> Reply to this email directly, view it on GitHub, or unsubscribe. >>> >>> [ { "@context": "http://schema.org", "@type": "EmailMessage", >> "potentialAction": { "@type": "ViewAction", "target": " >> https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", >> "url": " >> https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641400047", >> "name": "View Issue" }, "description": "View this Issue on GitHub", >> "publisher": { "@type": "Organization", "name": "GitHub", "url": " >> https://github.com" } } ] >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> , >> or unsubscribe >> >> . >> > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or unsubscribe. > > [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641612813", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-641612813", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Okay. Thank you Glen.

[gvanem]

Sorry to butt in. I also tried building on Windows using MSVC-2019 and failed. E.g. on compiling lib/detect_impl.cc with stuff like:

 int r = clock_gettime(CLOCK_REALTIME, &ts);

Why not gr::high_res_timer_now();?

So I'm not sure what compiler is chosen to give Windows support. MinGW-w64?

[glangsto]

Hello Gisle,

Thanks for testing the build in Windows. What exactly was the error message?

We’ve not really gotten the clock time ultra-precise, on a Raspberry Pi, in any case. Maybe the gr::high_res_timer_now() might be exactly what we need. I’ll have to google the documentation.

Did the other modules build?

Best regards,

Glen

On Jun 11, 2020, at 8:47 AM, Gisle Vanem notifications@github.com wrote:

Sorry to butt in. I also tried building on Windows using MSVC-2019 and failed. E.g. on compiling lib/detect_impl.cc with stuff like:

int r = clock_gettime(CLOCK_REALTIME, &ts); Why not gr::high_res_timer_now();?

So I'm not sure what compiler is chosen to give Windows support. MinGW-w64?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642622957", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642622957", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[gvanem]

What exactly was the error message?

detect_impl.cc(121,29): error: use of undeclared identifier 'CLOCK_REALTIME'
      int r = clock_gettime(CLOCK_REALTIME, &ts);

Did the other modules build?

No, the mess the GNU-radio folks created when going from boost::shared_ptr to std::shared_ptr has made it impossible.

[glangsto]

Hi Gisle,

I think you’ve revealed the problem that we’ve not “Upgraded” to 3.8.

What build environment are you working in Gnuradio 3.7 or 3.8?

We’ve been making half hearted, repeatedly failed, attempts to get our code running with 3.8. There are just too many changes to figure them all out.

The gnuradio dynamic environment is great for code=super=heroes, but I’m afraid I’m stuck.

Sorry,

Glen

PS that’s why I’m recommending just downloading the gnuradio 3.7 with the whole OS for Raspberry Pi 4.

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes: https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

Our goal was to make it easy to get started with home radio astronomy.

The download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NESDR, AIRSPY mini (6 MHz), SDRplay RSP1A dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

PSS, We’d love to have a complete Raspberry PI OS download that included an operating Gnuradio 3.8, if it included support for AIRSPY, SDRPlay, NESDR and PlutoSdr.

I gave a live demo of a home radio telescope in operation, detecting the Milky Way.
The very beginning shows the telescope in operation, and the last 5 minutes shows the strong Milky Way signal you can see with only a 10inch diameter horn. My wife, Katherine, assisted by pointing the telescope on and off of the Milky Way.

The webinar is compressed to a reasonable size here: https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4 https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4

On Jun 11, 2020, at 1:28 PM, Gisle Vanem <notifications@github.com mailto:notifications@github.com> wrote:

What exactly was the error message?

detect_impl.cc http://detect_impl.cc/(121,29): error: use of undeclared identifier 'CLOCK_REALTIME' int r = clock_gettime(CLOCK_REALTIME, &ts);

Did the other modules build?

No, the mess the GNU-radio folks created when going from boost::shared_ptr to std::shared_ptr has made it impossible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org http://schema.org/", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444 https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444", "url": "https://github.com/WVURAIL/gr- https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com https://github.com/" } } ]

[dave290]

Glen,

Just to verify, I don't need the Sdrplay OS to run gr-radio_astro, right? In other words, it should still be possible for me to install the gr-radio_astro package on the Raspbian OS that comes with the Pi? (Of course, I would have to install GNU 3.7 on my own.)

Dave

On Thu, Jun 11, 2020 at 3:06 PM Glen Langston notifications@github.com wrote:

Hi Gisle,

I think you’ve revealed the problem that we’ve not “Upgraded” to 3.8.

What build environment are you working in Gnuradio 3.7 or 3.8?

We’ve been making half hearted, repeatedly failed, attempts to get our code running with 3.8. There are just too many changes to figure them all out.

The gnuradio dynamic environment is great for code=super=heroes, but I’m afraid I’m stuck.

Sorry,

Glen

PS that’s why I’m recommending just downloading the gnuradio 3.7 with the whole OS for Raspberry Pi 4.

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes:

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing < https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

Our goal was to make it easy to get started with home radio astronomy.

The download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NESDR, AIRSPY mini (6 MHz), SDRplay RSP1A dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

PSS, We’d love to have a complete Raspberry PI OS download that included an operating Gnuradio 3.8, if it included support for AIRSPY, SDRPlay, NESDR and PlutoSdr.

I gave a live demo of a home radio telescope in operation, detecting the Milky Way. The very beginning shows the telescope in operation, and the last 5 minutes shows the strong Milky Way signal you can see with only a 10inch diameter horn. My wife, Katherine, assisted by pointing the telescope on and off of the Milky Way.

The webinar is compressed to a reasonable size here:

https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4 < https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4

On Jun 11, 2020, at 1:28 PM, Gisle Vanem <notifications@github.com mailto:notifications@github.com> wrote:

What exactly was the error message?

detect_impl.cc http://detect_impl.cc/(121,29): error: use of undeclared identifier 'CLOCK_REALTIME' int r = clock_gettime(CLOCK_REALTIME, &ts);

Did the other modules build?

No, the mess the GNU-radio folks created when going from boost::shared_ptr to std::shared_ptr has made it impossible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org http://schema.org/", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444 < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444>", "url": "https://github.com/WVURAIL/gr- https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com https://github.com/" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642901089, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ4UKSFEBS6CDT2JRP3RWE2MRANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Certainly you can install Gnuradio yourself. Depending on the SDR you’re using it could completely install the device SDR support too.

After installing gr-radio_astro, there is are test programs

vectordemo.py and vectordemo_c2.py

in gr-radio_astro/examples

that test our custom software build, but don’t require an SDR.

However that is considerably more work than just downloading and writing the OS onto a SD card.

At minimum, installing the SD card version allows testing your hardware, separate from the install.

Glen

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes: https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

On Jun 15, 2020, at 5:34 PM, dave290 notifications@github.com wrote:

Glen,

Just to verify, I don't need the Sdrplay OS to run gr-radio_astro, right? In other words, it should still be possible for me to install the gr-radio_astro package on the Raspbian OS that comes with the Pi? (Of course, I would have to install GNU 3.7 on my own.)

Dave

On Thu, Jun 11, 2020 at 3:06 PM Glen Langston notifications@github.com wrote:

Hi Gisle,

I think you’ve revealed the problem that we’ve not “Upgraded” to 3.8.

What build environment are you working in Gnuradio 3.7 or 3.8?

We’ve been making half hearted, repeatedly failed, attempts to get our code running with 3.8. There are just too many changes to figure them all out.

The gnuradio dynamic environment is great for code=super=heroes, but I’m afraid I’m stuck.

Sorry,

Glen

PS that’s why I’m recommending just downloading the gnuradio 3.7 with the whole OS for Raspberry Pi 4.

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes:

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing < https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

Our goal was to make it easy to get started with home radio astronomy.

The download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NESDR, AIRSPY mini (6 MHz), SDRplay RSP1A dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

PSS, We’d love to have a complete Raspberry PI OS download that included an operating Gnuradio 3.8, if it included support for AIRSPY, SDRPlay, NESDR and PlutoSdr.

I gave a live demo of a home radio telescope in operation, detecting the Milky Way. The very beginning shows the telescope in operation, and the last 5 minutes shows the strong Milky Way signal you can see with only a 10inch diameter horn. My wife, Katherine, assisted by pointing the telescope on and off of the Milky Way.

The webinar is compressed to a reasonable size here:

https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4 < https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4

On Jun 11, 2020, at 1:28 PM, Gisle Vanem <notifications@github.com mailto:notifications@github.com> wrote:

What exactly was the error message?

detect_impl.cc http://detect_impl.cc/(121,29): error: use of undeclared identifier 'CLOCK_REALTIME' int r = clock_gettime(CLOCK_REALTIME, &ts);

Did the other modules build?

No, the mess the GNU-radio folks created when going from boost::shared_ptr to std::shared_ptr has made it impossible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org http://schema.org/", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444 < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444>", "url": "https://github.com/WVURAIL/gr- https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com https://github.com/" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642901089, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ4UKSFEBS6CDT2JRP3RWE2MRANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-644402381", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-644402381", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Got it. Thank you!

On Tue, Jun 16, 2020 at 6:04 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Certainly you can install Gnuradio yourself. Depending on the SDR you’re using it could completely install the device SDR support too.

After installing gr-radio_astro, there is are test programs

vectordemo.py and vectordemo_c2.py

in gr-radio_astro/examples

that test our custom software build, but don’t require an SDR.

However that is considerably more work than just downloading and writing the OS onto a SD card.

At minimum, installing the SD card version allows testing your hardware, separate from the install.

Glen

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes:

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

On Jun 15, 2020, at 5:34 PM, dave290 notifications@github.com wrote:

Glen,

Just to verify, I don't need the Sdrplay OS to run gr-radio_astro, right? In other words, it should still be possible for me to install the gr-radio_astro package on the Raspbian OS that comes with the Pi? (Of course, I would have to install GNU 3.7 on my own.)

Dave

On Thu, Jun 11, 2020 at 3:06 PM Glen Langston notifications@github.com wrote:

Hi Gisle,

I think you’ve revealed the problem that we’ve not “Upgraded” to 3.8.

What build environment are you working in Gnuradio 3.7 or 3.8?

We’ve been making half hearted, repeatedly failed, attempts to get our code running with 3.8. There are just too many changes to figure them all out.

The gnuradio dynamic environment is great for code=super=heroes, but I’m afraid I’m stuck.

Sorry,

Glen

PS that’s why I’m recommending just downloading the gnuradio 3.7 with the whole OS for Raspberry Pi 4.

Here’s the Raspberry PI OS for SDRs. It will run on a Pi 3, but runs much better on a Pi 4. It is BIG, 2.3 Gigabytes:

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing <

https://drive.google.com/file/d/1yjCdpyF_T0Lb4uwVfz-mSzp4DTqDq6Uj/view?usp=sharing

Our goal was to make it easy to get started with home radio astronomy.

The download completely overwrites the previous contends of the SDcard. You can start with a new blank card (8, 16 or 32 GB).

The OS has absolutely all the code you need to observe, except your horn, and the SDR. The code works with AIRSPY full-size (10 MHz), NESDR, AIRSPY mini (6 MHz), SDRplay RSP1A dongles.

The OS has Gnuradio 3.7+ installed, with all the WVURAIL code also installed.

You have to login via VNC (Virtual Network Connection) on your PC. The PI address is 192.168.1.110 for the Raspberry Pi.

PSS, We’d love to have a complete Raspberry PI OS download that included an operating Gnuradio 3.8, if it included support for AIRSPY, SDRPlay, NESDR and PlutoSdr.

I gave a live demo of a home radio telescope in operation, detecting the Milky Way. The very beginning shows the telescope in operation, and the last 5 minutes shows the strong Milky Way signal you can see with only a 10inch diameter horn. My wife, Katherine, assisted by pointing the telescope on and off of the Milky Way.

The webinar is compressed to a reasonable size here:

https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4 <

https://www.gb.nrao.edu/~glangsto/aas2020/Langston2020AasTelescopeWebinar.mp4

On Jun 11, 2020, at 1:28 PM, Gisle Vanem <notifications@github.com mailto:notifications@github.com> wrote:

What exactly was the error message?

detect_impl.cc http://detect_impl.cc/(121,29): error: use of undeclared identifier 'CLOCK_REALTIME' int r = clock_gettime(CLOCK_REALTIME, &ts);

Did the other modules build?

No, the mess the GNU-radio folks created when going from boost::shared_ptr to std::shared_ptr has made it impossible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org http://schema.org/", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444 <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642825444 ", "url": "https://github.com/WVURAIL/gr- <https://github.com/WVURAIL/gr- radio_astro/issues/20#issuecomment-642825444", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com https://github.com/" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-642901089 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ4UKSFEBS6CDT2JRP3RWE2MRANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-644402381", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-644402381", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-644694549, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2OQZWDRBMPC4UV4CDRW5GVJANCNFSM4NS6UUEQ .

[dave290]

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi notifications@github.com wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi notifications@github.com wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston notifications@github.com wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi <notifications@github.com

wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ .

[dave290]

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz physicsmandave@gmail.com wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston notifications@github.com wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz physicsmandave@gmail.com wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston notifications@github.com wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Okay, I'll try this.

(Also, I did follow your instrux to modify the file Nsfintegrate30.py, changing 3e6 on line 84 to 2.4e6. Still get same error message)

Taking my daughter to get her an apartment for next semester, so I probably won't do more until the weekend.

Thanks, Dave

On Fri, Jun 19, 2020 at 11:12 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz <physicsmandave@gmail.com

wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646723332, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ3TNWEZ3OMEQASW7XTRXOFAXANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Sorry my message was unclear. You didn’t need to modify NsfItegrate30.py

That’s created by gnuradio-companion, so changes won’t stay.

The "git pull" step will fix all the problems, I think.

No need to recompile or anything.

after the update, just run the program again.

Glen

PS you might now get a message about overwriting, since you changed a file. Delete any files that “git" complains will be overwritten

On Jun 19, 2020, at 12:22 PM, dave290 notifications@github.com wrote:

Okay, I'll try this.

(Also, I did follow your instrux to modify the file Nsfintegrate30.py, changing 3e6 on line 84 to 2.4e6. Still get same error message)

Taking my daughter to get her an apartment for next semester, so I probably won't do more until the weekend.

Thanks, Dave

On Fri, Jun 19, 2020 at 11:12 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz <physicsmandave@gmail.com

wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646723332, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ3TNWEZ3OMEQASW7XTRXOFAXANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Okay, I did the git pull, and the new files transferred properly (after I deleted the files that git complained about overwriting)

When I ran rtl_test from command line, it said 52 bytes were lost in async mode with sample rate at 2.048 MHz. (It's not clear to me how to change the sample rate to 2.4 MHz used for this test program, but maybe that's not necessary?)

When I run NsfIntegrate30 in Gnu, I still get this error message: File "/usr/local/lib/python2.7/dist-packages/radio_astro/radioastronomy.py", line 740 in, read_spec_ast f2=open(fullname,'r') IOError: [Errno 2] No such file or directory: 'Integrate30.not'

On Fri, Jun 19, 2020 at 11:51 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Sorry my message was unclear. You didn’t need to modify NsfItegrate30.py

That’s created by gnuradio-companion, so changes won’t stay.

The "git pull" step will fix all the problems, I think.

No need to recompile or anything.

after the update, just run the program again.

Glen

PS you might now get a message about overwriting, since you changed a file. Delete any files that “git" complains will be overwritten

On Jun 19, 2020, at 12:22 PM, dave290 notifications@github.com wrote:

Okay, I'll try this.

(Also, I did follow your instrux to modify the file Nsfintegrate30.py, changing 3e6 on line 84 to 2.4e6. Still get same error message)

Taking my daughter to get her an apartment for next semester, so I probably won't do more until the weekend.

Thanks, Dave

On Fri, Jun 19, 2020 at 11:12 AM Glen Langston <notifications@github.com

wrote:

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz < physicsmandave@gmail.com

wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646723332 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ3TNWEZ3OMEQASW7XTRXOFAXANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646749168, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZZZF5PK7DNNZELE6DLRXOJP3ANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

On Jun 19, 2020, at 6:11 PM, dave290 notifications@github.com wrote:

Okay, I did the git pull, and the new files transferred properly (after I deleted the files that git complained about overwriting)

When I ran rtl_test from command line, it said 52 bytes were lost in async mode with sample rate at 2.048 MHz. (It's not clear to me how to change the sample rate to 2.4 MHz used for this test program, but maybe that's not necessary?)

When I run NsfIntegrate30 in Gnu, I still get this error message: File "/usr/local/lib/python2.7/dist-packages/radio_astro/radioastronomy.py", line 740 in, read_spec_ast f2=open(fullname,'r') IOError: [Errno 2] No such file or directory: 'Integrate30.not'

On Fri, Jun 19, 2020 at 11:51 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Sorry my message was unclear. You didn’t need to modify NsfItegrate30.py

That’s created by gnuradio-companion, so changes won’t stay.

The "git pull" step will fix all the problems, I think.

No need to recompile or anything.

after the update, just run the program again.

Glen

PS you might now get a message about overwriting, since you changed a file. Delete any files that “git" complains will be overwritten

On Jun 19, 2020, at 12:22 PM, dave290 notifications@github.com wrote:

Okay, I'll try this.

(Also, I did follow your instrux to modify the file Nsfintegrate30.py, changing 3e6 on line 84 to 2.4e6. Still get same error message)

Taking my daughter to get her an apartment for next semester, so I probably won't do more until the weekend.

Thanks, Dave

On Fri, Jun 19, 2020 at 11:12 AM Glen Langston <notifications@github.com

wrote:

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz < physicsmandave@gmail.com

wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646723332 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ3TNWEZ3OMEQASW7XTRXOFAXANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646749168, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZZZF5PK7DNNZELE6DLRXOJP3ANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646877755", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646877755", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

On Jun 19, 2020, at 6:11 PM, dave290 notifications@github.com wrote:

Okay, I did the git pull, and the new files transferred properly (after I deleted the files that git complained about overwriting)

When I ran rtl_test from command line, it said 52 bytes were lost in async mode with sample rate at 2.048 MHz. (It's not clear to me how to change the sample rate to 2.4 MHz used for this test program, but maybe that's not necessary?)

When I run NsfIntegrate30 in Gnu, I still get this error message: File "/usr/local/lib/python2.7/dist-packages/radio_astro/radioastronomy.py", line 740 in, read_spec_ast f2=open(fullname,'r') IOError: [Errno 2] No such file or directory: 'Integrate30.not'

On Fri, Jun 19, 2020 at 11:51 AM Glen Langston <notifications@github.com

wrote:

Hi Dave,

Sorry my message was unclear. You didn’t need to modify NsfItegrate30.py

That’s created by gnuradio-companion, so changes won’t stay.

The "git pull" step will fix all the problems, I think.

No need to recompile or anything.

after the update, just run the program again.

Glen

PS you might now get a message about overwriting, since you changed a file. Delete any files that “git" complains will be overwritten

On Jun 19, 2020, at 12:22 PM, dave290 notifications@github.com wrote:

Okay, I'll try this.

(Also, I did follow your instrux to modify the file Nsfintegrate30.py, changing 3e6 on line 84 to 2.4e6. Still get same error message)

Taking my daughter to get her an apartment for next semester, so I probably won't do more until the weekend.

Thanks, Dave

On Fri, Jun 19, 2020 at 11:12 AM Glen Langston < notifications@github.com

wrote:

Hi Dave,

Thanks! Glad you were able to get the system to run.

I’d run some tests yesterday with the NeSDR dongle and found it was dropping some samples at 3.0 MHz.

2.4 MHz was running without drops.

I updated the repository yesterday. So, you might do the following to finish up.

cd ~/Research/gr-radio_astro git pull

cd examples

python NsfIntegrate30.py

or

python NsfIntegrate24.py

Good Luck

Glen

There is a test program: rtl_test

Try different sample rates

rtl_test -s 2e6

works fine

rtl_test -s 3e6

shows dropped samples

On Jun 19, 2020, at 11:57 AM, dave290 notifications@github.com wrote:

Also, both vector_demo.py and vector_demo2.py appear to work just fine.

On Fri, Jun 19, 2020 at 10:51 AM David Schultz < physicsmandave@gmail.com

wrote:

Hi Glen, Good news! I had problems getting etcher to work last night, but now it's working. I downloaded SDRplay and successfully installed/opened this on the pi. From within Gnu Companion, I can open NSFintegrate30. Right now, when I run it, I do get an error message, "IOError:[Errno 2] No such file or directory: 'Integrate30.not' However, I have yet to read the instructions(!) Please let me know if you think there is something I should fix. Dave

On Fri, Jun 19, 2020 at 10:40 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

You’re make pretty good progress. Glad to hear it!

But

You’re not done yet. There are several more steps that will take a while to get right. That’s why I asked you to try downloading the whole, complete, system.

Here are the first few of the Linux steps:

cd ~ git clone http://www.github.com/WVURAIL/gr-radio_astro cd gr-radio_astro mkdir build cd build cmake ../ make -j 3 sudo make install sudo ldconfig

That will install the radio astronomy programs.

However you’ll also need some python libraries

sudo apt-get install pip

I don’t remember all the python libraries at the moment.

The python code will tell you what is needed.

Good luck!

Glen

(alternatively just write the whole OS to the SD card).

On Jun 19, 2020, at 7:46 AM, dave290 notifications@github.com wrote:

Hi Pranav,

So, I obtained a Raspberry Pi 4 for running the radio astro program. I figured that the first thing to try was to go with the standard Raspbian OS. I was able to successfully install Gnuradio 3.7 and connect to my RTL-SDR.

Question: the installation instructions on GitHub for gr-radio_astro say to create a folder named "Build" within the existing folder "gr-XXX." Which folder, specifically, is "gr-XXX" ?

/usr/include/gnuradio - Contains all sorts of subfolders for gnu blocks, etc. /etc/gnuradio/config.d - Contains 11 .conf files for gnu /home/pi/.gnuradio/prefs - Contains 1 file, vmcircbuf.default_factory

I feel like the first folder is the appropriate one, but I wanted to check before I unpacked the zip file.

Thanks, Dave

On Fri, Jun 5, 2020 at 9:40 AM Pranav Sanghavi < notifications@github.com> wrote:

Well, it seems like I’ll have to fast track work on the windows compatible latest version of the package. We usually try to convince people to install Ubuntu on their computers because it just works beautifully but I can understand it might not even be feasible for some.

I’ll try and have one as soon as possible so that you can continue working on one. In the meantime if you’re open to installing Ubuntu feel free to email me (should be on my user profile page) I can help you through the process. 😅

Best, Pranav.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-639537963

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2D6YWSYV7XMR7FBSDRVD7XVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880

",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646591880

",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646703200

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZYXO7OWYM2ZFJPL7L3RXOBFVANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646711130 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646723332

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ3TNWEZ3OMEQASW7XTRXOFAXANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646728101 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646749168 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZZZF5PK7DNNZELE6DLRXOJP3ANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646877755", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646877755", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646908490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZZLSA45A7O5W76TKZTRXQA3JANCNFSM4NS6UUEQ .

<<< Welcome to GNU Radio Companion 3.7.13.4 >>>

Block paths: /usr/share/gnuradio/grc/blocks /usr/local/share/gnuradio/grc/blocks

Loading: "/home/pi/examples/NsfIntegrate30.grc"

Done

Generating: '/home/pi/examples/NsfIntegrate30.py'

Generating: '/home/pi/examples/NsfIntegrate30.py'

Executing: /usr/bin/python2 -u /home/pi/examples/NsfIntegrate30.py

Python package: h5py Not found. If needed, at the command line type: sudo apt install python-h5py or pip install h5py However we dom't recommend installing python packages using pip Use your OS local package manager used to install gnuradio to maintain consistent python environments

Python package: h5py Not found. If needed, at the command line type: pip install h5py

Python package: h5py Not found. If needed, at the command line type: sudo apt install h5py or pip install h5py However we dom't recommend installing python packages using pip Use your OS local package manager used to install 'gnuradio' to maintain consistent python environments

qt5ct: using qt5ct plugin Medianing 4 vectorsMedianing 4 vectorsMedianing 4 vectorsMedianing 4 vectorsTraceback (most recent call last): File "/home/pi/examples/NsfIntegrate30.py", line 1018, in main() File "/home/pi/examples/NsfIntegrate30.py", line 1006, in main tb = top_block_cls() File "/home/pi/examples/NsfIntegrate30.py", line 357, in init self.radio_astro_ra_integrate_1 = radio_astro.ra_integrate(ObsName+".not", observers_save, fftsize, Frequency, Bandwidth, Azimuth, Elevation, Record, obstype, int(4**4), units, 295., 10.) File "/usr/local/lib/python2.7/dist-packages/radio_astro/ra_integrate.py", line 116, in init self.obs.read_spec_ast(self.noteName) # read the parameters File "/usr/local/lib/python2.7/dist-packages/radio_astro/radioastronomy.py", line 740, in read_spec_ast f2 = open(fullname, 'r') IOError: [Errno 2] No such file or directory: 'Integrate30.not'

Done

[glangsto]

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com mailto:notifications@github.com> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston <notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

[dave290]

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston <notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ .

[glangsto]

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston <notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston notifications@github.com wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston notifications@github.com wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston notifications@github.com wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave and all,

I’ve been trying to diagnose the issue Dave was having with gnuradio-companion not finding some log files. So far not much progress.

In the mean time, I’ve updated the Raspberry Pi Kernel to enable the “Precision Time Protocol” ptp. I also figured out how to install h5py (which is apt-get install python-h5py), so that error message is gone.

EasyPlay, SDRplay’s, initial interface now lists 4 different sample rates for spectra. Pick the rate for your SDR.

1) NeSDR 3.0 MHz 2) AIRSPY mini 6.0 MHz 3) PlutoSdr 7.0 MHz 4) SDRplay 9.0 MHz.

There are programs to make spectral line observations and also detect transient events.

The New, Complete OS is at link:

https://drive.google.com/file/d/1SOLhVh1KSAWBeMOK1Z_dQSgP7h3LBLy0/view?usp=sharing

This is a 2.8 GByte file. It should be written to the SDcard with balena etcher.

Good Luck,

Glen

PS more changes will be needed to get the timing update complete, but this is a start on getting to micro-second accurate time on the Pis.

On Jun 22, 2020, at 2:49 PM, dave290 notifications@github.com wrote:

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston notifications@github.com wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Hi Glen,

Quick question: Can you tell me the username and password needed to login to the SDR-EasyPlay OS that you updated on GitHub, and shared in your last post? I copied the June 22 version to a SD card, and the first time I used it, I was able to start up without any password prompt. However, the second and third times, I was prompted for a username and password. You previously mentioned "Pi" was the username, and I have tried this with many combinations of obvious passwords (including none at all), to no avail.

Soon, I should be able to give you a longer report on what's working..

Thanks, Dave

On Mon, Jun 22, 2020 at 9:21 PM Glen Langston notifications@github.com wrote:

Hi Dave and all,

I’ve been trying to diagnose the issue Dave was having with gnuradio-companion not finding some log files. So far not much progress.

In the mean time, I’ve updated the Raspberry Pi Kernel to enable the “Precision Time Protocol” ptp. I also figured out how to install h5py (which is apt-get install python-h5py), so that error message is gone.

EasyPlay, SDRplay’s, initial interface now lists 4 different sample rates for spectra. Pick the rate for your SDR.

1) NeSDR 3.0 MHz 2) AIRSPY mini 6.0 MHz 3) PlutoSdr 7.0 MHz 4) SDRplay 9.0 MHz.

There are programs to make spectral line observations and also detect transient events.

The New, Complete OS is at link:

https://drive.google.com/file/d/1SOLhVh1KSAWBeMOK1Z_dQSgP7h3LBLy0/view?usp=sharing

This is a 2.8 GByte file. It should be written to the SDcard with balena etcher.

Good Luck,

Glen

PS more changes will be needed to get the timing update complete, but this is a start on getting to micro-second accurate time on the Pis.

On Jun 22, 2020, at 2:49 PM, dave290 notifications@github.com wrote:

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston < notifications@github.com> wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647866210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ6YVB6GO7HVFKKHL3TRYAGQ7ANCNFSM4NS6UUEQ .

[dave290]

Please ignore my previous email. I re-loaded the OS from a new as card, and am no longer prompted for login info. I will get back to you soon to let you know how things are progressing.

On Mon, Jun 29, 2020 at 4:02 PM David Schultz physicsmandave@gmail.com wrote:

Hi Glen,

Quick question: Can you tell me the username and password needed to login to the SDR-EasyPlay OS that you updated on GitHub, and shared in your last post? I copied the June 22 version to a SD card, and the first time I used it, I was able to start up without any password prompt. However, the second and third times, I was prompted for a username and password. You previously mentioned "Pi" was the username, and I have tried this with many combinations of obvious passwords (including none at all), to no avail.

Soon, I should be able to give you a longer report on what's working..

Thanks, Dave

On Mon, Jun 22, 2020 at 9:21 PM Glen Langston notifications@github.com wrote:

Hi Dave and all,

I’ve been trying to diagnose the issue Dave was having with gnuradio-companion not finding some log files. So far not much progress.

In the mean time, I’ve updated the Raspberry Pi Kernel to enable the “Precision Time Protocol” ptp. I also figured out how to install h5py (which is apt-get install python-h5py), so that error message is gone.

EasyPlay, SDRplay’s, initial interface now lists 4 different sample rates for spectra. Pick the rate for your SDR.

1) NeSDR 3.0 MHz 2) AIRSPY mini 6.0 MHz 3) PlutoSdr 7.0 MHz 4) SDRplay 9.0 MHz.

There are programs to make spectral line observations and also detect transient events.

The New, Complete OS is at link:

https://drive.google.com/file/d/1SOLhVh1KSAWBeMOK1Z_dQSgP7h3LBLy0/view?usp=sharing

This is a 2.8 GByte file. It should be written to the SDcard with balena etcher.

Good Luck,

Glen

PS more changes will be needed to get the timing update complete, but this is a start on getting to micro-second accurate time on the Pis.

On Jun 22, 2020, at 2:49 PM, dave290 notifications@github.com wrote:

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston <notifications@github.com

wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston < notifications@github.com> wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647866210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ6YVB6GO7HVFKKHL3TRYAGQ7ANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

There are a number of improvements in the latest versions. But maybe nothing critical for you. The word for all recent releases is

H!1drogen

I can not exactly remember what it was for the June 22 version, but I think it is that.

Note that for VNC there is no word needed. Once in, you can

sudo su

then change the pi word without needing to know the word.

Hope this helps!

Glen

The latest documentation is at

https://docs.google.com/document/d/10SegmKq_nLdu9Da8dwwof2xG5J1gole3f95JdRaEIxQ/edit?usp=sharing

and contains a link to the latest OS. Which is also below. The word is definitely the above for this version of the OS.

https://drive.google.com/file/d/12QfEosneqLEIQL4mx86z0q3VjvDUbd2x/view?usp=sharing

On Jun 29, 2020, at 5:02 PM, dave290 notifications@github.com wrote:

Hi Glen,

Quick question: Can you tell me the username and password needed to login to the SDR-EasyPlay OS that you updated on GitHub, and shared in your last post? I copied the June 22 version to a SD card, and the first time I used it, I was able to start up without any password prompt. However, the second and third times, I was prompted for a username and password. You previously mentioned "Pi" was the username, and I have tried this with many combinations of obvious passwords (including none at all), to no avail.

Soon, I should be able to give you a longer report on what's working..

Thanks, Dave

On Mon, Jun 22, 2020 at 9:21 PM Glen Langston notifications@github.com wrote:

Hi Dave and all,

I’ve been trying to diagnose the issue Dave was having with gnuradio-companion not finding some log files. So far not much progress.

In the mean time, I’ve updated the Raspberry Pi Kernel to enable the “Precision Time Protocol” ptp. I also figured out how to install h5py (which is apt-get install python-h5py), so that error message is gone.

EasyPlay, SDRplay’s, initial interface now lists 4 different sample rates for spectra. Pick the rate for your SDR.

1) NeSDR 3.0 MHz 2) AIRSPY mini 6.0 MHz 3) PlutoSdr 7.0 MHz 4) SDRplay 9.0 MHz.

There are programs to make spectral line observations and also detect transient events.

The New, Complete OS is at link:

https://drive.google.com/file/d/1SOLhVh1KSAWBeMOK1Z_dQSgP7h3LBLy0/view?usp=sharing

This is a 2.8 GByte file. It should be written to the SDcard with balena etcher.

Good Luck,

Glen

PS more changes will be needed to get the timing update complete, but this is a start on getting to micro-second accurate time on the Pis.

On Jun 22, 2020, at 2:49 PM, dave290 notifications@github.com wrote:

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston notifications@github.com wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston < notifications@github.com> wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647866210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ6YVB6GO7HVFKKHL3TRYAGQ7ANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-651364107", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-651364107", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Greetings Glen,

I hope you had a nice holiday weekend.

Good news! I have been able to collect hydrogen line data with gr-radio-astro on my raspberry pi. I'll share the details below. Data was collected with the June 22 version of the software (I recently updated to the June 28 version.)

I initially collected data with the file "spectrometer_w_cal.grc" I was able to open this in Companion and run it without problems (the h5py error message no longer appears.) I followed the instructions posted on GitHub, and collected data while looking into Perseus (target=Mirfak, 5 second collection time.) The data is shown in the attached files, Mirfak1-grastro.jpg and Mirfak2-grastro.jpg I also included files to show the hot and cold spectra I obtained, using the rtl-sdr at 2.4 MHz The first file is funky looking, since there is a negative dip in front of the two real peaks; however, I also had very bumpy hot and cold spectra. The second Mirfak scan looks better, since I found better locations for my hot and cold scans. I live in an urban neighborhood, with lots of power lines and a very narrow window of sky overhead. (I'm planning to do some night-time observations and am going to try to get access to my school's athletic field, which offers a much less obstructed view of the sky!)

For comparison, I also collected data using my own flowgraph program, which is much less sophisticated (it does not average, nor filter, nor do the boxcar/sinc function operation.) However, it does subtract a "cold" background. The result is shown in the file "Mirfak-Myprogram.jpg" You will see the same two features. Also notice the two features at lower frequencies, which appear to be some sort of aliasing effect (e.g. when I change the center frequency of my observation, these features "walk" around.) Anyway, I'm not worried, because I'm not planning to use this, but just wanted to make a comparison. I attached a png of my flowgraph, also.

I have not yet tried the NsfIntegrate24 to collect data, but I did notice that it can be run directly from a terminal, without a problem. (If I try to run this from Companion, I still get the error message that NsfIntegrate.not cannot be found.)

Do you recommend using NsfIntegrate instead of spectrometer_w_cal? Is there some advantage to one over the other? I noticed that the former program involves splitting the signal into four pieces and then recombining. The latter uses vector median blocks, is the logic different here?

Glen, thanks so much for your help getting this set up. I hope my questions were useful to you in some way. I plan to reach out to Prof. Bandura this week to join the radio-astro teacher group. I'd also like to stay in touch, as I would like to get my students involved (pandemic-allowing) with a project. Along those lines, I will use your non-git hub email address.

Best, David

On Mon, Jun 29, 2020 at 8:42 PM Glen Langston notifications@github.com wrote:

Hi Dave,

There are a number of improvements in the latest versions. But maybe nothing critical for you. The word for all recent releases is

H!1drogen

I can not exactly remember what it was for the June 22 version, but I think it is that.

Note that for VNC there is no word needed. Once in, you can

sudo su

then change the pi word without needing to know the word.

Hope this helps!

Glen

The latest documentation is at

https://docs.google.com/document/d/10SegmKq_nLdu9Da8dwwof2xG5J1gole3f95JdRaEIxQ/edit?usp=sharing

and contains a link to the latest OS. Which is also below. The word is definitely the above for this version of the OS.

https://drive.google.com/file/d/12QfEosneqLEIQL4mx86z0q3VjvDUbd2x/view?usp=sharing

On Jun 29, 2020, at 5:02 PM, dave290 notifications@github.com wrote:

Hi Glen,

Quick question: Can you tell me the username and password needed to login to the SDR-EasyPlay OS that you updated on GitHub, and shared in your last post? I copied the June 22 version to a SD card, and the first time I used it, I was able to start up without any password prompt. However, the second and third times, I was prompted for a username and password. You previously mentioned "Pi" was the username, and I have tried this with many combinations of obvious passwords (including none at all), to no avail.

Soon, I should be able to give you a longer report on what's working..

Thanks, Dave

On Mon, Jun 22, 2020 at 9:21 PM Glen Langston notifications@github.com wrote:

Hi Dave and all,

I’ve been trying to diagnose the issue Dave was having with gnuradio-companion not finding some log files. So far not much progress.

In the mean time, I’ve updated the Raspberry Pi Kernel to enable the “Precision Time Protocol” ptp. I also figured out how to install h5py (which is apt-get install python-h5py), so that error message is gone.

EasyPlay, SDRplay’s, initial interface now lists 4 different sample rates for spectra. Pick the rate for your SDR.

1) NeSDR 3.0 MHz 2) AIRSPY mini 6.0 MHz 3) PlutoSdr 7.0 MHz 4) SDRplay 9.0 MHz.

There are programs to make spectral line observations and also detect transient events.

The New, Complete OS is at link:

https://drive.google.com/file/d/1SOLhVh1KSAWBeMOK1Z_dQSgP7h3LBLy0/view?usp=sharing

This is a 2.8 GByte file. It should be written to the SDcard with balena etcher.

Good Luck,

Glen

PS more changes will be needed to get the timing update complete, but this is a start on getting to micro-second accurate time on the Pis.

On Jun 22, 2020, at 2:49 PM, dave290 notifications@github.com wrote:

Hi Glen,

Sounds good. I will try the software this week, sans Companion. I'll also see if I can do some trouble-shooting to see what's going on with Companion. I'm pretty new to Linux and GNU, so my progress is a little slow.

Thanks again for all of your help!

Dave

PS: I will send an email to your NSF address this afternoon.

On Mon, Jun 22, 2020 at 9:53 AM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks for your email. I’ve been trying to figure out why

gnuradio-companion is not finding the "*.not" (which stands for note, by the way).

So far I can only say it works for me. Not sure what to try next actually. Since you’ve downloaded the whole OS it should be exactly the same for you. Any hints you might have would be helpful.

FYI only the header of the “.not" file is important, and should contain your telescope location and any other local information you happen to know.

When observing, it is also very important to set the computer time correct, to get good coordinates.

Anything on the Observing screen should be over written in your output files.

Also maybe you could introduce yourself and tell us your plans?

Thanks

Glen

On Jun 21, 2020, at 1:09 PM, dave290 notifications@github.com wrote:

Hi Glen,

Yes, I will try to run the observation programs in Python this week. Over the last month, I created some simple flowgraphs in Gnu Companion which allow me to integrate signals for up to 10 seconds and do a crude background subtraction. With these, I am able to see peaks with reasonable frequency shifts in cygnus and cassiopea, using a 2.4 MHz bandpass. I mention this only because I know when I'm seeing "real" signal and can use it as a starting point when testing your program. (My flowgraphs do not calculate a proper power spectrum, and I know there's a lot more math behind this!)

As an aside, I'm a little disappointed with Gnu Companion, since it seems to be very glitchy, in a platform-dependent way. I've been going through Michael Ossmann's tutorials, and have created flowgraphs with filters, audio sinks, etc for FM radio. Although my flowgraphs work fine on a Windows laptop, different errors pop up on the Pi, depending on whether I use Raspbian or SDRPLAY. I've got some work cut out for me in learning to debug these things.

I watched the webinar you shared on student and teacher projects, and I'm really impressed! Would you mind if I contact you through your NSF email address? I'd like to share a little more information about myself and my professional and personal interests in radio astronomy.

Thanks for checking out the issues with Companion. I feel like we're very close to figuring this out!

Dave

On Sat, Jun 20, 2020 at 9:42 PM Glen Langston < notifications@github.com> wrote:

HI Dave,

I’ll try to figure out why the Companion version is not finding the files. There may be some sort of configuration file that needs an update.

Can you do your initial observations by running python?

I’ll look at this tomorrow afternoon.

Thanks for your update.

I guess the vector demo programs are working in companion, because they do not use configuration files?

Thanks

Glen

On Jun 20, 2020, at 7:59 AM, dave290 notifications@github.com wrote:

Glen,

I have the feeling the problem is trying to run the program in Companion (I have been using this all along.)

I checked the /examples directory, and both of these files"NsfIntegrate24.py" and "NsfIntegrate30.py" are present, along with a host of other ".not" files for other bandwidths (24,30,32,45,59, ... 100.)

When I run both "NsfIntegrate24.py" and "NsfIntegrate30.py" in a terminal window from the /examples directory, both seem to work, starting up a GUI and recording data. However, if I run these in Companion, I get the error message that I reported earlier. That is, for the former program it says "Integrate24.not" is missing when I run NsfIntegrate24.grc, and that "Integrate30.not" is missing when I run NsfIntegrate30.grc. (In Companion, I open each file from the /examples directory, and build before running.)

I did not try to copy "24.not" to "30.not", since it appears the files are both present, and look essentially identical in content, except for the bandwidths and a few parameter values.

This may not be relevant, but I noticed that 24 and 30 do not have "Event" files (eg., NsfIntegrate24Event.not and NsfIntegrate30Event.not are missing, while these are not missing for the other values.) I noticed that these files are also missing from the GitHub repository. I tried to copy and modify the Event file from "Integrate32Event.not" and rename as "Integrate30Event.not", but this did not alter the error message.

On Fri, Jun 19, 2020 at 9:51 PM Glen Langston < notifications@github.com> wrote:

Hi Dave,

Thanks again. I see the log file. I guess your running the design from inside gnuradio-companion.

1) You can ignore the h5py messages, they are a part of a different design.

2) I’m guessing you’ve cd-ed into

cd ~/examples

can you type:

ls Integrate30.*

You should see the missing file “Integrate30.not” there. I’ve just done another pull and I find it in my copy.

If there are any other Integrate??.not files copy one to Integrate30.not I’m finding Integrate24.not

so, first try

python NsfIntegrate24.py

then try

cp Integrate24.not NsfIntegrate30.not

and

python NsfIntegrate30.py

Attached is a design running, right after a git pull of the entire repository, just a few minutes ago.

Sorry to not be able to figure this out yet.

Glen

On Jun 19, 2020, at 9:03 PM, dave290 <notifications@github.com <mailto: notifications@github.com>> wrote:

Glen,

I attached the complete log from Companion, following startup, building and running of NsfIntegrate30.

You'll note the message about not being able to find Python package h5py. I did not attempt to install this yet. If you think I should, then which directory should I do this from?

Next time you are in Chicago, I definitely owe you a beer or two!

Dave

On Fri, Jun 19, 2020 at 7:43 PM Glen Langston < notifications@github.com mailto:notifications@github.com> wrote:

Hi Dave,

Glad you’re back at it. Thanks for reporting in your experiences!

The rtl_test is really just to show that the device is working, which is good. Missing a few bytes (52) right at the beginning is fine. The device should work fine at 2.0 MHz and 2.4 MHz sampling rate, which is what you’ve found.

I’m glad the "git pull" worked.

Unfortunately I’m puzzled by the error file error.

Maybe I skipped an instruction step?

After startup, it is necessary to change directories (but I think you are doing this).

ie:

cd ~/examples

then either

python NsfIntegrate30.py

or

gnuradio-companion NsfIntegrate30.grc

In gnuradio-companion you need to build the design, which is one of the buttons on the top.

Could you copy exactly the messages you get and send them to me? I’ll see if I can figure it out. (I know this is not much help, but it works for me…)

Thanks!

Glen

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646926141

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ2VKCJK5GTI6HCS67DRXQP4FANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671

",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-646985671

",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647070411

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ3QJXCVRVIHABWVC7LRXVXTFANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ",

"url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647155334 ",

"name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647569290

,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AP25FZ7IHBO6I4M7IAXFZBDRX5V7JANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856 ", "url": "

https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647707856 ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-647866210 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ6YVB6GO7HVFKKHL3TRYAGQ7ANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-651364107", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-651364107", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-651467438, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ5GVYOUTR3GS4XCMJDRZE7IDANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

Very glad to hear you’ve made such good progress. Congratulations!

I’ve answered your questions below.

On Jul 6, 2020, at 2:19 PM, dave290 notifications@github.com wrote:

Greetings Glen,

I hope you had a nice holiday weekend.

Good news! I have been able to collect hydrogen line data with gr-radio-astro on my raspberry pi. I'll share the details below. Data was collected with the June 22 version of the software (I recently updated to the June 28 version.)

Great. The Event Capture part is working much better in the June 28 version. The spectrometer code did not change much, so for your tests there is really no difference. The newer interface is a little clearer (I hope).

I initially collected data with the file "spectrometer_w_cal.grc" I was able to open this in Companion and run it without problems (the h5py error message no longer appears.) I followed the instructions posted on GitHub, and collected data while looking into Perseus (target=Mirfak, 5 second collection time.) The data is shown in the attached files, Mirfak1-grastro.jpg and Mirfak2-grastro.jpg I also included files to show the hot and cold spectra I obtained, using the rtl-sdr at 2.4 MHz The first file is funky looking, since there is a negative dip in front of the two real peaks; however, I also had very bumpy hot and cold spectra. The second Mirfak scan looks better, since I found better locations for my hot and cold scans. I live in an urban neighborhood, with lots of power lines and a very narrow window of sky overhead. (I'm planning to do some night-time observations and am going to try to get access to my school's athletic field, which offers a much less obstructed view of the sky!)

The spectrometer_w_cal program works very well, I understand. Glad you had good experience with it.

The main advantage of NsfIntegrate is in the processing after the observations. These programs are all obtained via

git clone http://www.github.com/glangsto/analyze

There you can average, Fix, plot raw spectra, plot calibrated spectra and also make maps of the whole sky. My mode of operating is to build weather proof telescopes and leave them outside for years at a time.

Making 1 hour averages of the spectra in a 24 hour period shows (I think) very interesting changes in the sky and the arms of the Milky Way rotate in and out of the telescope beam.

For comparison, I also collected data using my own flowgraph program, which is much less sophisticated (it does not average, nor filter, nor do the boxcar/sinc function operation.) However, it does subtract a "cold" background. The result is shown in the file "Mirfak-Myprogram.jpg" You will see the same two features. Also notice the two features at lower frequencies, which appear to be some sort of aliasing effect (e.g. when I change the center frequency of my observation, these features "walk" around.) Anyway, I'm not worried, because I'm not planning to use this, but just wanted to make a comparison. I attached a png of my flowgraph, also.

I did not get the image. Can you send it again?

I have not yet tried the NsfIntegrate24 to collect data, but I did notice that it can be run directly from a terminal, without a problem. (If I try to run this from Companion, I still get the error message that NsfIntegrate.not cannot be found.)

I have not been able to figure out why the companion is “not" finding the .not file. Yes please consider the work around of building new versions in companion, then after creatinging them, exit companion and try

python “NewDesignName.py”

This should work, yet allow you to integrate.

Do you recommend using NsfIntegrate instead of spectrometer_w_cal? Is there some advantage to one over the other? I noticed that the former program involves splitting the signal into four pieces and then recombining. The latter uses vector median blocks, is the logic different here?

The Integrate programs try to suppress short term interference by “median filtering” the data”

Quick mathematics note: consider that average of 4 values:

3. 2. 32. 3.

If the “32” is considered short term interference (which happens in radio astronomy) the averages of these 4 values is still 40/4 = 10

The median of 4 values is the average middle two of the 4. The median is 3+3/2 = 3. If the 32 was actually due to interference, then median is a more reasonable value of the true signal from the galaxy.

To go on and on; the “truth” is unknown in science, but the “average” is the most efficient estimate of the “truth" for measurements with gaussian distributed noise.

However the median of a small number of values is also an efficient estimate of the “truth”, but is much more resistant to “outliers”. (There are mathematical papers on this).

Glen, thanks so much for your help getting this set up. I hope my questions were useful to you in some way. I plan to reach out to Prof. Bandura this week to join the radio-astro teacher group. I'd also like to stay in touch, as I would like to get my students involved (pandemic-allowing) with a project. Along those lines, I will use your non-git hub email address.

I’m very glad you’ve got the strength to get this far in radio astronomy. I’m declaring you a “Science Aficionado”!

Best regards,

Glen

Best, David

On Mon, Jun 29, 2020 at 8:42 PM Glen Langston notifications@github.com wrote:

[dave290]

Hi Glen,

Thanks for your detailed feedback (and encouragement!) I've attached 2 jpg files below, one showing Mirfak scan taken with spectometer_w_cal.grc and the other taken with a simpler flowgraph that does not incorporate averaging, median calcs, or boxcar splicing(?) of signal. I included a png of the flowgraph so you can see exactly what my flowgraph did. Again, note that there are two peaks that are common to both scans (around 1420.5 and 1420.6 MHz) However, the simpler flowgraph also shows alias peaks (I think) which change frequency if I change the center frequency of the scan. I guess that the comparison confirms the "real" peaks and shows the inadequacy of not boxcar splicing?

Dave

On Tue, Jul 7, 2020 at 1:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Very glad to hear you’ve made such good progress. Congratulations!

I’ve answered your questions below.

On Jul 6, 2020, at 2:19 PM, dave290 notifications@github.com wrote:

Greetings Glen,

I hope you had a nice holiday weekend.

Good news! I have been able to collect hydrogen line data with gr-radio-astro on my raspberry pi. I'll share the details below. Data was collected with the June 22 version of the software (I recently updated to the June 28 version.)

Great. The Event Capture part is working much better in the June 28 version. The spectrometer code did not change much, so for your tests there is really no difference. The newer interface is a little clearer (I hope).

I initially collected data with the file "spectrometer_w_cal.grc" I was able to open this in Companion and run it without problems (the h5py error message no longer appears.) I followed the instructions posted on GitHub, and collected data while looking into Perseus (target=Mirfak, 5 second collection time.) The data is shown in the attached files, Mirfak1-grastro.jpg and Mirfak2-grastro.jpg I also included files to show the hot and cold spectra I obtained, using the rtl-sdr at 2.4 MHz The first file is funky looking, since there is a negative dip in front of the two real peaks; however, I also had very bumpy hot and cold spectra. The second Mirfak scan looks better, since I found better locations for my hot and cold scans. I live in an urban neighborhood, with lots of power lines and a very narrow window of sky overhead. (I'm planning to do some night-time observations and am going to try to get access to my school's athletic field, which offers a much less obstructed view of the sky!)

The spectrometer_w_cal program works very well, I understand. Glad you had good experience with it.

The main advantage of NsfIntegrate is in the processing after the observations. These programs are all obtained via

git clone http://www.github.com/glangsto/analyze

There you can average, Fix, plot raw spectra, plot calibrated spectra and also make maps of the whole sky. My mode of operating is to build weather proof telescopes and leave them outside for years at a time.

Making 1 hour averages of the spectra in a 24 hour period shows (I think) very interesting changes in the sky and the arms of the Milky Way rotate in and out of the telescope beam.

For comparison, I also collected data using my own flowgraph program, which is much less sophisticated (it does not average, nor filter, nor do the boxcar/sinc function operation.) However, it does subtract a "cold" background. The result is shown in the file "Mirfak-Myprogram.jpg" You will see the same two features. Also notice the two features at lower frequencies, which appear to be some sort of aliasing effect (e.g. when I change the center frequency of my observation, these features "walk" around.) Anyway, I'm not worried, because I'm not planning to use this, but just wanted to make a comparison. I attached a png of my flowgraph, also.

I did not get the image. Can you send it again?

I have not yet tried the NsfIntegrate24 to collect data, but I did notice that it can be run directly from a terminal, without a problem. (If I try to run this from Companion, I still get the error message that NsfIntegrate.not cannot be found.)

I have not been able to figure out why the companion is “not" finding the .not file. Yes please consider the work around of building new versions in companion, then after creatinging them, exit companion and try

python “NewDesignName.py”

This should work, yet allow you to integrate.

Do you recommend using NsfIntegrate instead of spectrometer_w_cal? Is there some advantage to one over the other? I noticed that the former program involves splitting the signal into four pieces and then recombining. The latter uses vector median blocks, is the logic different here?

The Integrate programs try to suppress short term interference by “median filtering” the data”

Quick mathematics note: consider that average of 4 values:

3. 2. 32. 3.

If the “32” is considered short term interference (which happens in radio astronomy) the averages of these 4 values is still 40/4 = 10

The median of 4 values is the average middle two of the 4. The median is 3+3/2 = 3. If the 32 was actually due to interference, then median is a more reasonable value of the true signal from the galaxy.

To go on and on; the “truth” is unknown in science, but the “average” is the most efficient estimate of the “truth" for measurements with gaussian distributed noise.

However the median of a small number of values is also an efficient estimate of the “truth”, but is much more resistant to “outliers”. (There are mathematical papers on this).

Glen, thanks so much for your help getting this set up. I hope my questions were useful to you in some way. I plan to reach out to Prof. Bandura this week to join the radio-astro teacher group. I'd also like to stay in touch, as I would like to get my students involved (pandemic-allowing) with a project. Along those lines, I will use your non-git hub email address.

I’m very glad you’ve got the strength to get this far in radio astronomy. I’m declaring you a “Science Aficionado”!

Best regards,

Glen

Best, David

On Mon, Jun 29, 2020 at 8:42 PM Glen Langston notifications@github.com wrote:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655055422, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ7ALUBCVZBEXS3KXGTR2NVEBANCNFSM4NS6UUEQ .

[glangsto]

Hi Dave,

I still do not see the figures.

Maybe send them directly to me: glen.i.langston@gmail.com

Thanks

Glen

On Jul 7, 2020, at 4:00 PM, dave290 notifications@github.com wrote:

Hi Glen,

Thanks for your detailed feedback (and encouragement!) I've attached 2 jpg files below, one showing Mirfak scan taken with spectometer_w_cal.grc and the other taken with a simpler flowgraph that does not incorporate averaging, median calcs, or boxcar splicing(?) of signal. I included a png of the flowgraph so you can see exactly what my flowgraph did. Again, note that there are two peaks that are common to both scans (around 1420.5 and 1420.6 MHz) However, the simpler flowgraph also shows alias peaks (I think) which change frequency if I change the center frequency of the scan. I guess that the comparison confirms the "real" peaks and shows the inadequacy of not boxcar splicing?

Dave

On Tue, Jul 7, 2020 at 1:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Very glad to hear you’ve made such good progress. Congratulations!

I’ve answered your questions below.

On Jul 6, 2020, at 2:19 PM, dave290 notifications@github.com wrote:

Greetings Glen,

I hope you had a nice holiday weekend.

Good news! I have been able to collect hydrogen line data with gr-radio-astro on my raspberry pi. I'll share the details below. Data was collected with the June 22 version of the software (I recently updated to the June 28 version.)

Great. The Event Capture part is working much better in the June 28 version. The spectrometer code did not change much, so for your tests there is really no difference. The newer interface is a little clearer (I hope).

I initially collected data with the file "spectrometer_w_cal.grc" I was able to open this in Companion and run it without problems (the h5py error message no longer appears.) I followed the instructions posted on GitHub, and collected data while looking into Perseus (target=Mirfak, 5 second collection time.) The data is shown in the attached files, Mirfak1-grastro.jpg and Mirfak2-grastro.jpg I also included files to show the hot and cold spectra I obtained, using the rtl-sdr at 2.4 MHz The first file is funky looking, since there is a negative dip in front of the two real peaks; however, I also had very bumpy hot and cold spectra. The second Mirfak scan looks better, since I found better locations for my hot and cold scans. I live in an urban neighborhood, with lots of power lines and a very narrow window of sky overhead. (I'm planning to do some night-time observations and am going to try to get access to my school's athletic field, which offers a much less obstructed view of the sky!)

The spectrometer_w_cal program works very well, I understand. Glad you had good experience with it.

The main advantage of NsfIntegrate is in the processing after the observations. These programs are all obtained via

git clone http://www.github.com/glangsto/analyze

There you can average, Fix, plot raw spectra, plot calibrated spectra and also make maps of the whole sky. My mode of operating is to build weather proof telescopes and leave them outside for years at a time.

Making 1 hour averages of the spectra in a 24 hour period shows (I think) very interesting changes in the sky and the arms of the Milky Way rotate in and out of the telescope beam.

For comparison, I also collected data using my own flowgraph program, which is much less sophisticated (it does not average, nor filter, nor do the boxcar/sinc function operation.) However, it does subtract a "cold" background. The result is shown in the file "Mirfak-Myprogram.jpg" You will see the same two features. Also notice the two features at lower frequencies, which appear to be some sort of aliasing effect (e.g. when I change the center frequency of my observation, these features "walk" around.) Anyway, I'm not worried, because I'm not planning to use this, but just wanted to make a comparison. I attached a png of my flowgraph, also.

I did not get the image. Can you send it again?

I have not yet tried the NsfIntegrate24 to collect data, but I did notice that it can be run directly from a terminal, without a problem. (If I try to run this from Companion, I still get the error message that NsfIntegrate.not cannot be found.)

I have not been able to figure out why the companion is “not" finding the .not file. Yes please consider the work around of building new versions in companion, then after creatinging them, exit companion and try

python “NewDesignName.py”

This should work, yet allow you to integrate.

Do you recommend using NsfIntegrate instead of spectrometer_w_cal? Is there some advantage to one over the other? I noticed that the former program involves splitting the signal into four pieces and then recombining. The latter uses vector median blocks, is the logic different here?

The Integrate programs try to suppress short term interference by “median filtering” the data”

Quick mathematics note: consider that average of 4 values:

3. 2. 32. 3.

If the “32” is considered short term interference (which happens in radio astronomy) the averages of these 4 values is still 40/4 = 10

The median of 4 values is the average middle two of the 4. The median is 3+3/2 = 3. If the 32 was actually due to interference, then median is a more reasonable value of the true signal from the galaxy.

To go on and on; the “truth” is unknown in science, but the “average” is the most efficient estimate of the “truth" for measurements with gaussian distributed noise.

However the median of a small number of values is also an efficient estimate of the “truth”, but is much more resistant to “outliers”. (There are mathematical papers on this).

Glen, thanks so much for your help getting this set up. I hope my questions were useful to you in some way. I plan to reach out to Prof. Bandura this week to join the radio-astro teacher group. I'd also like to stay in touch, as I would like to get my students involved (pandemic-allowing) with a project. Along those lines, I will use your non-git hub email address.

I’m very glad you’ve got the strength to get this far in radio astronomy. I’m declaring you a “Science Aficionado”!

Best regards,

Glen

Best, David

On Mon, Jun 29, 2020 at 8:42 PM Glen Langston notifications@github.com wrote:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655055422, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ7ALUBCVZBEXS3KXGTR2NVEBANCNFSM4NS6UUEQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655095600", "url": "https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655095600", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[dave290]

Okay, just sent.

On Tue, Jul 7, 2020 at 3:04 PM Glen Langston notifications@github.com wrote:

Hi Dave,

I still do not see the figures.

Maybe send them directly to me: glen.i.langston@gmail.com

Thanks

Glen

On Jul 7, 2020, at 4:00 PM, dave290 notifications@github.com wrote:

Hi Glen,

Thanks for your detailed feedback (and encouragement!) I've attached 2 jpg files below, one showing Mirfak scan taken with spectometer_w_cal.grc and the other taken with a simpler flowgraph that does not incorporate averaging, median calcs, or boxcar splicing(?) of signal. I included a png of the flowgraph so you can see exactly what my flowgraph did. Again, note that there are two peaks that are common to both scans (around 1420.5 and 1420.6 MHz) However, the simpler flowgraph also shows alias peaks (I think) which change frequency if I change the center frequency of the scan. I guess that the comparison confirms the "real" peaks and shows the inadequacy of not boxcar splicing?

Dave

On Tue, Jul 7, 2020 at 1:51 PM Glen Langston notifications@github.com wrote:

Hi Dave,

Very glad to hear you’ve made such good progress. Congratulations!

I’ve answered your questions below.

On Jul 6, 2020, at 2:19 PM, dave290 notifications@github.com wrote:

Greetings Glen,

I hope you had a nice holiday weekend.

Good news! I have been able to collect hydrogen line data with gr-radio-astro on my raspberry pi. I'll share the details below. Data was collected with the June 22 version of the software (I recently updated to the June 28 version.)

Great. The Event Capture part is working much better in the June 28 version. The spectrometer code did not change much, so for your tests there is really no difference. The newer interface is a little clearer (I hope).

I initially collected data with the file "spectrometer_w_cal.grc" I was able to open this in Companion and run it without problems (the h5py error message no longer appears.) I followed the instructions posted on GitHub, and collected data while looking into Perseus (target=Mirfak, 5 second collection time.) The data is shown in the attached files, Mirfak1-grastro.jpg and Mirfak2-grastro.jpg I also included files to show the hot and cold spectra I obtained, using the rtl-sdr at 2.4 MHz The first file is funky looking, since there is a negative dip in front of the two real peaks; however, I also had very bumpy hot and cold spectra. The second Mirfak scan looks better, since I found better locations for my hot and cold scans. I live in an urban neighborhood, with lots of power lines and a very narrow window of sky overhead. (I'm planning to do some night-time observations and am going to try to get access to my school's athletic field, which offers a much less obstructed view of the sky!)

The spectrometer_w_cal program works very well, I understand. Glad you had good experience with it.

The main advantage of NsfIntegrate is in the processing after the observations. These programs are all obtained via

git clone http://www.github.com/glangsto/analyze

There you can average, Fix, plot raw spectra, plot calibrated spectra and also make maps of the whole sky. My mode of operating is to build weather proof telescopes and leave them outside for years at a time.

Making 1 hour averages of the spectra in a 24 hour period shows (I think) very interesting changes in the sky and the arms of the Milky Way rotate in and out of the telescope beam.

For comparison, I also collected data using my own flowgraph program, which is much less sophisticated (it does not average, nor filter, nor do the boxcar/sinc function operation.) However, it does subtract a "cold" background. The result is shown in the file "Mirfak-Myprogram.jpg" You will see the same two features. Also notice the two features at lower frequencies, which appear to be some sort of aliasing effect (e.g. when I change the center frequency of my observation, these features "walk" around.) Anyway, I'm not worried, because I'm not planning to use this, but just wanted to make a comparison. I attached a png of my flowgraph, also.

I did not get the image. Can you send it again?

I have not yet tried the NsfIntegrate24 to collect data, but I did notice that it can be run directly from a terminal, without a problem. (If I try to run this from Companion, I still get the error message that NsfIntegrate.not cannot be found.)

I have not been able to figure out why the companion is “not" finding the .not file. Yes please consider the work around of building new versions in companion, then after creatinging them, exit companion and try

python “NewDesignName.py”

This should work, yet allow you to integrate.

Do you recommend using NsfIntegrate instead of spectrometer_w_cal? Is there some advantage to one over the other? I noticed that the former program involves splitting the signal into four pieces and then recombining. The latter uses vector median blocks, is the logic different here?

The Integrate programs try to suppress short term interference by “median filtering” the data”

Quick mathematics note: consider that average of 4 values:

3. 2. 32. 3.

If the “32” is considered short term interference (which happens in radio astronomy) the averages of these 4 values is still 40/4 = 10

The median of 4 values is the average middle two of the 4. The median is 3+3/2 = 3. If the 32 was actually due to interference, then median is a more reasonable value of the true signal from the galaxy.

To go on and on; the “truth” is unknown in science, but the “average” is the most efficient estimate of the “truth" for measurements with gaussian distributed noise.

However the median of a small number of values is also an efficient estimate of the “truth”, but is much more resistant to “outliers”. (There are mathematical papers on this).

Glen, thanks so much for your help getting this set up. I hope my questions were useful to you in some way. I plan to reach out to Prof. Bandura this week to join the radio-astro teacher group. I'd also like to stay in touch, as I would like to get my students involved (pandemic-allowing) with a project. Along those lines, I will use your non-git hub email address.

I’m very glad you’ve got the strength to get this far in radio astronomy. I’m declaring you a “Science Aficionado”!

Best regards,

Glen

Best, David

On Mon, Jun 29, 2020 at 8:42 PM Glen Langston < notifications@github.com> wrote:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655055422 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AP25FZ7ALUBCVZBEXS3KXGTR2NVEBANCNFSM4NS6UUEQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655095600", "url": " https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655095600", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": " https://github.com" } } ]

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WVURAIL/gr-radio_astro/issues/20#issuecomment-655097789, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP25FZ47CTJ7XPRMMPCRF5DR2N5UFANCNFSM4NS6UUEQ .