[Met_help] [rt.rap.ucar.edu #93257] History for mode tool read forecast and obs data error

[John Halley Gotway via RT]

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


Dear Sir:
     I used mode tool to verify WRF rain 6hr apcp with grid obs  by met7.0 ,met9.0-beta1, both read file error:
“Trouble reading forecast file” by met7.0 and “Trouble reading obs file ” by met9.0.

The forecast file I got from WRFv3.8 and UPPv2.1 , the obs is AWS+satellite combine.

Would you give me some advice how to solve this problem,thanks a lot


Gaohua 
All my wishes

发送自 Windows 10 版邮件应用



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

Subject: mode tool read forecast and obs data error
From: John Halley Gotway
Time: Thu Dec 05 13:10:13 2019

Gaohua,

I apologize for the delay in responding to your questions.  I see that
you
sent me 2 files:

(1) cmorph_20191116_06_d02.nc is a NetCDF file that was converted from
GRIB
to NetCDF using NCL.  This file does not follow the NetCDF CF (climate
forecast) conventions and it is a not a NetCDF file created by another
MET
tool.  So MET is unable to read it.  But you can definitely run the
original GRIB file through MET instead.  It should understand that
just
fine.

(2) rmaps_d02_4cmorph_2019111606_order.nc is also not a CF-compliant
NetCDF
file and doesn't follow any of the other NetCDF conventions that MET
knows
about.  But it does look like you attempted to make this look like the
output from another MET tool.

Here are some options.  You could either change the format of these
NetCDF
files to enable MET to read them.  Or you could write a python wrapper
script and use python embedding to read this data into MET.  Examples
of
this can be found on this page:

https://dtcenter.org/community-code/model-evaluation-tools-met/sample-
analysis-scripts

If you have full control over these file formats, I do think it'd be
simpler in the long run to modify that format instead of using python
embedding.  If you do not have control over these file formats, then
using
python embedding would also work.

Thanks,
John




On Mon, Dec 2, 2019 at 9:36 AM The RT System itself via RT <
met_help at ucar.edu> wrote:

>
> Mon Dec 02 09:35:33 2019: Request 93257 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>        Queue: met_help
>      Subject: mode tool read forecast and obs data error
>        Owner: johnhg
>   Requestors: hgao at ium.cn
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93257 >
>
>
> This transaction appears to have no content
>

------------------------------------------------
Subject: 答复: [rt.rap.ucar.edu #93257] mode tool read forecast and obs data error
From: hgao
Time: Fri Dec 06 03:00:30 2019

John,
Thank you so much for your attention,I will follow your suggest.

My best wishes
Gaohua

-----邮件原件-----
发件人: John Halley Gotway via RT [mailto:met_help at ucar.edu]
发送时间: 2019年12月6日 4:10
收件人: hgao at ium.cn
主题: Re: [rt.rap.ucar.edu #93257] mode tool read forecast and obs data
error

Gaohua,

I apologize for the delay in responding to your questions.  I see that
you sent me 2 files:

(1) cmorph_20191116_06_d02.nc is a NetCDF file that was converted from
GRIB to NetCDF using NCL.  This file does not follow the NetCDF CF
(climate
forecast) conventions and it is a not a NetCDF file created by another
MET tool.  So MET is unable to read it.  But you can definitely run
the original GRIB file through MET instead.  It should understand that
just fine.

(2) rmaps_d02_4cmorph_2019111606_order.nc is also not a CF-compliant
NetCDF file and doesn't follow any of the other NetCDF conventions
that MET knows about.  But it does look like you attempted to make
this look like the output from another MET tool.

Here are some options.  You could either change the format of these
NetCDF files to enable MET to read them.  Or you could write a python
wrapper script and use python embedding to read this data into MET.
Examples of this can be found on this page:

https://dtcenter.org/community-code/model-evaluation-tools-met/sample-
analysis-scripts

If you have full control over these file formats, I do think it'd be
simpler in the long run to modify that format instead of using python
embedding.  If you do not have control over these file formats, then
using python embedding would also work.

Thanks,
John




On Mon, Dec 2, 2019 at 9:36 AM The RT System itself via RT <
met_help at ucar.edu> wrote:

>
> Mon Dec 02 09:35:33 2019: Request 93257 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>        Queue: met_help
>      Subject: mode tool read forecast and obs data error
>        Owner: johnhg
>   Requestors: hgao at ium.cn
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93257
> >
>
>
> This transaction appears to have no content
>



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