>Eirh-Yu Hsie <address@hidden>
>Organization: University of Virginia
>Keywords: 200004072010.OAA01470 McIDAS-X ADDE RTGRIDS ALL ETA NGM DSSERVE
Hsie,
>It seems to me that I have a misconfigured XCD. Please take a look at the
>following 2 GRDLIST outpus and the output from igu.k:
The difference in the GRDLIST and IGU listings you sent in show that
the ADDE dataset definitions in the account you are running this from
are incorrect. The commands that you can run to set your ADDE dataset
definitions to match your XCD setup for GRID file decoding are:
<if running as user 'mcidas', cd to ~mcidas/workdata; if running as any
other user, cd ~/mcidas/data>
dsserve.k ADD RTGRIDS/ALL GRID 5000 5620 RT=YES "ALL Real-Time ETA Grids
dsserve.k ADD RTGRIDS/ETA GRID 5501 5620 RT=YES "Real-Time ETA Grids
dsserve.k ADD RTGRIDS/NGM GRID 5051 5090 RT=YES "Real-Time NGM Grids
Please let me know if this doesn't solve your problem.
Tom
*** Supporting information used for our inquiry system information base ***
DSSERVE is used to manage ADDE dataset definitions. Its basic function
is to generate a table, RESOLV.SRV, in the first writable directory
in a user's MCPATH set of directories. RESOLV.SRV is read by all McIDAS
ADDE data servers to determine the mapping between ADDE dataset name/group
and the files that comprise it.
The dsserve.k commands I provide above show this kind of dataset name/group
and McIDAS file mapping:
name/group GRID file realtime textual description
--------------+------------+-----------+------------------------------------
RTGRIDS/ALL 5000 5620 YES ALL Real-Time ETA Grids
RTGRIDS/ETA 5501 5620 YES Real-Time ETA Grids
RTGRIDS/NGM 5051 5090 YES Real-Time NGM Grids
All McIDAS ADDE commands like GRDLIST command cause a lookup in
RESOLV.SRV to see which file(s) are contained in the dataset name/group
specified. If the ADDE dataset definitions are incorrect, the ADDE
server process will return back the incorrect information. The
difference in the GRDLIST and IGU listings above demonstrate just this
sort of situation. The solution in all cases is:
o the determination of the exact set of files that should be included in
an ADDE dataset
o the setting up of RESOLV.SRV entries by one of three methods (two of
which are equivalent):
1) run McIDAS-X commands from the Unix command prompt
cd ~/workdata (user 'mcidas')
- or -
cd ~/mcidas/data (any other user)
dsserve.k ADD RTGRIDS/ALL GRID 5000 5620 RT=YES "ALL Real-Time ETA Grids
dsserve.k ADD RTGRIDS/ETA GRID 5501 5620 RT=YES "Real-Time ETA Grids
dsserve.k ADD RTGRIDS/NGM GRID 5051 5090 RT=YES "Real-Time NGM Grids
2) run McIDAS-X commands from the command window in a McIDAS-X session
DSSERVE ADD RTGRIDS/ALL GRID 5000 5620 RT=YES "ALL Real-Time ETA Grids
DSSERVE ADD RTGRIDS/ETA GRID 5501 5620 RT=YES "Real-Time ETA Grids
DSSERVE ADD RTGRIDS/NGM GRID 5051 5090 RT=YES "Real-Time NGM Grids
3) edit RESOLV.SRV directly
cd ~/workdata (user 'mcidas')
- or -
cd ~/mcidas/data (any other user)
set the lines for RTGRIDS/ALL, RTGRIDS/ETA, RTGRIDS/NGM as follows:
N1=RTGRIDS,N2=ALL,TYPE=GRID,RT=Y,K=GRID,R1=5001,R2=5400,C=Real-Time Grids,
N1=RTGRIDS,N2=ETA,TYPE=GRID,RT=Y,K=GRID,R1=5011,R2=5050,C=ETA Grids,
N1=RTGRIDS,N2=NGM,TYPE=GRID,RT=Y,K=GRID,R1=5051,R2=5090,C=NGM Grids,
CAUTION: if you decide to edit RESOLV.SRV directly, you must be
careful about the line syntax:
o commas (,) are used as value separators, they may not be used
for anything else
o the following characters are not valid (/), period (.), comma (,),
left bracket ([), right bracket (]) in the comment field
o each line must have a trailing comma (,)
>cumulus:[100]% grdlist.k RTGRIDS/ETA.ALL FORM=FILE
>DATASET NAME: RTGRIDS/ETA
> Dataset Position Creation Date Max Grids Directory Title
> ---------------- ------------- --------- -------------------------------
> 41 2000111 5000 ALL 00Z NGM 0 HR<=VT<=24 HR
> 51 2000111 5000 ALL 00Z NGM 24 HR< VT<=48 HR
>GRDLIST - done
>cumulus:[101]% grdlist.k RTGRIDS/NGM.ALL FORM=FILE
>DATASET NAME: RTGRIDS/NGM
> Dataset Position Creation Date Max Grids Directory Title
> ---------------- ------------- --------- -------------------------------
> 1 2000111 5000 ALL 00Z ETA 0 HR<=VT<=24 HR
> 11 2000111 5000 ALL 00Z ETA 24 HR< VT<=48 HR
> 21 2000111 5000 ALL 00Z ETA > 48 HR
> 31 2000111 5000 ALL 06Z ETA 0 HR<=VT<=24 HR
>GRDLIST - done
>cumulus:[102]% igu.k LIST 5000 6000
> GRIDFILE PROJ CREATED MAXGRD IDENT
> -------- ---- ------- ------ ----------------
> 5001 0 2000111 5000 Misc. Grids for 20 APR 2000
> 5051 0 2000111 5000 ALL 00Z NGM 0 HR<=VT<=24 HR
> 5061 0 2000111 5000 ALL 00Z NGM 24 HR< VT<=48 HR
> 5071 0 2000111 5000 ALL 12Z NGM 0 HR<=VT<=24 HR
> 5081 0 2000111 5000 ALL 12Z NGM 24 HR< VT<=48 HR
> 5101 0 2000111 5000 ALL 00Z MRF 0 HR<=VT<=24 HR
> 5111 0 2000111 5000 ALL 00Z MRF 24 HR< VT<=48 HR
> 5121 0 2000111 5000 ALL 00Z MRF 48 HR< VT<=72 HR
> 5131 0 2000111 5000 ALL 00Z MRF 72 HR< VT<=96 HR
> 5141 0 2000111 5000 ALL 00Z MRF > 96 HR
> 5201 0 2000111 5000 ALL 00Z MAPS
> 5211 0 2000111 5000 ALL 03Z MAPS
> 5221 0 2000111 5000 ALL 06Z MAPS
> 5231 0 2000111 5000 ALL 09Z MAPS
> 5241 0 2000111 5000 ALL 12Z MAPS
> 5251 0 2000111 5000 ALL 15Z MAPS
> 5261 0 2000111 5000 ALL 18Z MAPS
> 5301 0 2000111 24 MDR data for 20 APR 2000
> 5401 0 2000111 5000 ALL 00Z AVN 0 HR<=VT<=24 HR
> 5411 0 2000111 5000 ALL 00Z AVN 24 HR< VT<=48 HR
> 5421 0 2000111 5000 ALL 00Z AVN 48 HR< VT<=72 HR
> 5431 0 2000111 5000 ALL 12Z AVN 0 HR<=VT<=24 HR
> 5441 0 2000111 5000 ALL 12Z AVN 24 HR< VT<=48 HR
> 5451 0 2000111 5000 ALL 12Z AVN 48 HR< VT<=72 HR
> 5501 0 2000111 5000 ALL 00Z ETA 0 HR<=VT<=24 HR
> 5511 0 2000111 5000 ALL 00Z ETA 24 HR< VT<=48 HR
> 5521 0 2000111 5000 ALL 00Z ETA > 48 HR
> 5531 0 2000111 5000 ALL 06Z ETA 0 HR<=VT<=24 HR
> 5541 0 2000111 5000 ALL 06Z ETA 24 HR< VT<=48 HR
> 5561 0 2000111 5000 ALL 12Z ETA 0 HR<=VT<=24 HR
> 5571 0 2000111 5000 ALL 12Z ETA 24 HR< VT<=48 HR
> 5581 0 2000111 5000 ALL 12Z ETA > 48 HR
> 5591 0 2000111 5000 ALL 18Z ETA 0 HR<=VT<=24 HR
> 5601 0 2000111 5000 ALL 18Z ETA 24 HR< VT<=48 HR
> ---END OF LISTING
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.