Thanks for the offer Daryl, wow 2040!
I will be fortunate to still be around then!
Robert
-----Original Message-----
From: gembud <gembud-bounces@xxxxxxxxxxxxxxxx> On Behalf Of Herzmann, Daryl E
[AGRON]
Sent: Monday, December 28, 2020 6:45 AM
To: gembud@xxxxxxxxxxxxxxxx; Manousos, Peter C <pmanousos@xxxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [gembud] Solved - NMAP2 Data Selection Window Not
seeing gridded data with fhrs valid past Dec 31 2020
Good morning,
Looking at the most recent Unidata GEMPAK status report we read:
---------------------------
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.unidata.ucar.edu%2Fcommittees%2Fusercom%2F2020Sep%2Fstatusreports%2Findex.html%23awips2&data=04%7C01%7Crobert.r.mullenax%40nasa.gov%7C8ba00c46ff004ffe97be08d8ab2e940e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637447563877012561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kYslheBL91lCDTLVgcj%2FJ69l9D%2BgevP27UkUNUixnbc%3D&reserved=0
At this time, GEMPAK development has ceased, and support through Unidata is
very limited.
We are in contact with Unidata community GEMPAK experts who have volunteered to
help with questions/problems as their time allows and hope that others in the
community will be able to provide additional guidance to issues that arise.
--------------------------
Does this mean Unidata needs some folks to take over development of the github
repo? I would be certainly up to help out with pushing GEMPAK forward on
Github! I did look at the NCEP/NCO latest gempak release and they kicked this
can to 2040 :)
daryl
--
/**
* daryl herzmann
* Systems Analyst III -- Iowa Environmental Mesonet
*
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmesonet.agron.iastate.edu%2F&data=04%7C01%7Crobert.r.mullenax%40nasa.gov%7C8ba00c46ff004ffe97be08d8ab2e940e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637447563877012561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uZF6iVsb7tHzEnX7xBya6ydsUTbzKEipNcW%2BXDtQ1tM%3D&reserved=0
*/
________________________________________
From: gembud <gembud-bounces@xxxxxxxxxxxxxxxx> on behalf of Manousos, Peter C
via gembud <gembud@xxxxxxxxxxxxxxxx>
Sent: Sunday, December 27, 2020 11:58 AM
To: gembud@xxxxxxxxxxxxxxxx
Subject: [gembud] Solved - NMAP2 Data Selection Window Not seeing gridded data
with fhrs valid past Dec 31 2020
Thanks to Patrick, Kevin, and Pete P, here is how to solve this problem.
Note there are TWO files you must edit, the latter governs how the tic marks in
the nmap2 data selection window handles fhrs crossing the 2020/2021 threshold.
1. cd $GEMEXE and cp $GEMEXE/nmap2 $GEMEXE/nmap2.orig (keep an original
copy which you can revert to if needed)
2. cd $GEMPAK/source/gemlib/ti and edit two files (you may also want to
copies this to a “.orig”) for reference
* modify tiyy24.f “.le. 20” to “.le. 25” (the 25 is for 2025 and you
could make this more than 25 if you want but I assume Unidata will fix this by
then)
* modify ticcnt.f “.le. 20” to “.le. 25”
3. in the same directory
* type make clean
* then type make (warning if you did not change these above two
files at all, make will alert you that nothing is new to make).
4. archive the new .o files into gemlib.a with the following commands
* ar rv $GEMLIB/gemlib.a tiyy24.o (you should see a message “r –
tiyy24.o” )
* ar rv $GEMLIB/gemlib.a ticcnt.o (ditto but for ticcnt.o)
5. cd $GEMPAK/source/programs/gui/nmap2 then recompile nmap2
* make clean
* make nmap2
6. You can verify you got a new nmap2 executable, and once you have copy it
to $GEMEXE with the command cp nmap2 $GEMEXE
7. At this point you should re-source the Gemenviron (for us it looks like
this source /fewxops/GEMPAK/GEMPAK7/Gemenviron” . Another way to do this is
just open another terminal window (assuming your resource file upon opening the
window sources Gemenviron”
8. Then launch nmap2 with nmap2
This is how it worked on our system and yours will no doubt be a little
different but the hard part was figuring out which files to recompile and how
to add them to the gemlib.a archive.
Merry Christmas and Happy New Year.
From: gembud <gembud-bounces@xxxxxxxxxxxxxxxx> On Behalf Of Manousos, Peter C
via gembud
Sent: Saturday, December 26, 2020 7:04 PM
To: gembud@xxxxxxxxxxxxxxxx
Subject: Re: [gembud] [EXTERNAL] Re: NMAP2 Data Selection Window Not seeing
gridded data with fhrs valid past Dec 31 2020
Greetings. As an addendum – the mods you recommended work fine if all fhrs are
valid in 2021 (time line is rendered properly in NMAP2 data selection window
and the data renders just fine).
Somehow a run with fhrs crossing the 2020/2021 threshold is still jacked up.
PEte
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> On
Behalf Of Manousos, Peter C via gembud
Sent: Saturday, December 26, 2020 6:35 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
Subject: Re: [gembud] [EXTERNAL] Re: NMAP2 Data Selection Window Not seeing
gridded data with fhrs valid past Dec 31 2020
Hi Kevin – progress but not quite there yet. Result is a timeline in the data
selection window that has the correct number of frames but a invalid rendering
of available fhrs in a properly sequenced format (see image below). However
if you click LOAD you do get all 11 fhrs to load and display! BUT.. rendered
out of sequence where fhrs valid in 2021 are rendered first in sequence
followed by those valid in 2020. Despite being out of sequence the valid
times are proper in the lower left hand of the gui and also in the title of
each image. If you have any other suggestions please send them, I intend to
put together the proper steps one must take and send it as a final email in
this thread to help anyone else who runs into this issue.
Here is what we did based on your email.
1. cd $GEMPAK/source/gemlib/ti and typed make (verified a tiyy24.o
file was created)
2. From the same directory typed ar rv $GEMLIB/gemlib.a tiyy24.o and
received the message r - tiyy24.o with no warnings or errors
3. cd $GEMPAK/source/programs/gui/nmap2 and typed make clean then
make and received no warnings or errors (verified a new nmap2 exe was created).
4. cp nmap2 $GEMEXE/nmap2
Here is the feedback from the make command in nmap2 dir
gcc -DUNDERSCORE -DLinux -I/fewxops/GEMPAK/NAWIPS/gempak/include
-I/fewxops/GEMPAK/NAWIPS/os/linux64/include -I/usr/X11R6/include -DG_64BIT
-O2 -fPIC -g -I/usr/X11R6/include -I/usr/X11R6/include
-I/fewxops/GEMPAK/NAWIPS/extlibs/AODT -c nmap2.c
gfortran -fno-second-underscore -fno-range-check -fd-lines-as-comments
-I/fewxops/GEMPAK/NAWIPS/gempak/include
-I/fewxops/GEMPAK/NAWIPS/os/linux64/include -g -o nmap2 \
nmap2.o \
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmap2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/ginitp_alt.o
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gendp_alt.o
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmaplib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmap2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/Nxmlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/sfmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/snmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdplot2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdstream.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/grphgd.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdcfil.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/oabsfc.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libAODT_v64.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libAODT_v72.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gplt.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/device.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/xwp.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/xw.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/ps.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gn.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libgpc.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libnetcdf.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libjasper.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libpng.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libmel_bufr.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/textlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libxml2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libxslt.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libz.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/rsl.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libbz2.a -lpthread
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a \
-L/usr/X11R6/lib64 -lXm -L/usr/X11R6/lib64 -lXt -lX11 -lm -lrt
[cid:image001.png@01D6DC4A.3DF9F3D0]
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> On
Behalf Of Tyle, Kevin R
Sent: Saturday, December 26, 2020 6:01 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
Subject: Re: [gembud] [EXTERNAL] Re: NMAP2 Data Selection Window Not seeing
gridded data with fhrs valid past Dec 31 2020
Hey Pete, you also need to modify the $GEMLIB/gemlib.a archive with the
compiled tiyy24.o object file that gets produced after running "make" in the
$GEMPAK/source/gemlib/ti/ folder.
So, after running "make" in the ti folder,
ar rv $GEMLIB/gemlib.a tiyy24.o
Then after doing a make clean in the nmap2 directory, type "make" again and
that should pick up the revised tiyy24 subroutine.
Cheers,
Kevin
_________________________________________________
Kevin Tyle, M.S.; Manager of Departmental Computing NSF XSEDE Campus Champion
Dept. of Atmospheric & Environmental Sciences University at Albany Earth
Science 228, 1400 Washington Avenue Albany, NY 12222
ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx> | 518-442-4578 | @nywxguy |
he/him/his _________________________________________________
________________________________
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> on
behalf of Manousos, Peter C via gembud
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Sent: Saturday, December 26, 2020 5:52 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Subject: Re: [gembud] [EXTERNAL] Re: NMAP2 Data Selection Window Not seeing
gridded data with fhrs valid past Dec 31 2020
Thank you to Patrick, Kevin, and Pete P. Based on what you pointed out we
assumed we needed to merely recompile nmap2 but am still getting the same
result.
Here is what we did, but no luck - is there an additional step we may need or
do we need to recompile something else too? Pete
1. cd $GEMEXE and preserve the original executable with cp nmap2 nmap2.orig
2. cd $GEMPAK/source/gemlib/ti and preserve the original .f file then change
the .f file
* cp tiyy24.f tiyy24.f.orig
* edit tiyy24.f and change the line that has the code .le. 20 to
.le. 40
1. recompile nmap2
* cd $GEMPAK/source/programs/gui/nmap2 and then execute make Makefile
which results in a new nmap2 executable in this same directory
* cp nmap2 $GEMEXE
1. open a new terminal window and type nmap2 gives the same result where
it wont treat 2020 as in this century.
BTW the make command yielded no errors or warnings -- here is what it returned
gcc -DUNDERSCORE -DLinux -I/fewxops/GEMPAK/NAWIPS/gempak/include
-I/fewxops/GEMPAK/NAWIPS/os/linux64/include -I/usr/X11R6/include -DG_64BIT
-O2 -fPIC -g -I/usr/X11R6/include -I/usr/X11R6/include
-I/fewxops/GEMPAK/NAWIPS/extlibs/AODT -c nmap2.c
gfortran -fno-second-underscore -fno-range-check -fd-lines-as-comments
-I/fewxops/GEMPAK/NAWIPS/gempak/include
-I/fewxops/GEMPAK/NAWIPS/os/linux64/include -g -o nmap2 \
nmap2.o \
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmap2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/ginitp_alt.o
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gendp_alt.o
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmaplib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/nmap2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/Nxmlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/sfmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/snmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdplot2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdmap.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdstream.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/grphgd.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gdcfil.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/oabsfc.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libAODT_v64.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libAODT_v72.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gplt.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/device.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/xwp.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/xw.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/ps.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gn.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libgpc.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libnetcdf.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libjasper.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libpng.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libmel_bufr.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/textlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libxml2.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libxslt.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libz.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/rsl.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/libbz2.a -lpthread
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/cgemlib.a
/fewxops/GEMPAK/NAWIPS/os/linux64/lib/gemlib.a \
-L/usr/X11R6/lib64 -lXm -L/usr/X11R6/lib64 -lXt -lX11 -lm -lrt
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> On
Behalf Of Pete Pokrandt via gembud
Sent: Saturday, December 26, 2020 2:42 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [gembud] NMAP2 Data Selection Window Not seeing gridded
data with fhrs valid past Dec 31 2020
I'm sure GEMPAK is not the only software out there where this sort of thing is
going to happen.. Wonder what is a good value to change it to? 40? After all..
no one will be using GEMPAK anymore in 2041, right? haha..
I wonder how big of a rewrite it would be to use 4 digit years throughout
GEMPAK.. I shudder to think.. And that would probably break compatibility with
all older existing GEMPAK files archived everywhere, wouldn't it?
Pete
-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>
________________________________
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> on
behalf of ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>
<ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>>
Sent: Saturday, December 26, 2020 1:29 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Subject: Re: [gembud] NMAP2 Data Selection Window Not seeing gridded data with
fhrs valid past Dec 31 2020
Hah, I remember looking at that subroutine back in the Y2K days and thought,
"well no one is going to be using GEMPAK in 2021 ... " 🙂
_________________________________________________
Kevin Tyle, M.S.; Manager of Departmental Computing
NSF XSEDE Campus Champion
Dept. of Atmospheric & Environmental Sciences University at Albany Earth
Science 228, 1400 Washington Avenue Albany, NY 12222
ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx> | 518-442-4578 | @nywxguy |
he/him/his _________________________________________________
________________________________
From: Pete Pokrandt <poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>>
Sent: Saturday, December 26, 2020 2:24 PM
To: Tyle, Kevin R <ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>>;
gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Subject: Re: [gembud] NMAP2 Data Selection Window Not seeing gridded data with
fhrs valid past Dec 31 2020
Thanks, Kevin - you are a life saver! Nice sleuthing..
Pete
-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>
________________________________
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> on
behalf of ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>
<ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>>
Sent: Saturday, December 26, 2020 12:33 PM
To: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Subject: Re: [gembud] NMAP2 Data Selection Window Not seeing gridded data with
fhrs valid past Dec 31 2020
Looks like $GEMPAK/source/gemlib/ti/tiyy24.f is the file that needs to be
changed.
________________________________
From: gembud
<gembud-bounces@xxxxxxxxxxxxxxxx<mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> on
behalf of Patrick Marsh <pmarshwx@xxxxxxxxx<mailto:pmarshwx@xxxxxxxxx>>
Sent: Saturday, December 26, 2020 1:07 PM
To: Manousos, Peter C
<pmanousos@xxxxxxxxxxxxxxxxxxx<mailto:pmanousos@xxxxxxxxxxxxxxxxxxx>>
Cc: gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Subject: Re: [gembud] NMAP2 Data Selection Window Not seeing gridded data with
fhrs valid past Dec 31 2020
Hi, Pete,
This is the result of a GEMPAK bug within the time library. The version of
GEMPAK you are using does not recognize the year 2021, rather it reverts back
to 1921. So, instead of a Y2K bug, it's a Y2K21 bug.
The internal NCEP version of GEMPAK had a patch released earlier in December to
address this bug, but I suspect no one has incorporated this patch into the
community version.
Patrick
On Sat, Dec 26, 2020 at 12:00 PM Manousos, Peter C via gembud
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>> wrote:
Greetings. We are experiencing an unusual problem. NMAP2’s (v 7.1.1) data
selection window can’t seem to detect grid files for fhrs valid past Dec 31
2020.
This is happening with all our model grid data no matter if it’s the gfs,
ecmwf, naefs, gefs, etc. and for what its worth, the restore files do NOT have
a fhr limit specified.
Quick example is a listing of today’s 00z ECMWF which is typical and contains
the basic 500, 850 and surface fields out to f240 and which we can plot just
fine using gdplot3
-rw-rw-r-- 1 fewx fewx 890368 Dec 26 00:40 ecmwf_2020122600f000
-rw-rw-r-- 1 fewx fewx 888832 Dec 26 00:55 ecmwf_2020122600f024
-rw-rw-r-- 1 fewx fewx 887296 Dec 26 01:00 ecmwf_2020122600f048
-rw-rw-r-- 1 fewx fewx 884736 Dec 26 01:10 ecmwf_2020122600f072
-rw-rw-r-- 1 fewx fewx 882688 Dec 26 01:15 ecmwf_2020122600f096
-rw-rw-r-- 1 fewx fewx 882688 Dec 26 01:20 ecmwf_2020122600f120
-rw-rw-r-- 1 fewx fewx 882176 Dec 26 01:30 ecmwf_2020122600f144
-rw-rw-r-- 1 fewx fewx 883200 Dec 26 01:35 ecmwf_2020122600f168
-rw-rw-r-- 1 fewx fewx 883712 Dec 26 01:45 ecmwf_2020122600f192
-rw-rw-r-- 1 fewx fewx 884224 Dec 26 01:50 ecmwf_2020122600f216
-rw-rw-r-- 1 fewx fewx 884736 Dec 26 01:55 ecmwf_2020122600f240
However the data selection window in NMAP2 only shows data through fhr 120. At
the time of this writing fhr 120 corresponds to Dec 31 2020 00z.
By tomorrow we will only be able to see in NMAP2 data out through fhr 96 and so
on.
We did try to mess with the Calendar function but this did not help. If anyone
else is experiencing this and if so any workarounds?
Pete
[cid:image002.png@01D6DC4A.3DF9F3D0]
________________________________
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.
_______________________________________________
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.
gembud mailing list
gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.unidata.ucar.edu%2Fmailing_lists%2F&data=04%7C01%7Crobert.r.mullenax%40nasa.gov%7C8ba00c46ff004ffe97be08d8ab2e940e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637447563877012561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EVDh2%2FUtMdNAwmo%2FGVxoFrimhysNu7HSKon46KrYIP0%3D&reserved=0
--
Dr. Patrick Marsh (@pmarshwx)
Chief, Science Support Branch
NOAA/NWS/NCEP Storm Prediction Center
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pmarshwx.com%2F&data=04%7C01%7Crobert.r.mullenax%40nasa.gov%7C8ba00c46ff004ffe97be08d8ab2e940e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637447563877012561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IOcgku2O0JHNAXMDTwceEEVSHNdidz7JSvWWSXnyWzo%3D&reserved=0<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecure-web.cisco.com%2F1CVcJkeXnveHhD09_qXz1iMzvuI7cTcH5Xh72jc6ZG3LE00BiSHLVLeuOzweyS6oPz-as2FuQe4WzuHbCyd8OtkAL-Sq7P_sMs4MYanbdZzmujA6htaXu70qESKkN-OuAWEDBGZw2S6SQQUuK_Jjcp_HNNyVeF_Jbut_IZ2T8uvHPYrvC3sBMZxEBsh8dx2zh6GIdWKfhLs5yKm7brNEH9e-zOTxixQy1k7zvBObf43h6j9MOibA5dG1j8hf9oc5r4tWg9KeQSJ60ZbAtZYieI60yK5sBG1v8-Z4yTj8KxHEjq3UN3gida1mgNWSuyb5QqPoj3EviYi968vqN5z5JtLBXyPX7ktuczTsbS_GX28v_5WsSwqNvAJz4LoGENXRe%2Fhttp%253A%252F%252Fwww.pmarshwx.com%252F&data=04%7C01%7Crobert.r.mullenax%40nasa.gov%7C8ba00c46ff004ffe97be08d8ab2e940e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637447563877012561%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rB%2FqMqYGMckStQbUbMnvut9yTJIVNUeNBIgXCwz%2Fk%2F8%3D&reserved=0>
________________________________
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.
________________________________
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.
________________________________
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.
________________________________
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.
