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

20000828: McIDAS RTGRIDS MRF/AVN data (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20000828: McIDAS RTGRIDS MRF/AVN data (cont.)
  • Date: Mon, 28 Aug 2000 08:31:03 -0600
>From: Bill Fingerhut <address@hidden>
>Organization: Lyndon State
>Keywords: 200007061904.e66J4vT23872 McIDAS-XCD RTGRIDS MRF AVN

Bill,

Mark and I got things working last Friday.  I'm sorry I didn't blast
you a note letting you know that we found that the reason you were not
getting all of the MRF grids was the request line in ~ldm/ldmd.conf
was not asking for them.

>> Now, I try to see if I can list out actual GRID files that are said
>> to comprise one of the dataset/groups:
>> 
>> GRDLIST RTGRIDS/ALL.ALL FORM=FILE
>> GRDLIST: No Data Found
>> GRDLIST - done
>> GRDLIST failed, RC=2

This turned out to be an incompatibility between my 7.7 GRIDLIST and your
7.6 server.  I FTPed the file needed to correct the situation to your
machine while Mark and I were on the phone.  Right after that, I could
do GRID listings off of cirrus.

>I get a response to this GRDLIST - if this helps.
>
>GRDLIST RTGRIDS/ALL.ALL FORM=FILE
>DATASET NAME: RTGRIDS/ALL 
>          
>Dataset Position  Creation Date Max Grids         Directory Title      
>  ----------------  ------------- --------- ------------------------------- 
>         1             2000241       5000   Misc. Grids for 28 AUG 2000  
>        10             2000240       5000   Misc. Grids for 27 AUG 2000 
>        80             2000240       5000   ALL  12Z NGM 0  HR<=VT<=24 HR 
>        90             2000240       5000   ALL  12Z NGM 24 HR< VT<=48 HR 
>       201             2000241       5000   ALL  00Z MAPS                 
>       231             2000241       5000   ALL  09Z MAPS                 
>       250             2000240       5000   ALL  12Z MAPS                  
>       260             2000240       5000   ALL  15Z MAPS                  
>       270             2000240       5000   ALL  18Z MAPS                  
>       280             2000240       5000   ALL  21Z MAPS                 
>       301             2000241         24   MDR data for 28 AUG 2000      
>       310             2000240         24   MDR data for 27 AUG 2000      
>       460             2000240       5000   ALL  12Z AVN 0  HR<=VT<=24 HR 
>       470             2000240       5000   ALL  12Z AVN 24 HR< VT<=48 HR 
>       480             2000240       5000   ALL  12Z AVN 48 HR< VT<=72 HR
>       490             2000240       5000   ALL  12Z AVN 72 HR< VT<=96 HR
>       500             2000240       5000   ALL  12Z AVN 96 HR< VT<=120HR
>       501             2000241       5000   ALL  00Z ETA 0  HR<=VT<=24 HR
>       511             2000241       5000   ALL  00Z ETA 24 HR< VT<=48 HR
>       570             2000240       5000   ALL  12Z ETA 0  HR<=VT<=24 HR
>       580             2000240       5000   ALL  12Z ETA 24 HR< VT<=48 HR
>       590             2000240       5000   ALL  12Z ETA 48 HR< VT<=72 HR
>       600             2000240       5000   ALL  18Z ETA 0  HR<=VT<=24 HR
>       610             2000240       5000   ALL  18Z ETA 24 HR< VT<=48 HR
>GRDLIST - done                                                              
>
>DATALOC LIST RTGRIDS                                                        

When I ran the same command on Saturday, I saw that cirrus _had_ received
and decoded the MRF run from Friday night.  Why your system is not showing
this today, is a mystery to me now, since motherlode got the grids OK.

We will have to make sure that Mark didn't revisit the request issue
and attempt to cut down on the amount of model data being requested
(I doubt that he did, by the way).  It really is in your best interest
to not request all of the model data given that your network connection
is somewhat limited.

Tom