Thanks for the descriptions! I always like to turn my black boxes into a shade
of grey, whenever possible.
Much appreciated,
Chris
--
Dr. Christopher G. Herbster
Associate Professor
Director of Science and Technology
for the ERAU Weather Center
Applied Aviation Sciences
Embry-Riddle Aeronautical Univ.
600 S. Clyde Morris Blvd.
Daytona Beach, FL 32114-3900
386.226.6444 Office
386.226.6446 Weather Center
http://wx.erau.edu/
Schedule at: http://wx.erau.edu/faculty/herbster/Schedules/
-----Original Message-----
From: ldm-users-bounces@xxxxxxxxxxxxxxxx
[mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Hughes, Brian
Sent: Thursday, March 30, 2017 10:43 AM
To: ldm-users@xxxxxxxxxxxxxxxx
Subject: Re: [ldm-users] uniwisc feed receive times
Hi Chris,
Long ago, I managed the system which processes the current GOES images for
NOAAPort. The GVAR is received at NOAA's Satellite Operations Facility (NSOF)
in Suitland, MD (Wallops handles uplink and telemetry, and some backup image
processing) and the GOES Ingest and NOAAPort Interface (GINI) waits until a
scan is almost complete or complete, then uses McIDAS to re-project the images,
adds some NOAAPort comms headers and trailers (TIGExx, TIGWxx, TIGNxx, etc)
then transfers the processed images over to the NCF for uplink to NOAAPort.
The GOES-R to NOAAPort process was designed to minimize latency as much as
possible and enable the 1 min or 30 sec temporal coverage. (The GOES sats have
had 1 min scan capability all along, but it was only allowed for research
purposes since AWIPS could not handle the 1 minute schedules. This "Super Rapid
Scan Operation" would cause the NWS to receive "Routine" schedule only because
SRSO schedule could not be used concurrently with the 7.5 minute "Rapid Scan",
and why GOES-R proving ground could only use the backup GOES-14 in SRSO during
the summer when backup GOES sats would be routinely taken out of storage for
testing)
-Brian
Brian K. Hughes, PMP, ITIL v3 | Director | Weather Information and Technology
Solutions Unisys | Federal Systems | Direct 703-234-9875 | Cell 443-614-6026 |
brian.hughes@xxxxxxxxxx | weather.unisys.com
2476 Swedesford Road | Malvern, PA 19355
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is for use only by the intended recipient. If you received this in
error, please contact the sender and delete the e-mail and its attachments from
all devices.
----------------------------------------------------------------------
Message: 1
Date: Wed, 29 Mar 2017 18:07:23 +0000
From: David Fitzgerald <David.Fitzgerald@xxxxxxxxxxxxxxxx>
To: "Herbster, Christopher G." <herbstec@xxxxxxxx>,
"'ldm-users@xxxxxxxxxxxxxxxx'" <ldm-users@xxxxxxxxxxxxxxxx>
Subject: Re: [ldm-users] uniwisc feed receive times
Message-ID:
<958EF916EB06874283F9B8F820726DD301D5A192CE@xxxxxxxxxx.local>
Content-Type: text/plain; charset="us-ascii"
Thanks for the info. You helped clear things up.
Dave
From: Herbster, Christopher G. [mailto:herbstec@xxxxxxxx]
Sent: Wednesday, March 29, 2017 1:29 PM
To: David Fitzgerald <David.Fitzgerald@xxxxxxxxxxxxxxxx>;
'ldm-users@xxxxxxxxxxxxxxxx' <ldm-users@xxxxxxxxxxxxxxxx>
Subject: RE: uniwisc feed receive times
Hi Dave,
The timestamp of the image is the time that the scan began. There are many
different scanning strategies and regions, and each of them takes a different
amount of time to complete.
Speculating that the routine schedule was in place for yesterday, and using
this resource
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ospo.noaa.gov%2FOperations%2FGOES%2Feast%2Fimager-routine.html&data=02%7C01%7CBrian.Hughes%40unisys.com%7Cf223f0835a8a4f2a2d6a08d476ce9d91%7C8d894c2b238f490b8dd1d93898c5bf83%7C0%7C0%7C636264077164261686&sdata=opnb6tgIRnPTn%2BmSNJwSN%2BkrrX2jC9GbNP2ndXgwA8s%3D&reserved=0,
I see that a typical 1345 UTC image would be the Northern Hemisphere Extended
sector, which takes 14:15 (14.25 minutes) to complete. This image did not
complete until 13:59:15. I do not know the magic that occurs to bring the
images into the LDM IDD feed, but there is much less latency than you might
think there is given the time to conduct the sector scan. A full disk image,
done every three hours for WMO data sharing, takes 26:02.
We have a NOAAPort ingest system, so we get some data that way. Those images
are first downloaded to Wallops Island, and then bounce around through some
absurd number of miles to get to our dish. (I really do not know enough about
this to say any more, and may have already stepped outside of an accurate
description.)
I hope this helps,
Chris H.
--
Dr. Christopher G. Herbster
Associate Professor
Director of Science and Technology
for the ERAU Weather Center
Applied Aviation Sciences
Embry-Riddle Aeronautical Univ.
600 S. Clyde Morris Blvd.
Daytona Beach, FL 32114-3900
386.226.6444 Office
386.226.6446 Weather Center
***********
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are recorded in
the Unidata inquiry tracking system and made publicly available through the
web. Users who post to any of the lists we maintain are reminded to remove any
personal information that they do not want to be made public.
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
