Thought I’d share the interesting multiPlots from the New England Grape group from yesterday, that show large Doppler shift and signal strength excursions, presumably during the G2 geomagnetic storm of 8-7 and 8-8. The 4 plots are in pretty good agreement.
The ”green bands” around 1400-1600 are of the type we’ve seen when the Fldigi Frequency window is accidentally incremented when a user is trying to set Op Mode to NULL, which is right above the frequency window. It can also happen when the Pi is powered down, then back up and the Bodnar freq is not yet locked or system time is not sync’ed to NTP before Fldigi starts recording. The WWVfilechk2.py program is designed fix these problems but I’m not sure it fixes every instance of them.
We were curious as to why the multiPlot.py program shows these bands and the single plotter WWV_plt2.py does not. The reason is that WWV_plt2.py uses the fldigi-calculated Doppler shift value in the SrawData analysis[date].csv file, whereas multiPlot.py uses data from the Sdata directory file which does not contain the calculated Doppler shift, so it calculates it from the recorded Freq value. If Freq value is off, Doppler will be off. The butterworth filter must be trying to average or smooth out the discontinuity, somehow. Thus the color bands.
I may work on a script to delay Fldigi startup until Bodnar and system time are set, as we can poll the status of both.
Thanks & 73
You received this message because you are subscribed to the Google Groups "hamsci-grape" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hamsci-grape...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hamsci-grape/00fe01d8ac14%24a19612c0%24e4c23840%24%40verizon.net.
Here's mine from Cleveland, also 10 MHz. At least some of the features are similar.
To view this discussion on the web visit https://groups.google.com/d/msgid/hamsci-grape/1575935628.2942638.1660071534702%40mail.yahoo.com.
Here’s 5MHz from mid-Missouri. Not as dramatic.
To view this discussion on the web visit https://groups.google.com/d/msgid/hamsci-grape/F3AD47A0-3E23-4625-AE55-835754766FE3%40gmail.com.
Thank you for sending links to the new plotting tools. We will download and try them out!
The ringing/spikes in our multiPlot Doppler graph for that day were due to the fact that multiPlot.py uses data from the Sdata directory, which does not contain the Doppler shift calculated by Fldigi. Instead, the program calculates shift by the difference between observed frequency, based on Fldigi’s set frequency in the Frequency Window, and beaconfreq from the csv file header. If that Fldigi Frequency Window frequency is accidentally changed by the operator clicking somewhere in that window, the Fldigi frequency can be easily modified without the operator being aware of it. The butterworth filter then creates the ringing and large spikes around the discontinuity in the resulting graph.
On the other hand, the single plotter, WWV_plt2.py, uses data from the Srawdata directory, which contains Doppler shift already calculated by Fldigi, which does not seem to change if the operator changes the Frequency Window entry. So the single plotter doesn’t see the glitch.
I think that if the new plotting code uses files uploaded from Sdata, it may continue to show these bands/spikes or similar, if Fldigi frequency setting is disturbed. We have thought there may be a way to lock the Fldigi frequency window, but have not looked at the code.
In the new few days I will install your new code and try it out with our data from 2022-08-08, and let you know. Thanks very much for giving us a chance to test it.
73, Bill AB1XB
To view this discussion on the web visit https://groups.google.com/d/msgid/hamsci-grape/84924155-BD90-439D-A6A8-53499FA71561%40scranton.edu.