[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010405: minor fix to nmap2 time library routine (fwd)



Scott and Steve,

I have the following note from John Horel regarding the use of archived data 
in NMAP setting the date/time. Another site ran into the same problem
and also was able to implement this fix. I haven't gone back and 
learned all the ins and outs of what the time slider is doing.

Steve

Steve Chiswell
Unidata User Support


---------- Forwarded message ----------
Date: Thu, 05 Apr 2001 12:33:33 -0600
From: Unidata Support <address@hidden>
To: address@hidden
Subject: 20010405: minor fix to nmap2 time library routine


------- Forwarded Message

>To: address@hidden
>cc: address@hidden
>From: "John D. Horel" <address@hidden>
>Subject: minor fix to nmap2 time library routine
>Organization: UCAR/Unidata
>Keywords: 200101312207.f0VM7BX24816

This bug is so esoteric that I won't bother sending it out to the gembud list. 
I was unable to plot surface data in nmap2 from last February using the pop up 
"set time" widget. After putting in a bunch of write statements, I traced the 
symptom to $GEMPAKHOME/source/nmaplib/nsf/nsfdspl.f where it was calling
nsf_tlst and using endtim. Since my time window was far from the endtim, it was 
not plotting any data. I switched endtim to dattim and things appear to be 
working both on current data and retrospective data.

Here's the line in nsfdspl.f that was modified. 


c jdh 01/01 replaced endtim with dattim in call as it made it impossible
c to plot data from previous year
        CALL NSF_TLST ( alias, cycle, isbcat, dattim, mrange,
     +                  timstr, lenstr, numt, iret )

I'm not sure if this solves the problem entirely, but at least I'm looking at 
both current and old surface data now.

Regards,

John


------- End of Forwarded Message