[Met_help] [rt.rap.ucar.edu #97322] History for Problem with forecast file while running mode

Tue Nov 17 10:47:01 MST 2020

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

Hello,

I am trying to use the MODE tool to evaluate model output with Stage-IV
data. I have used nco to extract the total precipitation variables from the
NWP model output and make a *.nc file. But, when I use the MODE command it
gives me the following error:
[image: image.png]
my command: ./bin/mode
 ./MODE_PROCEDURE/WRF413_TesT/AFWA_TOTPRECIP_2018101112_new.nc
./MODE_PROCEDURE/STAGEIV_Test/2018101112_Anl/sum_Stage4_20181011.nc
./MODE_PROCEDURE/MODE_Files_nc/MODEConfig_APCP_WWE
since it is saying that there is some trouble in reading my fcst file, I am
attaching my fcst file also.

It would be great if you could suggest a way to make it work. It seems like
I need to reformat my file, is there any particular way/format to do this?

Bests,
Ummul

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

Subject: Problem with forecast file while running mode
From: John Halley Gotway
Time: Tue Nov 03 08:59:04 2020

Ummul,

The MET tools support only a few flavors of NetCDF file formats,
including:
- those following the climate-forecast (CF) convention, as defined by:
   http://cfconventions.org/cf-conventions/cf-conventions.html
- output from the WRF model that has been post-processed using the
wrf_interp utility.
- NetCDF output created by one of the other MET tools.

In addition, MET can read gridded data in GRIB1 or GRIB2 format. And
it can
also be passed as input using python embedding.

The fact that MODE cannot read your input file has nothing to do with
the
MODE tool itself. All of the MET tools read data using common library
code.
So if one of them can read a gridded data file, you can be pretty
confident
that all of them can.

For this reason, I always recommend that when getting started with a
new
file format, users first run it through MET's plot_data_plane tool.
Once
plot_data_plane is able to read/plot the data at the correct location
on
earth and oriented in the expected way, you know that you've figured
out
the formatting issues.

I would recommend running both of your inputs to MODE through
plot_data_plane first. The chances that running nco utilities on some
NetCDF file will result in one of the 3 NetCDF formats I described
above
are very slim.

If you are running the WRF model by any chance, I'd definitely
recommend
post-processing its output using UPP. That writes GRIB1 or GRIB2
output
files that MET handles very well.

Thanks,
John

On Mon, Nov 2, 2020 at 6:26 PM Ummul Khaira via RT <met_help at ucar.edu>
wrote:

>
> Mon Nov 02 18:25:38 2020: Request 97322 was acted upon.
> Transaction: Ticket created by ummul.khaira at uconn.edu
>        Queue: met_help
>      Subject: Problem with forecast file while running mode
>        Owner: Nobody
>   Requestors: ummul.khaira at uconn.edu
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97322 >
>
>
> Hello,
>
> I am trying to use the MODE tool to evaluate model output with
Stage-IV
> data. I have used nco to extract the total precipitation variables
from the
> NWP model output and make a *.nc file. But, when I use the MODE
command it
> gives me the following error:
> [image: image.png]
> my command: ./bin/mode
>  ./MODE_PROCEDURE/WRF413_TesT/AFWA_TOTPRECIP_2018101112_new.nc
> ./MODE_PROCEDURE/STAGEIV_Test/2018101112_Anl/sum_Stage4_20181011.nc
> ./MODE_PROCEDURE/MODE_Files_nc/MODEConfig_APCP_WWE
> since it is saying that there is some trouble in reading my fcst
file, I am
> attaching my fcst file also.
>
> It would be great if you could suggest a way to make it work. It
seems like
> I need to reformat my file, is there any particular way/format to do
this?
>
> Bests,
> Ummul
>
>

------------------------------------------------
Subject: Problem with forecast file while running mode
From: Ummul Khaira
Time: Wed Nov 04 09:01:01 2020

Thanks for the tip! I'll try that.

Bests,
Ummul

<https://www.avast.com/sig-
email?utm_medium=email&utm_source=link&utm_campaign=sig-
email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-
email?utm_medium=email&utm_source=link&utm_campaign=sig-
email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Nov 3, 2020 at 10:59 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:

> *Message sent from a system outside of UConn.*
>
>
> Ummul,
>
> The MET tools support only a few flavors of NetCDF file formats,
including:
> - those following the climate-forecast (CF) convention, as defined
by:
>    http://cfconventions.org/cf-conventions/cf-conventions.html
> - output from the WRF model that has been post-processed using the
> wrf_interp utility.
> - NetCDF output created by one of the other MET tools.
>
> In addition, MET can read gridded data in GRIB1 or GRIB2 format. And
it can
> also be passed as input using python embedding.
>
> The fact that MODE cannot read your input file has nothing to do
with the
> MODE tool itself. All of the MET tools read data using common
library code.
> So if one of them can read a gridded data file, you can be pretty
confident
> that all of them can.
>
> For this reason, I always recommend that when getting started with a
new
> file format, users first run it through MET's plot_data_plane tool.
Once
> plot_data_plane is able to read/plot the data at the correct
location on
> earth and oriented in the expected way, you know that you've figured
out
> the formatting issues.
>
> I would recommend running both of your inputs to MODE through
> plot_data_plane first. The chances that running nco utilities on
some
> NetCDF file will result in one of the 3 NetCDF formats I described
above
> are very slim.
>
> If you are running the WRF model by any chance, I'd definitely
recommend
> post-processing its output using UPP. That writes GRIB1 or GRIB2
output
> files that MET handles very well.
>
> Thanks,
> John
>
>
> On Mon, Nov 2, 2020 at 6:26 PM Ummul Khaira via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Mon Nov 02 18:25:38 2020: Request 97322 was acted upon.
> > Transaction: Ticket created by ummul.khaira at uconn.edu
> >        Queue: met_help
> >      Subject: Problem with forecast file while running mode
> >        Owner: Nobody
> >   Requestors: ummul.khaira at uconn.edu
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97322 >
> >
> >
> > Hello,
> >
> > I am trying to use the MODE tool to evaluate model output with
Stage-IV
> > data. I have used nco to extract the total precipitation variables
from
> the
> > NWP model output and make a *.nc file. But, when I use the MODE
command
> it
> > gives me the following error:
> > [image: image.png]
> > my command: ./bin/mode
> >  ./MODE_PROCEDURE/WRF413_TesT/AFWA_TOTPRECIP_2018101112_new.nc
> >
./MODE_PROCEDURE/STAGEIV_Test/2018101112_Anl/sum_Stage4_20181011.nc
> > ./MODE_PROCEDURE/MODE_Files_nc/MODEConfig_APCP_WWE
> > since it is saying that there is some trouble in reading my fcst
file, I
> am
> > attaching my fcst file also.
> >
> > It would be great if you could suggest a way to make it work. It
seems
> like
> > I need to reformat my file, is there any particular way/format to
do
> this?
> >
> > Bests,
> > Ummul
> >
> >
>
>

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