[Met_help] [rt.rap.ucar.edu #83127] History for question about ascii2nc warnings
Howard Soh via RT
met_help at ucar.edu
Thu Nov 30 13:42:50 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I ran ascii2nc using a text file containing observations in little_r format and received several warnings. An example of one warning is as follows:
WARNING:
WARNING: LittleRHandler::_processObs() -> Storing message type as "FM-96" for unexpected report type "FM-96".
WARNING:
My understanding is that this is not a problem since the output NetCDF file will contain the same report type string as is contained in the input text file.
Is this warning something I need to be concerned about?
Thanks.
R/
John
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: question about ascii2nc warnings
From: Howard Soh
Time: Mon Nov 27 14:14:07 2017
The warning means the report type "FM-95" is not in the message type
mapping, message_type_map at the ASCII2NC configuration file.
If the input message type is not converted by message type mapping,
the space (" ") at the input message type is converted to underscore
("_").
Cheers,
Howard
FYI:
The default configuration:
message_type_map = [
{ key = "FM-12 SYNOP"; val = "ADPSFC"; },
{ key = "FM-13 SHIP"; val = "SFCSHP"; },
{ key = "FM-15 METAR"; val = "ADPSFC"; },
{ key = "FM-18 BUOY"; val = "SFCSHP"; },
{ key = "FM-281 QSCAT"; val = "ASCATW"; },
{ key = "FM-32 PILOT"; val = "ADPUPA"; },
{ key = "FM-35 TEMP"; val = "ADPUPA"; },
{ key = "FM-88 SATOB"; val = "SATWND"; },
{ key = "FM-97 ACARS"; val = "AIRCFT"; }
];
On Mon Nov 27 13:19:13 2017, john.w.raby2.civ at mail.mil wrote:
> I ran ascii2nc using a text file containing observations in little_r
> format and received several warnings. An example of one warning is
as
> follows:
>
> WARNING:
> WARNING: LittleRHandler::_processObs() -> Storing message type as
"FM-
> 96" for unexpected report type "FM-96".
> WARNING:
>
> My understanding is that this is not a problem since the output
NetCDF
> file will contain the same report type string as is contained in the
> input text file.
>
> Is this warning something I need to be concerned about?
>
> Thanks.
>
> R/
> John
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #83127] question about ascii2nc warnings
From: Howard Soh
Time: Mon Nov 27 15:19:59 2017
You are right. It's not a problem on saving NetCDF file. It could be
an
issue when this output becomes the input to other MET tools which
filter
the observation data by the message type. ascii2nc can convert the
input
message type to the common message type for other MET tools. It's
configured by message_type_map for Ascii2NcConfig file. If you update
the message_type_map to specify how FM-96 should be interpreted, those
warnings should go away.
The default mapping is
message_type_map = [
{ key = "FM-12 SYNOP"; val = "ADPSFC"; },
{ key = "FM-13 SHIP"; val = "SFCSHP"; },
{ key = "FM-15 METAR"; val = "ADPSFC"; },
{ key = "FM-18 BUOY"; val = "SFCSHP"; },
{ key = "FM-281 QSCAT"; val = "ASCATW"; },
{ key = "FM-32 PILOT"; val = "ADPUPA"; },
{ key = "FM-35 TEMP"; val = "ADPUPA"; },
{ key = "FM-88 SATOB"; val = "SATWND"; },
{ key = "FM-97 ACARS"; val = "AIRCFT"; }
];
Cheers,
Howard
FYI:
For example (the default configuration if not changed), point_stat and
ensemble_stat are configured to filter out by the message type
"ADPUPA".
You should disable the filtering by message type or change
"message_type" to "FM-96".
On 11/27/2017 1:19 PM, Raby, John W USA CIV via RT wrote:
> Mon Nov 27 13:19:13 2017: Request 83127 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: question about ascii2nc warnings
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83127 >
>
>
> I ran ascii2nc using a text file containing observations in little_r
format and received several warnings. An example of one warning is as
follows:
>
> WARNING:
> WARNING: LittleRHandler::_processObs() -> Storing message type as
"FM-96" for unexpected report type "FM-96".
> WARNING:
>
> My understanding is that this is not a problem since the output
NetCDF file will contain the same report type string as is contained
in the input text file.
>
> Is this warning something I need to be concerned about?
>
> Thanks.
>
> R/
> John
>
>
------------------------------------------------
Subject: question about ascii2nc warnings
From: Raby, John W USA CIV
Time: Tue Nov 28 16:25:02 2017
CLASSIFICATION: UNCLASSIFIED
I consulted the config file for ascii2nc and discovered a possible
explanation
for the warnings. This is an indication that the mapping of report
strings to
message types has not been specified. My plan is to use the config
file to
specify the mappings as needed and this should remove the warnings and
result
in a NetDF file which contains the standard message types which can be
read by
MET.
Please cancel this ticket if my explanation above is correct.
Thanks.
R/
John
-----Original Message-----
From: met_help at ucar.edu via RT [mailto:met_help at ucar.edu]
Sent: Monday, November 27, 2017 1:19 PM
To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
Subject: [Non-DoD Source] [rt.rap.ucar.edu #83127] AutoReply: question
about
ascii2nc warnings
All active links contained in this email were disabled. Please verify
the
identity of the sender, and confirm the authenticity of all links
contained
within the message prior to copying and pasting the address to a Web
browser.
----
Greetings,
This message has been automatically generated in response to the
creation of a
trouble ticket regarding:
"question about ascii2nc warnings",
a summary of which appears below.
There is no need to reply to this message right now. Your ticket has
been
assigned an ID of [rt.rap.ucar.edu #83127].
Please include the string:
[rt.rap.ucar.edu #83127]
in the subject line of all future correspondence about this issue. To
do so,
you may reply to this message.
For more information, please see:
MET Online Tutorial:
Caution-
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
MET Users Guide:
Caution-https://www.dtcenter.org/met/users/docs/overview.php
MET FAQs:
Caution-https://www.dtcenter.org/met/users/support/faqs/index.php
MET-Help Email Archive:
Caution-http://mailman.ucar.edu/pipermail/met_help
Thank you,
met_help at ucar.edu
-------------------------------------------------------------------------
I ran ascii2nc using a text file containing observations in little_r
format
and received several warnings. An example of one warning is as
follows:
WARNING:
WARNING: LittleRHandler::_processObs() -> Storing message type as "FM-
96" for
unexpected report type "FM-96".
WARNING:
My understanding is that this is not a problem since the output NetCDF
file
will contain the same report type string as is contained in the input
text
file.
Is this warning something I need to be concerned about?
Thanks.
R/
John
CLASSIFICATION: UNCLASSIFIED
------------------------------------------------
Subject: question about ascii2nc warnings
From: John Halley Gotway
Time: Tue Nov 28 17:34:48 2017
Hi John,
Did you not receive an email from Howard Soh on this ticket?
He wrote you back but perhaps it didn't go through.
Here's his response:
You are right. It's not a problem on saving NetCDF file. It could be
an
issue when this output becomes the input to other MET tools which
filter
the observation data by the message type. ascii2nc can convert the
input
message type to the common message type for other MET tools. It's
configured by message_type_map for Ascii2NcConfig file. If you update
the message_type_map to specify how FM-96 should be interpreted, those
warnings should go away.
The default mapping is
message_type_map = [
{ key = "FM-12 SYNOP"; val = "ADPSFC"; },
{ key = "FM-13 SHIP"; val = "SFCSHP"; },
{ key = "FM-15 METAR"; val = "ADPSFC"; },
{ key = "FM-18 BUOY"; val = "SFCSHP"; },
{ key = "FM-281 QSCAT"; val = "ASCATW"; },
{ key = "FM-32 PILOT"; val = "ADPUPA"; },
{ key = "FM-35 TEMP"; val = "ADPUPA"; },
{ key = "FM-88 SATOB"; val = "SATWND"; },
{ key = "FM-97 ACARS"; val = "AIRCFT"; }
];
Cheers,
Howard
FYI:
For example (the default configuration if not changed), point_stat and
ensemble_stat are configured to filter out by the message type
"ADPUPA".
You should disable the filtering by message type or change
"message_type" to "FM-96".
On Tue, Nov 28, 2017 at 4:25 PM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83127 >
>
> CLASSIFICATION: UNCLASSIFIED
>
> I consulted the config file for ascii2nc and discovered a possible
> explanation
> for the warnings. This is an indication that the mapping of report
strings
> to
> message types has not been specified. My plan is to use the config
file to
> specify the mappings as needed and this should remove the warnings
and
> result
> in a NetDF file which contains the standard message types which can
be
> read by
> MET.
>
> Please cancel this ticket if my explanation above is correct.
>
> Thanks.
>
> R/
> John
>
> -----Original Message-----
> From: met_help at ucar.edu via RT [mailto:met_help at ucar.edu]
> Sent: Monday, November 27, 2017 1:19 PM
> To: Raby, John W CIV USARMY RDECOM ARL (US)
<john.w.raby2.civ at mail.mil>
> Subject: [Non-DoD Source] [rt.rap.ucar.edu #83127] AutoReply:
question
> about
> ascii2nc warnings
>
> All active links contained in this email were disabled. Please
verify the
> identity of the sender, and confirm the authenticity of all links
contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
>
>
> ----
>
> Greetings,
>
> This message has been automatically generated in response to the
creation
> of a
> trouble ticket regarding:
> "question about ascii2nc warnings",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket
has been
> assigned an ID of [rt.rap.ucar.edu #83127].
>
> Please include the string:
>
> [rt.rap.ucar.edu #83127]
>
> in the subject line of all future correspondence about this issue.
To do
> so,
> you may reply to this message.
>
> For more information, please see:
>
> MET Online Tutorial:
> Caution-https://www.dtcenter.org/met/users/support/online_
> tutorial/index.php
>
> MET Users Guide:
> Caution-https://www.dtcenter.org/met/users/docs/overview.php
>
> MET FAQs:
> Caution-https://www.dtcenter.org/met/users/support/faqs/index.php
>
> MET-Help Email Archive:
> Caution-http://mailman.ucar.edu/pipermail/met_help
>
> Thank you,
> met_help at ucar.edu
>
>
-------------------------------------------------------------------------
> I ran ascii2nc using a text file containing observations in little_r
format
> and received several warnings. An example of one warning is as
follows:
>
> WARNING:
> WARNING: LittleRHandler::_processObs() -> Storing message type as
"FM-96"
> for
> unexpected report type "FM-96".
> WARNING:
>
> My understanding is that this is not a problem since the output
NetCDF file
> will contain the same report type string as is contained in the
input text
> file.
>
> Is this warning something I need to be concerned about?
>
> Thanks.
>
> R/
> John
>
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
------------------------------------------------
More information about the Met_help
mailing list