[gembud] Surface & upper air corruption?

  • To: "gembud@xxxxxxxxxxxxxxxx" <gembud@xxxxxxxxxxxxxxxx>
  • Subject: [gembud] Surface & upper air corruption?
  • From: "Boothe, Mark (CIV)" <maboothe@xxxxxxx>
  • Date: Wed, 30 Oct 2019 15:40:50 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nps.edu; dmarc=pass action=none header.from=nps.edu; dkim=pass header.d=nps.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KpuNgON0Y8yt7tkzbzGGqQiW4jqUaztYFqgq9EuVFEU=; b=IJtqRn/eKGIgYkNWfDKwmue83HmtVoCO9Wr2mJF7ZxDBk7fC3ZL7uzSfBBXYIxg3ModH9LOcgBa9s3f72H5aAOGN+N93DlaFW3MCWDgZ8qqD8jaEwl+/jvDzWIRl4rpWoReBsbRsZObSTYvI71Ry+POdNSEvVsG1E1YEOh+QHQgoaTjwXvBMZEPt/MMsW8IZ/J40p0evY2I+Ob7LQLwov1avH4AA0VhNWqnhdDMGZyTXtTAw0XxDc5kFlCfsd2HscWASaz3kL76Dh4SMhCQqHar909hbsabJ/BiOkueYNN3mJhhtXgC4LvPiHBxc8rkSOocMvV397FGYwlJ8A8KzQA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hzSCMpCBYes1FGQgfdVlNsUXYq9nWXWcM/E2bHh9gQ/VZdoNbHCYeqkGeTLr8pHJwpgjG9Z+l03zEv6dEnNsVBp9bEjHKgSmcyHVaspwLRxOknQzO4UPJYkyRfD+O+g0EuQm4PvMG5rvVB1g1pgQjp7AtwDLqFSPeEghc+3AOE3OJ0x8m2vMybCuiQCP7xhbkijAwlYkob3QddIJ4nRnTKoUT9oUjK+XE7os5crM5LE8zlrgytossfj3Tnt4TOdXUtVci024esQTuZk4kRyOUkTC7ao3IrjnlQiyaADzBwRqT2Uwh+i2OVnoS7ZCg+RsBpIn9CgQdKSPYTPDrV7nsQ==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=maboothe@xxxxxxx;
Hello Gembud list,

While our reception of satellite and model data are good here at NPS, GARP 
crashes upon request for surface or upper air observations. We've noticed this 
problem, intermittently for the last week or so.  If a particular day is 
unavailable, data for the following day, starting at 0000 UTC, can sometimes be 
fine, which seems to suggest that once a particular day's gempak file is 
"corrupted", it is completely corrupted for the entire day.

Does anyone know of a common cause of this problem?  If it is a problem caused 
by just a single bad datum point, is it possible to "surgically" remove the 
offending point from the .gem file? Is there a way to search the 'dcmetr.log' 
file to find the culprit? What would I usually search for? (Or am I barking up 
the wrong tree?)

Thanks in advance for any guidance,
Mark Boothe
Naval Postgraduate School
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the gembud archives: