Re: [ldm-users] GRB data feed issues - incomplete files/gaps?

  • To: Mike Zuranski <zuranski.wx@xxxxxxxxx>
  • Subject: Re: [ldm-users] GRB data feed issues - incomplete files/gaps?
  • From: Daniel Forrest <dforrest@xxxxxxxx>
  • Date: Wed, 6 Aug 2025 17:35:26 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wisc.edu; dmarc=pass action=none header.from=wisc.edu; dkim=pass header.d=wisc.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=p9rSuI7LV5o3EKKDbRi6jiW/W+O377GML2lXmxxfFF8=; b=GkMs/YkBr4AlP2Nc7mefLVBBtPKYqT028OcmgInF6LsTyCNrwInUGC01B/rGQlL1nL3VyRTOlOsHW/DyjASGeUyll7tFJmvFLsFghRynwNQBi6GtY4y4K3U0R2vigeRIHUx6N1W58sKBvSCbDXsH+6HXfwhmrhtk2WSNShmKWmo8gD49HgOM7vIsjuRJbb5p+WvqLWeJ6SLl1JV0DI0in09FVLrOoPxXYPOY52c7nDQTcLt7pnwgm2Q5z4kHjrNJGqE8IViUqo0geGlHIcqRBaaQOC8/RroGxyPd5w1aRxUXh3UMAOslWnu5rIoumTnSv+HRFSZy47z1C+yCgATZGw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=cZNqkVD0IpwKIHIubb8RZ3yrWC7ayeXuBnFyp/BwD/koAcBx89d+NqUQpqYAGSi4tOJM+jo/T3C8W+OZOpGz4woN3bbIgF3zjk+1h7P9MA6D9LC09VmIJkTnyPSRM2vrHR8ZZSBDh3okj8AA7WRMdu4jbqiyqvbSKWh7iJQSMe2eYs/CSWDU+bY2xhRfn8H2uR6jsXvF0/qbrpQGzdNbbkdwWq0WLu8pLatS1kHv13H6fj/FG+ddaPh5iQkXMN6sZ6XbU7IElLHPeQ7u/0PT9b16BemMnThmfBMJw0aB90xQQqv53/k75n8mHEJxAsXOr5hpfBq49bFagQMc8Dxi1A==
Mike and Pete,

The Unidata GRB feed is a combination of the raw Unidata feed and the
UW GRB feed.  The combined feed fills in any holes due to RFI at
either site.  So the path is:

Unidata -> UW -> combined data -> Unidata


UW is currently experiencing network issues sending data to the
outside world and this is causing the large dropouts.

I have notified Unidata and hopefully they can switch to their raw GRB
data until this issue is resolved.


On Wed, Aug 06, 2025 at 01:24:40PM -0400, Mike Zuranski wrote:
> OH, I thought you noticed this through Wisc's GRB as well.  I'll just back
> away now, hopefully someone there can shed some more light.
> 
> On Wed, Aug 6, 2025 at 1:23 PM Pete Pokrandt <poker@xxxxxxxxxxxx> wrote:
> > 
> > I'm not sure this is an upstream issue, for exactly your reasoning - those
> > other sites don't seem to be affected, and they must be using GRB data, but
> > maybe not from the Unidata source?
> > 
> > Doesn't the Unidata GRB data feed originate from some dishes up by the
> > mesa lab? I'm thinking it's something with this particular Unidata
> > processing, rather than an upstream data issue.
> > 
> > Maybe wind? or smoke? or dish alignment? or ?? I don't know the details of
> > the processing but that's my gut feeling, that it's something with the data
> > processing between the Unidata dishes and the SATELLITE data feed origin
> > box..
> > 
> > Pete
> > 
> > Pete Pokrandt - System Engineer IV
> > UW-Madison Dept of Atmospheric and Oceanic Sciences
> > 608-262-3086  - poker@xxxxxxxxxxxx
> > ------------------------------

-- 
Daniel K. Forrest               Space Science and
dforrest@xxxxxxxx               Engineering Center
(608) 890 - 0558                University of Wisconsin, Madison

  • 2025 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: