[Met_help] [rt.rap.ucar.edu #42250] History for rt.rap.ucar.edu #42218

Tue Nov 23 08:57:24 MST 2010

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

Dear sir,

Thank you very much. I think it will solve my purpose. And I will definitely try to run WRF Post processor.

.............................................................

Rekha Bharali Gogoi

Scientist

NE-SAC,GOI,

Dept. of Space,

Umiam,Meghalaya.

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

Subject: rt.rap.ucar.edu #42218
From: rekha bharali
Time: Sun Nov 21 23:03:22 2010

Dear Sir,

Sorry for troubling you again and again. As your suggestion I have
mailed to wrfhelp regarding WPP instollation and running. But yet I am
waiting for a reply. In the mean time I tried to run Point-Stat tool
by doing the modification as you told. But again I am facing some
problem with the following error:

./bin/point_stat /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-
09-24_00\:00\:00_PLEV tutorial/out/pb2nc/test.nc
tutorial/config/PointStatConfig_test -outdir tutorial/out/point_stat
-v 2
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=18446744073105566028
Forecast File: /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-09-
24_00:00:00_PLEV
Climatology File: none
Configuration File: tutorial/config/PointStatConfig_test
Observation File: tutorial/out/pb2nc/test.nc

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

Reading records for TT(0,5,*,*).

ERROR: read_levels_pinterp() -> no range specified for parsing
TT(0,5,*,*) from the p_interp NetCDF file
/root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-09-24_00:00:00_PLEV

Actually my problem is, I could not understand how to explicitly
specify in the configuration file the names and dimensions of the
NetCDF variables to be read. I read the User Guide several times to
understand the format of var_name(i,...,j,*,*). But I don't get
anything.

Please help
.............................................................

Rekha Bharali Gogoi

Scientist

NE-SAC,GOI,

Dept. of Space,

Umiam,Meghalaya.

--- On Fri, 19/11/10, RAL HelpDesk {for Paul Oldenburg}
<met_help at ucar.edu> wrote:

From: RAL HelpDesk {for Paul Oldenburg} <met_help at ucar.edu>
Subject: [rt.rap.ucar.edu #42250] Resolved: rt.rap.ucar.edu #42218
To: rekha_tu at yahoo.co.in
Date: Friday, 19 November, 2010, 11:31 PM

According to our records, your request has been resolved. If you have
any
further questions or concerns, please respond to this message.

------------------------------------------------
Subject: rt.rap.ucar.edu #42218
From: John Halley Gotway
Time: Mon Nov 22 11:37:24 2010

Rekha,

Thank you for pointing out this problem in reading the output from the
p_interp tool.  It has exposed a bug in the MET code.  It actually has
exposed two problems in MET:

(1) In reading the data for the "TT" variable, we found a bug that
Point-Stat was expecting to find a range of pressure levels to be
verified rather than just a single one - like you were requesting
in your config file.  We've modified a single source file to enable
the verification of a single level.  Please replace the file
"METv3.0/lib/vx_met_util/read_gridded_data.cc" with the attached
version of that file.

(2) We found a second problem in reading the fields for variables UU
and VV.  The problem is that MET isn't accounting for the stagger of
the U and V wind fields in the p_interp output.  I was able to
make some small changes so that Point-Stat could read these fields BUT
it is not a great fix.  It basically assumes that there really is no
stagger and places the winds in the same location as the
mass points.  We'll need to work with the p_interp folks to discuss
how we should add support for these staggered fields, but in the
short-term, if you'd like to just get MET running, you can use the
attached fixes.  Please replace the files
"METv3.0/lib/vx_gdata/pinterp_file.cc and .h" with the attached
versions of those files.

Please be aware that this is not a permanent fix.  Hopefully, we'll be
able to come up with a better way to handle the staggered data, but it
may take some time.

Once you've applied these patched files, please go to the top-level
METv3.0 directory and execute a "make clean" followed by a "make".

Thanks,
John Halley Gotway
met_help at ucar.edu

On 11/21/2010 11:03 PM, RAL HelpDesk {for rekha bharali} wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42250 >
>
> Dear Sir,
>
> Sorry for troubling you again and again. As your suggestion I have
mailed to wrfhelp regarding WPP instollation and running. But yet I am
waiting for a reply. In the mean time I tried to run Point-Stat tool
by doing the modification as you told. But again I am facing some
problem with the following error:
>
> ./bin/point_stat /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-
09-24_00\:00\:00_PLEV tutorial/out/pb2nc/test.nc
tutorial/config/PointStatConfig_test -outdir tutorial/out/point_stat
-v 2
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=18446744073105566028
> Forecast File: /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-
09-24_00:00:00_PLEV
> Climatology File: none
> Configuration File: tutorial/config/PointStatConfig_test
> Observation File: tutorial/out/pb2nc/test.nc
>
>
--------------------------------------------------------------------------------
>
> Reading records for TT(0,5,*,*).
>
>
> ERROR: read_levels_pinterp() -> no range specified for parsing
TT(0,5,*,*) from the p_interp NetCDF file
/root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-09-24_00:00:00_PLEV
>
> Actually my problem is, I could not understand how to explicitly
specify in the configuration file the names and dimensions of the
NetCDF variables to be read. I read the User Guide several times to
understand the format of var_name(i,...,j,*,*). But I don't get
anything.
>
> Please help
> .............................................................
>
> Rekha Bharali Gogoi
>
> Scientist
>
> NE-SAC,GOI,
>
> Dept. of Space,
>
> Umiam,Meghalaya.
>
> --- On Fri, 19/11/10, RAL HelpDesk {for Paul Oldenburg}
<met_help at ucar.edu> wrote:
>
> From: RAL HelpDesk {for Paul Oldenburg} <met_help at ucar.edu>
> Subject: [rt.rap.ucar.edu #42250] Resolved: rt.rap.ucar.edu #42218
> To: rekha_tu at yahoo.co.in
> Date: Friday, 19 November, 2010, 11:31 PM
>
> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.
>
>
>

------------------------------------------------
Subject: rt.rap.ucar.edu #42218
From: rekha bharali
Time: Mon Nov 22 23:07:59 2010

Dear Sir

Thanks a lot. I have tried with all the files given by you and it runs
well. And the other good thing is I have downloaded the latest WPP and
installed as well as execute it successfully. Without any problem I am
able to run MET with the GRIB output from WPP. Thank you so much.

With regards

.............................................................

Rekha Bharali Gogoi

Scientist

NE-SAC,GOI,

Dept. of Space,

Umiam,Meghalaya.

--- On Tue, 23/11/10, RAL HelpDesk {for John Halley Gotway}
<met_help at ucar.edu> wrote:

From: RAL HelpDesk {for John Halley Gotway} <met_help at ucar.edu>
Subject: Re: [rt.rap.ucar.edu #42250]
To: rekha_tu at yahoo.co.in
Cc: bullock at ucar.edu
Date: Tuesday, 23 November, 2010, 12:07 AM

Rekha,

Thank you for pointing out this problem in reading the output from the
p_interp tool.  It has exposed a bug in the MET code.  It actually has
exposed two problems in MET:

(1) In reading the data for the "TT" variable, we found a bug that
Point-Stat was expecting to find a range of pressure levels to be
verified rather than just a single one - like you were requesting
in your config file.  We've modified a single source file to enable
the verification of a single level.  Please replace the file
"METv3.0/lib/vx_met_util/read_gridded_data.cc" with the attached
version of that file.

(2) We found a second problem in reading the fields for variables UU
and VV.  The problem is that MET isn't accounting for the stagger of
the U and V wind fields in the p_interp output.  I was able to
make some small changes so that Point-Stat could read these fields BUT
it is not a great fix.  It basically assumes that there really is no
stagger and places the winds in the same location as the
mass points.  We'll need to work with the p_interp folks to discuss
how we should add support for these staggered fields, but in the
short-term, if you'd like to just get MET running, you can use the
attached fixes.  Please replace the files
"METv3.0/lib/vx_gdata/pinterp_file.cc and .h" with the attached
versions of those files.

Please be aware that this is not a permanent fix.  Hopefully, we'll be
able to come up with a better way to handle the staggered data, but it
may take some time.

Once you've applied these patched files, please go to the top-level
METv3.0 directory and execute a "make clean" followed by a "make".

Thanks,
John Halley Gotway
met_help at ucar.edu

On 11/21/2010 11:03 PM, RAL HelpDesk {for rekha bharali} wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42250 >
>
> Dear Sir,
>
> Sorry for troubling you again and again. As your suggestion I have
mailed to wrfhelp regarding WPP instollation and running. But yet I am
waiting for a reply. In the mean time I tried to run Point-Stat tool
by doing the modification as you told. But again I am facing some
problem with the following error:
>
> ./bin/point_stat /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-
09-24_00\:00\:00_PLEV tutorial/out/pb2nc/test.nc
tutorial/config/PointStatConfig_test -outdir tutorial/out/point_stat
-v 2
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=18446744073105566028
> Forecast File: /root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-
09-24_00:00:00_PLEV
> Climatology File: none
> Configuration File: tutorial/config/PointStatConfig_test
> Observation File: tutorial/out/pb2nc/test.nc
>
>
--------------------------------------------------------------------------------
>
> Reading records for TT(0,5,*,*).
>
>
> ERROR: read_levels_pinterp() -> no range specified for parsing
TT(0,5,*,*) from the p_interp NetCDF file
/root/Desktop/WRF_desktop/P_INTERP/wrfout_d01_2010-09-24_00:00:00_PLEV
>
> Actually my problem is, I could not understand how to explicitly
specify in the configuration file the names and dimensions of the
NetCDF variables to be read. I read the User Guide several times to
understand the format of var_name(i,...,j,*,*). But I don't get
anything.
>
> Please help
> .............................................................
>
> Rekha Bharali Gogoi
>
> Scientist
>
> NE-SAC,GOI,
>
> Dept. of Space,
>
> Umiam,Meghalaya.
>
> --- On Fri, 19/11/10, RAL HelpDesk {for Paul Oldenburg}
<met_help at ucar.edu> wrote:
>
> From: RAL HelpDesk {for Paul Oldenburg} <met_help at ucar.edu>
> Subject: [rt.rap.ucar.edu #42250] Resolved: rt.rap.ucar.edu #42218
> To: rekha_tu at yahoo.co.in
> Date: Friday, 19 November, 2010, 11:31 PM
>
> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.
>
>
>

-----Inline Attachment Follows-----

-----Inline Attachment Follows-----

-----Inline Attachment Follows-----

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