[Met_help] [rt.rap.ucar.edu #84436] History for MODEConfig_default

Mon Apr 9 08:57:06 MDT 2018

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

Sir:

    Here are my question,

    An error appeared when running MODE with a test file in NetCDF format,

    It seems that the NetCDF file cannot be read correctly. While the nc file was written refereced to an standard GRIB file output from UPP.

    So I'm wondering the reason.
    The NetCDF file and MODEConig file are in the accessory.
    Thank you very much!

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

Subject: MODEConfig_default
From: Julie Prestopnik
Time: Fri Mar 16 09:25:33 2018

Hello.  I see that you are encountering a problem with MODE reading
your
NetCDF file.

MET supports a few flavors of NetCDF...
 - Gridded NetCDF files following the CF-convention
 - Gridded NetCDF output of the WRF p_interp / wrf_interp utility
 - Internal MET formatted NetCDF file

When you pass MET a NetCDF file, it inspects the file to determine its
type.  If it's not CF-compliant or a p_interp / wrf_interp file, MET
assumes it's the 3rd type.  The 3rd type is basically just the output
of
pcp_combine tool.

I have attached a sample input file that is the output of pcp_combine,
so
that you can take a look.

I hope this is helpful.  Please let us know if you have any other
questions.

Julie

On Thu, Mar 15, 2018 at 10:15 PM, Zhuang from Nuist via RT <
met_help at ucar.edu> wrote:

>
> Thu Mar 15 22:15:54 2018: Request 84436 was acted upon.
> Transaction: Ticket created by zxrxz3212009 at 163.com
>        Queue: met_help
>      Subject: MODEConfig_default
>        Owner: Nobody
>   Requestors: zxrxz3212009 at 163.com
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84436 >
>
>
> Sir:
>
>     Here are my question,
>
>     An error appeared when running MODE with a test file in NetCDF
format,
>
>
>
>     It seems that the NetCDF file cannot be read correctly. While
the nc
> file was written refereced to an standard GRIB file output from UPP.
>
>     So I'm wondering the reason.
>     The NetCDF file and MODEConig file are in the accessory.
>     Thank you very much!
>

------------------------------------------------
Subject: MODEConfig_default
From: Zhuang from Nuist
Time: Thu Mar 22 09:21:42 2018

Sir:
    Thanks for your kindly reply.
    Due to my recent attempt, new gridded NetCDF file converted from
wrfout file using CDO (e.g. cdo -r -f nc selvar,RAINC  wrfout_d02_**
wrfout_new, However, 'Times' variable cannot be dealed with CDO) can
be successfully read by MET like MODE.
    But when it comes to MTD, such files above cannot be  recognized
due to failure determined the valid time

   Is there any approach to solve this issure?  Any better way to
convert the original wrfout files to standard input NetCDF format for
MET?
  I've tried UPP to convert wrfout files to grb format, which can be
directly read by MET, But unfortunately, UPP cannot deal with missing
value for variable in original wrfout file, that why I'm tring to
figure out how to directly use converted nc files as input for MTD.
  Thank u very much! I'm looking forward to your reply.

At 2018-03-16 23:25:34, "Julie Prestopnik via RT" <met_help at ucar.edu>
wrote:
>Hello.  I see that you are encountering a problem with MODE reading
your
>NetCDF file.
>
>MET supports a few flavors of NetCDF...
> - Gridded NetCDF files following the CF-convention
> - Gridded NetCDF output of the WRF p_interp / wrf_interp utility
> - Internal MET formatted NetCDF file
>
>When you pass MET a NetCDF file, it inspects the file to determine
its
>type.  If it's not CF-compliant or a p_interp / wrf_interp file, MET
>assumes it's the 3rd type.  The 3rd type is basically just the output
of
>pcp_combine tool.
>
>I have attached a sample input file that is the output of
pcp_combine, so
>that you can take a look.
>
>I hope this is helpful.  Please let us know if you have any other
questions.
>
>Julie
>
>On Thu, Mar 15, 2018 at 10:15 PM, Zhuang from Nuist via RT <
>met_help at ucar.edu> wrote:
>
>>
>> Thu Mar 15 22:15:54 2018: Request 84436 was acted upon.
>> Transaction: Ticket created by zxrxz3212009 at 163.com
>>        Queue: met_help
>>      Subject: MODEConfig_default
>>        Owner: Nobody
>>   Requestors: zxrxz3212009 at 163.com
>>       Status: new
>>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84436 >
>>
>>
>> Sir:
>>
>>     Here are my question,
>>
>>     An error appeared when running MODE with a test file in NetCDF
format,
>>
>>
>>
>>     It seems that the NetCDF file cannot be read correctly. While
the nc
>> file was written refereced to an standard GRIB file output from
UPP.
>>
>>     So I'm wondering the reason.
>>     The NetCDF file and MODEConig file are in the accessory.
>>     Thank you very much!
>>
>

------------------------------------------------
Subject: MODEConfig_default
From: Julie Prestopnik
Time: Fri Mar 23 15:02:05 2018

While MODE may have been able to read the data, the timing info won't
accurate in the MET output files. Instead, you'll see "19700101" which
is
unixtime = 0.

I suspect that the time in your file is not specified in a CF-
compliant
way. I would suggest making your file more CF-compliant.  Information
for
the CF coordinate time convention can be found here:
http://cfconventions.org/cf-conventions/v1.6.0/cf-
conventions.html#time-coordinate

I am not familiar with CDO so I cannot offer suggestions on how to do
that
using CDO.  We generally suggest using the UPP to output a GRIB file
that
MET can read.  If you are having problems with the UPP not working
well
with missing values for variables, I would suggest writing to UPP
helpdesk (
upp-help at ucar.edu) to get some guidance.

I hope that helps!

Julie

On Thu, Mar 22, 2018 at 9:21 AM, Zhuang from Nuist via RT
<met_help at ucar.edu
> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84436 >
>
> Sir:
>     Thanks for your kindly reply.
>     Due to my recent attempt, new gridded NetCDF file converted from
> wrfout file using CDO (e.g. cdo -r -f nc selvar,RAINC  wrfout_d02_**
> wrfout_new, However, 'Times' variable cannot be dealed with CDO) can
be
> successfully read by MET like MODE.
>     But when it comes to MTD, such files above cannot be  recognized
due
> to failure determined the valid time
>
>    Is there any approach to solve this issure?  Any better way to
convert
> the original wrfout files to standard input NetCDF format for MET?
>   I've tried UPP to convert wrfout files to grb format, which can be
> directly read by MET, But unfortunately, UPP cannot deal with
missing value
> for variable in original wrfout file, that why I'm tring to figure
out how
> to directly use converted nc files as input for MTD.
>   Thank u very much! I'm looking forward to your reply.
>
>
>
>
>
>
>
>
> At 2018-03-16 23:25:34, "Julie Prestopnik via RT"
<met_help at ucar.edu>
> wrote:
> >Hello.  I see that you are encountering a problem with MODE reading
your
> >NetCDF file.
> >
> >MET supports a few flavors of NetCDF...
> > - Gridded NetCDF files following the CF-convention
> > - Gridded NetCDF output of the WRF p_interp / wrf_interp utility
> > - Internal MET formatted NetCDF file
> >
> >When you pass MET a NetCDF file, it inspects the file to determine
its
> >type.  If it's not CF-compliant or a p_interp / wrf_interp file,
MET
> >assumes it's the 3rd type.  The 3rd type is basically just the
output of
> >pcp_combine tool.
> >
> >I have attached a sample input file that is the output of
pcp_combine, so
> >that you can take a look.
> >
> >I hope this is helpful.  Please let us know if you have any other
> questions.
> >
> >Julie
> >
> >On Thu, Mar 15, 2018 at 10:15 PM, Zhuang from Nuist via RT <
> >met_help at ucar.edu> wrote:
> >
> >>
> >> Thu Mar 15 22:15:54 2018: Request 84436 was acted upon.
> >> Transaction: Ticket created by zxrxz3212009 at 163.com
> >>        Queue: met_help
> >>      Subject: MODEConfig_default
> >>        Owner: Nobody
> >>   Requestors: zxrxz3212009 at 163.com
> >>       Status: new
> >>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84436 >
> >>
> >>
> >> Sir:
> >>
> >>     Here are my question,
> >>
> >>     An error appeared when running MODE with a test file in
NetCDF
> format,
> >>
> >>
> >>
> >>     It seems that the NetCDF file cannot be read correctly. While
the nc
> >> file was written refereced to an standard GRIB file output from
UPP.
> >>
> >>     So I'm wondering the reason.
> >>     The NetCDF file and MODEConig file are in the accessory.
> >>     Thank you very much!
> >>
> >
>
>

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