[Met_help] [rt.rap.ucar.edu #55584] History for about MODE configuration file
Paul Oldenburg via RT
met_help at ucar.edu
Tue Apr 24 12:12:33 MDT 2012
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: about MODE configuration file
From: 吳小榆
Time: Fri Mar 30 02:47:45 2012
Dear sir,
I used METv3.0.1,
(1) how to set "fcst_field" in the mode configuration file
"WrfModeConfig_APCP_24"?
The forecast file is NetCDF file from pcp_conbine, so i set :
fcst_field = "APCP_24(180,150,lon,lat)";
when i administered mode.sh print the message:
MetNcFile::data(NcVar *, const LongArray &, WrfData &) -> needed 2
arguments for variable APCP_24, got 4
if i set ,
fcst_field = "APCP_24(180,150)";
or
fcst_field = "APCP_24(lat,lon)";
the message was:
MetNcFile::data(NcVar *, const LongArray &, WrfData &) const -> bad
star
count ... 0
if i set,
fcst_field = "APCP_24(*,*)";
the message was:
NetCDF: Attribute not found
Could you explain what do the "data(NcVar *, const LongArray &,
WrfData &)"
and "var_name(i,...,j,*,*)" mean?
(2) Isn't right by the pcp_combine.sh setting?
my pcp_combine.sh setting by :
../bin/pcp_combine \
-subtract ../data/Namandol_fcst/WRFPRS_d03.048 48
../data/Namandol_fcst/WRFPRS_d03.024 24 \
../out/pcp_combine/Namandol_fct_2011082918V_24A.nc \
and
ncdump -h Namandol_fct_2011082918V_24A.nc ,print the message:
float APCP_24(lat, lon) ;
APCP_24:name = "APCP" ;
APCP_24:long_name = "Total precipitation" ;
APCP_24:level = "A24" ;
APCP_24:units = "kg/m^2" ;
APCP_24:grib_code = 61 ;
APCP_24:_FillValue = -9999.f ;
APCP_24:init_time = "20110827_180000" ;
APCP_24:init_time_ut = 1314468000 ;
APCP_24:valid_time = "20110829_180000" ;
APCP_24:valid_time_ut = 1314640800 ;
APCP_24:accum_time = "240000" ;
APCP_24:accum_time_sec = 86400 ;
Thank you very much!
Kate
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #55584]about MODE configuration file and pcp_combine.sh setting
From: Paul Oldenburg
Time: Fri Mar 30 08:51:39 2012
Kate,
To answer question 1, please look at the test script in the scripts
directory under the MET installation folder,
$MET_BASE/scripts/test_mode.sh. This script calls mode using the
output of pcp_combine. You can see in the
configuration files, $MET_BASE/scripts/config/MODEConfig_APCP_12/24,
that the fcst_field and obs_field are specified
like this:
fcst_field = "APCP_24(*,*)";
The reason is that, in the ncdump output you sent, the APCP_24
variable has two dimensions. In MET, the syntax is to
provide a * in the dimensions that you want to use all indexes from.
The answer to question 2 is that your pcp_combine
output looks valid and reasonable. If you have any questions about
this, please let me know.
Paul
On 03/30/2012 02:47 AM, 吳小榆 via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=55584>
>
> Dear sir,
>
> I used METv3.0.1,
> (1) how to set "fcst_field" in the mode configuration file
> "WrfModeConfig_APCP_24"?
>
> The forecast file is NetCDF file from pcp_conbine, so i set :
> fcst_field = "APCP_24(180,150,lon,lat)";
>
> when i administered mode.sh print the message:
> MetNcFile::data(NcVar *, const LongArray&, WrfData&) -> needed 2
> arguments for variable APCP_24, got 4
>
> if i set ,
> fcst_field = "APCP_24(180,150)";
> or
> fcst_field = "APCP_24(lat,lon)";
> the message was:
> MetNcFile::data(NcVar *, const LongArray&, WrfData&) const -> bad
star
> count ... 0
>
> if i set,
> fcst_field = "APCP_24(*,*)";
> the message was:
> NetCDF: Attribute not found
>
> Could you explain what do the "data(NcVar *, const LongArray&,
WrfData&)"
> and "var_name(i,...,j,*,*)" mean?
>
> (2) Isn't right by the pcp_combine.sh setting?
>
> my pcp_combine.sh setting by :
> ../bin/pcp_combine \
> -subtract ../data/Namandol_fcst/WRFPRS_d03.048 48
> ../data/Namandol_fcst/WRFPRS_d03.024 24 \
> ../out/pcp_combine/Namandol_fct_2011082918V_24A.nc \
>
> and
> ncdump -h Namandol_fct_2011082918V_24A.nc ,print the message:
> float APCP_24(lat, lon) ;
> APCP_24:name = "APCP" ;
> APCP_24:long_name = "Total precipitation" ;
> APCP_24:level = "A24" ;
> APCP_24:units = "kg/m^2" ;
> APCP_24:grib_code = 61 ;
> APCP_24:_FillValue = -9999.f ;
> APCP_24:init_time = "20110827_180000" ;
> APCP_24:init_time_ut = 1314468000 ;
> APCP_24:valid_time = "20110829_180000" ;
> APCP_24:valid_time_ut = 1314640800 ;
> APCP_24:accum_time = "240000" ;
> APCP_24:accum_time_sec = 86400 ;
>
>
> Thank you very much!
>
> Kate
------------------------------------------------
Subject: about MODE configuration file
From: 吳小榆
Time: Tue Apr 17 00:26:39 2012
Paul,
Following the MODEConfig_APCP_24 setting:
fcst_field = "APCP_24(*,*)";
When i type './mode.sh' the output message was:
*** Running MODE on APCP using netCDF input for both forecast and
observation ***
DEBUG 1: Default Config File:
/home/joray/tzyu/METv3.1/data/config/MODEConfig_default
DEBUG 1: Match Config File: config/MODEConfig_APCP_24
DEBUG 1: Merge Config File: config/MODEConfig_APCP_24
DEBUG 1: Forecast File:
../out/pcp_combine/NMD_fcst_24L_2011082818V_24A.nc
DEBUG 1: Observation File: ../out/ascii2nc/precip24_2011082818.nc
NetCDF: Attribute not found
I don't know what went wrong?nc files? or setting error? Could you
please
help me to look on the files and setting on the ftp files?
Thank you very much!
Kate
2012/3/30 Paul Oldenburg via RT <met_help at ucar.edu>
> Kate,
>
> To answer question 1, please look at the test script in the scripts
> directory under the MET installation folder,
> $MET_BASE/scripts/test_mode.sh. This script calls mode using the
output
> of pcp_combine. You can see in the
> configuration files, $MET_BASE/scripts/config/MODEConfig_APCP_12/24,
that
> the fcst_field and obs_field are specified
> like this:
>
> fcst_field = "APCP_24(*,*)";
>
> The reason is that, in the ncdump output you sent, the APCP_24
variable
> has two dimensions. In MET, the syntax is to
> provide a * in the dimensions that you want to use all indexes from.
The
> answer to question 2 is that your pcp_combine
> output looks valid and reasonable. If you have any questions about
this,
> please let me know.
>
> Paul
>
>
>
>
> On 03/30/2012 02:47 AM, 吳小榆 via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=55584>
> >
> > Dear sir,
> >
> > I used METv3.0.1,
> > (1) how to set "fcst_field" in the mode configuration file
> > "WrfModeConfig_APCP_24"?
> >
> > The forecast file is NetCDF file from pcp_conbine, so i set :
> > fcst_field = "APCP_24(180,150,lon,lat)";
> >
> > when i administered mode.sh print the message:
> > MetNcFile::data(NcVar *, const LongArray&, WrfData&) -> needed 2
> > arguments for variable APCP_24, got 4
> >
> > if i set ,
> > fcst_field = "APCP_24(180,150)";
> > or
> > fcst_field = "APCP_24(lat,lon)";
> > the message was:
> > MetNcFile::data(NcVar *, const LongArray&, WrfData&) const ->
bad star
> > count ... 0
> >
> > if i set,
> > fcst_field = "APCP_24(*,*)";
> > the message was:
> > NetCDF: Attribute not found
> >
> > Could you explain what do the "data(NcVar *, const LongArray&,
WrfData&)"
> > and "var_name(i,...,j,*,*)" mean?
> >
> > (2) Isn't right by the pcp_combine.sh setting?
> >
> > my pcp_combine.sh setting by :
> > ../bin/pcp_combine \
> > -subtract ../data/Namandol_fcst/WRFPRS_d03.048 48
> > ../data/Namandol_fcst/WRFPRS_d03.024 24 \
> > ../out/pcp_combine/Namandol_fct_2011082918V_24A.nc \
> >
> > and
> > ncdump -h Namandol_fct_2011082918V_24A.nc ,print the message:
> > float APCP_24(lat, lon) ;
> > APCP_24:name = "APCP" ;
> > APCP_24:long_name = "Total precipitation" ;
> > APCP_24:level = "A24" ;
> > APCP_24:units = "kg/m^2" ;
> > APCP_24:grib_code = 61 ;
> > APCP_24:_FillValue = -9999.f ;
> > APCP_24:init_time = "20110827_180000" ;
> > APCP_24:init_time_ut = 1314468000 ;
> > APCP_24:valid_time = "20110829_180000" ;
> > APCP_24:valid_time_ut = 1314640800 ;
> > APCP_24:accum_time = "240000" ;
> > APCP_24:accum_time_sec = 86400 ;
> >
> >
> > Thank you very much!
> >
> > Kate
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #55584]about MODE configuration file and pcp_combine.sh setting
From: Paul Oldenburg
Time: Tue Apr 17 09:25:15 2012
Kate,
The MET mode tool only accepts one gridded forecast field and one
gridded observation field. It appears that your
forecast field is gridded, but your observation field is point
observations, not a gridded field. Depending on what you
intend to use mode for, you can run it using the forecast field
against itself to generate output. This will work with
the configuration file that you sent me. However, I think mode
resolves more meaningful objects if you make two changes
to the config file:
fcst_conv_thresh = "ge350.0";
obs_conv_thresh = "ge350.0";
Here is how I ran mode:
$MET_BASE/bin/mode \
NMD_fcst_24L_2011082818V_24A.nc \
NMD_fcst_24L_2011082818V_24A.nc \
MODEConfig_APCP_24 \
-outdir . -v 3
If you have gridded 24hr precip observations that are on the same grid
as your model data, you should try to run mode
using that. Otherwise, there are global precip observations called
TRMM available through a link on the MET website
here:
http://www.dtcenter.org/met/users/downloads/observation_data.php.
Also on that page is an R script that can be
used to convert the TRMM data from text format to a gridded NetCDF
file in a format that MET can read. The gridded TRMM
data is in lat/long projection, so you would have to re-grid your
model data to use it in mode.
Please let me know if you have any questions.
Thanks,
Paul
On 04/17/2012 12:26 AM, 吳小榆 via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=55584>
>
> Paul,
>
> Following the MODEConfig_APCP_24 setting:
> fcst_field = "APCP_24(*,*)";
>
> When i type './mode.sh' the output message was:
>
> *** Running MODE on APCP using netCDF input for both forecast and
> observation ***
> DEBUG 1: Default Config File:
> /home/joray/tzyu/METv3.1/data/config/MODEConfig_default
> DEBUG 1: Match Config File: config/MODEConfig_APCP_24
> DEBUG 1: Merge Config File: config/MODEConfig_APCP_24
> DEBUG 1: Forecast File:
../out/pcp_combine/NMD_fcst_24L_2011082818V_24A.nc
> DEBUG 1: Observation File: ../out/ascii2nc/precip24_2011082818.nc
> NetCDF: Attribute not found
>
> I don't know what went wrong?nc files? or setting error? Could you
please
> help me to look on the files and setting on the ftp files?
>
> Thank you very much!
> Kate
>
> 2012/3/30 Paul Oldenburg via RT<met_help at ucar.edu>
>
>> Kate,
>>
>> To answer question 1, please look at the test script in the scripts
>> directory under the MET installation folder,
>> $MET_BASE/scripts/test_mode.sh. This script calls mode using the
output
>> of pcp_combine. You can see in the
>> configuration files,
$MET_BASE/scripts/config/MODEConfig_APCP_12/24, that
>> the fcst_field and obs_field are specified
>> like this:
>>
>> fcst_field = "APCP_24(*,*)";
>>
>> The reason is that, in the ncdump output you sent, the APCP_24
variable
>> has two dimensions. In MET, the syntax is to
>> provide a * in the dimensions that you want to use all indexes
from. The
>> answer to question 2 is that your pcp_combine
>> output looks valid and reasonable. If you have any questions about
this,
>> please let me know.
>>
>> Paul
>>
>>
>>
>>
>> On 03/30/2012 02:47 AM, 吳小榆 via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=55584>
>>>
>>> Dear sir,
>>>
>>> I used METv3.0.1,
>>> (1) how to set "fcst_field" in the mode configuration file
>>> "WrfModeConfig_APCP_24"?
>>>
>>> The forecast file is NetCDF file from pcp_conbine, so i set :
>>> fcst_field = "APCP_24(180,150,lon,lat)";
>>>
>>> when i administered mode.sh print the message:
>>> MetNcFile::data(NcVar *, const LongArray&, WrfData&) -> needed 2
>>> arguments for variable APCP_24, got 4
>>>
>>> if i set ,
>>> fcst_field = "APCP_24(180,150)";
>>> or
>>> fcst_field = "APCP_24(lat,lon)";
>>> the message was:
>>> MetNcFile::data(NcVar *, const LongArray&, WrfData&) const ->
bad star
>>> count ... 0
>>>
>>> if i set,
>>> fcst_field = "APCP_24(*,*)";
>>> the message was:
>>> NetCDF: Attribute not found
>>>
>>> Could you explain what do the "data(NcVar *, const LongArray&,
WrfData&)"
>>> and "var_name(i,...,j,*,*)" mean?
>>>
>>> (2) Isn't right by the pcp_combine.sh setting?
>>>
>>> my pcp_combine.sh setting by :
>>> ../bin/pcp_combine \
>>> -subtract ../data/Namandol_fcst/WRFPRS_d03.048 48
>>> ../data/Namandol_fcst/WRFPRS_d03.024 24 \
>>> ../out/pcp_combine/Namandol_fct_2011082918V_24A.nc \
>>>
>>> and
>>> ncdump -h Namandol_fct_2011082918V_24A.nc ,print the message:
>>> float APCP_24(lat, lon) ;
>>> APCP_24:name = "APCP" ;
>>> APCP_24:long_name = "Total precipitation" ;
>>> APCP_24:level = "A24" ;
>>> APCP_24:units = "kg/m^2" ;
>>> APCP_24:grib_code = 61 ;
>>> APCP_24:_FillValue = -9999.f ;
>>> APCP_24:init_time = "20110827_180000" ;
>>> APCP_24:init_time_ut = 1314468000 ;
>>> APCP_24:valid_time = "20110829_180000" ;
>>> APCP_24:valid_time_ut = 1314640800 ;
>>> APCP_24:accum_time = "240000" ;
>>> APCP_24:accum_time_sec = 86400 ;
>>>
>>>
>>> Thank you very much!
>>>
>>> Kate
>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list