Hi Robert,
This is excellent data! I built a VLF receiver and use a Raspberry Pi
with Audio Injector soundcard to capture the VLF spectrum up to 48
kHz. I wasn't monitoring NPM, unfortunately, but I think I will now. I
have plots of NAA, NAU, and NLK for those three days. I use
vlfrx-tools to capture and record amplitude and phase of the carrier.
Unfortunately for those three days, due to a Trimble firmware issue
that they refuse to fix currently, I don't have phase data because of
a GPS receiver issue.
I have attached my plots of NAA and NAU for those three days. NLK
didn't seem to indicate anything significant from my VLF receiver's
QTH but I attached the plot anyway. You can definitely see a dip in
NAA's amplitude on the 15th at 5-6UT. You can see a dip with NAU too,
but I'm not sure if that is significant, but comparing the day before
and after, it might be. Do you also have plots from NAA and NLK?
Your plots of NPM may show ionospheric perturbation, but even with my
NAA plots, it also could be typical diurnal activity of the ionosphere
at VLF. With VLF transmitters and SIDs, including the Tonga event,
propagation path from the transmitter to your VLF receiver's QTH plays
a very important role in whether you will see a SID in your data.
One paper applicable to this (gravity waves affecting VLF propagation)
can be found here:
https://angeo.copernicus.org/articles/38/385/2020/angeo-38-385-2020.pdf
I had another paper about how the propagation path affects SID
detection but for the life of me, I cannot find it right now. I'll
post it when I do.
Thanks.
Jonathan
KC3EEY
> --
> Please follow the HamSCI Community Participation Guidelines at
>
http://hamsci.org/hamsci-community-participation-guidelines.
> ---
> You received this message because you are subscribed to the Google Groups
> "HamSCI" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
hamsci+un...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/hamsci/3302faa6-cd22-40af-b482-be4b2ff2d2fbn%40googlegroups.com.
>