[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20050607: Gempak - GDDIAG not copying/creating grids
- Subject: 20050607: Gempak - GDDIAG not copying/creating grids
- Date: Tue, 07 Jun 2005 13:42:58 -0600
Tom,
You have not correctly specified the type of packing for GPACK. See
the "phelp gpack" information at the GDDIAG prompt.
As an example, you could try:
GPACK=GRIB/32
or
GPACK=NONE
Also note, as I mentioned, GRDAREA is not a valid parameter for GDDIAG in the
old
5.7.2 version you sare using. Your output shows that GDDIAG does not list the
GRDAREA
parameter. In order to create a new grid area or projection, you would need to
be using the current version of GEMPAK (5.8.2a). Entering GRDAREA in your
script has no effect.
Steve Chiswell
Unidata User Support
>From: Tom Green <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200506071836.j57IakZu014000
>This is a multi-part message in MIME format.
>--------------050406060602020004040002
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Steve,
>
>I'm not sure why my scripts didn't come through. I've inserted the text
>of both the script and the output I receive when running the script in
>this message - I thought the web form had taken care of downloading the
>scripts.
>
>I had originally listed no value for gpack, leaving it blank as a
>default. After receiving your e-mail, I changed it to GPACK = 32.
>Attempting that gave me two segmentation faults and a GEMPAK file
>equaling half a gigabyte. Also, in regards to the grid that I am using,
>I originally used gdcfil to create the blank GEMPAK file which I am
>using. If it's of any help to know, regardless of the name, all of my
>files contain RUC-40 data.
>
>Thanks again for your help.
>
>Tom
>
>
>
>THE (original) SCRIPT I RAN:
>#! /bin/csh
>source /meas/home/tom/.cshrc_Linux
>
>#cp blank.gem gscript.gem
>
>foreach date ( 020302 030301 )
>#foreach hh ( 00 03 06 09 12 15 18 21 )
>foreach hh ( 00 )
>set gfile = '/nfs/watauga2/tom/ruc_final/20'$date'_small40.gem'
>set gfile2 = '/nfs/watauga2/tom/mikecode/script.gem'
>set gtime = $date'/'$hh'00F000'
>
>gddiag << endinput
>grdarea = 28;-105;45;-72
>grdarea = rdu-
>gdfile = $gfile
>gdoutf = $gfile2
>gfunc = avor(obs)
>gdattim = $gtime
>glevel = 850
>gvcord = pres
>grdnam = vort
>gpack =
>r
>
>glevel = 500
>r
>
>gfu=adv(tmpk,wnd)
>grdnam=tadv
>r
>
>gfu=div(wnd)
>gle=1000
>grdnam=divwnd
>r
>
>exit
>endinput
>
>#end hour loop
>end
>
>#end date loop
>end
>
>
>THE OUTPUT FROM THE (original) SCRIPT:
>DFILE Grid file
>/nfs/watauga2/tom/ruc_final/20030301_small40.gem
> GDOUTF Output grid file
>/nfs/watauga2/tom/mikecode/gscript.gem
> GFUNC Scalar grid div(wnd)
> GDATTIM Grid date/time 030301/0000F000
> GLEVEL Grid level 1000
> GVCORD Grid vertical coordinate pres
> GRDNAM Grid parameter name divwnd
> GPACK Packing type/number of bits
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>020302/0000F000 850 PRES VORT
>Enter a new grid parameter name, <cr> to accept or type EXIT: Parameters
>requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>020302/0000F000 500 PRES VORT
>Enter a new grid parameter name, <cr> to accept or type EXIT: Parameters
>requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>020302/0000F000 500 PRES TADV
>Enter a new grid parameter name, <cr> to accept or type EXIT: Parameters
>requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>020302/0000F000 1000 PRES DIVWND
>Enter a new grid parameter name, <cr> to accept or type EXIT: Parameters
>requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GDFILE Grid file
>/nfs/watauga2/tom/ruc_final/20020302_small40.gem
> GDOUTF Output grid file
>/nfs/watauga2/tom/mikecode/gscript.gem
> GFUNC Scalar grid div(wnd)
> GDATTIM Grid date/time 020302/0000F000
> GLEVEL Grid level 1000
> GVCORD Grid vertical coordinate pres
> GRDNAM Grid parameter name divwnd
> GPACK Packing type/number of bits
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>030301/0000F000 850 PRES VORT
>Enter a new grid parameter name, <cr> to accept or type EXIT: Warning:
>range too big 1.69069247E+20 1.26782856E+20 -4.22863904E+19
> 214748367 16
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>030301/0000F000 500 PRES VORT
>Enter a new grid parameter name, <cr> to accept or type EXIT: Warning:
>range too big 1.69069247E+20 1.26782856E+20 -4.22863904E+19
> 214748367 16
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>030301/0000F000 500 PRES TADV
>Enter a new grid parameter name, <cr> to accept or type EXIT: Warning:
>range too big INF INF -3.05245639E+30 214748367 16
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>
> TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>030301/0000F000 1000 PRES DIVWND
>Enter a new grid parameter name, <cr> to accept or type EXIT: Warning:
>range too big 1.69073152E+20 4.22852601E+19 -1.26787888E+20
> 214748367 16
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GPACK.
> GEMPAK-GDDIAG>
>
>
>Unidata Support wrote:
>
>>Tom,
>>
>>Your message didn't show your script, but you should check your
>>use of GPACK where you will have to specify the range by the number of
>>bits used to pack the data, or no packing. If you are using GRIB packing then
>>the default number of bits will be 16, but if that isn't enough for your data
> range
>>you can increase that up to 32 bits. See phelp GPACK. If in doubt, try
>>NONE for the packing.
>>
>>Also, the current release of GEMPAK 5.8.2 has the capability to create the gr
> id file
>>if it doesn't exist, as well as reproject to a new grid. The old version that
> you are
>>running does not have those features.
>>
>>Steve Chiswell
>>Unidata User Support
>>
>>
>>
>>
>>
>>>From: "Tom Green" <address@hidden>
>>>Organization: UCAR/Unidata
>>Keywords: 200506071432.j57EWxjF015731
>>>
>>>
>>
>>
>>
>>>Institution: North Carolina State University
>>>Package Version: 5.7.2p2
>>>Operating System: Linux
>>>Hardware Information: unsure-N/A
>>>Inquiry: Hello,
>>>
>>>I\'m currently trying to create grids for temperature advection, vorticity,
> et
>>>c. as shown in the script to be used by a Fortran program. I believe that s
> o
>>>me, but not all, of the data files that I am using have bad data at some poi
> n
>>>ts in the grid, because when using GDDIAG on the second time listed in the s
> c
>>>ript, I get the \"Warning: Range Too High\" message when GDDIAG is creating
> t
>>>he grids. The temperature advection, vorticity, etc. fields do NOT exist in
>
>>>the original file - I am asking GDDIAG to create them and put them in the ou
> t
>>>put file.
>>>
>>>If I use GDCNTR to plot these grids in the original files and use a small ga
> re
>>>a (ex. RDU), there is no problem with the plots. Likewise, GARP is also abl
> e
>>> to display the quantites when using the original files. In my script, I at
> t
>>>empted to have GDDIAG only compute these quantites for a smaller geographica
> l
>>> area, but that didn\'t seem to work either.
>>>
>>>If I have bad data along the sides of the grid, is there any way for me to c
> re
>>>ate these new grids that I want? I want GEMPAK to create these grids rather
>
>>>than attempt to do it in Fortran because of map factor issues, but I also do
> n
>>>\'t need the values of the entire grid - the garea \"RDU-\" is sufficient fo
> r
>>> what I need. Any help you can provide would be greatly appreciated!
>>>
>>>Tom
>>>
>>>
>>>
>>>
>>>
>>--
>>****************************************************************************
>>Unidata User Support UCAR Unidata Program
>>(303)497-8643 P.O. Box 3000
>>address@hidden Boulder, CO 80307
>>----------------------------------------------------------------------------
>>Unidata WWW Service http://my.unidata.ucar.edu/content/support
>>----------------------------------------------------------------------------
>>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.
>>
>>
>
>--
>Tom Green
>Graduate Research Assistant
>Department of Marine, Earth, and Atmospheric Sciences
>North Carolina State University
>Raleigh, NC
>Work phone: 515-1447
>E-mail: address@hidden
>
>
>--------------050406060602020004040002
>Content-Type: text/html; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
><html>
><head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> <title></title>
></head>
><body bgcolor="#ffffff" text="#000000">
>Steve,<br>
><br>
>I'm not sure why my scripts didn't come through. I've inserted the
>text of both the script and the output I receive when running the
>script in this message - I thought the web form had taken care of
>downloading the scripts.<br>
><br>
>I had originally listed no value for gpack, leaving it blank as a
>default. After receiving your e-mail, I changed it to GPACK = 32.
>Attempting that gave me two segmentation faults and a GEMPAK file
>equaling half a gigabyte. Also, in regards to the grid that I am
>using, I originally used gdcfil to create the blank GEMPAK file which I
>am using. If it's of any help to know, regardless of the name, all of
>my files contain RUC-40 data.<br>
><br>
>Thanks again for your help.<br>
><br>
>Tom<br>
><br>
><br>
><br>
>THE (original) SCRIPT I RAN:<br>
>#! /bin/csh<br>
>source /meas/home/tom/.cshrc_Linux<br>
><br>
>#cp blank.gem gscript.gem<br>
><br>
>foreach date ( 020302 030301 )<br>
>#foreach hh ( 00 03 06 09 12 15 18 21 )<br>
>foreach hh ( 00 )<br>
>set gfile = '/nfs/watauga2/tom/ruc_final/20'$date'_small40.gem'<br>
>set gfile2 = '/nfs/watauga2/tom/mikecode/script.gem'<br>
>set gtime = $date'/'$hh'00F000'<br>
><br>
>gddiag << endinput<br>
>grdarea = 28;-105;45;-72<br>
>grdarea = rdu-<br>
>gdfile = $gfile<br>
>gdoutf = $gfile2<br>
>gfunc = avor(obs)<br>
>gdattim = $gtime<br>
>glevel = 850<br>
>gvcord = pres<br>
>grdnam = vort<br>
>gpack = <br>
>r<br>
><br>
>glevel = 500<br>
>r<br>
><br>
>gfu=adv(tmpk,wnd)<br>
>grdnam=tadv<br>
>r<br>
><br>
>gfu=div(wnd)<br>
>gle=1000<br>
>grdnam=divwnd<br>
>r<br>
><br>
>exit<br>
>endinput<br>
><br>
>#end hour loop<br>
>end<br>
><br>
>#end date loop<br>
>end<br>
><br>
><br>
>THE OUTPUT FROM THE (original) SCRIPT:<br>
>DFILE Grid file &nb
> sp; &n
> bsp;
>/nfs/watauga2/tom/ruc_final/20030301_small40.gem<br>
> GDOUTF Output grid file &
> nbsp;
>/nfs/watauga2/tom/mikecode/gscript.gem<br>
> GFUNC Scalar grid &
> nbsp;
> div(wnd)<br>
> GDATTIM Grid date/time &n
> bsp;
> 030301/0000F000<br>
> GLEVEL Grid level &
> nbsp;
> 1000<br>
> GVCORD Grid vertical coordinate  
> ; pres<br>
> GRDNAM Grid parameter name &nbs
> p; divwnd<br>
> GPACK Packing type/number of bits &nb
> sp; <br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>020302/0000F000 &nb
> sp; 850&nbs
> p; PRES VORT  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>020302/0000F000 &nb
> sp; 500&nbs
> p; PRES VORT  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>020302/0000F000 &nb
> sp; 500&nbs
> p; PRES TADV  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><
> br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>020302/0000F000 &nb
> sp; 1000 &nb
> sp; PRES DIVWND &n
> bsp; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<br>
> GPACK.<br>
> GEMPAK-GDDIAG> GDFILE Grid file &n
> bsp; &
> nbsp;
>/nfs/watauga2/tom/ruc_final/20020302_small40.gem<br>
> GDOUTF Output grid file &
> nbsp;
>/nfs/watauga2/tom/mikecode/gscript.gem<br>
> GFUNC Scalar grid &
> nbsp;
> div(wnd)<br>
> GDATTIM Grid date/time &n
> bsp;
> 020302/0000F000<br>
> GLEVEL Grid level &
> nbsp;
> 1000<br>
> GVCORD Grid vertical coordinate  
> ; pres<br>
> GRDNAM Grid parameter name &nbs
> p; divwnd<br>
> GPACK Packing type/number of bits &nb
> sp; <br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG>
>GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>030301/0000F000 &nb
> sp; 850&nbs
> p; PRES VORT  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Warning: range too big 1.69069247E+20 1.26782856E+20 -4.2286
> 3904E+19<br>
> 214748367 16<br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>030301/0000F000 &nb
> sp; 500&nbs
> p; PRES VORT  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Warning: range too big 1.69069247E+20 1.26782856E+20 -4.2286
> 3904E+19<br>
> 214748367 16<br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>030301/0000F000 &nb
> sp; 500&nbs
> p; PRES TADV  
> ; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Warning: range too big INF INF -3.05245639E+30 214748367 16<
> br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG> GEMPAK-GDDIAG><
> br>
><br>
> TIME1
> TIME2 LEVL
> 1 LEVL2 VCORD PARM<br>
>030301/0000F000 &nb
> sp; 1000 &nb
> sp; PRES DIVWND &n
> bsp; <br>
>Enter a new grid parameter name, <cr> to accept or type EXIT:
>Warning: range too big 1.69073152E+20 4.22852601E+19 -1.2678
> 7888E+20<br>
> 214748367 16<br>
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,<
> br>
> GPACK.<br>
> GEMPAK-GDDIAG><br>
><br>
><br>
>Unidata Support wrote:
><blockquote cite="address@hidden"
> type="cite">
> <pre wrap="">Tom,
>
>Your message didn't show your script, but you should check your
>use of GPACK where you will have to specify the range by the number of
>bits used to pack the data, or no packing. If you are using GRIB packing then
>the default number of bits will be 16, but if that isn't enough for your data
> range
>you can increase that up to 32 bits. See phelp GPACK. If in doubt, try
>NONE for the packing.
>
>Also, the current release of GEMPAK 5.8.2 has the capability to create the gri
> d file
>if it doesn't exist, as well as reproject to a new grid. The old version that
> you are
>running does not have those features.
>
>Steve Chiswell
>Unidata User Support
>
>
>
> </pre>
> <blockquote type="cite">
> <pre wrap="">From: "Tom Green" <a class="moz-txt-link-rfc2396E" href="mail
> to:address@hidden"><address@hidden></a>
>Organization: UCAR/Unidata
>Keywords: 200506071432.j57EWxjF015731
> </pre>
> </blockquote>
> <pre wrap=""><!---->
> </pre>
> <blockquote type="cite">
> <pre wrap="">Institution: North Carolina State University
>Package Version: 5.7.2p2
>Operating System: Linux
>Hardware Information: unsure-N/A
>Inquiry: Hello,
>
>I\'m currently trying to create grids for temperature advection, vorticity, et
>c. as shown in the script to be used by a Fortran program. I believe that so
>me, but not all, of the data files that I am using have bad data at some poin
>ts in the grid, because when using GDDIAG on the second time listed in the sc
>ript, I get the \"Warning: Range Too High\" message when GDDIAG is creating t
>he grids. The temperature advection, vorticity, etc. fields do NOT exist in
>the original file - I am asking GDDIAG to create them and put them in the out
>put file.
>
>If I use GDCNTR to plot these grids in the original files and use a small gare
>a (ex. RDU), there is no problem with the plots. Likewise, GARP is also able
> to display the quantites when using the original files. In my script, I att
>empted to have GDDIAG only compute these quantites for a smaller geographical
> area, but that didn\'t seem to work either.
>
>If I have bad data along the sides of the grid, is there any way for me to cre
>ate these new grids that I want? I want GEMPAK to create these grids rather
>than attempt to do it in Fortran because of map factor issues, but I also don
>\'t need the values of the entire grid - the garea \"RDU-\" is sufficient for
> what I need. Any help you can provide would be greatly appreciated!
>
>Tom
>
>
>
> </pre>
> </blockquote>
> <pre wrap=""><!---->--
>**************************************************************************** &
> lt;
>Unidata User Support UCAR Unidata Program &
> lt;
>(303)497-8643 P.O. Box 3000 &
> lt;
><a class="moz-txt-link-abbreviated" href="mailto:address@hidden";>sup
> address@hidden</a> Boulder, CO 80307
> <
>---------------------------------------------------------------------------- &
> lt;
>Unidata WWW Service <a class="moz-txt-link-freetext" href="http:/
> /my.unidata.ucar.edu/content/support">http://my.unidata.ucar.edu/content/supp
> ort</a> <
>---------------------------------------------------------------------------- &
> lt;
>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.
> </pre>
></blockquote>
><br>
><pre class="moz-signature" cols="72">--
>Tom Green
>Graduate Research Assistant
>Department of Marine, Earth, and Atmospheric Sciences
>North Carolina State University
>Raleigh, NC
>Work phone: 515-1447
>E-mail: <a class="moz-txt-link-abbreviated" href="mailto:address@hidden
> u">address@hidden</a>
></pre>
></body>
></html>
>
>--------------050406060602020004040002--
>
--
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.