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

[McIDAS #AAZ-699855]: mcidas GRDLIST FRAN=



Hi Bill,

First, let me apologize for the incredible tardiness of this reply!

re:
> Long time since I had a Mcidas problem. How have you been ?

I have been well, thank you (but busy).  How is life in the Northeast?
The winter season has been _very_ interesting here in Colorado.  I have
received over 95 inches of snow at my house (in the foothills at 8150
feet above Boulder) so far.  I have really been enjoying the snow,
but the wind storms that have occurred in between a couple of the storms
was "challenging".  The snow that drifted around my neighborhood settled
into esker-like ridges was as hard as concrete.  The county snowplows
that typically come through our neighborhood were getting stuck, so road
graters were eventually used.  All-in-all, it has been very interesting.
The good news is that my Internet connection has continued to work nicely
:-)

> Problem: When I use GRDLIST with the keyword FRAN=, I don't see all the
> grids on my server. Interestingly, I don't have a problem on motherlode.

Interesting.  I had not tried using the FRANGE= keyword sequence, so I
had not run into this.  The fact that it does not occur on motherlode
hints that the problem is one that was introduced in McIDAS-X v2006 --
motherlode is still running v2005+.

> -- To document the problem, I opened a text file. Here are the
> responses:
> 
> TFILE did OPEN on window 0
> 
> -- Make sure I am looking at my server, omega:
> 
> DATALOC LIST
> Group Name Server IP Address
> -------------------- ----------------------------------------
> AMRC UWAMRC.SSEC.WISC.EDU
> BLIZZARD ADDE.UCAR.EDU
> CIMSS OMEGA.LSC.VSC.EDU
> EAST <LOCAL-DATA>
> EUM_AD <LOCAL-DATA>
> GINICOMP ADDE.UCAR.EDU
> GINIEAST ADDE.UCAR.EDU
> GINIWEST ADDE.UCAR.EDU
> GOESEAST <LOCAL-DATA>
> ME7 IO.SCA.UQAM.CA
> MYDATA <LOCAL-DATA>
> NEXRCOMP ADDE.UCAR.EDU
> PUB <LOCAL-DATA>
> RTGRIDS OMEGA.LSC.VSC.EDU
> RTIMAGES OMEGA.LSC.VSC.EDU
> RTNEXRAD ADDE.UCAR.EDU
> RTPTSRC OMEGA.LSC.VSC.EDU
> RTWXTEXT OMEGA.LSC.VSC.EDU
> TOPO OMEGA.LSC.VSC.EDU
> WEST <LOCAL-DATA>
> <LOCAL-DATA> indicates that data will be accessed from the local data 
> directory.
> DATALOC -- done
> 
> -- Check what is on my server:
> 
> GRDLIST RTGRIDS/NAM DAY=030 TIME=00 PAR=T LEV=2 GPRO=LAMB GRIB=211 NUM=29
> Dataset position 10     Directory Title= ALL  00Z NAM 0  HR<=VT<=24 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM    0 30 JAN 07030 00:00:00   138 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM    6 30 JAN 07030 06:00:00  1694 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   12 30 JAN 07030 12:00:00  2366 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   18 30 JAN 07030 18:00:00  3838 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   24 31 JAN 07031 00:00:00  5164 
> LAMB

> Dataset position 20     Directory Title= ALL  00Z NAM 24 HR< VT<=48 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM   30 31 JAN 07031 06:00:00   840 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   36 31 JAN 07031 12:00:00  2163 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   42 31 JAN 07031 18:00:00  3359 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   48 01 FEB 07032 00:00:00  4491 
> LAMB

> Dataset position 30     Directory Title= ALL  00Z NAM 48 HR< VT<=72 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM   54 01 FEB 07032 06:00:00   621 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   60 01 FEB 07032 12:00:00  2201 
> LAMB
> Number of grids listed = 11
> GRDLIST - done
> 
> -- I have 11 grids going out 60 hours. That's good.

Very good.

> -- Now, repeat the same query using the FRAN= keyword:
> 
> GRDLIST RTGRIDS/NAM DAY=030 TIME=00 PAR=T LEV=2 GPRO=LAMB GRIB=211 NUM=29 
> FRAN=0 48 6

> Dataset position 10     Directory Title= ALL  00Z NAM 0  HR<=VT<=24 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM    0 30 JAN 07030 00:00:0o   138 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM    6 30 JAN 07030 06:00:00  1694 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   12 30 JAN 07030 12:00:00  2366 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   18 30 JAN 07030 18:00:00  3838 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   24 31 JAN 07031 00:00:00  5164 
> LAMB
> Number of grids listed = 5
> GRDLIST - done
> 
> -- So, I don't see forecast beyond 24 hours ?????? That is not correct.

Hmm... it is suspicious that the listing ends after the grids from a single
output file have been included.

> -- Let's repeat this on motherlode.
> 
> DATALOC ADD RTGRIDS ADDE.UCAR.EDU
> 
> Group Name                    Server IP Address
> --------------------         ----------------------------------------
> RTGRIDS                      ADDE.UCAR.EDU
> 
> <LOCAL-DATA> indicates that data will be accessed from the local data
> directory.
> DATALOC -- done

> GRDLIST RTGRIDS/NAM DAY=030 TIME=00 PAR=T LEV=2 GPRO=LAMB GRIB=211 NUM=29 
> FRAN=0 48 6
> Dataset position 10     Directory Title= ALL  00Z NAM 0  HR<=VT<=24 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM    0 30 JAN 07030 00:00:00   138 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM    6 30 JAN 07030 06:00:00  1673 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   12 30 JAN 07030 12:00:00  2337 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   18 30 JAN 07030 18:00:00  3794 
> LAMB

> Dataset position 20     Directory Title= ALL  00Z NAM 24 HR< VT<=48 HR
> PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME     GRID  
> PRO
> ---- ---------- ------------ -------- ---- ---- ------------ -------- ----- 
> ----
> T        2 M    30 JAN 07030 00:00:00  NAM   30 31 JAN 07031 06:00:00   835 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   36 31 JAN 07031 12:00:00  2144 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   42 31 JAN 07031 18:00:00  3288 
> LAMB
> T        2 M    30 JAN 07030 00:00:00  NAM   48 01 FEB 07032 00:00:00  4419 
> LAMB
> Number of grids listed = 8
> GRDLIST - done
> 
> -- Okay, I see forecast beyond 24 hours, and out to 48 hours, just what
> I should see.

Yup, it looks like a problem might have been introduced in v2006.  Alternately,
the cause of the different listings could be the platform on which the server
is running: motherlode runs Solaris SPARC v5.9, and I _think_ that your server
is running Linux.  This really shouldn't be the cause of the problem, but
you never know...

> So, I would guess that nothing is wrong with GRDLIST using FRAN=, but
> something is not right with our server omega.

It is likely a problem with with the grid server, gdirserv, not the client.
The reason I say this is your client works correctly when listing from
motherlode and not when listing from your own server.
 
> Can you suggest what to fix on our server ???

Before recommending a workaround/fix, I need to replicate the problem on
a machine here at the UPC and then figure out what is causing the problem.

> Thanks, Bill

Again, I apologize for my slow response.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: AAZ-699855
Department: Support McIDAS
Priority: Urgent
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.