[Met_help] [rt.rap.ucar.edu #83548] History for A issue with MET, thanks
Julie Prestopnik via RT
met_help at ucar.edu
Tue Jan 16 09:26:02 MST 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MET supporter,
I am a user of MET and recently I started using MET to verify some results
in New Zealand, however I noticed that MET cannot read the WRF output
right, here is an attached example from plot_data_plane and seems the
entire dataset got read upside-down ~ to me the same thing happens to other
MET applications as well.
May I kindly ask if I need to do something special to deal with the data
from south-hemisphere (or netcdf) ? (or probably I missed some
configurations in MET ?). I attached my WRF out which is written out from
wrf_interp, and the graph from plot_data_plane
Thanks a lot for your help !
Regards, Sijin
wrfout link:
https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-gDAt3E
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: A issue with MET, thanks
From: Julie Prestopnik
Time: Thu Jan 11 09:31:07 2018
Hello Sijin.
Unfortunately, MET does not read the NetCDF output of WRF directly.
There
are two main issues here. First, wrfout files are on hybrid pressure
levels in the vertical, and second, some of the output variables are
defined on a staggered grid. Some sort of post-processing is required
prior to verifying this data in MET.
You have two options. The wrf_interp utility is reads WRF-ARW output
and
converts from hybrid vertical levels to pressure levels. MET is able
to
read the output of wrf_interp, but only variables defined on the
non-staggered dimension. So temperatures are fine, but not winds.
The second option is running unified postprocessor (UPP). It reads
WRF-ARW
and WRF-NMM, interpolates to pressure levels, computes many derived
variables, and can interpolate to whatever output grid you'd like.
It's
output is GRIB1 or GRIB2 which MET can easily read. For these
reasons, we
recommend using UPP instead of wrf_interp.
If you're able to, please try using UPP to post process the WRF data.
That
should resolve the problem you are experiencing.
Thanks,
Julie
On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT
<met_help at ucar.edu>
wrote:
>
> Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> Transaction: Ticket created by zsjzyhzp at gmail.com
> Queue: met_help
> Subject: A issue with MET, thanks
> Owner: Nobody
> Requestors: zsjzyhzp at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
>
>
> Dear MET supporter,
>
> I am a user of MET and recently I started using MET to verify some
results
> in New Zealand, however I noticed that MET cannot read the WRF
output
> right, here is an attached example from plot_data_plane and seems
the
> entire dataset got read upside-down ~ to me the same thing happens
to other
> MET applications as well.
>
> May I kindly ask if I need to do something special to deal with the
data
> from south-hemisphere (or netcdf) ? (or probably I missed some
> configurations in MET ?). I attached my WRF out which is written out
from
> wrf_interp, and the graph from plot_data_plane
>
> Thanks a lot for your help !
>
> Regards, Sijin
>
> wrfout link:
> https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-gDAt3E
>
>
------------------------------------------------
Subject: A issue with MET, thanks
From: Zhang Sijin
Time: Thu Jan 11 15:06:45 2018
Hello Julie,
Thanks a lot for your quick reply
Actually the wrfout I sent over last time was already from wrf_interp,
and
the reason we tried this was because the outputs from UPP do not give
us
the right answer as well ~ here is the UPP grib attached and the plots
from
plot_data_plane, seems the wrfout gets shifted by MET to somewhere
unknown.
I used MET for other places before and seems they all good, but not
sure
why this WRF has issues with MET.
Thanks a lot for your time and I really appreciate your help !
Regards, Sijin
On 12 January 2018 at 05:31, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hello Sijin.
>
> Unfortunately, MET does not read the NetCDF output of WRF directly.
There
> are two main issues here. First, wrfout files are on hybrid
pressure
> levels in the vertical, and second, some of the output variables are
> defined on a staggered grid. Some sort of post-processing is
required
> prior to verifying this data in MET.
>
> You have two options. The wrf_interp utility is reads WRF-ARW
output and
> converts from hybrid vertical levels to pressure levels. MET is
able to
> read the output of wrf_interp, but only variables defined on the
> non-staggered dimension. So temperatures are fine, but not winds.
>
> The second option is running unified postprocessor (UPP). It reads
WRF-ARW
> and WRF-NMM, interpolates to pressure levels, computes many derived
> variables, and can interpolate to whatever output grid you'd like.
It's
> output is GRIB1 or GRIB2 which MET can easily read. For these
reasons, we
> recommend using UPP instead of wrf_interp.
>
> If you're able to, please try using UPP to post process the WRF
data. That
> should resolve the problem you are experiencing.
>
> Thanks,
> Julie
>
> On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> > Transaction: Ticket created by zsjzyhzp at gmail.com
> > Queue: met_help
> > Subject: A issue with MET, thanks
> > Owner: Nobody
> > Requestors: zsjzyhzp at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
> >
> >
> > Dear MET supporter,
> >
> > I am a user of MET and recently I started using MET to verify some
> results
> > in New Zealand, however I noticed that MET cannot read the WRF
output
> > right, here is an attached example from plot_data_plane and seems
the
> > entire dataset got read upside-down ~ to me the same thing happens
to
> other
> > MET applications as well.
> >
> > May I kindly ask if I need to do something special to deal with
the data
> > from south-hemisphere (or netcdf) ? (or probably I missed some
> > configurations in MET ?). I attached my WRF out which is written
out from
> > wrf_interp, and the graph from plot_data_plane
> >
> > Thanks a lot for your help !
> >
> > Regards, Sijin
> >
> > wrfout link:
> > https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-gDAt3E
> >
> >
>
>
------------------------------------------------
Subject: A issue with MET, thanks
From: Julie Prestopnik
Time: Thu Jan 11 15:32:40 2018
My apologies for the miscommunication. I believe that the data in the
input file is packed upside down.
met-6.0 should be able to handle the issue and turn the world back
right
side up.
What version of MET are you using?
Thanks,
Julie
On Thu, Jan 11, 2018 at 3:06 PM, Zhang Sijin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
>
> Hello Julie,
>
> Thanks a lot for your quick reply
>
> Actually the wrfout I sent over last time was already from
wrf_interp, and
> the reason we tried this was because the outputs from UPP do not
give us
> the right answer as well ~ here is the UPP grib attached and the
plots from
> plot_data_plane, seems the wrfout gets shifted by MET to somewhere
unknown.
>
> I used MET for other places before and seems they all good, but not
sure
> why this WRF has issues with MET.
>
> Thanks a lot for your time and I really appreciate your help !
>
> Regards, Sijin
>
>
>
>
>
>
>
>
> On 12 January 2018 at 05:31, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
>
> > Hello Sijin.
> >
> > Unfortunately, MET does not read the NetCDF output of WRF
directly.
> There
> > are two main issues here. First, wrfout files are on hybrid
pressure
> > levels in the vertical, and second, some of the output variables
are
> > defined on a staggered grid. Some sort of post-processing is
required
> > prior to verifying this data in MET.
> >
> > You have two options. The wrf_interp utility is reads WRF-ARW
output and
> > converts from hybrid vertical levels to pressure levels. MET is
able to
> > read the output of wrf_interp, but only variables defined on the
> > non-staggered dimension. So temperatures are fine, but not winds.
> >
> > The second option is running unified postprocessor (UPP). It
reads
> WRF-ARW
> > and WRF-NMM, interpolates to pressure levels, computes many
derived
> > variables, and can interpolate to whatever output grid you'd like.
It's
> > output is GRIB1 or GRIB2 which MET can easily read. For these
reasons,
> we
> > recommend using UPP instead of wrf_interp.
> >
> > If you're able to, please try using UPP to post process the WRF
data.
> That
> > should resolve the problem you are experiencing.
> >
> > Thanks,
> > Julie
> >
> > On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> > > Transaction: Ticket created by zsjzyhzp at gmail.com
> > > Queue: met_help
> > > Subject: A issue with MET, thanks
> > > Owner: Nobody
> > > Requestors: zsjzyhzp at gmail.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548
> >
> > >
> > >
> > > Dear MET supporter,
> > >
> > > I am a user of MET and recently I started using MET to verify
some
> > results
> > > in New Zealand, however I noticed that MET cannot read the WRF
output
> > > right, here is an attached example from plot_data_plane and
seems the
> > > entire dataset got read upside-down ~ to me the same thing
happens to
> > other
> > > MET applications as well.
> > >
> > > May I kindly ask if I need to do something special to deal with
the
> data
> > > from south-hemisphere (or netcdf) ? (or probably I missed some
> > > configurations in MET ?). I attached my WRF out which is written
out
> from
> > > wrf_interp, and the graph from plot_data_plane
> > >
> > > Thanks a lot for your help !
> > >
> > > Regards, Sijin
> > >
> > > wrfout link:
> > > https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-
gDAt3E
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: A issue with MET, thanks
From: Zhang Sijin
Time: Thu Jan 11 15:56:02 2018
Hi Julie,
I am using the version of 6.0. Thanks
Sijin
On 12 January 2018 at 11:32, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> My apologies for the miscommunication. I believe that the data in
the
> input file is packed upside down.
>
> met-6.0 should be able to handle the issue and turn the world back
right
> side up.
>
> What version of MET are you using?
>
> Thanks,
> Julie
>
> On Thu, Jan 11, 2018 at 3:06 PM, Zhang Sijin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
> >
> > Hello Julie,
> >
> > Thanks a lot for your quick reply
> >
> > Actually the wrfout I sent over last time was already from
wrf_interp,
> and
> > the reason we tried this was because the outputs from UPP do not
give us
> > the right answer as well ~ here is the UPP grib attached and the
plots
> from
> > plot_data_plane, seems the wrfout gets shifted by MET to somewhere
> unknown.
> >
> > I used MET for other places before and seems they all good, but
not sure
> > why this WRF has issues with MET.
> >
> > Thanks a lot for your time and I really appreciate your help !
> >
> > Regards, Sijin
> >
> >
> >
> >
> >
> >
> >
> >
> > On 12 January 2018 at 05:31, Julie Prestopnik via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hello Sijin.
> > >
> > > Unfortunately, MET does not read the NetCDF output of WRF
directly.
> > There
> > > are two main issues here. First, wrfout files are on hybrid
pressure
> > > levels in the vertical, and second, some of the output variables
are
> > > defined on a staggered grid. Some sort of post-processing is
required
> > > prior to verifying this data in MET.
> > >
> > > You have two options. The wrf_interp utility is reads WRF-ARW
output
> and
> > > converts from hybrid vertical levels to pressure levels. MET is
able
> to
> > > read the output of wrf_interp, but only variables defined on the
> > > non-staggered dimension. So temperatures are fine, but not
winds.
> > >
> > > The second option is running unified postprocessor (UPP). It
reads
> > WRF-ARW
> > > and WRF-NMM, interpolates to pressure levels, computes many
derived
> > > variables, and can interpolate to whatever output grid you'd
like. It's
> > > output is GRIB1 or GRIB2 which MET can easily read. For these
reasons,
> > we
> > > recommend using UPP instead of wrf_interp.
> > >
> > > If you're able to, please try using UPP to post process the WRF
data.
> > That
> > > should resolve the problem you are experiencing.
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT
<met_help at ucar.edu
> >
> > > wrote:
> > >
> > > >
> > > > Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> > > > Transaction: Ticket created by zsjzyhzp at gmail.com
> > > > Queue: met_help
> > > > Subject: A issue with MET, thanks
> > > > Owner: Nobody
> > > > Requestors: zsjzyhzp at gmail.com
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83548
> > >
> > > >
> > > >
> > > > Dear MET supporter,
> > > >
> > > > I am a user of MET and recently I started using MET to verify
some
> > > results
> > > > in New Zealand, however I noticed that MET cannot read the WRF
output
> > > > right, here is an attached example from plot_data_plane and
seems the
> > > > entire dataset got read upside-down ~ to me the same thing
happens to
> > > other
> > > > MET applications as well.
> > > >
> > > > May I kindly ask if I need to do something special to deal
with the
> > data
> > > > from south-hemisphere (or netcdf) ? (or probably I missed some
> > > > configurations in MET ?). I attached my WRF out which is
written out
> > from
> > > > wrf_interp, and the graph from plot_data_plane
> > > >
> > > > Thanks a lot for your help !
> > > >
> > > > Regards, Sijin
> > > >
> > > > wrfout link:
> > > > https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-
gDAt3E
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: A issue with MET, thanks
From: Julie Prestopnik
Time: Thu Jan 11 22:42:18 2018
Hi Sijin. Thank you for letting me know you are using met-6.1.
I have attached a file, wrfout.ps. New Zealand appears to be in the
correct place now. Please take a look and see if that looks accurate.
I produced this image by running the following:
plot_data_plane wrfout.nc wrfout.ps 'name="T2"; level="(0,*,*)";
file_type=NETCDF_PINT;'
Please note "file_type" at the end. The "file_type" entry specifies
the
input file type rather than letting the code determine ithe type
itself. I
added NETCDF_PINT to let MET know that it was a NetCDF file from
pinterp,
or wrf_interp, and that seemed to work.
Julie
On Thu, Jan 11, 2018 at 3:56 PM, Zhang Sijin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
>
> Hi Julie,
>
> I am using the version of 6.0. Thanks
>
> Sijin
>
> On 12 January 2018 at 11:32, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
>
> > My apologies for the miscommunication. I believe that the data in
the
> > input file is packed upside down.
> >
> > met-6.0 should be able to handle the issue and turn the world back
right
> > side up.
> >
> > What version of MET are you using?
> >
> > Thanks,
> > Julie
> >
> > On Thu, Jan 11, 2018 at 3:06 PM, Zhang Sijin via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
> > >
> > > Hello Julie,
> > >
> > > Thanks a lot for your quick reply
> > >
> > > Actually the wrfout I sent over last time was already from
wrf_interp,
> > and
> > > the reason we tried this was because the outputs from UPP do not
give
> us
> > > the right answer as well ~ here is the UPP grib attached and the
plots
> > from
> > > plot_data_plane, seems the wrfout gets shifted by MET to
somewhere
> > unknown.
> > >
> > > I used MET for other places before and seems they all good, but
not
> sure
> > > why this WRF has issues with MET.
> > >
> > > Thanks a lot for your time and I really appreciate your help !
> > >
> > > Regards, Sijin
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 12 January 2018 at 05:31, Julie Prestopnik via RT <
> met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hello Sijin.
> > > >
> > > > Unfortunately, MET does not read the NetCDF output of WRF
directly.
> > > There
> > > > are two main issues here. First, wrfout files are on hybrid
pressure
> > > > levels in the vertical, and second, some of the output
variables are
> > > > defined on a staggered grid. Some sort of post-processing is
> required
> > > > prior to verifying this data in MET.
> > > >
> > > > You have two options. The wrf_interp utility is reads WRF-ARW
output
> > and
> > > > converts from hybrid vertical levels to pressure levels. MET
is able
> > to
> > > > read the output of wrf_interp, but only variables defined on
the
> > > > non-staggered dimension. So temperatures are fine, but not
winds.
> > > >
> > > > The second option is running unified postprocessor (UPP). It
reads
> > > WRF-ARW
> > > > and WRF-NMM, interpolates to pressure levels, computes many
derived
> > > > variables, and can interpolate to whatever output grid you'd
like.
> It's
> > > > output is GRIB1 or GRIB2 which MET can easily read. For these
> reasons,
> > > we
> > > > recommend using UPP instead of wrf_interp.
> > > >
> > > > If you're able to, please try using UPP to post process the
WRF data.
> > > That
> > > > should resolve the problem you are experiencing.
> > > >
> > > > Thanks,
> > > > Julie
> > > >
> > > > On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT <
> met_help at ucar.edu
> > >
> > > > wrote:
> > > >
> > > > >
> > > > > Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> > > > > Transaction: Ticket created by zsjzyhzp at gmail.com
> > > > > Queue: met_help
> > > > > Subject: A issue with MET, thanks
> > > > > Owner: Nobody
> > > > > Requestors: zsjzyhzp at gmail.com
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=83548
> > > >
> > > > >
> > > > >
> > > > > Dear MET supporter,
> > > > >
> > > > > I am a user of MET and recently I started using MET to
verify some
> > > > results
> > > > > in New Zealand, however I noticed that MET cannot read the
WRF
> output
> > > > > right, here is an attached example from plot_data_plane and
seems
> the
> > > > > entire dataset got read upside-down ~ to me the same thing
happens
> to
> > > > other
> > > > > MET applications as well.
> > > > >
> > > > > May I kindly ask if I need to do something special to deal
with the
> > > data
> > > > > from south-hemisphere (or netcdf) ? (or probably I missed
some
> > > > > configurations in MET ?). I attached my WRF out which is
written
> out
> > > from
> > > > > wrf_interp, and the graph from plot_data_plane
> > > > >
> > > > > Thanks a lot for your help !
> > > > >
> > > > > Regards, Sijin
> > > > >
> > > > > wrfout link:
> > > > > https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-
gDAt3E
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: A issue with MET, thanks
From: Zhang Sijin
Time: Tue Jan 16 02:31:18 2018
Hi Julie,
Thanks for your quick reply, sorry I have been out of my office and
away
from my computer for the most of days this week, and just got an
opportunity to try your solution and seems the plots are good after
adding
the additional term like you suggested ! Thanks a lot for your help
again !
Regards, Sijin
On 12 January 2018 at 18:42, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Sijin. Thank you for letting me know you are using met-6.1.
>
> I have attached a file, wrfout.ps. New Zealand appears to be in
the
> correct place now. Please take a look and see if that looks
accurate.
>
> I produced this image by running the following:
>
> plot_data_plane wrfout.nc wrfout.ps 'name="T2"; level="(0,*,*)";
> file_type=NETCDF_PINT;'
>
> Please note "file_type" at the end. The "file_type" entry specifies
the
> input file type rather than letting the code determine ithe type
itself. I
> added NETCDF_PINT to let MET know that it was a NetCDF file from
pinterp,
> or wrf_interp, and that seemed to work.
>
> Julie
>
> On Thu, Jan 11, 2018 at 3:56 PM, Zhang Sijin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548 >
> >
> > Hi Julie,
> >
> > I am using the version of 6.0. Thanks
> >
> > Sijin
> >
> > On 12 January 2018 at 11:32, Julie Prestopnik via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > My apologies for the miscommunication. I believe that the data
in the
> > > input file is packed upside down.
> > >
> > > met-6.0 should be able to handle the issue and turn the world
back
> right
> > > side up.
> > >
> > > What version of MET are you using?
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Thu, Jan 11, 2018 at 3:06 PM, Zhang Sijin via RT
<met_help at ucar.edu
> >
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83548
>
> > > >
> > > > Hello Julie,
> > > >
> > > > Thanks a lot for your quick reply
> > > >
> > > > Actually the wrfout I sent over last time was already from
> wrf_interp,
> > > and
> > > > the reason we tried this was because the outputs from UPP do
not give
> > us
> > > > the right answer as well ~ here is the UPP grib attached and
the
> plots
> > > from
> > > > plot_data_plane, seems the wrfout gets shifted by MET to
somewhere
> > > unknown.
> > > >
> > > > I used MET for other places before and seems they all good,
but not
> > sure
> > > > why this WRF has issues with MET.
> > > >
> > > > Thanks a lot for your time and I really appreciate your help !
> > > >
> > > > Regards, Sijin
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 12 January 2018 at 05:31, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hello Sijin.
> > > > >
> > > > > Unfortunately, MET does not read the NetCDF output of WRF
directly.
> > > > There
> > > > > are two main issues here. First, wrfout files are on hybrid
> pressure
> > > > > levels in the vertical, and second, some of the output
variables
> are
> > > > > defined on a staggered grid. Some sort of post-processing
is
> > required
> > > > > prior to verifying this data in MET.
> > > > >
> > > > > You have two options. The wrf_interp utility is reads WRF-
ARW
> output
> > > and
> > > > > converts from hybrid vertical levels to pressure levels.
MET is
> able
> > > to
> > > > > read the output of wrf_interp, but only variables defined on
the
> > > > > non-staggered dimension. So temperatures are fine, but not
winds.
> > > > >
> > > > > The second option is running unified postprocessor (UPP).
It reads
> > > > WRF-ARW
> > > > > and WRF-NMM, interpolates to pressure levels, computes many
derived
> > > > > variables, and can interpolate to whatever output grid you'd
like.
> > It's
> > > > > output is GRIB1 or GRIB2 which MET can easily read. For
these
> > reasons,
> > > > we
> > > > > recommend using UPP instead of wrf_interp.
> > > > >
> > > > > If you're able to, please try using UPP to post process the
WRF
> data.
> > > > That
> > > > > should resolve the problem you are experiencing.
> > > > >
> > > > > Thanks,
> > > > > Julie
> > > > >
> > > > > On Wed, Jan 10, 2018 at 7:29 PM, Zhang Sijin via RT <
> > met_help at ucar.edu
> > > >
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > Wed Jan 10 19:29:14 2018: Request 83548 was acted upon.
> > > > > > Transaction: Ticket created by zsjzyhzp at gmail.com
> > > > > > Queue: met_help
> > > > > > Subject: A issue with MET, thanks
> > > > > > Owner: Nobody
> > > > > > Requestors: zsjzyhzp at gmail.com
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=83548
> > > > >
> > > > > >
> > > > > >
> > > > > > Dear MET supporter,
> > > > > >
> > > > > > I am a user of MET and recently I started using MET to
verify
> some
> > > > > results
> > > > > > in New Zealand, however I noticed that MET cannot read the
WRF
> > output
> > > > > > right, here is an attached example from plot_data_plane
and seems
> > the
> > > > > > entire dataset got read upside-down ~ to me the same thing
> happens
> > to
> > > > > other
> > > > > > MET applications as well.
> > > > > >
> > > > > > May I kindly ask if I need to do something special to deal
with
> the
> > > > data
> > > > > > from south-hemisphere (or netcdf) ? (or probably I missed
some
> > > > > > configurations in MET ?). I attached my WRF out which is
written
> > out
> > > > from
> > > > > > wrf_interp, and the graph from plot_data_plane
> > > > > >
> > > > > > Thanks a lot for your help !
> > > > > >
> > > > > > Regards, Sijin
> > > > > >
> > > > > > wrfout link:
> > > > > >
https://drive.google.com/open?id=1S12Y_Ymjro6pEiLcf6RdrLiTk-
> gDAt3E
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list