GR_Swig_make unknown command about gr-radio_astro

[glangsto]

Hi I recently had this issue too. The “main” branch of gr-radio_radio_astro needs gnuradio 3.9 The most recent Ubuntu now has gnuradio 3.10, so you need to Git pull gr-radio_astro Cd gr-radio_astro Then Git branch gr310 Then the build instructions will work. We need to update the main branch to be compatible with gr310 now. (I think) Good luck Glen PS the commands above are from memory, please check the documentation…. From: anthony.fuller ***@***.***> Sent: Sunday, September 25, 2022 7:52 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Subscribed ***@***.***> Subject: [EXTERNAL] - [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. I guess gr-radio_astro isn't make for Ubuntu 22.04? Is there a work around to the gr_swig_make unknown command? CMake Error at swig/CMakeLists.txt:37 (include): include could not find requested file: GrSwig CMake Error at swig/CMakeLists.txt:51 (GR_SWIG_MAKE): Unknown CMake command "GR_SWIG_MAKE". — Reply to this email directly, view it on GitHub<#44>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGF6DZ5MSMMEDG7WKBDWADQRXANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[fventuri]

@glangsto - I agree with you that the default branch should be compatible with gr310, since now Ubuntu LTS comes with GNU Radio 3.10.
Perhaps we could rename the current main branch to say gr37 (or something like that), and gr310 branch tom main (and make that one the default branch in GitHub).

I can definitely help with that.

Franco

[fventuri]

@anthfuller - that error is probably because the default branch of gr-radio_astro (main) is still based on GNU Radio 3.7 (or 3.8) that used SWIG for the Python bindings.
Newer versions of GNU Radio (3.9 and 3.10) use pybind11.

You can build the gr-radio_astro OOT module for one of these recent versions of GNU Radio by just switching to the gr310 branch after cloning this repository, i.e.:

git clone https://github.com/WVURAIL/gr-radio_astro.git
cd gr-radio_astro
git checkout gr310
mkdir build
cd build
cmake ..
make
sudo make install
sudo ldconfig

Hope this helps,
Franco

[anthfuller]

Hi Franco!
I'll give it a try tomorrow and let you know.
Thank you!

[anthfuller]

Gentlemen I am up and running, thank you so much!! I'm modifying the Spectrometer_w_cal to use the KrakenSDR five channel RTL-SDR receiver. I'm only testing with two channels and an internal noise source for the moment.

[anthfuller]

I'm also currently working on a radio astronomy interferometer using two, 3-meter dishes. Hopefully I can obtain one or two more 3-meter satellite dishes, which aren't easy to come by now. Either you're ordering over seas with astronomical shipping cost or you're building your own. :-D

[fventuri]

.@anthfuller - I am glad you got it to work.
Let us know how it goes with the interferometer; are you going to write/publish your experiments and results somewhere?

Franco

[anthfuller]

Hi Franco!

I'm hoping to get the system up and running within 30 days! The project has been long overdue. If all goes well, I'll publish all results at the Society of Amateur Radio Astronomers (SARA).

[anthfuller]

There are several issues to work out. One, I'm using a linear power source for the H1 receivers due to the equipment shed being to close to the satellite dishes. I'll also most likely line the inside of the equipment shed with Titan RF to create a faraday cage. I'm looking to motorize both dishes, but most EL/AZ rotors won't fit my pole mounts without some type of modifications (welding). So, I may have to work with actuators, one horizontal, the other altered for vertical. Not the best, but for now, until I can figure that part out or use maybe a slew drive, don't know.

[anthfuller]

[fventuri]

@anthfuller - Thanks for the nice pictures Anthony! You have a very impressive setup there!
I am looking forward to read your results on SARA, and let me know if you need any help with the Python code.

Franco

[glangsto]

Hi I also agree with you. The WVU group has been updating the branch status. Glen From: Franco Venturi ***@***.***> Sent: Monday, September 26, 2022 7:52 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. @glangsto<https://github.com/glangsto> - I agree with you that the default branch should be compatible with gr310, since now Ubuntu LTS comes with GNU Radio 3.10. Perhaps we could rename the current main branch to say gr37 (or something like that), and gr310 branch tom main (and make that one the default branch in GitHub). I can definitely help with that. Franco — Reply to this email directly, view it on GitHub<#44 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGHA2P3KM3GMTLCQTLDWAIZITANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[anthfuller]

@anthfuller - Thanks for the nice pictures Anthony! You have a very impressive setup there! I am looking forward to read your results on SARA, and let me know if you need any help with the Python code.

Franco

Thank you, Franco! I definitely may require help. At the moment, I'm working on getting the Nsf-gr-radio_astro example interfaces setup, for after the data has been pulled. Particularly temperature in Kelvin and the velocity (km/sec).
https://github.com/WVURAIL/gr-radio_astro/wiki/Nsf-gr-radio_astro

[glangsto]

HI Your system temperature measurements show your amplifier and horn have very good performance. Anything below 100K is excellent. Best regards Glen Maybe more fully describe your amplifier, horn, feed probe in a “LightWork Memo”! From: anthony.fuller ***@***.***> Sent: Tuesday, September 27, 2022 1:23 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. @anthfuller<https://github.com/anthfuller> - Thanks for the nice pictures Anthony! You have a very impressive setup there! I am looking forward to read your results on SARA, and let me know if you need any help with the Python code. Franco Thank you, Franco! I definitely may require help. At the moment, I'm working on getting the Nsf-gr-radio_astro example interfaces setup, for after the data has been pulled. Particularly temperature in Kelvin and the velocity (km/sec). https://github.com/WVURAIL/gr-radio_astro/wiki/Nsf-gr-radio_astro [gr-astro_radio]<https://user-images.githubusercontent.com/38588965/192594189-af971358-2553-43e9-942a-5ea8af0083f2.png> — Reply to this email directly, view it on GitHub<#44 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGBDQ2QIQQHPCXTARHLWAMUPXANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[anthfuller]

Hi Glen, Question on the Nsfintegrate60.grc, is the K-FIT designating Kelvin in a FIT file?

…

On Mon, Oct 3, 2022 at 10:43 AM Glen Langston ***@***.***> wrote: HI Your system temperature measurements show your amplifier and horn have very good performance. Anything below 100K is excellent. Best regards Glen Maybe more fully describe your amplifier, horn, feed probe in a “LightWork Memo”! From: anthony.fuller ***@***.***> Sent: Tuesday, September 27, 2022 1:23 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. @anthfuller<https://github.com/anthfuller> - Thanks for the nice pictures Anthony! You have a very impressive setup there! I am looking forward to read your results on SARA, and let me know if you need any help with the Python code. Franco Thank you, Franco! I definitely may require help. At the moment, I'm working on getting the Nsf-gr-radio_astro example interfaces setup, for after the data has been pulled. Particularly temperature in Kelvin and the velocity (km/sec). https://github.com/WVURAIL/gr-radio_astro/wiki/Nsf-gr-radio_astro [gr-astro_radio]< https://user-images.githubusercontent.com/38588965/192594189-af971358-2553-43e9-942a-5ea8af0083f2.png> — Reply to this email directly, view it on GitHub< #44 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AADRXGBDQ2QIQQHPCXTARHLWAMUPXANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJGNEJN52J5FXY536HL34RDWBLWITANCNFSM6AAAAAAQVJTCZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[glangsto]

Hi Anthony, Good question, concerning the units written by the Integrate programs. No, the units of all the files are always “Counts”. The “offline” program “T” can create files with units of “Kelvins”. Also I’ve started some Jupyter notebooks that show the calibration process step by step. These really need more documentation, even though Jupyter notebooks are supposed to be self-documenting. These are available via git clone https://www.github.com/glangsto/jupyter I’ve run these using the Google “collaboratory” environment, on the raspberry pi, after installing “jupyter-lab” and using the NOIRLab’s datalab environment. One very nice thing about getting a NOIRLab account is that let you have a Terabyte of storage. The also have most of the astronomy python code already installed. Glen From: anthony.fuller ***@***.***> Sent: Monday, October 3, 2022 11:12 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) Hi Glen, Question on the Nsfintegrate60.grc, is the K-FIT designating Kelvin in a FIT file?

On Mon, Oct 3, 2022 at 10:43 AM Glen Langston ***@***.***<mailto:***@***.***>> wrote: HI Your system temperature measurements show your amplifier and horn have very good performance. Anything below 100K is excellent. Best regards Glen Maybe more fully describe your amplifier, horn, feed probe in a “LightWork Memo”! From: anthony.fuller ***@***.***<mailto:***@***.***>> Sent: Tuesday, September 27, 2022 1:23 PM To: WVURAIL/gr-radio_astro ***@***.***<mailto:***@***.***>> Cc: Langston, Glen ***@***.***<mailto:***@***.***>>; Mention ***@***.***<mailto:***@***.***>> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. @anthfuller<https://github.com/anthfuller> - Thanks for the nice pictures Anthony! You have a very impressive setup there! I am looking forward to read your results on SARA, and let me know if you need any help with the Python code. Franco Thank you, Franco! I definitely may require help. At the moment, I'm working on getting the Nsf-gr-radio_astro example interfaces setup, for after the data has been pulled. Particularly temperature in Kelvin and the velocity (km/sec). https://github.com/WVURAIL/gr-radio_astro/wiki/Nsf-gr-radio_astro [gr-astro_radio]< https://user-images.githubusercontent.com/38588965/192594189-af971358-2553-43e9-942a-5ea8af0083f2.png> — Reply to this email directly, view it on GitHub< #44 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AADRXGBDQ2QIQQHPCXTARHLWAMUPXANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***<mailto:***@***.******@***.***>>> — Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJGNEJN52J5FXY536HL34RDWBLWITANCNFSM6AAAAAAQVJTCZM> . You are receiving this because you were mentioned.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub<#44 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGEHYEDLQE36KCV7WFLWBON65ANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[glangsto]

Hi Anthony, You’ve built a fantastic observatory! Impressive! I’m looking forward to seeing your interferometer results. Glen FYI I’ve been working to design the “simplest” observatory. No moving parts, except when the students move the telescope from one elevation to another. From: anthony.fuller ***@***.***> Sent: Monday, September 26, 2022 9:58 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. There are a several issues to work out. One, I'm using a linear power source for the H1 receivers due to the equipment shed being to close to the satellite dishes. I'll also most likely line the inside of the equipment shed with Titan RF to create a faraday cage. I'm looking to motorize both dishes, but most EL/AZ rotors won't fit my pole mounts without some type of modifications (welding). So, I may have to work with actuators, one horizontal, the other altered for vertical. Not the best, but for now, until I can figure that part out or user maybe a slew drive, don't know. [RAS_Observatory]<https://user-images.githubusercontent.com/38588965/192413380-4668bfd4-88f6-4b8a-902f-b7f45524201b.jpg> — Reply to this email directly, view it on GitHub<#44 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGGALA3YTCPCFQH4QQDWAJID3ANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[anthfuller]

Hi Glen! Thank you so much! But I'm still learning a lot. The Nsfintergrate 60, I've tweaked for 2.4 MZh in order to work with the KrakenSDR five channel RTL-SDR receiver. I'm studying what a lot of the examples do and going through the old & new WVurail documentation. Some ofits clear, some I'm trying to obtain and understanding of it to some of the demos and observations in the Examples directory. I'll send my GRC file for review if you or anyone wishes to review? I welcome all the help I can get. 😄

…

On Tue, Oct 4, 2022, 7:51 AM Glen Langston ***@***.***> wrote: Hi Anthony, You’ve built a fantastic observatory! Impressive! I’m looking forward to seeing your interferometer results. Glen FYI I’ve been working to design the “simplest” observatory. No moving parts, except when the students move the telescope from one elevation to another. From: anthony.fuller ***@***.***> Sent: Monday, September 26, 2022 9:58 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe. There are a several issues to work out. One, I'm using a linear power source for the H1 receivers due to the equipment shed being to close to the satellite dishes. I'll also most likely line the inside of the equipment shed with Titan RF to create a faraday cage. I'm looking to motorize both dishes, but most EL/AZ rotors won't fit my pole mounts without some type of modifications (welding). So, I may have to work with actuators, one horizontal, the other altered for vertical. Not the best, but for now, until I can figure that part out or user maybe a slew drive, don't know. [RAS_Observatory]< https://user-images.githubusercontent.com/38588965/192413380-4668bfd4-88f6-4b8a-902f-b7f45524201b.jpg> — Reply to this email directly, view it on GitHub< #44 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AADRXGGALA3YTCPCFQH4QQDWAJID3ANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJGNEJIZE7HH5R5YY2VTNLDWBQK2HANCNFSM6AAAAAAQVJTCZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[anthfuller]

I will look into the offline program and Jupyter note books, Glen. Thank you!

…

On Tue, Oct 4, 2022, 6:43 AM Glen Langston ***@***.***> wrote: Hi Anthony, Good question, concerning the units written by the Integrate programs. No, the units of all the files are always “Counts”. The “offline” program “T” can create files with units of “Kelvins”. Also I’ve started some Jupyter notebooks that show the calibration process step by step. These really need more documentation, even though Jupyter notebooks are supposed to be self-documenting. These are available via git clone https://www.github.com/glangsto/jupyter I’ve run these using the Google “collaboratory” environment, on the raspberry pi, after installing “jupyter-lab” and using the NOIRLab’s datalab environment. One very nice thing about getting a NOIRLab account is that let you have a Terabyte of storage. The also have most of the astronomy python code already installed. Glen From: anthony.fuller ***@***.***> Sent: Monday, October 3, 2022 11:12 PM To: WVURAIL/gr-radio_astro ***@***.***> Cc: Langston, Glen ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown command (Issue #44) Hi Glen, Question on the Nsfintegrate60.grc, is the K-FIT designating Kelvin in a FIT file? On Mon, Oct 3, 2022 at 10:43 AM Glen Langston ***@***.***<mailto:***@***.***>> wrote: > HI > Your system temperature measurements show your amplifier and horn have > very good performance. Anything below 100K is excellent. > > Best regards > > Glen > > Maybe more fully describe your amplifier, horn, feed probe in a “LightWork > Memo”! > > > From: anthony.fuller ***@***.***<mailto:***@***.***>> > Sent: Tuesday, September 27, 2022 1:23 PM > To: WVURAIL/gr-radio_astro ***@***.***<mailto:***@***.***>> > Cc: Langston, Glen ***@***.***<mailto:***@***.***>>; Mention ***@***.***<mailto:***@***.***>> > Subject: [EXTERNAL] - Re: [WVURAIL/gr-radio_astro] GR_Swig_make unknown > command (Issue #44) > > This email originated from outside of the National Science Foundation. Do > not click links or open attachments unless you recognize the sender and > know the content is safe. > > > @anthfuller<https://github.com/anthfuller> - Thanks for the nice pictures > Anthony! You have a very impressive setup there! I am looking forward to > read your results on SARA, and let me know if you need any help with the > Python code. > > Franco > > Thank you, Franco! I definitely may require help. At the moment, I'm > working on getting the Nsf-gr-radio_astro example interfaces setup, for > after the data has been pulled. Particularly temperature in Kelvin and the > velocity (km/sec). > https://github.com/WVURAIL/gr-radio_astro/wiki/Nsf-gr-radio_astro > > [gr-astro_radio]< > https://user-images.githubusercontent.com/38588965/192594189-af971358-2553-43e9-942a-5ea8af0083f2.png> > > > — > Reply to this email directly, view it on GitHub< > #44 (comment)>, > or unsubscribe< > https://github.com/notifications/unsubscribe-auth/AADRXGBDQ2QIQQHPCXTARHLWAMUPXANCNFSM6AAAAAAQVJTCZM>. > > You are receiving this because you were mentioned.Message ID: > ***@***.******@***.***<mailto:***@***.******@***.***>>> > > — > Reply to this email directly, view it on GitHub > < #44 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AJGNEJN52J5FXY536HL34RDWBLWITANCNFSM6AAAAAAQVJTCZM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***<mailto:***@***.***>> > — Reply to this email directly, view it on GitHub< #44 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AADRXGEHYEDLQE36KCV7WFLWBON65ANCNFSM6AAAAAAQVJTCZM>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJGNEJL2TCG6CRJ6ONBYOJTWBQC3RANCNFSM6AAAAAAQVJTCZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>