[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20000131: dcreanal, pmsl grids
- Subject: 20000131: dcreanal, pmsl grids
- Date: Wed, 02 Feb 2000 16:02:14 -0700
Emily,
The one field in your output that doesn't show up is the vertical
coordinate name "NONE". This should be found in the
$GEMTBL/grid/vcrdgrib1.tbl table.
But, for some reason, it doesn't appear that you are getting this value.
You might try looking in $GEMTBL/grid/vcrdgrib1.tbl to make sure that
the file doesn't have the coordinate commented out.
The Netcdf level_desc for this grie is Sea Level which should get mapped
to vertical coordinate number 0, which should be the first entry
in the coordinate table:
000 Reserved grid level NONE 0
If this line starts with a "!" or doesn't exist then that would explain your
trouble.
Steve Chiswell
Unidata User Support
>From: Emily K Grover <address@hidden>
>Organization: .
>Keywords: 200002011849.LAA22132
>Hi Steve,
>
>You're right, I wasn't decoding into monthly files. I was able to run the
>programs that I need on the files you sent me. However, I wanted to make
>sure that I could reproduce the monthly files you sent me. I used the
>exact same command (dcreanal slp.1948.nc YYYYMM_slp.gem), but got
>different output. When I run the above command I get the following:
>
>ventisca% dcreanal slp.1948.nc 194801_slp.gem
> Changing center table to cntrgrib1.tbl
> Changing vertical coord table to vcrdgrib1.tbl
> Changing WMO parameter table to ncarncep1.tbl
> Changing center parameter table to ncarncep1.tbl
>opening 194801_slp.gem 480101/0000
> 480101/0000 PMSL 0 -1
> 480102/0000 PMSL 0 -1
> 480103/0000 PMSL 0 -1
> 480104/0000 PMSL 0 -1
> 480105/0000 PMSL 0 -1
>
>
>When you ran dcreanal, it produced:
>
>> Changing center table to cntrgrib1.tbl
>> Changing vertical coord table to vcrdgrib1.tbl
>> Changing WMO parameter table to ncarncep1.tbl
>> Changing center parameter table to ncarncep1.tbl
>> opening 194801_slp.gem 480101/0000
>> 480101/0000 PMSL NONE 0 -1
>> 480102/0000 PMSL NONE 0 -1
>> 480103/0000 PMSL NONE 0 -1
>> 480104/0000 PMSL NONE 0 -1
>> 480105/0000 PMSL NONE 0 -1
>> ...etc.
>>
>
>I ran gdinfo om the files that I created and again, I get different output
>than when run on your files. GDINFO on my monthly files gives me:
> NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
> 1 480101/0000 ****** PMSL
> 2 480102/0000 ****** PMSL
> 3 480103/0000 ****** PMSL
> 4 480104/0000 ****** PMSL
>
>GDINFO on your monthly files gives me:
> NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
> 1 480101/0000 0 NONE PMSL
> 2 480102/0000 0 NONE PMSL
> 3 480103/0000 0 NONE PMSL
> 4 480104/0000 0 NONE PMSL
> 5 480105/0000 0 NONE PMSL
>
>The monthly files I create are not even the same size as the ones you
>created- they are smaller by approx 300K. Again, I am using the same
>source data and command. Do you know why this is happening?
>
>Thank you,
>Emily
>
>_________________________________________________________________________
>Emily K. Grover MMMMMM MMMMMM
>University of Michigan MMMMM MMMMM
>Atmospheric, Oceanic, and Space Sciences MMMMMM MMMMMM
>Mesoscale Meteorology Laboratory MMMMMMM MMMMMMM
>734.764.0564 MMMM MMMMM MMMM
> MMMM MMM MMMM
> MMMM MMMM
> MMMMMM MMMMMM
>_________________________________________________________________________
>
>
>On Mon, 31 Jan 2000, Unidata Support wrote:
>
>>
>> Emily,
>>
>> I ran dcreanal on your data as follows to create monthly files:
>> dcreanal slp.1948.nc YYYYMM_slp.gem
>>
>> This produced:
>> Changing center table to cntrgrib1.tbl
>> Changing vertical coord table to vcrdgrib1.tbl
>> Changing WMO parameter table to ncarncep1.tbl
>> Changing center parameter table to ncarncep1.tbl
>> opening 194801_slp.gem 480101/0000
>> 480101/0000 PMSL NONE 0 -1
>> 480102/0000 PMSL NONE 0 -1
>> 480103/0000 PMSL NONE 0 -1
>> 480104/0000 PMSL NONE 0 -1
>> 480105/0000 PMSL NONE 0 -1
>> ...etc.
>>
>>
>> I was able to display these files normally.
>>
>> At this point, I don't know why your were unsucessful. Is
>the
>above output
>> what your received? Did you decode into monthly files? Since there are 366
>> times in the file (and you can only have 200 times in a GEMPAK file), you
>> have to split it up somehow- so monthly is the easiest choice. If you have a
> ny more
>> information on how you decoded the file, let me know.
>>
>> I'll attach the tarfile of decoded files in a separate message.
>> You can unpack the tarfile with "zcat tarfile.Z | tar xvf -"
>>
>> Steve Chiswell
>> Unidata User SUpport
>>
>>
>>
>>
>