[Met_help] [rt.rap.ucar.edu #59352] History for Test of ASCII2NC with little_r input
John Halley Gotway via RT
met_help at ucar.edu
Mon Feb 4 09:03:59 MST 2013
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I conducted a test of the alpha version of ASCII2NC to see if I could convert a little_r file containing MADIS observations to netcdf format for Point-Stat. The dialog below doesn't show any errors or warnings and an output file was created, but I can't tell if the file is really as it should be for Point-Stat to read. I tried using the ncdump command to view the .nc file, but it produces only some header information. I don't see the observation data as I'm able to do when I look at the output of ASCII2NC after it processes normal MADIS text files. See attached "test" file with the ncdump output. The screen dialog is as follows:
$ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000 qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG 1: Reading little_r ASCII Observation file: qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
DEBUG 1: Creating NetCDF Observation file: qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
DEBUG 2: Processing 5735 Little_r reports.
NetCDF: Start+count exceeds dimension bound
Do I have to do anything to the little_r file before I input it to ASCII2NC? I don't believe that the data contained in the little_r file are in the ASCII point observation format. Could this be a problem?
Thanks.
R/
John
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input
From: John Halley Gotway
Time: Tue Nov 20 10:06:24 2012
John,
The following line in the output you sent indicates that an error
occurred in the creation of the NetCDF file:
NetCDF: Start+count exceeds dimension bound
Are you able to send me the input little_r file you're using for
testing purposes?
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
That'd probably be the quickest way to debug.
Thanks,
John
On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>
> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: Test of ASCII2NC with little_r input
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
>
> I conducted a test of the alpha version of ASCII2NC to see if I
could convert a little_r file containing MADIS observations to netcdf
format for Point-Stat. The dialog below doesn't show any errors or
warnings and an output file was created, but I can't tell if the file
is really as it should be for Point-Stat to read. I tried using the
ncdump command to view the .nc file, but it produces only some header
information. I don't see the observation data as I'm able to do when I
look at the output of ASCII2NC after it processes normal MADIS text
files. See attached "test" file with the ncdump output. The screen
dialog is as follows:
>
> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
> DEBUG 1: Reading little_r ASCII Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> DEBUG 1: Creating NetCDF Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 2: Processing 5735 Little_r reports.
> NetCDF: Start+count exceeds dimension bound
>
>
> Do I have to do anything to the little_r file before I input it to
ASCII2NC? I don't believe that the data contained in the little_r file
are in the ASCII point observation format. Could this be a problem?
>
> Thanks.
>
> R/
> John
>
>
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Tue Nov 20 11:47:01 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
Thanks. I've attached the file.
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, November 20, 2012 10:06 AM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
John,
The following line in the output you sent indicates that an error
occurred in
the creation of the NetCDF file:
NetCDF: Start+count exceeds dimension bound
Are you able to send me the input little_r file you're using for
testing
purposes?
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
That'd probably be the quickest way to debug.
Thanks,
John
On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>
> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: Test of ASCII2NC with little_r input
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
> >
>
>
> I conducted a test of the alpha version of ASCII2NC to see if I
could
> convert a little_r file containing MADIS observations to netcdf
format for
> Point-Stat. The dialog below doesn't show any errors or warnings and
an
> output file was created, but I can't tell if the file is really as
it should
> be for Point-Stat to read. I tried using the ncdump command to view
the .nc
> file, but it produces only some header information. I don't see the
> observation data as I'm able to do when I look at the output of
ASCII2NC
> after it processes normal MADIS text files. See attached "test" file
with
> the ncdump output. The screen dialog is as follows:
>
> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
> 1: Reading little_r ASCII Observation file:
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> DEBUG 1: Creating NetCDF Observation file:
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 2: Processing 5735 Little_r reports.
> NetCDF: Start+count exceeds dimension bound
>
>
> Do I have to do anything to the little_r file before I input it to
ASCII2NC?
> I don't believe that the data contained in the little_r file are in
the
> ASCII point observation format. Could this be a problem?
>
> Thanks.
>
> R/
> John
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: John Halley Gotway
Time: Tue Nov 20 12:37:51 2012
John,
I was able to run your data through the latest development version of
ascii2nc with no real problems. I did get a bunch of warnings like
the following:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 13088.
A little_r report consists of one header line, one or more data lines,
and an end of report line. The header line is supposed to list the
number of data lines to follow. The ASCII2NC tool reads all
of the data lines that are present and prints a warning if the number
found doesn't match the number from the header line. That's the
source of this warning message.
I've attached to this message the output of my run with your data, as
well as the latest version of the ascii2nc.cc file. You could try
recompiling with this and running again.
Just let me know if more issues arise.
John
On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks. I've attached the file.
>
> R/
>
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 10:06 AM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
>
> John,
>
> The following line in the output you sent indicates that an error
occurred in
> the creation of the NetCDF file:
> NetCDF: Start+count exceeds dimension bound
>
> Are you able to send me the input little_r file you're using for
testing
> purposes?
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>
> That'd probably be the quickest way to debug.
>
> Thanks,
> John
>
> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>
>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: Test of ASCII2NC with little_r input
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>
>>
>>
>> I conducted a test of the alpha version of ASCII2NC to see if I
could
>> convert a little_r file containing MADIS observations to netcdf
format for
>> Point-Stat. The dialog below doesn't show any errors or warnings
and an
>> output file was created, but I can't tell if the file is really as
it should
>> be for Point-Stat to read. I tried using the ncdump command to view
the .nc
>> file, but it produces only some header information. I don't see the
>> observation data as I'm able to do when I look at the output of
ASCII2NC
>> after it processes normal MADIS text files. See attached "test"
file with
>> the ncdump output. The screen dialog is as follows:
>>
>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
>> 1: Reading little_r ASCII Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> DEBUG 1: Creating NetCDF Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 2: Processing 5735 Little_r reports.
>> NetCDF: Start+count exceeds dimension bound
>>
>>
>> Do I have to do anything to the little_r file before I input it to
ASCII2NC?
>> I don't believe that the data contained in the little_r file are in
the
>> ASCII point observation format. Could this be a problem?
>>
>> Thanks.
>>
>> R/
>> John
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: John Halley Gotway
Time: Tue Nov 20 12:37:51 2012
DEBUG 1: Reading little_r ASCII Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
DEBUG 1: Creating NetCDF Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
DEBUG 2: Processing 5735 Little_r reports.
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 2836.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 5233.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (27) on
line number 7579.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 7888.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (42) does not match the number found in the data (64) on
line number 10911.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 10960.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (39)
on line number 11090.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (21)
on line number 11114.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (26)
on line number 11143.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (22)
on line number 11168.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (14)
on line number 11185.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (25)
on line number 11213.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (12)
on line number 11228.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (16)
on line number 11247.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (13)
on line number 11263.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (13)
on line number 11279.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (202) does not match the number found in the data (7) on
line number 11289.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 12090.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 12095.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 13088.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (3) on
line number 16358.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 18319.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 23180.
WARNING:
WARNING:
WARNING: process_little_r_obs() -> the number of data lines specified
in the header (1) does not match the number found in the data (2) on
line number 23193.
WARNING:
DEBUG 2: Finished processing 31008 observations from 5735 Little_r
reports.
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Tue Nov 20 12:59:15 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
Thanks for your help. So, from what you found, I was running ASCII2NC
correctly, just needed the more recent version of the tool. I will get
this
update to our sysadm for a recompile and then give it try.
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, November 20, 2012 12:38 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
(UNCLASSIFIED)
John,
I was able to run your data through the latest development version of
ascii2nc
with no real problems. I did get a bunch of warnings like the
following:
WARNING: process_little_r_obs() -> the number of data lines specified
in the
header (1) does not match the number found in the data (2) on line
number
13088.
A little_r report consists of one header line, one or more data lines,
and an
end of report line. The header line is supposed to list the number of
data
lines to follow. The ASCII2NC tool reads all of the data lines that
are
present and prints a warning if the number found doesn't match the
number from
the header line. That's the source of this warning message.
I've attached to this message the output of my run with your data, as
well as
the latest version of the ascii2nc.cc file. You could try recompiling
with
this and running again.
Just let me know if more issues arise.
John
On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks. I've attached the file.
>
> R/
>
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 10:06 AM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
> Robert E Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
> input
>
> John,
>
> The following line in the output you sent indicates that an error
> occurred in the creation of the NetCDF file:
> NetCDF: Start+count exceeds dimension bound
>
> Are you able to send me the input little_r file you're using for
> testing purposes?
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>
> That'd probably be the quickest way to debug.
>
> Thanks,
> John
>
> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>
>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: Test of ASCII2NC with little_r input
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>
>>
>>
>> I conducted a test of the alpha version of ASCII2NC to see if I
could
>> convert a little_r file containing MADIS observations to netcdf
>> format for Point-Stat. The dialog below doesn't show any errors or
>> warnings and an output file was created, but I can't tell if the
file
>> is really as it should be for Point-Stat to read. I tried using the
>> ncdump command to view the .nc file, but it produces only some
header
>> information. I don't see the observation data as I'm able to do
when
>> I look at the output of ASCII2NC after it processes normal MADIS
text
>> files. See attached "test" file with the ncdump output. The screen
dialog
>> is as follows:
>>
>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
>> 1: Reading little_r ASCII Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> DEBUG 1: Creating NetCDF Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 2: Processing 5735 Little_r reports.
>> NetCDF: Start+count exceeds dimension bound
>>
>>
>> Do I have to do anything to the little_r file before I input it to
>> ASCII2NC?
>> I don't believe that the data contained in the little_r file are in
>> the ASCII point observation format. Could this be a problem?
>>
>> Thanks.
>>
>> R/
>> John
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Tue Nov 20 15:41:43 2012
John,
Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
It's possible that I was too hasty though - to be more thorough, I
could
have checked that plugging in the latest version of ASCII2NC into the
version of MET you're running would compile well. Is it METv4.0 that
you're using?
If you have compilation problems, let me know.
Thanks,
John
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks for your help. So, from what you found, I was running
ASCII2NC
> correctly, just needed the more recent version of the tool. I will
get
> this
> update to our sysadm for a recompile and then give it try.
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 12:38 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E
> Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> I was able to run your data through the latest development version
of
> ascii2nc
> with no real problems. I did get a bunch of warnings like the
following:
>
> WARNING: process_little_r_obs() -> the number of data lines
specified in
> the
> header (1) does not match the number found in the data (2) on line
number
> 13088.
>
> A little_r report consists of one header line, one or more data
lines, and
> an
> end of report line. The header line is supposed to list the number
of
> data
> lines to follow. The ASCII2NC tool reads all of the data lines that
are
> present and prints a warning if the number found doesn't match the
number
> from
> the header line. That's the source of this warning message.
>
> I've attached to this message the output of my run with your data,
as well
> as
> the latest version of the ascii2nc.cc file. You could try
recompiling
> with
> this and running again.
>
> Just let me know if more issues arise.
>
> John
>
> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks. I've attached the file.
>>
>> R/
>>
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 10:06 AM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input
>>
>> John,
>>
>> The following line in the output you sent indicates that an error
>> occurred in the creation of the NetCDF file:
>> NetCDF: Start+count exceeds dimension bound
>>
>> Are you able to send me the input little_r file you're using for
>> testing purposes?
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>
>> That'd probably be the quickest way to debug.
>>
>> Thanks,
>> John
>>
>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>
>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>> Queue: met_help
>>> Subject: Test of ASCII2NC with little_r input
>>> Owner: Nobody
>>> Requestors: john.w.raby2.civ at mail.mil
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>
>>>
>>>
>>> I conducted a test of the alpha version of ASCII2NC to see if I
could
>>> convert a little_r file containing MADIS observations to netcdf
>>> format for Point-Stat. The dialog below doesn't show any errors or
>>> warnings and an output file was created, but I can't tell if the
file
>>> is really as it should be for Point-Stat to read. I tried using
the
>>> ncdump command to view the .nc file, but it produces only some
header
>>> information. I don't see the observation data as I'm able to do
when
>>> I look at the output of ASCII2NC after it processes normal MADIS
text
>>> files. See attached "test" file with the ncdump output. The screen
>>> dialog
>>> is as follows:
>>>
>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
>>> 1: Reading little_r ASCII Observation file:
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>> DEBUG 1: Creating NetCDF Observation file:
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>> DEBUG 2: Processing 5735 Little_r reports.
>>> NetCDF: Start+count exceeds dimension bound
>>>
>>>
>>> Do I have to do anything to the little_r file before I input it to
>>> ASCII2NC?
>>> I don't believe that the data contained in the little_r file are
in
>>> the ASCII point observation format. Could this be a problem?
>>>
>>> Thanks.
>>>
>>> R/
>>> John
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Tue Nov 20 15:54:17 2012
John -
I was off the net for a while, sorry for the delay. Yes we are using
the patched version of V4.0.
R/
John
________________________________________
From: John Halley Gotway via RT [met_help at ucar.edu]
Sent: Tuesday, November 20, 2012 3:41 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
John,
Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
It's possible that I was too hasty though - to be more thorough, I
could
have checked that plugging in the latest version of ASCII2NC into the
version of MET you're running would compile well. Is it METv4.0 that
you're using?
If you have compilation problems, let me know.
Thanks,
John
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks for your help. So, from what you found, I was running
ASCII2NC
> correctly, just needed the more recent version of the tool. I will
get
> this
> update to our sysadm for a recompile and then give it try.
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 12:38 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E
> Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> I was able to run your data through the latest development version
of
> ascii2nc
> with no real problems. I did get a bunch of warnings like the
following:
>
> WARNING: process_little_r_obs() -> the number of data lines
specified in
> the
> header (1) does not match the number found in the data (2) on line
number
> 13088.
>
> A little_r report consists of one header line, one or more data
lines, and
> an
> end of report line. The header line is supposed to list the number
of
> data
> lines to follow. The ASCII2NC tool reads all of the data lines that
are
> present and prints a warning if the number found doesn't match the
number
> from
> the header line. That's the source of this warning message.
>
> I've attached to this message the output of my run with your data,
as well
> as
> the latest version of the ascii2nc.cc file. You could try
recompiling
> with
> this and running again.
>
> Just let me know if more issues arise.
>
> John
>
> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks. I've attached the file.
>>
>> R/
>>
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 10:06 AM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input
>>
>> John,
>>
>> The following line in the output you sent indicates that an error
>> occurred in the creation of the NetCDF file:
>> NetCDF: Start+count exceeds dimension bound
>>
>> Are you able to send me the input little_r file you're using for
>> testing purposes?
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>
>> That'd probably be the quickest way to debug.
>>
>> Thanks,
>> John
>>
>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>
>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>> Queue: met_help
>>> Subject: Test of ASCII2NC with little_r input
>>> Owner: Nobody
>>> Requestors: john.w.raby2.civ at mail.mil
>>> Status: new
>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>
>>>
>>>
>>> I conducted a test of the alpha version of ASCII2NC to see if I
could
>>> convert a little_r file containing MADIS observations to netcdf
>>> format for Point-Stat. The dialog below doesn't show any errors or
>>> warnings and an output file was created, but I can't tell if the
file
>>> is really as it should be for Point-Stat to read. I tried using
the
>>> ncdump command to view the .nc file, but it produces only some
header
>>> information. I don't see the observation data as I'm able to do
when
>>> I look at the output of ASCII2NC after it processes normal MADIS
text
>>> files. See attached "test" file with the ncdump output. The screen
>>> dialog
>>> is as follows:
>>>
>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
>>> 1: Reading little_r ASCII Observation file:
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>> DEBUG 1: Creating NetCDF Observation file:
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>> DEBUG 2: Processing 5735 Little_r reports.
>>> NetCDF: Start+count exceeds dimension bound
>>>
>>>
>>> Do I have to do anything to the little_r file before I input it to
>>> ASCII2NC?
>>> I don't believe that the data contained in the little_r file are
in
>>> the ASCII point observation format. Could this be a problem?
>>>
>>> Thanks.
>>>
>>> R/
>>> John
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Wed Nov 21 12:47:39 2012
John,
OK, I did the following:
(1) Untarred the METv4.0 release.
(2) Applied the latest set of METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
(3) Applied the set of little_r patches I sent you
(METv4.0_little_r_20120926.tar.gz).
(4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I just sent you.
I built MET and it compiled fine.
Then I ran ascii2nc with the little_r observation file you sent, and
it produced meaningful output with the same warnings I mentioned
previously.
So it should work fine.
Thanks,
John
On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> I was off the net for a while, sorry for the delay. Yes we are using
the patched version of V4.0.
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 3:41 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
>
> John,
>
> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
> It's possible that I was too hasty though - to be more thorough, I
could
> have checked that plugging in the latest version of ASCII2NC into
the
> version of MET you're running would compile well. Is it METv4.0
that
> you're using?
>
> If you have compilation problems, let me know.
>
> Thanks,
> John
>
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>> correctly, just needed the more recent version of the tool. I will
get
>> this
>> update to our sysadm for a recompile and then give it try.
>>
>> R/
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 12:38 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E
>> Jr
>> CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r input
>> (UNCLASSIFIED)
>>
>> John,
>>
>> I was able to run your data through the latest development version
of
>> ascii2nc
>> with no real problems. I did get a bunch of warnings like the
following:
>>
>> WARNING: process_little_r_obs() -> the number of data lines
specified in
>> the
>> header (1) does not match the number found in the data (2) on line
number
>> 13088.
>>
>> A little_r report consists of one header line, one or more data
lines, and
>> an
>> end of report line. The header line is supposed to list the number
of
>> data
>> lines to follow. The ASCII2NC tool reads all of the data lines
that are
>> present and prints a warning if the number found doesn't match the
number
>> from
>> the header line. That's the source of this warning message.
>>
>> I've attached to this message the output of my run with your data,
as well
>> as
>> the latest version of the ascii2nc.cc file. You could try
recompiling
>> with
>> this and running again.
>>
>> Just let me know if more issues arise.
>>
>> John
>>
>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks. I've attached the file.
>>>
>>> R/
>>>
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>>
>>> John,
>>>
>>> The following line in the output you sent indicates that an error
>>> occurred in the creation of the NetCDF file:
>>> NetCDF: Start+count exceeds dimension bound
>>>
>>> Are you able to send me the input little_r file you're using for
>>> testing purposes?
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>
>>> That'd probably be the quickest way to debug.
>>>
>>> Thanks,
>>> John
>>>
>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>> Queue: met_help
>>>> Subject: Test of ASCII2NC with little_r input
>>>> Owner: Nobody
>>>> Requestors: john.w.raby2.civ at mail.mil
>>>> Status: new
>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>
>>>>
>>>>
>>>> I conducted a test of the alpha version of ASCII2NC to see if I
could
>>>> convert a little_r file containing MADIS observations to netcdf
>>>> format for Point-Stat. The dialog below doesn't show any errors
or
>>>> warnings and an output file was created, but I can't tell if the
file
>>>> is really as it should be for Point-Stat to read. I tried using
the
>>>> ncdump command to view the .nc file, but it produces only some
header
>>>> information. I don't see the observation data as I'm able to do
when
>>>> I look at the output of ASCII2NC after it processes normal MADIS
text
>>>> files. See attached "test" file with the ncdump output. The
screen
>>>> dialog
>>>> is as follows:
>>>>
>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
DEBUG
>>>> 1: Reading little_r ASCII Observation file:
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>> DEBUG 1: Creating NetCDF Observation file:
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>> NetCDF: Start+count exceeds dimension bound
>>>>
>>>>
>>>> Do I have to do anything to the little_r file before I input it
to
>>>> ASCII2NC?
>>>> I don't believe that the data contained in the little_r file are
in
>>>> the ASCII point observation format. Could this be a problem?
>>>>
>>>> Thanks.
>>>>
>>>> R/
>>>> John
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>>
>
>
>
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Wed Nov 21 12:56:55 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
Thanks for setting it up so we integrate into our current patched
version of
V4.0. I have cc'd Bob Flanigan on this email so he can take note.
When ASCII2NC processes the little_r file does it produce the MET
specific
ASCII format ready for Point-Stat?
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, November 21, 2012 12:48 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
(UNCLASSIFIED)
John,
OK, I did the following:
(1) Untarred the METv4.0 release.
(2) Applied the latest set of METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
(3) Applied the set of little_r patches I sent you
(METv4.0_little_r_20120926.tar.gz).
(4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I
just sent you.
I built MET and it compiled fine.
Then I ran ascii2nc with the little_r observation file you sent, and
it
produced meaningful output with the same warnings I mentioned
previously.
So it should work fine.
Thanks,
John
On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> I was off the net for a while, sorry for the delay. Yes we are using
the
> patched version of V4.0.
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Tuesday, November 20, 2012 3:41 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
> Robert E Jr CIV (US)
> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
> input (UNCLASSIFIED)
>
> John,
>
> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
> It's possible that I was too hasty though - to be more thorough, I
> could have checked that plugging in the latest version of ASCII2NC
> into the version of MET you're running would compile well. Is it
> METv4.0 that you're using?
>
> If you have compilation problems, let me know.
>
> Thanks,
> John
>
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>> correctly, just needed the more recent version of the tool. I will
>> get this update to our sysadm for a recompile and then give it try.
>>
>> R/
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 12:38 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input
>> (UNCLASSIFIED)
>>
>> John,
>>
>> I was able to run your data through the latest development version
of
>> ascii2nc with no real problems. I did get a bunch of warnings like
>> the following:
>>
>> WARNING: process_little_r_obs() -> the number of data lines
specified
>> in the header (1) does not match the number found in the data (2)
on
>> line number 13088.
>>
>> A little_r report consists of one header line, one or more data
>> lines, and an end of report line. The header line is supposed to
>> list the number of data lines to follow. The ASCII2NC tool reads
all
>> of the data lines that are present and prints a warning if the
number
>> found doesn't match the number from the header line. That's the
>> source of this warning message.
>>
>> I've attached to this message the output of my run with your data,
as
>> well as the latest version of the ascii2nc.cc file. You could try
>> recompiling with this and running again.
>>
>> Just let me know if more issues arise.
>>
>> John
>>
>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks. I've attached the file.
>>>
>>> R/
>>>
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>>
>>> John,
>>>
>>> The following line in the output you sent indicates that an error
>>> occurred in the creation of the NetCDF file:
>>> NetCDF: Start+count exceeds dimension bound
>>>
>>> Are you able to send me the input little_r file you're using for
>>> testing purposes?
>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>
>>> That'd probably be the quickest way to debug.
>>>
>>> Thanks,
>>> John
>>>
>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>> Queue: met_help
>>>> Subject: Test of ASCII2NC with little_r input
>>>> Owner: Nobody
>>>> Requestors: john.w.raby2.civ at mail.mil
>>>> Status: new
>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>
>>>>
>>>>
>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>> could convert a little_r file containing MADIS observations to
>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>> errors or warnings and an output file was created, but I can't
tell
>>>> if the file is really as it should be for Point-Stat to read. I
>>>> tried using the ncdump command to view the .nc file, but it
>>>> produces only some header information. I don't see the
observation
>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>> it processes normal MADIS text files. See attached "test" file
with
>>>> the ncdump output. The screen dialog is as follows:
>>>>
>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>> DEBUG
>>>> 1: Reading little_r ASCII Observation file:
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>> DEBUG 1: Creating NetCDF Observation file:
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>> NetCDF: Start+count exceeds dimension bound
>>>>
>>>>
>>>> Do I have to do anything to the little_r file before I input it
to
>>>> ASCII2NC?
>>>> I don't believe that the data contained in the little_r file are
in
>>>> the ASCII point observation format. Could this be a problem?
>>>>
>>>> Thanks.
>>>>
>>>> R/
>>>> John
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>>
>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Wed Nov 21 14:03:37 2012
Yes, that's correct. It does.
John
On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks for setting it up so we integrate into our current patched
version of
> V4.0. I have cc'd Bob Flanigan on this email so he can take note.
>
> When ASCII2NC processes the little_r file does it produce the MET
specific
> ASCII format ready for Point-Stat?
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 12:48 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> OK, I did the following:
>
> (1) Untarred the METv4.0 release.
> (2) Applied the latest set of METv4.0 patches:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> (3) Applied the set of little_r patches I sent you
> (METv4.0_little_r_20120926.tar.gz).
> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I
> just sent you.
>
> I built MET and it compiled fine.
>
> Then I ran ascii2nc with the little_r observation file you sent, and
it
> produced meaningful output with the same warnings I mentioned
previously.
>
> So it should work fine.
>
> Thanks,
> John
>
> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> John -
>>
>> I was off the net for a while, sorry for the delay. Yes we are
using the
>> patched version of V4.0.
>> R/
>> John
>>
>> ________________________________________
>> From: John Halley Gotway via RT [met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 3:41 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input (UNCLASSIFIED)
>>
>> John,
>>
>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>> It's possible that I was too hasty though - to be more thorough,
I
>> could have checked that plugging in the latest version of ASCII2NC
>> into the version of MET you're running would compile well. Is it
>> METv4.0 that you're using?
>>
>> If you have compilation problems, let me know.
>>
>> Thanks,
>> John
>>
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>>> correctly, just needed the more recent version of the tool. I will
>>> get this update to our sysadm for a recompile and then give it
try.
>>>
>>> R/
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>> (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> I was able to run your data through the latest development version
of
>>> ascii2nc with no real problems. I did get a bunch of warnings
like
>>> the following:
>>>
>>> WARNING: process_little_r_obs() -> the number of data lines
specified
>>> in the header (1) does not match the number found in the data (2)
on
>>> line number 13088.
>>>
>>> A little_r report consists of one header line, one or more data
>>> lines, and an end of report line. The header line is supposed to
>>> list the number of data lines to follow. The ASCII2NC tool reads
all
>>> of the data lines that are present and prints a warning if the
number
>>> found doesn't match the number from the header line. That's the
>>> source of this warning message.
>>>
>>> I've attached to this message the output of my run with your data,
as
>>> well as the latest version of the ascii2nc.cc file. You could try
>>> recompiling with this and running again.
>>>
>>> Just let me know if more issues arise.
>>>
>>> John
>>>
>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks. I've attached the file.
>>>>
>>>> R/
>>>>
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input
>>>>
>>>> John,
>>>>
>>>> The following line in the output you sent indicates that an error
>>>> occurred in the creation of the NetCDF file:
>>>> NetCDF: Start+count exceeds dimension bound
>>>>
>>>> Are you able to send me the input little_r file you're using for
>>>> testing purposes?
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>
>>>> That'd probably be the quickest way to debug.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>> Queue: met_help
>>>>> Subject: Test of ASCII2NC with little_r input
>>>>> Owner: Nobody
>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>> Status: new
>>>>> Ticket <URL:
>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>
>>>>>
>>>>>
>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>> could convert a little_r file containing MADIS observations to
>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>> errors or warnings and an output file was created, but I can't
tell
>>>>> if the file is really as it should be for Point-Stat to read. I
>>>>> tried using the ncdump command to view the .nc file, but it
>>>>> produces only some header information. I don't see the
observation
>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>> it processes normal MADIS text files. See attached "test" file
with
>>>>> the ncdump output. The screen dialog is as follows:
>>>>>
>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>> DEBUG
>>>>> 1: Reading little_r ASCII Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>>
>>>>> Do I have to do anything to the little_r file before I input it
to
>>>>> ASCII2NC?
>>>>> I don't believe that the data contained in the little_r file are
in
>>>>> the ASCII point observation format. Could this be a problem?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> R/
>>>>> John
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Wed Nov 21 14:29:33 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
FYI, Bob Flanigan is our sysadm and now also our IASO and will get
necessary
approvals (if any) to implement the new ascii2nc.cc and then do the
MET build.
I'm not sure but he may not get to this until next week.
I will update you when this happens and I test it.
Have a Happy Thanksgiving!
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, November 21, 2012 2:04 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
(UNCLASSIFIED)
Yes, that's correct. It does.
John
On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks for setting it up so we integrate into our current patched
> version of V4.0. I have cc'd Bob Flanigan on this email so he can
take note.
>
> When ASCII2NC processes the little_r file does it produce the MET
> specific ASCII format ready for Point-Stat?
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 12:48 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
> Robert E Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
> input
> (UNCLASSIFIED)
>
> John,
>
> OK, I did the following:
>
> (1) Untarred the METv4.0 release.
> (2) Applied the latest set of METv4.0 patches:
>
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.p
> hp
> (3) Applied the set of little_r patches I sent you
> (METv4.0_little_r_20120926.tar.gz).
> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
> version I just sent you.
>
> I built MET and it compiled fine.
>
> Then I ran ascii2nc with the little_r observation file you sent, and
> it produced meaningful output with the same warnings I mentioned
previously.
>
> So it should work fine.
>
> Thanks,
> John
>
> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> John -
>>
>> I was off the net for a while, sorry for the delay. Yes we are
using
>> the patched version of V4.0.
>> R/
>> John
>>
>> ________________________________________
>> From: John Halley Gotway via RT [met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 3:41 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input (UNCLASSIFIED)
>>
>> John,
>>
>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>> It's possible that I was too hasty though - to be more thorough,
I
>> could have checked that plugging in the latest version of ASCII2NC
>> into the version of MET you're running would compile well. Is it
>> METv4.0 that you're using?
>>
>> If you have compilation problems, let me know.
>>
>> Thanks,
>> John
>>
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks for your help. So, from what you found, I was running
>>> ASCII2NC correctly, just needed the more recent version of the
tool.
>>> I will get this update to our sysadm for a recompile and then give
it try.
>>>
>>> R/
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>> (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> I was able to run your data through the latest development version
>>> of ascii2nc with no real problems. I did get a bunch of warnings
>>> like the following:
>>>
>>> WARNING: process_little_r_obs() -> the number of data lines
>>> specified in the header (1) does not match the number found in the
>>> data (2) on line number 13088.
>>>
>>> A little_r report consists of one header line, one or more data
>>> lines, and an end of report line. The header line is supposed to
>>> list the number of data lines to follow. The ASCII2NC tool reads
>>> all of the data lines that are present and prints a warning if the
>>> number found doesn't match the number from the header line.
That's
>>> the source of this warning message.
>>>
>>> I've attached to this message the output of my run with your data,
>>> as well as the latest version of the ascii2nc.cc file. You could
>>> try recompiling with this and running again.
>>>
>>> Just let me know if more issues arise.
>>>
>>> John
>>>
>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks. I've attached the file.
>>>>
>>>> R/
>>>>
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
>>>> little_r input
>>>>
>>>> John,
>>>>
>>>> The following line in the output you sent indicates that an error
>>>> occurred in the creation of the NetCDF file:
>>>> NetCDF: Start+count exceeds dimension bound
>>>>
>>>> Are you able to send me the input little_r file you're using for
>>>> testing purposes?
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>
>>>> That'd probably be the quickest way to debug.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>> Queue: met_help
>>>>> Subject: Test of ASCII2NC with little_r input
>>>>> Owner: Nobody
>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>> Status: new
>>>>> Ticket <URL:
>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>
>>>>>
>>>>>
>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>> could convert a little_r file containing MADIS observations to
>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>> errors or warnings and an output file was created, but I can't
>>>>> tell if the file is really as it should be for Point-Stat to
read.
>>>>> I tried using the ncdump command to view the .nc file, but it
>>>>> produces only some header information. I don't see the
observation
>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>> it processes normal MADIS text files. See attached "test" file
>>>>> with the ncdump output. The screen dialog is as follows:
>>>>>
>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>> DEBUG
>>>>> 1: Reading little_r ASCII Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>>
>>>>> Do I have to do anything to the little_r file before I input it
to
>>>>> ASCII2NC?
>>>>> I don't believe that the data contained in the little_r file are
>>>>> in the ASCII point observation format. Could this be a problem?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> R/
>>>>> John
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Mon Dec 03 09:32:32 2012
John -
Bob Flanigan recompiled MET V4.0 with all the patches from your email
and this morning I tested ascii2nc again, but no success.
See the dialog I received below and the text file output from ncdump.
I've also attached the output .nc file.
[jraby at carson ~/MET_obs/little_r]
$ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
DEBUG 1: Reading little_r ASCII Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
DEBUG 1: Creating NetCDF Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
DEBUG 2: Processing 5735 Little_r reports.
NetCDF: Start+count exceeds dimension bound
Bob recommended that we check the netcdf and compiler versions to see
if there might be a problem.
Our compiler type is gcc444 and the netcdf version is cdf413.
Do you have any thoughts on what might be the problem?
Thanks.
R/
John
________________________________________
From: John Halley Gotway via RT [met_help at ucar.edu]
Sent: Wednesday, November 21, 2012 2:03 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
Yes, that's correct. It does.
John
On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Thanks for setting it up so we integrate into our current patched
version of
> V4.0. I have cc'd Bob Flanigan on this email so he can take note.
>
> When ASCII2NC processes the little_r file does it produce the MET
specific
> ASCII format ready for Point-Stat?
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 12:48 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> OK, I did the following:
>
> (1) Untarred the METv4.0 release.
> (2) Applied the latest set of METv4.0 patches:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> (3) Applied the set of little_r patches I sent you
> (METv4.0_little_r_20120926.tar.gz).
> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I
> just sent you.
>
> I built MET and it compiled fine.
>
> Then I ran ascii2nc with the little_r observation file you sent, and
it
> produced meaningful output with the same warnings I mentioned
previously.
>
> So it should work fine.
>
> Thanks,
> John
>
> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> John -
>>
>> I was off the net for a while, sorry for the delay. Yes we are
using the
>> patched version of V4.0.
>> R/
>> John
>>
>> ________________________________________
>> From: John Halley Gotway via RT [met_help at ucar.edu]
>> Sent: Tuesday, November 20, 2012 3:41 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input (UNCLASSIFIED)
>>
>> John,
>>
>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>> It's possible that I was too hasty though - to be more thorough,
I
>> could have checked that plugging in the latest version of ASCII2NC
>> into the version of MET you're running would compile well. Is it
>> METv4.0 that you're using?
>>
>> If you have compilation problems, let me know.
>>
>> Thanks,
>> John
>>
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>>> correctly, just needed the more recent version of the tool. I will
>>> get this update to our sysadm for a recompile and then give it
try.
>>>
>>> R/
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>> (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> I was able to run your data through the latest development version
of
>>> ascii2nc with no real problems. I did get a bunch of warnings
like
>>> the following:
>>>
>>> WARNING: process_little_r_obs() -> the number of data lines
specified
>>> in the header (1) does not match the number found in the data (2)
on
>>> line number 13088.
>>>
>>> A little_r report consists of one header line, one or more data
>>> lines, and an end of report line. The header line is supposed to
>>> list the number of data lines to follow. The ASCII2NC tool reads
all
>>> of the data lines that are present and prints a warning if the
number
>>> found doesn't match the number from the header line. That's the
>>> source of this warning message.
>>>
>>> I've attached to this message the output of my run with your data,
as
>>> well as the latest version of the ascii2nc.cc file. You could try
>>> recompiling with this and running again.
>>>
>>> Just let me know if more issues arise.
>>>
>>> John
>>>
>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks. I've attached the file.
>>>>
>>>> R/
>>>>
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input
>>>>
>>>> John,
>>>>
>>>> The following line in the output you sent indicates that an error
>>>> occurred in the creation of the NetCDF file:
>>>> NetCDF: Start+count exceeds dimension bound
>>>>
>>>> Are you able to send me the input little_r file you're using for
>>>> testing purposes?
>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>
>>>> That'd probably be the quickest way to debug.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>> Queue: met_help
>>>>> Subject: Test of ASCII2NC with little_r input
>>>>> Owner: Nobody
>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>> Status: new
>>>>> Ticket <URL:
>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>
>>>>>
>>>>>
>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>> could convert a little_r file containing MADIS observations to
>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>> errors or warnings and an output file was created, but I can't
tell
>>>>> if the file is really as it should be for Point-Stat to read. I
>>>>> tried using the ncdump command to view the .nc file, but it
>>>>> produces only some header information. I don't see the
observation
>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>> it processes normal MADIS text files. See attached "test" file
with
>>>>> the ncdump output. The screen dialog is as follows:
>>>>>
>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>> DEBUG
>>>>> 1: Reading little_r ASCII Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>>
>>>>> Do I have to do anything to the little_r file before I input it
to
>>>>> ASCII2NC?
>>>>> I don't believe that the data contained in the little_r file are
in
>>>>> the ASCII point observation format. Could this be a problem?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> R/
>>>>> John
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Tue Dec 04 12:46:36 2012
John,
I was worried about something like this. It's dangerous when you try
to "patch" releases with enhancements - there are so many little
things that can go wrong. I suppose it's possible that there's a
problem with the version of NetCDF, but I would expect that to be a
problem at compile time rather than at run time.
Are you sure that Bob has followed the exact steps I described?
(1) Untarred the METv4.0 release.
(2) Applied the latest set of METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
(3) Applied the set of little_r patches I sent you:
METv4.0_little_r_20120926.tar.gz
(4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I just sent you.
When I followed those exact steps, I was able to compile MET fine and
run ascii2nc on the data you sent me without any problems.
Let me know how it goes. It'll be easier when we just get to the next
release, METv4.1, which will include all this functionality.
Thanks,
John
On 12/03/2012 09:32 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> Bob Flanigan recompiled MET V4.0 with all the patches from your
email and this morning I tested ascii2nc again, but no success.
>
> See the dialog I received below and the text file output from
ncdump. I've also attached the output .nc file.
>
> [jraby at carson ~/MET_obs/little_r]
> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 1: Reading little_r ASCII Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> DEBUG 1: Creating NetCDF Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 2: Processing 5735 Little_r reports.
> NetCDF: Start+count exceeds dimension bound
>
> Bob recommended that we check the netcdf and compiler versions to
see if there might be a problem.
>
> Our compiler type is gcc444 and the netcdf version is cdf413.
>
> Do you have any thoughts on what might be the problem?
>
> Thanks.
>
> R/
> John
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 2:03 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
>
> Yes, that's correct. It does.
>
> John
>
> On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks for setting it up so we integrate into our current patched
version of
>> V4.0. I have cc'd Bob Flanigan on this email so he can take note.
>>
>> When ASCII2NC processes the little_r file does it produce the MET
specific
>> ASCII format ready for Point-Stat?
>>
>> R/
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, November 21, 2012 12:48 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
>> CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r input
>> (UNCLASSIFIED)
>>
>> John,
>>
>> OK, I did the following:
>>
>> (1) Untarred the METv4.0 release.
>> (2) Applied the latest set of METv4.0 patches:
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>> (3) Applied the set of little_r patches I sent you
>> (METv4.0_little_r_20120926.tar.gz).
>> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I
>> just sent you.
>>
>> I built MET and it compiled fine.
>>
>> Then I ran ascii2nc with the little_r observation file you sent,
and it
>> produced meaningful output with the same warnings I mentioned
previously.
>>
>> So it should work fine.
>>
>> Thanks,
>> John
>>
>> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> John -
>>>
>>> I was off the net for a while, sorry for the delay. Yes we are
using the
>>> patched version of V4.0.
>>> R/
>>> John
>>>
>>> ________________________________________
>>> From: John Halley Gotway via RT [met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 3:41 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>>> It's possible that I was too hasty though - to be more
thorough, I
>>> could have checked that plugging in the latest version of ASCII2NC
>>> into the version of MET you're running would compile well. Is it
>>> METv4.0 that you're using?
>>>
>>> If you have compilation problems, let me know.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>>>> correctly, just needed the more recent version of the tool. I
will
>>>> get this update to our sysadm for a recompile and then give it
try.
>>>>
>>>> R/
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input
>>>> (UNCLASSIFIED)
>>>>
>>>> John,
>>>>
>>>> I was able to run your data through the latest development
version of
>>>> ascii2nc with no real problems. I did get a bunch of warnings
like
>>>> the following:
>>>>
>>>> WARNING: process_little_r_obs() -> the number of data lines
specified
>>>> in the header (1) does not match the number found in the data (2)
on
>>>> line number 13088.
>>>>
>>>> A little_r report consists of one header line, one or more data
>>>> lines, and an end of report line. The header line is supposed to
>>>> list the number of data lines to follow. The ASCII2NC tool reads
all
>>>> of the data lines that are present and prints a warning if the
number
>>>> found doesn't match the number from the header line. That's the
>>>> source of this warning message.
>>>>
>>>> I've attached to this message the output of my run with your
data, as
>>>> well as the latest version of the ascii2nc.cc file. You could
try
>>>> recompiling with this and running again.
>>>>
>>>> Just let me know if more issues arise.
>>>>
>>>> John
>>>>
>>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>> John -
>>>>>
>>>>> Thanks. I've attached the file.
>>>>>
>>>>> R/
>>>>>
>>>>> John
>>>>>
>>>>> -----Original Message-----
>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>>> To: Raby, John W CIV (US)
>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>>> Robert E Jr CIV (US)
>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>>> input
>>>>>
>>>>> John,
>>>>>
>>>>> The following line in the output you sent indicates that an
error
>>>>> occurred in the creation of the NetCDF file:
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>> Are you able to send me the input little_r file you're using for
>>>>> testing purposes?
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>
>>>>> That'd probably be the quickest way to debug.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>>
>>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>>> Queue: met_help
>>>>>> Subject: Test of ASCII2NC with little_r input
>>>>>> Owner: Nobody
>>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>>> Status: new
>>>>>> Ticket <URL:
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>>
>>>>>>
>>>>>>
>>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>>> could convert a little_r file containing MADIS observations to
>>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>>> errors or warnings and an output file was created, but I can't
tell
>>>>>> if the file is really as it should be for Point-Stat to read. I
>>>>>> tried using the ncdump command to view the .nc file, but it
>>>>>> produces only some header information. I don't see the
observation
>>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>>> it processes normal MADIS text files. See attached "test" file
with
>>>>>> the ncdump output. The screen dialog is as follows:
>>>>>>
>>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>>> DEBUG
>>>>>> 1: Reading little_r ASCII Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>
>>>>>>
>>>>>> Do I have to do anything to the little_r file before I input it
to
>>>>>> ASCII2NC?
>>>>>> I don't believe that the data contained in the little_r file
are in
>>>>>> the ASCII point observation format. Could this be a problem?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> R/
>>>>>> John
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Tue Dec 04 13:14:31 2012
John -
I will have Bob Flanigan recheck the steps. If I do a retest, I'll
send you an update. Otherwise, I guess we will wait for the release.
Are you expecting the release to be in Jan 2013?
Thanks.
R/
John
________________________________________
From: John Halley Gotway via RT [met_help at ucar.edu]
Sent: Tuesday, December 04, 2012 12:46 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
John,
I was worried about something like this. It's dangerous when you try
to "patch" releases with enhancements - there are so many little
things that can go wrong. I suppose it's possible that there's a
problem with the version of NetCDF, but I would expect that to be a
problem at compile time rather than at run time.
Are you sure that Bob has followed the exact steps I described?
(1) Untarred the METv4.0 release.
(2) Applied the latest set of METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
(3) Applied the set of little_r patches I sent you:
METv4.0_little_r_20120926.tar.gz
(4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I just sent you.
When I followed those exact steps, I was able to compile MET fine and
run ascii2nc on the data you sent me without any problems.
Let me know how it goes. It'll be easier when we just get to the next
release, METv4.1, which will include all this functionality.
Thanks,
John
On 12/03/2012 09:32 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> Bob Flanigan recompiled MET V4.0 with all the patches from your
email and this morning I tested ascii2nc again, but no success.
>
> See the dialog I received below and the text file output from
ncdump. I've also attached the output .nc file.
>
> [jraby at carson ~/MET_obs/little_r]
> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 1: Reading little_r ASCII Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> DEBUG 1: Creating NetCDF Observation file:
qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 2: Processing 5735 Little_r reports.
> NetCDF: Start+count exceeds dimension bound
>
> Bob recommended that we check the netcdf and compiler versions to
see if there might be a problem.
>
> Our compiler type is gcc444 and the netcdf version is cdf413.
>
> Do you have any thoughts on what might be the problem?
>
> Thanks.
>
> R/
> John
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 2:03 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input (UNCLASSIFIED)
>
> Yes, that's correct. It does.
>
> John
>
> On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks for setting it up so we integrate into our current patched
version of
>> V4.0. I have cc'd Bob Flanigan on this email so he can take note.
>>
>> When ASCII2NC processes the little_r file does it produce the MET
specific
>> ASCII format ready for Point-Stat?
>>
>> R/
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, November 21, 2012 12:48 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
>> CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r input
>> (UNCLASSIFIED)
>>
>> John,
>>
>> OK, I did the following:
>>
>> (1) Untarred the METv4.0 release.
>> (2) Applied the latest set of METv4.0 patches:
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>> (3) Applied the set of little_r patches I sent you
>> (METv4.0_little_r_20120926.tar.gz).
>> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version I
>> just sent you.
>>
>> I built MET and it compiled fine.
>>
>> Then I ran ascii2nc with the little_r observation file you sent,
and it
>> produced meaningful output with the same warnings I mentioned
previously.
>>
>> So it should work fine.
>>
>> Thanks,
>> John
>>
>> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> John -
>>>
>>> I was off the net for a while, sorry for the delay. Yes we are
using the
>>> patched version of V4.0.
>>> R/
>>> John
>>>
>>> ________________________________________
>>> From: John Halley Gotway via RT [met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 3:41 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>>> It's possible that I was too hasty though - to be more
thorough, I
>>> could have checked that plugging in the latest version of ASCII2NC
>>> into the version of MET you're running would compile well. Is it
>>> METv4.0 that you're using?
>>>
>>> If you have compilation problems, let me know.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>>>> correctly, just needed the more recent version of the tool. I
will
>>>> get this update to our sysadm for a recompile and then give it
try.
>>>>
>>>> R/
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input
>>>> (UNCLASSIFIED)
>>>>
>>>> John,
>>>>
>>>> I was able to run your data through the latest development
version of
>>>> ascii2nc with no real problems. I did get a bunch of warnings
like
>>>> the following:
>>>>
>>>> WARNING: process_little_r_obs() -> the number of data lines
specified
>>>> in the header (1) does not match the number found in the data (2)
on
>>>> line number 13088.
>>>>
>>>> A little_r report consists of one header line, one or more data
>>>> lines, and an end of report line. The header line is supposed to
>>>> list the number of data lines to follow. The ASCII2NC tool reads
all
>>>> of the data lines that are present and prints a warning if the
number
>>>> found doesn't match the number from the header line. That's the
>>>> source of this warning message.
>>>>
>>>> I've attached to this message the output of my run with your
data, as
>>>> well as the latest version of the ascii2nc.cc file. You could
try
>>>> recompiling with this and running again.
>>>>
>>>> Just let me know if more issues arise.
>>>>
>>>> John
>>>>
>>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>> John -
>>>>>
>>>>> Thanks. I've attached the file.
>>>>>
>>>>> R/
>>>>>
>>>>> John
>>>>>
>>>>> -----Original Message-----
>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>>> To: Raby, John W CIV (US)
>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>>> Robert E Jr CIV (US)
>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>>> input
>>>>>
>>>>> John,
>>>>>
>>>>> The following line in the output you sent indicates that an
error
>>>>> occurred in the creation of the NetCDF file:
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>> Are you able to send me the input little_r file you're using for
>>>>> testing purposes?
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>
>>>>> That'd probably be the quickest way to debug.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>>
>>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>>> Queue: met_help
>>>>>> Subject: Test of ASCII2NC with little_r input
>>>>>> Owner: Nobody
>>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>>> Status: new
>>>>>> Ticket <URL:
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>>
>>>>>>
>>>>>>
>>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>>> could convert a little_r file containing MADIS observations to
>>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>>> errors or warnings and an output file was created, but I can't
tell
>>>>>> if the file is really as it should be for Point-Stat to read. I
>>>>>> tried using the ncdump command to view the .nc file, but it
>>>>>> produces only some header information. I don't see the
observation
>>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>>> it processes normal MADIS text files. See attached "test" file
with
>>>>>> the ncdump output. The screen dialog is as follows:
>>>>>>
>>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>>> DEBUG
>>>>>> 1: Reading little_r ASCII Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>
>>>>>>
>>>>>> Do I have to do anything to the little_r file before I input it
to
>>>>>> ASCII2NC?
>>>>>> I don't believe that the data contained in the little_r file
are in
>>>>>> the ASCII point observation format. Could this be a problem?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> R/
>>>>>> John
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Tue Dec 04 14:03:53 2012
John,
We're working toward a release at the end of January, but recent staff
changes will likely require us to push it to the end of February.
John
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> I will have Bob Flanigan recheck the steps. If I do a retest, I'll
send
> you an update. Otherwise, I guess we will wait for the release. Are
you
> expecting the release to be in Jan 2013?
>
> Thanks.
>
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Tuesday, December 04, 2012 12:46 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E
> Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> I was worried about something like this. It's dangerous when you
try to
> "patch" releases with enhancements - there are so many little things
that
> can go wrong. I suppose it's possible that there's a
> problem with the version of NetCDF, but I would expect that to be a
> problem at compile time rather than at run time.
>
> Are you sure that Bob has followed the exact steps I described?
>
> (1) Untarred the METv4.0 release.
> (2) Applied the latest set of METv4.0 patches:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> (3) Applied the set of little_r patches I sent you:
> METv4.0_little_r_20120926.tar.gz
> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with
the
> version I just sent you.
>
> When I followed those exact steps, I was able to compile MET fine
and run
> ascii2nc on the data you sent me without any problems.
>
> Let me know how it goes. It'll be easier when we just get to the
next
> release, METv4.1, which will include all this functionality.
>
> Thanks,
> John
>
> On 12/03/2012 09:32 AM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> John -
>>
>> Bob Flanigan recompiled MET V4.0 with all the patches from your
email
>> and this morning I tested ascii2nc again, but no success.
>>
>> See the dialog I received below and the text file output from
ncdump.
>> I've also attached the output .nc file.
>>
>> [jraby at carson ~/MET_obs/little_r]
>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 1: Reading little_r ASCII Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> DEBUG 1: Creating NetCDF Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 2: Processing 5735 Little_r reports.
>> NetCDF: Start+count exceeds dimension bound
>>
>> Bob recommended that we check the netcdf and compiler versions to
see if
>> there might be a problem.
>>
>> Our compiler type is gcc444 and the netcdf version is cdf413.
>>
>> Do you have any thoughts on what might be the problem?
>>
>> Thanks.
>>
>> R/
>> John
>> ________________________________________
>> From: John Halley Gotway via RT [met_help at ucar.edu]
>> Sent: Wednesday, November 21, 2012 2:03 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert
>> E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input (UNCLASSIFIED)
>>
>> Yes, that's correct. It does.
>>
>> John
>>
>> On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks for setting it up so we integrate into our current patched
>>> version of
>>> V4.0. I have cc'd Bob Flanigan on this email so he can take note.
>>>
>>> When ASCII2NC processes the little_r file does it produce the MET
>>> specific
>>> ASCII format ready for Point-Stat?
>>>
>>> R/
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Wednesday, November 21, 2012 12:48 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert
>>> E Jr
>>> CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>> (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> OK, I did the following:
>>>
>>> (1) Untarred the METv4.0 release.
>>> (2) Applied the latest set of METv4.0 patches:
>>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>>> (3) Applied the set of little_r patches I sent you
>>> (METv4.0_little_r_20120926.tar.gz).
>>> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
>>> version I
>>> just sent you.
>>>
>>> I built MET and it compiled fine.
>>>
>>> Then I ran ascii2nc with the little_r observation file you sent,
and it
>>> produced meaningful output with the same warnings I mentioned
>>> previously.
>>>
>>> So it should work fine.
>>>
>>> Thanks,
>>> John
>>>
>>> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> John -
>>>>
>>>> I was off the net for a while, sorry for the delay. Yes we are
using
>>>> the
>>>> patched version of V4.0.
>>>> R/
>>>> John
>>>>
>>>> ________________________________________
>>>> From: John Halley Gotway via RT [met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 3:41 PM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input (UNCLASSIFIED)
>>>>
>>>> John,
>>>>
>>>> Yes, that's correct. Sorry you need to involve a sysadmin in the
>>>> process.
>>>> It's possible that I was too hasty though - to be more
thorough, I
>>>> could have checked that plugging in the latest version of
ASCII2NC
>>>> into the version of MET you're running would compile well. Is it
>>>> METv4.0 that you're using?
>>>>
>>>> If you have compilation problems, let me know.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>>
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>> John -
>>>>>
>>>>> Thanks for your help. So, from what you found, I was running
ASCII2NC
>>>>> correctly, just needed the more recent version of the tool. I
will
>>>>> get this update to our sysadm for a recompile and then give it
try.
>>>>>
>>>>> R/
>>>>> John
>>>>>
>>>>> -----Original Message-----
>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>>>> To: Raby, John W CIV (US)
>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>>> Robert E Jr CIV (US)
>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>>> input
>>>>> (UNCLASSIFIED)
>>>>>
>>>>> John,
>>>>>
>>>>> I was able to run your data through the latest development
version of
>>>>> ascii2nc with no real problems. I did get a bunch of warnings
like
>>>>> the following:
>>>>>
>>>>> WARNING: process_little_r_obs() -> the number of data lines
specified
>>>>> in the header (1) does not match the number found in the data
(2) on
>>>>> line number 13088.
>>>>>
>>>>> A little_r report consists of one header line, one or more data
>>>>> lines, and an end of report line. The header line is supposed
to
>>>>> list the number of data lines to follow. The ASCII2NC tool
reads all
>>>>> of the data lines that are present and prints a warning if the
number
>>>>> found doesn't match the number from the header line. That's the
>>>>> source of this warning message.
>>>>>
>>>>> I've attached to this message the output of my run with your
data, as
>>>>> well as the latest version of the ascii2nc.cc file. You could
try
>>>>> recompiling with this and running again.
>>>>>
>>>>> Just let me know if more issues arise.
>>>>>
>>>>> John
>>>>>
>>>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>>
>>>>>> Classification: UNCLASSIFIED
>>>>>> Caveats: NONE
>>>>>>
>>>>>> John -
>>>>>>
>>>>>> Thanks. I've attached the file.
>>>>>>
>>>>>> R/
>>>>>>
>>>>>> John
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>>>> To: Raby, John W CIV (US)
>>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US);
Dumais,
>>>>>> Robert E Jr CIV (US)
>>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>>>> input
>>>>>>
>>>>>> John,
>>>>>>
>>>>>> The following line in the output you sent indicates that an
error
>>>>>> occurred in the creation of the NetCDF file:
>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>
>>>>>> Are you able to send me the input little_r file you're using
for
>>>>>> testing purposes?
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>>
>>>>>> That'd probably be the quickest way to debug.
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>>>
>>>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>>>> Queue: met_help
>>>>>>> Subject: Test of ASCII2NC with little_r input
>>>>>>> Owner: Nobody
>>>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>>>> Status: new
>>>>>>> Ticket <URL:
>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I conducted a test of the alpha version of ASCII2NC to see if
I
>>>>>>> could convert a little_r file containing MADIS observations to
>>>>>>> netcdf format for Point-Stat. The dialog below doesn't show
any
>>>>>>> errors or warnings and an output file was created, but I can't
tell
>>>>>>> if the file is really as it should be for Point-Stat to read.
I
>>>>>>> tried using the ncdump command to view the .nc file, but it
>>>>>>> produces only some header information. I don't see the
observation
>>>>>>> data as I'm able to do when I look at the output of ASCII2NC
after
>>>>>>> it processes normal MADIS text files. See attached "test" file
with
>>>>>>> the ncdump output. The screen dialog is as follows:
>>>>>>>
>>>>>>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v
3
>>>>>>> DEBUG
>>>>>>> 1: Reading little_r ASCII Observation file:
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>>
>>>>>>>
>>>>>>> Do I have to do anything to the little_r file before I input
it to
>>>>>>> ASCII2NC?
>>>>>>> I don't believe that the data contained in the little_r file
are in
>>>>>>> the ASCII point observation format. Could this be a problem?
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> R/
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Classification: UNCLASSIFIED
>>>>>> Caveats: NONE
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: Test of ASCII2NC with little_r input
From: Raby, John W USA CIV
Time: Thu Dec 06 08:47:22 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
Bob thought of something which might have affected the success of the
ASCII2NC
test we did here.
During the recompile he noted that in the Make Config File there is a
section
where you specify the tools you want to compile. He did not select
grib2.
Would this have affected the test? What is the impact of not selecting
grib2
on other aspecst of MET?
Thanks.
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, December 04, 2012 12:47 PM
To: Raby, John W CIV (US)
Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
CIV (US)
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
(UNCLASSIFIED)
John,
I was worried about something like this. It's dangerous when you try
to
"patch" releases with enhancements - there are so many little things
that can
go wrong. I suppose it's possible that there's a problem with the
version of
NetCDF, but I would expect that to be a problem at compile time rather
than at
run time.
Are you sure that Bob has followed the exact steps I described?
(1) Untarred the METv4.0 release.
(2) Applied the latest set of METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
(3) Applied the set of little_r patches I sent you:
METv4.0_little_r_20120926.tar.gz
(4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
version
I just sent you.
When I followed those exact steps, I was able to compile MET fine and
run
ascii2nc on the data you sent me without any problems.
Let me know how it goes. It'll be easier when we just get to the next
release, METv4.1, which will include all this functionality.
Thanks,
John
On 12/03/2012 09:32 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> John -
>
> Bob Flanigan recompiled MET V4.0 with all the patches from your
email and
> this morning I tested ascii2nc again, but no success.
>
> See the dialog I received below and the text file output from
ncdump. I've
> also attached the output .nc file.
>
> [jraby at carson ~/MET_obs/little_r]
> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 1: Reading little_r ASCII Observation file:
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
> DEBUG 1: Creating NetCDF Observation file:
> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
> DEBUG 2: Processing 5735 Little_r reports.
> NetCDF: Start+count exceeds dimension bound
>
> Bob recommended that we check the netcdf and compiler versions to
see if
> there might be a problem.
>
> Our compiler type is gcc444 and the netcdf version is cdf413.
>
> Do you have any thoughts on what might be the problem?
>
> Thanks.
>
> R/
> John
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Wednesday, November 21, 2012 2:03 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
> Robert E Jr CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
> input (UNCLASSIFIED)
>
> Yes, that's correct. It does.
>
> John
>
> On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> John -
>>
>> Thanks for setting it up so we integrate into our current patched
>> version of V4.0. I have cc'd Bob Flanigan on this email so he can
take
>> note.
>>
>> When ASCII2NC processes the little_r file does it produce the MET
>> specific ASCII format ready for Point-Stat?
>>
>> R/
>> John
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Wednesday, November 21, 2012 12:48 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input
>> (UNCLASSIFIED)
>>
>> John,
>>
>> OK, I did the following:
>>
>> (1) Untarred the METv4.0 release.
>> (2) Applied the latest set of METv4.0 patches:
>>
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.
>> php
>> (3) Applied the set of little_r patches I sent you
>> (METv4.0_little_r_20120926.tar.gz).
>> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
>> version I just sent you.
>>
>> I built MET and it compiled fine.
>>
>> Then I ran ascii2nc with the little_r observation file you sent,
and
>> it produced meaningful output with the same warnings I mentioned
>> previously.
>>
>> So it should work fine.
>>
>> Thanks,
>> John
>>
>> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> John -
>>>
>>> I was off the net for a while, sorry for the delay. Yes we are
using
>>> the patched version of V4.0.
>>> R/
>>> John
>>>
>>> ________________________________________
>>> From: John Halley Gotway via RT [met_help at ucar.edu]
>>> Sent: Tuesday, November 20, 2012 3:41 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>>> It's possible that I was too hasty though - to be more
thorough,
>>> I could have checked that plugging in the latest version of
ASCII2NC
>>> into the version of MET you're running would compile well. Is it
>>> METv4.0 that you're using?
>>>
>>> If you have compilation problems, let me know.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> John -
>>>>
>>>> Thanks for your help. So, from what you found, I was running
>>>> ASCII2NC correctly, just needed the more recent version of the
>>>> tool. I will get this update to our sysadm for a recompile and
then give
>>>> it try.
>>>>
>>>> R/
>>>> John
>>>>
>>>> -----Original Message-----
>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
>>>> little_r input
>>>> (UNCLASSIFIED)
>>>>
>>>> John,
>>>>
>>>> I was able to run your data through the latest development
version
>>>> of ascii2nc with no real problems. I did get a bunch of warnings
>>>> like the following:
>>>>
>>>> WARNING: process_little_r_obs() -> the number of data lines
>>>> specified in the header (1) does not match the number found in
the
>>>> data (2) on line number 13088.
>>>>
>>>> A little_r report consists of one header line, one or more data
>>>> lines, and an end of report line. The header line is supposed to
>>>> list the number of data lines to follow. The ASCII2NC tool reads
>>>> all of the data lines that are present and prints a warning if
the
>>>> number found doesn't match the number from the header line.
That's
>>>> the source of this warning message.
>>>>
>>>> I've attached to this message the output of my run with your
data,
>>>> as well as the latest version of the ascii2nc.cc file. You could
>>>> try recompiling with this and running again.
>>>>
>>>> Just let me know if more issues arise.
>>>>
>>>> John
>>>>
>>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>> John -
>>>>>
>>>>> Thanks. I've attached the file.
>>>>>
>>>>> R/
>>>>>
>>>>> John
>>>>>
>>>>> -----Original Message-----
>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>>> To: Raby, John W CIV (US)
>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>>> Robert E Jr CIV (US)
>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
>>>>> little_r input
>>>>>
>>>>> John,
>>>>>
>>>>> The following line in the output you sent indicates that an
error
>>>>> occurred in the creation of the NetCDF file:
>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>
>>>>> Are you able to send me the input little_r file you're using for
>>>>> testing purposes?
>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>
>>>>> That'd probably be the quickest way to debug.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>>
>>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>>> Queue: met_help
>>>>>> Subject: Test of ASCII2NC with little_r input
>>>>>> Owner: Nobody
>>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>>> Status: new
>>>>>> Ticket <URL:
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>>
>>>>>>
>>>>>>
>>>>>> I conducted a test of the alpha version of ASCII2NC to see if I
>>>>>> could convert a little_r file containing MADIS observations to
>>>>>> netcdf format for Point-Stat. The dialog below doesn't show any
>>>>>> errors or warnings and an output file was created, but I can't
>>>>>> tell if the file is really as it should be for Point-Stat to
>>>>>> read. I tried using the ncdump command to view the .nc file,
but
>>>>>> it produces only some header information. I don't see the
>>>>>> observation data as I'm able to do when I look at the output of
>>>>>> ASCII2NC after it processes normal MADIS text files. See
attached
>>>>>> "test" file with the ncdump output. The screen dialog is as
follows:
>>>>>>
>>>>>> $ ascii2nc
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v 3
>>>>>> DEBUG
>>>>>> 1: Reading little_r ASCII Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>
>>>>>>
>>>>>> Do I have to do anything to the little_r file before I input it
>>>>>> to ASCII2NC?
>>>>>> I don't believe that the data contained in the little_r file
are
>>>>>> in the ASCII point observation format. Could this be a problem?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> R/
>>>>>> John
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r input (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu Dec 06 09:17:48 2012
John,
Turning support for GRIB2 on/off should have no impact on the
functionality of the ASCII2NC tool. It just enable the MET tools to
read gridded GRIB2 files, but there are several other libraries
required to do so: NCEP's grib2c library, jasperlib, zlib, and libpng.
John
On 12/06/2012 08:47 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Bob thought of something which might have affected the success of
the ASCII2NC
> test we did here.
>
> During the recompile he noted that in the Make Config File there is
a section
> where you specify the tools you want to compile. He did not select
grib2.
> Would this have affected the test? What is the impact of not
selecting grib2
> on other aspecst of MET?
>
> Thanks.
>
> R/
> John
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, December 04, 2012 12:47 PM
> To: Raby, John W CIV (US)
> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
Robert E Jr
> CIV (US)
> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with little_r
input
> (UNCLASSIFIED)
>
> John,
>
> I was worried about something like this. It's dangerous when you
try to
> "patch" releases with enhancements - there are so many little things
that can
> go wrong. I suppose it's possible that there's a problem with the
version of
> NetCDF, but I would expect that to be a problem at compile time
rather than at
> run time.
>
> Are you sure that Bob has followed the exact steps I described?
>
> (1) Untarred the METv4.0 release.
> (2) Applied the latest set of METv4.0 patches:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> (3) Applied the set of little_r patches I sent you:
> METv4.0_little_r_20120926.tar.gz
> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with
the version
> I just sent you.
>
> When I followed those exact steps, I was able to compile MET fine
and run
> ascii2nc on the data you sent me without any problems.
>
> Let me know how it goes. It'll be easier when we just get to the
next
> release, METv4.1, which will include all this functionality.
>
> Thanks,
> John
>
> On 12/03/2012 09:32 AM, Raby, John W USA CIV via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>
>> John -
>>
>> Bob Flanigan recompiled MET V4.0 with all the patches from your
email and
>> this morning I tested ascii2nc again, but no success.
>>
>> See the dialog I received below and the text file output from
ncdump. I've
>> also attached the output .nc file.
>>
>> [jraby at carson ~/MET_obs/little_r]
>> $ ascii2nc qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 1: Reading little_r ASCII Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>> DEBUG 1: Creating NetCDF Observation file:
>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>> DEBUG 2: Processing 5735 Little_r reports.
>> NetCDF: Start+count exceeds dimension bound
>>
>> Bob recommended that we check the netcdf and compiler versions to
see if
>> there might be a problem.
>>
>> Our compiler type is gcc444 and the netcdf version is cdf413.
>>
>> Do you have any thoughts on what might be the problem?
>>
>> Thanks.
>>
>> R/
>> John
>> ________________________________________
>> From: John Halley Gotway via RT [met_help at ucar.edu]
>> Sent: Wednesday, November 21, 2012 2:03 PM
>> To: Raby, John W CIV (US)
>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>> Robert E Jr CIV (US)
>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>> input (UNCLASSIFIED)
>>
>> Yes, that's correct. It does.
>>
>> John
>>
>> On 11/21/2012 12:56 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> John -
>>>
>>> Thanks for setting it up so we integrate into our current patched
>>> version of V4.0. I have cc'd Bob Flanigan on this email so he can
take
>>> note.
>>>
>>> When ASCII2NC processes the little_r file does it produce the MET
>>> specific ASCII format ready for Point-Stat?
>>>
>>> R/
>>> John
>>>
>>> -----Original Message-----
>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>> Sent: Wednesday, November 21, 2012 12:48 PM
>>> To: Raby, John W CIV (US)
>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>> Robert E Jr CIV (US)
>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>> input
>>> (UNCLASSIFIED)
>>>
>>> John,
>>>
>>> OK, I did the following:
>>>
>>> (1) Untarred the METv4.0 release.
>>> (2) Applied the latest set of METv4.0 patches:
>>>
>>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.
>>> php
>>> (3) Applied the set of little_r patches I sent you
>>> (METv4.0_little_r_20120926.tar.gz).
>>> (4) Replaced METv4.0/src/tools/other/ascii2nc/ascii2nc.cc with the
>>> version I just sent you.
>>>
>>> I built MET and it compiled fine.
>>>
>>> Then I ran ascii2nc with the little_r observation file you sent,
and
>>> it produced meaningful output with the same warnings I mentioned
>>> previously.
>>>
>>> So it should work fine.
>>>
>>> Thanks,
>>> John
>>>
>>> On 11/20/2012 03:54 PM, Raby, John W USA CIV via RT wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>
>>>> John -
>>>>
>>>> I was off the net for a while, sorry for the delay. Yes we are
using
>>>> the patched version of V4.0.
>>>> R/
>>>> John
>>>>
>>>> ________________________________________
>>>> From: John Halley Gotway via RT [met_help at ucar.edu]
>>>> Sent: Tuesday, November 20, 2012 3:41 PM
>>>> To: Raby, John W CIV (US)
>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>> Robert E Jr CIV (US)
>>>> Subject: RE: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
little_r
>>>> input (UNCLASSIFIED)
>>>>
>>>> John,
>>>>
>>>> Yes, that's correct. Sorry you need to involve a sysadmin in the
process.
>>>> It's possible that I was too hasty though - to be more
thorough,
>>>> I could have checked that plugging in the latest version of
ASCII2NC
>>>> into the version of MET you're running would compile well. Is it
>>>> METv4.0 that you're using?
>>>>
>>>> If you have compilation problems, let me know.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>>
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>> John -
>>>>>
>>>>> Thanks for your help. So, from what you found, I was running
>>>>> ASCII2NC correctly, just needed the more recent version of the
>>>>> tool. I will get this update to our sysadm for a recompile and
then give
>>>>> it try.
>>>>>
>>>>> R/
>>>>> John
>>>>>
>>>>> -----Original Message-----
>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>> Sent: Tuesday, November 20, 2012 12:38 PM
>>>>> To: Raby, John W CIV (US)
>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US); Dumais,
>>>>> Robert E Jr CIV (US)
>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
>>>>> little_r input
>>>>> (UNCLASSIFIED)
>>>>>
>>>>> John,
>>>>>
>>>>> I was able to run your data through the latest development
version
>>>>> of ascii2nc with no real problems. I did get a bunch of
warnings
>>>>> like the following:
>>>>>
>>>>> WARNING: process_little_r_obs() -> the number of data lines
>>>>> specified in the header (1) does not match the number found in
the
>>>>> data (2) on line number 13088.
>>>>>
>>>>> A little_r report consists of one header line, one or more data
>>>>> lines, and an end of report line. The header line is supposed
to
>>>>> list the number of data lines to follow. The ASCII2NC tool
reads
>>>>> all of the data lines that are present and prints a warning if
the
>>>>> number found doesn't match the number from the header line.
That's
>>>>> the source of this warning message.
>>>>>
>>>>> I've attached to this message the output of my run with your
data,
>>>>> as well as the latest version of the ascii2nc.cc file. You
could
>>>>> try recompiling with this and running again.
>>>>>
>>>>> Just let me know if more issues arise.
>>>>>
>>>>> John
>>>>>
>>>>> On 11/20/2012 11:47 AM, Raby, John W USA CIV via RT wrote:
>>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352 >
>>>>>>
>>>>>> Classification: UNCLASSIFIED
>>>>>> Caveats: NONE
>>>>>>
>>>>>> John -
>>>>>>
>>>>>> Thanks. I've attached the file.
>>>>>>
>>>>>> R/
>>>>>>
>>>>>> John
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>>>>>> Sent: Tuesday, November 20, 2012 10:06 AM
>>>>>> To: Raby, John W CIV (US)
>>>>>> Cc: Reen, Brian P CTR (US); Passner, Jeffrey E CIV (US);
Dumais,
>>>>>> Robert E Jr CIV (US)
>>>>>> Subject: Re: [rt.rap.ucar.edu #59352] Test of ASCII2NC with
>>>>>> little_r input
>>>>>>
>>>>>> John,
>>>>>>
>>>>>> The following line in the output you sent indicates that an
error
>>>>>> occurred in the creation of the NetCDF file:
>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>
>>>>>> Are you able to send me the input little_r file you're using
for
>>>>>> testing purposes?
>>>>>> qc_obs_used_earth_relative.d01.2012-03-
01_18_00_00.0000
>>>>>>
>>>>>> That'd probably be the quickest way to debug.
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>> On 11/20/2012 09:05 AM, Raby, John W USA CIV via RT wrote:
>>>>>>>
>>>>>>> Tue Nov 20 09:05:48 2012: Request 59352 was acted upon.
>>>>>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>>>>>> Queue: met_help
>>>>>>> Subject: Test of ASCII2NC with little_r input
>>>>>>> Owner: Nobody
>>>>>>> Requestors: john.w.raby2.civ at mail.mil
>>>>>>> Status: new
>>>>>>> Ticket <URL:
>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=59352
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I conducted a test of the alpha version of ASCII2NC to see if
I
>>>>>>> could convert a little_r file containing MADIS observations to
>>>>>>> netcdf format for Point-Stat. The dialog below doesn't show
any
>>>>>>> errors or warnings and an output file was created, but I can't
>>>>>>> tell if the file is really as it should be for Point-Stat to
>>>>>>> read. I tried using the ncdump command to view the .nc file,
but
>>>>>>> it produces only some header information. I don't see the
>>>>>>> observation data as I'm able to do when I look at the output
of
>>>>>>> ASCII2NC after it processes normal MADIS text files. See
attached
>>>>>>> "test" file with the ncdump output. The screen dialog is as
follows:
>>>>>>>
>>>>>>> $ ascii2nc
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc -v
3
>>>>>>> DEBUG
>>>>>>> 1: Reading little_r ASCII Observation file:
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000
>>>>>>> DEBUG 1: Creating NetCDF Observation file:
>>>>>>> qc_obs_used_earth_relative.d01.2012-03-01_18_00_00.0000.nc
>>>>>>> DEBUG 2: Processing 5735 Little_r reports.
>>>>>>> NetCDF: Start+count exceeds dimension bound
>>>>>>>
>>>>>>>
>>>>>>> Do I have to do anything to the little_r file before I input
it
>>>>>>> to ASCII2NC?
>>>>>>> I don't believe that the data contained in the little_r file
are
>>>>>>> in the ASCII point observation format. Could this be a
problem?
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> R/
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Classification: UNCLASSIFIED
>>>>>> Caveats: NONE
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Classification: UNCLASSIFIED
>>>>> Caveats: NONE
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
More information about the Met_help
mailing list