[Met_help] [rt.rap.ucar.edu #63572] History for MET Question

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Hello, I am writing to inquire about a problem with ascii2nc.  I have attached two files with this email, one is a text file with correctly coded upper air data (soundings).  The second is the obs.nc file that was produced by ascii2nc for this file. 

As you can see, in the text file, there are several different latitude/longitudes that are given.  However, I noticed that after I ran my point-stat program, the values were written to the corresponding point-stat file all under the same latitude and longitude signature.  For example, I did an evaluation for temperature in the 1000-950mb layer, and all of the correct values were input, but the latitude/longitudes were not correct (the latitude and longitude that were written for all values was simply the first lat/lon of the file).   I traced this problem back to a conversion between my text file and the netcdf file during "ascii2nc".  It appears that the ncdf file only contains one lat/lon pair. 

I was wondering why this is, if this is a problem in MET, or if I am perhaps overlooking something. 

Thanks in advance

- Andrew


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Re: [rt.rap.ucar.edu #63572] MET Question
From: John Halley Gotway
Time: Thu Oct 24 14:44:39 2013

Andrew,

Good catch and thanks for letting us know about it!  This is in fact a
bug in ascii2nc that was introduced in METv4.1.  I've fixed the
problem and posted a bugfix for it here:
   http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php

You can read about the issue posted today (10/24/2013).

Please try updating your build of METv4.1 and make sure that the
problem is resolved.

Thanks,
John Halley Gotway
met_help at ucar.edu

On 10/24/2013 08:37 AM, Andrew J. via RT wrote:
>
> Thu Oct 24 08:37:21 2013: Request 63572 was acted upon.
> Transaction: Ticket created by andrewwx at yahoo.com
>         Queue: met_help
>       Subject: MET Question
>         Owner: Nobody
>    Requestors: andrewwx at yahoo.com
>        Status: new
>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=63572 >
>
>
> Hello, I am writing to inquire about a problem with ascii2nc.  I
have attached two files with this email, one is a text file with
correctly coded upper air data (soundings).  The second is the obs.nc
file that was produced by ascii2nc for this file.
>
> As you can see, in the text file, there are several different
latitude/longitudes that are given.  However, I noticed that after I
ran my point-stat program, the values were written to the
corresponding point-stat file all under the same latitude and
longitude signature.  For example, I did an evaluation for temperature
in the 1000-950mb layer, and all of the correct values were input, but
the latitude/longitudes were not correct (the latitude and longitude
that were written for all values was simply the first lat/lon of the
file).   I traced this problem back to a conversion between my text
file and the netcdf file during "ascii2nc".  It appears that the ncdf
file only contains one lat/lon pair.
>
> I was wondering why this is, if this is a problem in MET, or if I am
perhaps overlooking something.
>
> Thanks in advance
>
> - Andrew
>

------------------------------------------------