[Geomag-daily] Daily Report, Monday, June 25th, 2018, YD 176

[Sauter, Edward]

Greg,
Thanks for the input.  At Fredericksburg and other observatories, our
observers might tell us if there was lightning during the time in
question.  Otherwise we look at the nature of the disturbance to see what
might have caused the disturbance.  If the problem persists, we will
investigate potential sources, like the ones you suggested, to see if there
is a cause outside of our acquisition system.

Ed

On Mon, Jun 25, 2018 at 4:05 PM, Lucas, Greg <glucas at usgs.gov> wrote:

> Operations team,
>
> I'm curious if 'lightning' gets classified differently than any other
> artificial disturbance in processing, or why it is critical to ask whether
> it was lightning in the reports? Possibly to make sure it isn't faulty
> electronics?
>
> I'm sure you all don't like me giving you more data to look at, but here
> it is anyways :)
>
> *Lightning maps:*
> <http://en.blitzortung.org/historical_maps.php?map=30>
> http://en.blitzortung.org/historical_maps.php
> You can select previous days/times and get a general idea of whether there
> was lightning in the area or not.
> Per Ed's comments below:
> FRD appears to be lightning
> SJG appears to be lightning
> TUC does *not* appear to be lightning.
>
> *Historic Weather Reports:*
> There are many automated weather reporting stations (generally at
> airports) that you can access the historical records of. There was some
> strong storm that blew through Fredericksburg on 6/24 for instance.
> FRD Data
> <https://www.wunderground.com/history/airport/KEZF/2018/6/24/DailyHistory.html?req_city=Fredericksburg&req_state=VA&req_statename=Virginia&reqdb.zip=22401&reqdb.magic=1&reqdb.wmo=99999>
> You can also search for other days/locations in there too. This can all be
> automated to send alerts if there are storms in the area etc... Possibly a
> fun and useful task for a summer student?
>
> Greg
>
>
>
> On Mon, Jun 25, 2018 at 3:33 PM, Sauter, Edward <esauter at usgs.gov> wrote:
>
>> All,
>> The following discrepancies were noted this day:
>>
>> *Barrow.  The Total Field magnetometer is still awaiting a replacement
>> electronics.  Therefore all derived products are absent: D, Del F, X, Y,
>> Dist, SQ, and SV. *
>>
>> *Deadhorse.  There were data gaps in the Fluxgate and Temperature data at
>> the following times and dates: **1633 through 1645 UT, 6/23/18 (YD 174),
>> 1630 through 1634 UT, 6/24/18 (YD 175), and 0651 through 0659 UT, 6/25/18
>> (YD 176). This suggests a problem with the 802 **acquisition** unit
>> and/or GPS timing. *
>>
>> *Fredericksburg.  There were numerous Artificial Disturbances from 1859
>> through 2129 UT, 6/24/18 (YD 175).  Lightning? *
>>
>> *Tucson.     There were numerous Artificial Disturbances from 0438
>> through 0528 UT, on 6/25/18 (YD 176).  Lightning? *
>>
>> *San Juan.  *
>> *There were numerous Artificial Disturbances from 0738 through 0930 UT,
>> on 6/23/18 (YD 174). *
>>
>> *Dist, SQ and SV.   As mentioned above, the Dist, SQ and SV plots from
>> Barrow are absent.  There are gaps at Tucson in the Dist, Sq and SV plots
>> at the following times and dates: 0533 through 0539 UT and 2105 through
>> 2154 UT, 6/24/18 (YD 175), and 1139 through 1254 UT, 6/25/18 (YD 176).
>> These gaps correspond with internet outages at Tucson. *
>>
>> *Boulder E-Field.  None*
>>
>> *DST.    There is the daily offset in the USGS Dst-1min plot resulting
>> from the corresponding data gap in the plot for Kakioka at around the
>> end/start of each day.*
>>
>> That's all.
>>
>> Ed Sauter
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/geomag-daily/attachments/20180625/7dd2f154/attachment-0001.html>