Re: [gembud] nexr2rhi - can that be used witn .ar2v data from NCEI directly?

Greetings Peter,

The "oops" error message is coming from here as a failed attempt to read the 
station identifier...

https://github.com/Unidata/gempak/blob/main/gempak/source/programs/upc/programs/nexr2rhi/rnex2.c#L94

I am unsure of your RADFIL nomenclature, I tried reproducing this locally after 
downloading the file from here:

https://s3.amazonaws.com/unidata-nexrad-level2/index.html#2026/03/17/KCLE/

and then setting `RADFIL   = KCLE20260317_125917_V06` , but then I get a 
segfault

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

Backtrace for this error:
#0  0x7f97e80238a0 in ???
#1  0x7f97e8022a45 in ???
#2  0x7f97e7c3fc2f in ???
#3  0x43def6 in wsr88d_ray_to_float_type31
        at /home/akrherz/projects/gempak/extlibs/rsl/src/wsr88d.c:1092
#4  0x43a0f7 in wsr88d_load_sweep_into_volume
        at /home/akrherz/projects/gempak/extlibs/rsl/src/wsr88d_to_radar.c:106
#5  0x43a79f in RSL_wsr88d_to_radar
        at /home/akrherz/projects/gempak/extlibs/rsl/src/wsr88d_to_radar.c:361
#6  0x40879c in rnex2_
        at 
/home/akrherz/projects/gempak/gempak/source/programs/upc/programs/nexr2rhi/rnex2.c:152
#7  0x403d81 in nexr2rhi
        at 
/home/akrherz/projects/gempak/gempak/source/programs/upc/programs/nexr2rhi/nexr2rhi.f:171
#8  0x404be2 in main
        at 
/home/akrherz/projects/gempak/gempak/source/programs/upc/programs/nexr2rhi/nexr2rhi.f:331
Segmentation fault (core dumped)

This Unidata program source code hasn't been touched in 14 years(!!).  You may 
need to look at other approaches to generate such plots!

daryl

________________________________________
From: gembud <gembud-bounces@xxxxxxxxxxxxxxxx> on behalf of Manousos, Peter C 
<pmanousos@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 23, 2026 10:32 AM
To: GEMBUD (gembud@xxxxxxxxxxxxxxxx)
Subject: [gembud] nexr2rhi - can that be used witn .ar2v data from NCEI 
directly?

Greetings – experimenting with creating a cross section using a level ii 
archive volume scan retrieved from NCEI (file name 
KxxxYYYYMMDD_HHMMSS_V06.ar2v) and following the example online 13. Radar 
Programs<https://unidata.github.io/gempak/tutorial/radar_programs.html> (last 
one on the page).

Using GEMPAK 7.14.0.1’s NEXR2RHI – my settings are as follows but see – note 
the line “oops look like…” in the output and no data is read .

Just wondering first if we can use the NCEI Archive Level II data and if so any 
tips on what to enter for radfil since the example on line doesn’t match the 
help in nex2rhi (do a   ph radfil  to see what I mean)

Thanks..

GEMPAK-NEXR2RHI>r
oops look file NEXRII|/home/awips/KCLE20260317_125917_V06.ar2v -1
NEXR2RHI PARAMETERS

Radar file:                 NEXRII|/home/awips/KCLE20260317_125917_V06.ar2v
Date/time:
 Vertical coordinate:       hght
Endpoints:                 @300;460>@620;460
Radar Center point 460,460      Radar Lat   0.00 Radar Lon    0.00
Number of horizontal points:   920
Number of vertical points:   251
Scaling factor:        10** 0      Max:       0.000000    Min:       0.000000   
 Panel:  0


LEVELS:         0.00
COLORS:            6
LINTYP:            1
LINWID:            1
LABEL:             1
Enter <cr> to accept parameters or type EXIT:

CXSTNS   = cle>cak
GVCORD   = hght
PTYPE    = lin
YAXIS    = 0/20000
CINT     = 5/-25/50
SCALE    = 0
LINE     = 6
BORDER   = 1
TITLE    = test
CLEAR    = yes
DEVICE   = xw|test|1024;768
TEXT     = .8
PANEL    = 0
CLRBAR   = 1
CONTUR   = 0
FINT     =
FLINE    =
CTYPE    = c
RADFIL   = NEXRII|/home/awips/KCLE20260317_125917_V06.ar2v
RADPARM  = dz
RADTIM   = last
INTERP   = y

________________________________

The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.