[ldm-users] level2 via LDM

  • To: "ldm-users@xxxxxxxxxxxxxxxx" <ldm-users@xxxxxxxxxxxxxxxx>
  • Subject: [ldm-users] level2 via LDM
  • From: Victor Gensini <vgensini@xxxxxxx>
  • Date: Tue, 29 Sep 2020 16:30:11 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=niu.edu; dmarc=pass action=none header.from=niu.edu; dkim=pass header.d=niu.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=GTc+ED7JM+hul7mflV4iyV7maxU4JdP27hA28ECRI+A=; b=G0F89kT/umvVFcaQKAJpp1ak3KeJK1IalCh6tlzFeAYvDKnnHMJSBVst75oFzELy9Omwfwyn35893tNtahfHQdCc/8nWjDSrGXhnXhYaYYhEAGG0qZXDYLTPmCVSPzpVkLeE1kcZbmtQRUw01/qU3p0x0uM468zOYwJ0OI8izVSY8+S+1/VYNUVczuFOvxOtWOgjtd2i0ToNegVLPayWsy4WQGCLXYV+W22WKqj5kqIG62sdg7II7jLhlu9MdUxQz2pSaYLNyy2HxViEDTfr4iCPUcR5+Cr69wA1cWOvdUEUipJ2QiCgjw3SOI58APeDvRWQgZTk5Y0Yxf2dmnHCcg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F89qMfzxjG8fxq3BgUMx+uwyuMYuPjcEELowIwJYYGiRlcg4OrGjn4wRAqbw8mGxCBZIfWchQzBDA3HeRh5Tt7APMoh05IuTLMoXn/2I/3dn5u5hNG/w1xP8FHrCWSb/4uBlT2MkcmEuoE3A/4qpzbfGpUuc9OTd8TP9xDvMsvWbP7liOoqsug2zmg+LBGADASpJAcEzvzNQs272LYW4IbfbAu6YIMpU6MTnA6HIq2bbv2a+eSy2RDUs4hN7RUHmQ3fjkAfPHX26TTl332JVUr6YPp+jYVEQPSsK6Av33DRNVW4j+7iRYq8Z8spAnExRpsmo+eluB8Zogm0hc8NMug==
  • Authentication-results: unidata.ucar.edu; dkim=none (message not signed) header.d=none; unidata.ucar.edu; dmarc=none action=none header.from=niu.edu;
Tom/Steve and LDM junkies,

Have there been any recent changes to the format of LEVEL2 radar files coming 
over LDM that I perhaps missed?

A couple of weeks ago, I had a couple scripts start to break that are using 
gpnexr2_gf with:

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x7FD1DF3C1697
#1  0x7FD1DF3C1CDE
#2  0x7FD1DE8BC3AF
#3  0x7FD1DE9F0B54
#4  0x4BCFCB
#5  0x4B8E59
#6  0x4B93C7
#7  0x42A510
#8  0x4288FE
#9  0x40F5A7
#10  0x40903D
#11  0x40554A
#12  0x405588
#13  0x7FD1DE8A8504
#14  0x4046D7
#15  0xFFFFFFFFFFFFFFFF
Segmentation fault (core dumped)

A quick peek of the file size for these stations (relative to others) indicate 
nearly a doubling (in some cases tripling) of the file size versus other 
stations that are still working. As an example, compare your file sizes today 
for KDVN and KILX, both of which are in VCP 35.

I'm using the standard hhmmssRadarII perl script to create the volumes off of 
LDM. Again, no issues for some sites, and then this memory error is popping up 
for others. I sense a change in file contents or format...

Any/all ideas welcome.

Victor


-----------------------------------------------

Vittorio (Victor) A. Gensini, Ph.D., CCM

Associate Professor

Department of Geographic and Atmospheric Sciences

Northern Illinois University

DeKalb, IL 60115

https://atlas.niu.edu<http://atlas.niu.edu>

https://wcs.niu.edu<http://wcs.niu.edu/>

<http://a><http://atlas.niu.edu>
  • 2020 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: