Repository navigation
General Forum #7
Replies: 0 comments 90 replies
|
Welcome everyone to DSPIRA! Feel free to ask questions here! |
|
The web page for Electronics Forum is broken. |
|
|
So, we're trying to cut this square can with the recommended canopener. How in the world did you do this with this can opener?!?!?!?!?! |
|
Did you watch the video?
Best,
Robert Baker
…On Thu, Jul 22, 2021 at 8:46 PM natewvgsi ***@***.***> wrote:
So, we're trying to cut this square can with the recommended canopener.
How in the world did you do this with this can opener?!?!?!?!?!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-885329384>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZERAIUHPJFZ4JAYTT7Z6LTZC3WTANCNFSM4TT25DVQ>
.
|
|
We did, finally figuring out we purchased the wrong Oxo can opener! We
finally did beat the can into submission and are moving on today. Thanks!!
…On Fri, Jul 23, 2021 at 9:04 AM rbaker314 ***@***.***> wrote:
Did you watch the video?
Best,
Robert Baker
On Thu, Jul 22, 2021 at 8:46 PM natewvgsi ***@***.***> wrote:
> So, we're trying to cut this square can with the recommended canopener.
> How in the world did you do this with this can opener?!?!?!?!?!
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-885329384
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ABZERAIUHPJFZ4JAYTT7Z6LTZC3WTANCNFSM4TT25DVQ
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-885623292>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU6E3ZQWA5TCOXLYWA4FKITTZFSFJANCNFSM4TT25DVQ>
.
--
Nate
|
|
Hello all - we were inspired by the work here to build a telescope for our own RET program in Hawaii. I then refined the design a bit through a graduate seminar and have added more documentation and software on the later stages to go from raw data to a rotation curve. Hopefully this is helpful to others on the forum https://github.com/interstellarmedium/HI_telescope |
|
Hi
You have made great progress!
Congratulations!
Cheers
Glen
… On Jan 25, 2022, at 3:29 PM, Jonathan Williams ***@***.***> wrote:
Hello all - we were inspired by the work here to build a telescope for our own RET program in Hawaii. I then refined the design a bit through a graduate seminar and have added more documentation and software on the later stages to go from raw data to a rotation curve. Hopefully this is helpful to others on the forum https://github.com/interstellarmedium/HI_telescope
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
|
|
Hi Jonathan,
Glad to see you’ve found the HI4PI survey.
We’ve been working with Benjamin Winkel, at Max Planck,
who provided a lower resolution, all sky image of hydrogen.
You might enjoy looking at the sky, using the jupyter notebook
at this site:
https://github.com/glangsto/hi4pi
The HI4PI images are beautiful.
Best regards
Glen
Glen I Langston, Ph. D.
Galactic Astronomy Program Director
National Science Foundation
304-456-3032
… On Jan 25, 2022, at 3:34 PM, Glen Langston ***@***.***> wrote:
This email originated from outside of the National Science Foundation. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi
You have made great progress!
Congratulations!
Cheers
Glen
> On Jan 25, 2022, at 3:29 PM, Jonathan Williams ***@***.***> wrote:
>
>
> Hello all - we were inspired by the work here to build a telescope for our own RET program in Hawaii. I then refined the design a bit through a graduate seminar and have added more documentation and software on the later stages to go from raw data to a rotation curve. Hopefully this is helpful to others on the forum https://github.com/interstellarmedium/HI_telescope
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> Triage notifications on the go with GitHub Mobile for iOS or Android.
> You are receiving this because you are subscribed to this thread.
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
|
|
Hi Glen, Thanks for pointing this out - very useful indeed! Jonathan |
|
Hi
I’ve been working to get all our horn observations accessible via
the very fun/remarkable jupyter notebooks.
John Makous pointed out how easy it is to use the Google Colaboratory site.
If you download the attached jupyter notebook and then upload it to the google
web site
collab.research.google.com
Then you can calibrate and view the saved observations and all the other
notebooks.
You can also upload your observations and plot them with these tools too.
Good luck!
Glen
… On Jan 25, 2022, at 3:34 PM, Glen Langston ***@***.***> wrote:
Hi
You have made great progress!
Congratulations!
Cheers
Glen
> On Jan 25, 2022, at 3:29 PM, Jonathan Williams ***@***.***> wrote:
>
>
> Hello all - we were inspired by the work here to build a telescope for our own RET program in Hawaii. I then refined the design a bit through a graduate seminar and have added more documentation and software on the later stages to go from raw data to a rotation curve. Hopefully this is helpful to others on the forum https://github.com/interstellarmedium/HI_telescope
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> Triage notifications on the go with GitHub Mobile for iOS or Android.
> You are receiving this because you are subscribed to this thread.
>
|
|
Arg…
The GitHub site that manages these emails removes attachments.
But the attachment is available as a link also:
https://github.com/glangsto/jupyter/blob/master/MilkyWayPlottingColab.ipynb
This whole script runs in less than a minute.
For those of you not familiar with notebooks,
Click in the first box.
Then simultaneously type “Shift and Return” keys to step through the commands.
Its fun…
Cheers
Glen
… On Feb 8, 2022, at 10:46 AM, Glen Langston ***@***.***> wrote:
Hi
I’ve been working to get all our horn observations accessible via
the very fun/remarkable jupyter notebooks.
John Makous pointed out how easy it is to use the Google Colaboratory site.
If you download the attached jupyter notebook and then upload it to the google
web site
collab.research.google.com
Then you can calibrate and view the saved observations and all the other
notebooks.
You can also upload your observations and plot them with these tools too.
Good luck!
Glen
<MilkyWayPlottingColab.ipynb>
> On Jan 25, 2022, at 3:34 PM, Glen Langston ***@***.***> wrote:
>
> Hi
> You have made great progress!
>
> Congratulations!
>
> Cheers
>
> Glen
>
>
>> On Jan 25, 2022, at 3:29 PM, Jonathan Williams ***@***.***> wrote:
>>
>>
>> Hello all - we were inspired by the work here to build a telescope for our own RET program in Hawaii. I then refined the design a bit through a graduate seminar and have added more documentation and software on the later stages to go from raw data to a rotation curve. Hopefully this is helpful to others on the forum https://github.com/interstellarmedium/HI_telescope
>>
>> —
>> Reply to this email directly, view it on GitHub, or unsubscribe.
>> Triage notifications on the go with GitHub Mobile for iOS or Android.
>> You are receiving this because you are subscribed to this thread.
>>
>
|
|
A lot of my students have Macs, so I have been thinking about trying to set the software up on Raspberry Pi instead, but I have some logistical questions for anyone who has used the Pi. What are you using for a display? Do you have dedicated monitors, or are you remotely connecting from a laptop? And if the telescope is outside, how are you powering the Pi? Is battery life an issue? Thanks, |
|
Hi Evan, We have used raspberry Pis extensively. Typical we login remotely using ssh into the pi or use a vncviewer. Sometimes we attach to a monitor if available or if the initial network setup went awry. One can power the raspberry pi using power over ethernet but that may or may not require a separate hardware. @GlenLangston @glangsto has more experience with having telescopes with raspberry pi's out in the field. -P |
|
Hi Evan,
Hope your exploration of radio astronomy is going well.
As Pranav said, we frequently use Raspberry Pi’s for Radio Astronomy.
The code is all available as a single (large) download from:
https://drive.google.com/file/d/1tF6BaEj1Sabq6fJXeNpMsqcb8RStfqJs/view?usp=sharing
This code should be installed on a 16GB (or bigger) SD card using
balena-Etcher and then plugged into your Raspberry Pi 4B or 400.
You may need a monitor and keyboard for the initial setup, but
after that you can run using VNC, which allows you to use any laptop
to see what is going on.
The installation guide and examples are in a PDF at:
https://drive.google.com/file/d/1nvr6mUQsmsFC07G4KLD4oQAHfzUOfY-b/view?usp=sharing
Many people have successfully done this.
Good Luck!
Glen
Alternatively you can read the excellent step-by-step instructions for building
a radio telescope and install the code by downloading the packages from GitHub.
This has been extensively tested too.
See: https://wvurail.org/dspira-lessons/forum/
… On Oct 17, 2022, at 11:49 AM, Pranav Sanghavi ***@***.***> wrote:
Hi Evan,
We have used raspberry Pis extensively. Typical we login remotely using ssh into the pi or use a vncviewer. Sometimes we attach to a monitor if available or if the initial network setup went awry.
One can power the raspberry pi using power over ethernet but that may or may not require a separate hardware. @GlenLangston @glangsto has more experience with having telescopes with raspberry pi's out in the field.
-P
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
Hi Glen However, the Notebook code exhibits the same general issues as I was seeing on the Raspberry Pi. It does, though, exhibit an additional problem not seen on the Raspberry Pi (at least not with the test data set). The main issue is they both seem to have issues computing baselines in the calibration process. The Raspberry Pi shows the following for the .hot files - The Notebook code shows the following similar error for the same files- I’m assuming its the same routine having the issue in both systems. In both cases the calibrated graphs never get presented relative to a baseline and take on a strong V shaped appearance (though do appear to illustrate what looks like a peak at about 1420.4MHz) Whether it’s a coding issue or something in my data files I’m uncertain but so far have failed to identify anything in the data. Looking at the Console output for the calibration step in the Notebook version its clear the code includes a number of data validation steps so its possible there is a data issue here; eg - I’ve also spotted a weird issue with processing of the of hot/cold files in the Notebook version of the Raw plotting but which isn’t manifested in the Raspberry Pi version. My test files consist of 4 .hot files and 10 .ast files. The Notebook Raw plot shows a legend in which the first 5 files have Az/El of 0.0 / -90.0 where the fifth file in fact contains Az/El values of 45.0 / 45.0. Its also the case that this Raw plot legend only shows 13 lines rather than the 14 I assume it should show??? These two observations make me think there may be a variable initialisation issue where the code moves from processing the .hot files to processing the .ast files. One final question - I notice the NsfIntegrate24.py code generates a Hot.hot file and a Cold.ast file. What is the purpose of these and are they required for any processing we are discussing? I'll take a further look at the analysis code on GitHub and see if I can spot any obvious issue but not being that familiar with the underling process logic it could be a long job. Does any of the code in your custom modules/classes rely on custom C/C++ code or can I safely assume that its all in the Python code (even if some of it is converted to Cython or whatever)? Regards |
|
Hello John and all,
I suggest we try to meet via Zoom and I share my screen to show you what I’d expect
the code to do, so far as analyzing the data.
I’m guessing that perhaps the spectral width calculation may have a bug.
I’m primarily using an Airspy Mini, that has 6 MHz bandwidth, so
there is plenty of hydrogen un-occuppied bandwidth for fitting a baseline.
I suggest we try to meet tomorrow, Tuesday, February 4th at 3:00 PM Eastern Time.
If this time does not work, please suggest another time/date.
All who are interested may join via this link:
Zoom Link: http://bit.ly/LibertyService
or
https://us02web.zoom.us/j/4527333215?pwd=ZzRLQ21qdDBxK04ybUpMQlRWY1V2dz09
Meeting ID: 452 733 3215
Passcode: spirit
Or call:
+13126266799,,4527333215# US (Chicago)
I will show one of my Pi’s in operation and some of the data we’ve captured.
Then perhaps you can show me the issues you’re seeing.
Best regards
Glen
… On Feb 1, 2025, at 8:01 PM, johncneal ***@***.***> wrote:
Hi Glen
I got your Jupyter notebook working in Google Colab - it let me pull it in using the url you provided. I saved it as a copy in my Colab space and I was also able to link Colab to my Google Drive. That way I was able to easily point the Notebook file paths at .ast and .hot files on my Google Drive.
However, the Notebook code exhibits the same general issues as I was seeing on the Raspberry Pi. It does, though, exhibit an additional problem not seen on the Raspberry Pi (at least not with the test data set).
The main issue is they both seem to have issues computing baselines in the calibration process. The Raspberry Pi shows the following for the .hot files -
Imax Error computing baseline: 1038
The Notebook code shows the following similar error for the same files-
Imax Error computing baseline: 1129
I’m assuming its the same routine having the issue in both systems. In both cases the calibrated graphs never get presented relative to a baseline and take on a strong V shaped appearance (though do appear to illustrate what looks like a peak at about 1420.4MHz)
Whether it’s a coding issue or something in my data files I’m uncertain but so far have failed to identify anything in the data. Looking at the Console output for the calibration step in the Notebook version its clear the code includes a number of data validation steps so its possible there is a data issue here; eg -
Found 4 Hot load observations
No high Galactic Latitude data
Min, Max El: 45.0, 45.0 deg; Min, Max Glat: 1.87, 2.70 deg
Found 10 Cold Sky Obs.; Min El = 45.0, Low Gal Lat: -2.3
Imax Error computing baseline: 1129
Median Receiver Temp: 305.43 +/- 11.98 (11.95 12.01) (K)
Ploting Intensity versus Velocity
Date: 2025-01-29
Imax Error computing baseline: 1129
Time AZ,EL (deg) Lon,Lat (deg) Max-(K)-Median X (km/s) Count
09:27:13 45.0, 45.0 113.7, -2.0 356.75 336.06 -163.183 509232
I’ve also spotted a weird issue with processing of the of hot/cold files in the Notebook version of the Raw plotting but which isn’t manifested in the Raspberry Pi version. My test files consist of 4 .hot files and 10 .ast files. The Notebook Raw plot shows a legend in which the first 5 files have Az/El of 0.0 / -90.0 where the fifth file in fact contains Az/El values of 45.0 / 45.0.
Its also the case that this Raw plot legend only shows 13 lines rather than the 14 I assume it should show???
These two observations make me think there may be a variable initialisation issue where the code moves from processing the .hot files to processing the .ast files.
One final question - I notice the NsfIntegrate24.py code generates a Hot.hot file and a Cold.ast file. What is the purpose of these and are they required for any processing we are discussing?
I'll take a further look at the analysis code on GitHub and see if I can spot any obvious issue but not being that familiar with the underling process logic it could be a long job. Does any of the code in your custom modules/classes rely on custom C/C++ code or can I safely assume that its all in the Python code (even if some of it is converted to Cython or whatever)?
Regards
John
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
Hi Glen |
|
Hello
I hope all are gathering marvelous observations of the Milky Way.
I’ve been trying to prepare software for an upgrade to the Raspberry Pi 5.
I’ve tested Operating System with the Pi 5 and it works for the AIRSPY mini,
SDRPlay RSP1A, and RTL SDR dongle
https://drive.google.com/file/d/14qf-V3fCHeP2BkOS8qnkJEQZzGFUJlho/view?usp=drive_link
This version also works with the Pi 4s. It is big, 2.7 Gbytes, and contains
all the observing and analysis code.
I’ve also tried to update the latest analysis code and improved the plots for
classroom demos (I think) with this version for the Pi 4.
This version has been tested with a few more devices.
https://drive.google.com/file/d/1LsCPTrOi41kCFKDCgTqdC4QWY8n7oYGA/view?usp=drive_link
This version is slightly bigger, at 2.9 Gbytes.
Good Luck,
Glen
… On Feb 3, 2025, at 4:13 PM, johncneal ***@***.***> wrote:
Hi Glen
Zoom session as proposed is good for me - it will be 8:00PM here in the UK.
I've identified a couple of other things which may or may not be relevant which I'll endeavour to document in preparation.
Regards
john
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
I'm having trouble with my headless display. It is set at 1920x1080. The splash page shows up perfectly, but NsfIntegrate100 only shows half of the intensity vs frequency graph display, the Median, hot, cold, reference bar obscures anything after the green line due to the airspy 100 |
|
I get a perfect screen match if the monitor is plugged into the HDMI on the pi. I don't when the monitor is detached. |
|
Hi Joe,
You can use
“sudo rasps-config” to change the “headless” display settings.
You have to reboot after your changes.
I had the same problem. I think you need to set the “headless” VNC display size to the max.
Good luck
Glen.
… On May 12, 2025, at 2:01 AM, JoeWise-LA ***@***.***> wrote:
JoeWise-LA
left a comment
(WVURAIL/dspira-lessons#2)
I'm having trouble with my headless display. It is set at 1920x1080. The splash page shows up perfectly, but NsfIntegrate100 only shows half of the intensity vs frequency graph display, the Median, hot, cold, reference bar obscures anything after the green line due to the airspy 100
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
I did that and had no success. I am going to attach a monitor, VNC in and then take the monitor off. I'm hoping that will work and I just can't shutdown or reboot without doing it again. I'll let you all know. |
|
HI Joe,
You’re up late (or very early). I just double checked and my pi is set to 1920x1080 VNC (headless) resolution, and it works fine with VNC.
I’m now guessing it is something about you laptop’s VNC settings, but I don’t know what.
Glen
From: JoeWise-LA ***@***.***>
Sent: Monday, May 12, 2025 2:02 AM
To: WVURAIL/dspira-lessons ***@***.***>
Cc: Langston, Glen ***@***.***>; Mention ***@***.***>
Subject: [EXTERNAL] - Re: [WVURAIL/dspira-lessons] dspira-lessons/forum/ (#2)
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.
[https://avatars.githubusercontent.com/u/121590581?s=20&v=4]JoeWise-LA left a comment (WVURAIL/dspira-lessons#2)<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2870945172>
I'm having trouble with my headless display. It is set at 1920x1080. The splash page shows up perfectly, but NsfIntegrate100 only shows half of the intensity vs frequency graph display, the Median, hot, cold, reference bar obscures anything after the green line due to the airspy 100
—
Reply to this email directly, view it on GitHub<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2870945172>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRXGC5HPNHYVUZTPH5UX326A2L7AVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZQHE2DKMJXGI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
My guess is that it is something with my settings. We've come to the same conclusion. Thanks for the validation. |
|
Hi Joe I can reassure though, that I have all the WVURAIL radioastro suite up and running on a Raspi 5 (even have it booting from and storing data on an NVMe SSD connected to the RasPi 5's new PCIe controller. Regards |
|
Thanks John, did you open GNU/GRC and there was a zoom in the software? I'm
taking a look right now.
Joe
…On Wed, May 14, 2025 at 10:38 AM johncneal ***@***.***> wrote:
*johncneal* left a comment (WVURAIL/dspira-lessons#2)
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215>
Hi Joe
Did you manage to sort this problem?
I seem to recall I had a puzzling issue running GNURadio companion on my
Raspberry Pi 5 when I first set it up. It seemed reluctant to show me the
whole of a form. It turned out to be some weird "zoom the view" type of
problem and once I'd zoomed out a bit in GRC the problem went away and I
haven't seen it since. I mention this because we obviously have GNU/GRC
running and some aspects of RaspiOS for the Raspberry Pi 5 such as the
graphical processing and desktop have seen dramatic engineering changes
under RaspiOS Bookworm compared to earlier versions. This may of course be
irrelevant if you are on a RasPi 4 :-)
I can reassure though, that I have all the WVURAIL radioastro suite up and
running on a Raspi 5 (even have it booting from and storing data on an NVMe
SSD connected to the RasPi 5's new PCIe controller.
Regards
john
—
Reply to this email directly, view it on GitHub
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A47VGNOFFBCRIYOKDKRSAJ326N5S5AVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBRGAZTGMRRGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hi Joe
I can’t be sure the problem you have is the same as the one I described but it was similar. When I opened the NsfIntegrate grc file in Gnuradio-companion it wouldn’t let me scroll to the bottom of the form. Adjusting the zoom level showed me the rest of the form. That said, VNC was showing me the full RasPi desktop at the time. It seemed worth mentioning though given the NsfIntegrate programs utilise GNU/GRC.
Subsequent to that I looked into VNC settings. Haven’t yet had time to play with them but I notice each computer you connect to can have settings on the Properties->Options tab for Picture quality and Scaling. The latter let you ‘scale’ and set aspect ratio in various ways. Mine are set to Picture quality = Automatic and Scaling = Automatic.
Hope that helps.
John
…Sent from my iPhone
On 15 May 2025, at 09:31, JoeWise-LA ***@***.***> wrote:
[https://avatars.githubusercontent.com/u/121590581?s=20&v=4]JoeWise-LA left a comment (WVURAIL/dspira-lessons#2)<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883013005>
Thanks John, did you open GNU/GRC and there was a zoom in the software? I'm <br> taking a look right now. <br> <br> Joe <br> <br> On Wed, May 14, 2025 at 10:38 AM johncneal ***@***.***> wrote: <br> <br> > *johncneal* left a comment (WVURAIL/dspira-lessons#2) <br> > <https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215> <br> > <br> > Hi Joe <br> > Did you manage to sort this problem? <br> > I seem to recall I had a puzzling issue running GNURadio companion on my <br> > Raspberry Pi 5 when I first set it up. It seemed reluctant to show me the <br> > whole of a form. It turned out to be some weird "zoom the view" type of <br> > problem and once I'd zoomed out a bit in GRC the problem went away and I <br> > haven't seen it since. I mention this because we obviously have GNU/GRC <br> > running and some aspects of RaspiOS for the Raspberry Pi 5 such as the <br> > graphical processing and desktop have seen dramatic engineering changes <br> > under RaspiOS Bookworm compared to earlier versions. This may of course be <br> > irrelevant if you are on a RasPi 4 :-) <br> > <br> > I can reassure though, that I have all the WVURAIL radioastro suite up and <br> > running on a Raspi 5 (even have it booting from and storing data on an NVMe <br> > SSD connected to the RasPi 5's new PCIe controller. <br> > <br> > Regards <br> > john <br> > <br> > — <br> > Reply to this email directly, view it on GitHub <br> > <https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215>, <br> > or unsubscribe <br> > <https://github.com/notifications/unsubscribe-auth/A47VGNOFFBCRIYOKDKRSAJ326N5S5AVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBRGAZTGMRRGU> <br> > . <br> > You are receiving this because you commented.Message ID: <br> > ***@***.***> <br> > <br>
—
Reply to this email directly, view it on GitHub<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883013005>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADNSWXLKKMCDVXIV3T52WCL26RGGNAVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBTGAYTGMBQGU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thanks John, I'll let you know.
A parting gift, I leave for home tomorrow.
…On Thu, May 15, 2025, 4:24 PM johncneal ***@***.***> wrote:
*johncneal* left a comment (WVURAIL/dspira-lessons#2)
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883324427>
Hi Joe <br> I can’t be sure the problem you have is the same as the one I
described but it was similar. When I opened the NsfIntegrate grc file in
Gnuradio-companion it wouldn’t let me scroll to the bottom of the form.
Adjusting the zoom level showed me the rest of the form. That said, VNC was
showing me the full RasPi desktop at the time. It seemed worth mentioning
though given the NsfIntegrate programs utilise GNU/GRC. <br> <br>
Subsequent to that I looked into VNC settings. Haven’t yet had time to play
with them but I notice each computer you connect to can have settings on
the Properties->Options tab for Picture quality and Scaling. The latter
let you ‘scale’ and set aspect ratio in various ways. Mine are set to
Picture quality = Automatic and Scaling = Automatic. <br> <br> Hope that
helps. <br> John <br> <br> Sent from my iPhone <br> <br> On 15 May 2025, at
09:31, JoeWise-LA ***@***.***> wrote: <br> <br> <br> [
https://avatars.githubusercontent.com/u/121590581?s=20&v=4]JoeWise-LA
left a comment (WVURAIL/dspira-lessons#2)<
https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883013005>
<br> Thanks John, did you open GNU/GRC and there was a zoom in the
software? I&#39;m <br> taking a look right now. <br>
<br> Joe <br> <br> On Wed, May 14, 2025 at 10:38 AM
johncneal ***@***.***&gt; wrote: <br> <br> &gt;
*johncneal* left a comment (WVURAIL/dspira-lessons#2) <br> &gt;
&lt;
https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215&gt;
<br> &gt; <br> &gt; Hi Joe <br> &gt; Did you
manage to sort this problem? <br> &gt; I seem to recall I had a
puzzling issue running GNURadio companion on my <br> &gt;
Raspberry Pi 5 when I first set it up. It seemed reluctant to show me the
<br> &gt; whole of a form. It turned out to be some weird
&quot;zoom the view&quot; type of <br> &gt; problem and
once I&#39;d zoomed out a bit in GRC the problem went away and I
<br> &gt; haven&#39;t seen it since. I mention this because
we obviously have GNU/GRC <br> &gt; running and some aspects of
RaspiOS for the Raspberry Pi 5 such as the <br> &gt; graphical
processing and desktop have seen dramatic engineering changes <br>
&gt; under RaspiOS Bookworm compared to earlier versions. This may of
course be <br> &gt; irrelevant if you are on a RasPi 4 :-)
<br> &gt; <br> &gt; I can reassure though, that I have
all the WVURAIL radioastro suite up and <br> &gt; running on a
Raspi 5 (even have it booting from and storing data on an NVMe <br>
&gt; SSD connected to the RasPi 5&#39;s new PCIe controller.
<br> &gt; <br> &gt; Regards <br> &gt; john
<br> &gt; <br> &gt; — <br> &gt; Reply to this
email directly, view it on GitHub <br> &gt; &lt;
https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2881033215&gt;,
<br> &gt; or unsubscribe <br> &gt; &lt;
https://github.com/notifications/unsubscribe-auth/A47VGNOFFBCRIYOKDKRSAJ326N5S5AVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBRGAZTGMRRGU&gt;
<br> &gt; . <br> &gt; You are receiving this because
you commented.Message ID: <br> &gt; ***@***.***&gt;
<br> &gt; <br> <br> <br> — <br> Reply to this email
directly, view it on GitHub<
https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883013005>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ADNSWXLKKMCDVXIV3T52WCL26RGGNAVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBTGAYTGMBQGU>.
<br> You are receiving this because you commented.Message ID:
***@***.***> <br>
—
Reply to this email directly, view it on GitHub
<https://github.com/WVURAIL/dspira-lessons/issues/2#issuecomment-2883324427>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A47VGNOAQVEJ3KVU446FECL26RTO3AVCNFSM6AAAAABLE6ICTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBTGMZDINBSG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Comparing my amateur data to professional data! Having got what look like promising results from my 1m grid antenna, I’ve been comparing them to the equivalent data pulled from the Leiden/Argentine/Bonn (LAB) survey database. BUT while the plots look good I’m finding weirdly mixed results in the comparisons with the LAB data. I could see a few potential explanations for this so set about trying to identify the cause. I have a number of drift scans for which I process the .ast data files from NsfIntegrate24.py using the t.py program from Glen’s Analyze suite. I use the -W parameter to write out the calibrated TSys (.kel) files containing the velocity/intensity data. I’ve written some additional Python code (outside the Analyze suite) in which I read in data from the .kel files and use the Galactic Lat/Long values to pull data for those same coordinates from the LAB database. I then plot velocity v Intensity (temperature) for both mine and the LAB data sets on the same axes. I wasn’t expecting them to match too well but was delighted to see that an initial subset of the plots matched surprisingly well. Encouraged, I ran this analysis for a drift scan several hours long. This showed that closeness of fit started out fairly poor with around 20km/s difference between mine and the LAB data. The two plots then get closer as the drift scan continued to the point where they matched closely only to then diverge again. My first thought was this might be a VLSR issue and sure enough, checking the LAB data confirmed their data was corrected for VLSR. So I did some research around the internet looking for algorithms/code to correct my data for VLSR. I found the Astropy documentation of this area somewhat unclear and confusing but found one solution which looked as though it generated suitable velocity correction values, though applying this failed to solve the problem. The correspondence between mine and the LAB data within any given scan continued to ‘come and go’ as the Galactic Long/Lat changes, despite these being among values fed into the correction function. So two questions for the community - Can anyone point me at an appropriate VLSR correction solution - the .kel data files in hand would appear to provide all the likely dependent values. Secondly - can anyone suggest any other possible factors in this problem which I might look into? I’d attach .png files of three plots which illustrate the above issues but I can't see a way to add them here ???. John |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
General discussion for the DSPIRA community.
All reactions