[Met_help] [rt.rap.ucar.edu #61600] History for Obs data to feed in MET tools.
John Halley Gotway via RT
met_help at ucar.edu
Tue Jun 11 16:00:19 MDT 2013
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi John:
I have been reading the MET Users Guide for data formats and remained a bit
daunted by this constant interplay between all sorts of file formats - At
the moment my goal is rather succinct, I would like to be able to compare
my WRF forecast (lets say composite dBZ) with observations (from e.g, NMQ,
NCEP or another source).
Where can I obtain the observation file with formats compliant with MET as
the Users Guide does not point to any specific URL? Note that I am now able
to convert the WRF.NC files into GRIB1 files via UPP.
I would be interested in using the MODE tool for compiste dBZ during a
single model time. I have read, however, that MODE was designed to handle
accumulated precip and needs input from pcp_combine. How can I used
observed composite dBZ as input and where can I obtain the file with this
data in the correct format ?
The obs and WRF output data are initially not on the same grid + the WRF
data is staggered.
1) I assume that UPP de-staggers the data when converting to GRB1 correct ?
2) How do I interpolate the composite dBZ obs data onto the GRIB1-derived
grids or vice versa ?
3) Would you have a sample namelist available for me to run MODE once I'll
succeed in obtaining WRF and OBS data on the same regular grid ?.
NB: Would there be any plans in the future to make all the above process
more user friendly ? Aka a self-contained intuitive GUI package (like
Matlab) that reads in data directly from WRF or any other model, figures
out the computational grid the output data it is on, then reads in any
matching standard Level-II observations, figures out the format,
interpolate and destaggers the data and provide the desired plots and stats
to the user ? I have friends in many other fields (petroleum, chemistry,
biology, medecine) and we (meteorologists) are perhaps the only one having
to deal with those intermediate extra-curricular tedious tasks related to
installation of complicated packages, shell scripts, cumbersome binary file
formats (Especially GRIB which I despise) and programming in 10 different
languages. For instance, when my friend in bio-engineering received a new
apparatus designed to gather X/Y data on a given assay experiments, a
computer + GUI software came along with it to make all the stats and
required plots to him/her with a a single mouse click - No specific
computing skills were required other than basic Windows. Why isn't it the
same for meteorologists I wonder ? I am sure I am speaking for many
(similarly 'frustrated') individuals here as in the end, what matters to
everyone are the results-
Cheers and best,
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies* (OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Thu May 30 13:32:40 2013
Alex,
Here's a link to the MET website for some sources of observation data:
http://www.dtcenter.org/met/users/downloads/observation_data.php
MET can basically handle gridded data in GRIB1 or GRIB2 format. The
only other gridded data formats it can handle are the NetCDF output of
the pinterp utility, and the internal NetCDF format used by
MET. We'd like to more generally support CF-compliant NetCDF data,
but we haven't gotten that done yet.
MODE can be used to compare two different gridded data files. They
can be any of the gridded data files that MET supports - GRIB1, GRIB2,
NetCDF output of pcp_combine, and so on. MODE was developed
using accumulated precipitation data, but we have applied it to other
fields, including radar reflectivity. We just had to adjust the
convolution radius and threshold, and think about the other settings.
As for a source of gridded reflectivity data, I'm really not sure.
We've used RTMA data from NCEP in the past, and there's a link to that
on the observation data page. We've used Q2 data from NSSL
in the past, but we first had to get it into GRIB format. I see the
Q2 website (http://www.nssl.noaa.gov/projects/q2/) but can see how to
access the data directly.
Regarding UPP, yes, it destaggers the grid. We suggest using the
copygb utility for regridding GRIB1 data. copygb only handles GRIB1,
not GRIB2. To regrid GRIB2 data, you can use the cnvgrib
utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2 tool does some regridding, but it's pretty limited. Here's a
portion of the MET online tutorial that discussed copygb:
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
For examples of running MODE, please take a look in
METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running MODE. I'd also suggest reading through the MODE section of
the online tutorial:
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
Generally speaking, you should start by playing around with the
convolution radius and threshold to define objects that capture your
areas of interest.
Regarding future enhancements, at this point our funding is limited to
only support - no additional development. Hopefully, that will change
in the future. We have submitted a proposal that would
include development to support automated regridding of data. So you
could skip the copygb step, for example, before running grid_stat and
MODE. As for why the tools for petroleum, chemistry,
biology, and medicine are more sophisticated than those for
meteorology, I suspect there's more money driving the other
disciplines.
Thanks,
John
On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>
> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> Transaction: Ticket created by alexandre.o.fierro at gmail.com
> Queue: met_help
> Subject: Obs data to feed in MET tools.
> Owner: Nobody
> Requestors: alexandre.o.fierro at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
>
> Hi John:
>
> I have been reading the MET Users Guide for data formats and
remained a bit
> daunted by this constant interplay between all sorts of file formats
- At
> the moment my goal is rather succinct, I would like to be able to
compare
> my WRF forecast (lets say composite dBZ) with observations (from
e.g, NMQ,
> NCEP or another source).
>
> Where can I obtain the observation file with formats compliant with
MET as
> the Users Guide does not point to any specific URL? Note that I am
now able
> to convert the WRF.NC files into GRIB1 files via UPP.
>
> I would be interested in using the MODE tool for compiste dBZ during
a
> single model time. I have read, however, that MODE was designed to
handle
> accumulated precip and needs input from pcp_combine. How can I used
> observed composite dBZ as input and where can I obtain the file with
this
> data in the correct format ?
>
> The obs and WRF output data are initially not on the same grid + the
WRF
> data is staggered.
>
> 1) I assume that UPP de-staggers the data when converting to GRB1
correct ?
> 2) How do I interpolate the composite dBZ obs data onto the GRIB1-
derived
> grids or vice versa ?
> 3) Would you have a sample namelist available for me to run MODE
once I'll
> succeed in obtaining WRF and OBS data on the same regular grid ?.
>
> NB: Would there be any plans in the future to make all the above
process
> more user friendly ? Aka a self-contained intuitive GUI package
(like
> Matlab) that reads in data directly from WRF or any other model,
figures
> out the computational grid the output data it is on, then reads in
any
> matching standard Level-II observations, figures out the format,
> interpolate and destaggers the data and provide the desired plots
and stats
> to the user ? I have friends in many other fields (petroleum,
chemistry,
> biology, medecine) and we (meteorologists) are perhaps the only one
having
> to deal with those intermediate extra-curricular tedious tasks
related to
> installation of complicated packages, shell scripts, cumbersome
binary file
> formats (Especially GRIB which I despise) and programming in 10
different
> languages. For instance, when my friend in bio-engineering received
a new
> apparatus designed to gather X/Y data on a given assay experiments,
a
> computer + GUI software came along with it to make all the stats and
> required plots to him/her with a a single mouse click - No specific
> computing skills were required other than basic Windows. Why isn't
it the
> same for meteorologists I wonder ? I am sure I am speaking for many
> (similarly 'frustrated') individuals here as in the end, what
matters to
> everyone are the results-
>
> Cheers and best,
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Thu May 30 14:53:31 2013
Dear John:
Many thanks for your prompt and detailed reply.
I definitely blame the lack of funding in our field to hire software
engineers (at the level of the individuals working for MathWorks,
Google,
Facebook etc) to develop user friendly GUIs for meteorological use. I
truly
hope your team will get the funding it deserves to further enhance
this
very complex tool, which has a lot of potential and could definitely
be of
relevant use for routine forecasters.
I will give it a try using the precip data you specified for now -
I'll let
you know if I run into some issues.
South side of Norman and Purcell are in a tornado warning at the
moment -
my attention is now 'detoured' towards the sky.
Cheers and best,
Alexandre-
On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> Here's a link to the MET website for some sources of observation
data:
> http://www.dtcenter.org/met/users/downloads/observation_data.php
>
> MET can basically handle gridded data in GRIB1 or GRIB2 format. The
only
> other gridded data formats it can handle are the NetCDF output of
the
> pinterp utility, and the internal NetCDF format used by
> MET. We'd like to more generally support CF-compliant NetCDF data,
but we
> haven't gotten that done yet.
>
> MODE can be used to compare two different gridded data files. They
can be
> any of the gridded data files that MET supports - GRIB1, GRIB2,
NetCDF
> output of pcp_combine, and so on. MODE was developed
> using accumulated precipitation data, but we have applied it to
other
> fields, including radar reflectivity. We just had to adjust the
> convolution radius and threshold, and think about the other
settings.
>
> As for a source of gridded reflectivity data, I'm really not sure.
We've
> used RTMA data from NCEP in the past, and there's a link to that on
the
> observation data page. We've used Q2 data from NSSL
> in the past, but we first had to get it into GRIB format. I see the
Q2
> website (http://www.nssl.noaa.gov/projects/q2/) but can see how to
access
> the data directly.
>
> Regarding UPP, yes, it destaggers the grid. We suggest using the
copygb
> utility for regridding GRIB1 data. copygb only handles GRIB1, not
GRIB2.
> To regrid GRIB2 data, you can use the cnvgrib
> utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2
> tool does some regridding, but it's pretty limited. Here's a
portion of
> the MET online tutorial that discussed copygb:
>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>
> For examples of running MODE, please take a look in
> METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running
> MODE. I'd also suggest reading through the MODE section of the
online
> tutorial:
>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>
> Generally speaking, you should start by playing around with the
> convolution radius and threshold to define objects that capture your
areas
> of interest.
>
> Regarding future enhancements, at this point our funding is limited
to
> only support - no additional development. Hopefully, that will
change in
> the future. We have submitted a proposal that would
> include development to support automated regridding of data. So you
could
> skip the copygb step, for example, before running grid_stat and
MODE. As
> for why the tools for petroleum, chemistry,
> biology, and medicine are more sophisticated than those for
meteorology, I
> suspect there's more money driving the other disciplines.
>
> Thanks,
> John
>
> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >
> > Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> > Transaction: Ticket created by alexandre.o.fierro at gmail.com
> > Queue: met_help
> > Subject: Obs data to feed in MET tools.
> > Owner: Nobody
> > Requestors: alexandre.o.fierro at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> >
> > Hi John:
> >
> > I have been reading the MET Users Guide for data formats and
remained a
> bit
> > daunted by this constant interplay between all sorts of file
formats - At
> > the moment my goal is rather succinct, I would like to be able to
compare
> > my WRF forecast (lets say composite dBZ) with observations (from
e.g,
> NMQ,
> > NCEP or another source).
> >
> > Where can I obtain the observation file with formats compliant
with MET
> as
> > the Users Guide does not point to any specific URL? Note that I am
now
> able
> > to convert the WRF.NC files into GRIB1 files via UPP.
> >
> > I would be interested in using the MODE tool for compiste dBZ
during a
> > single model time. I have read, however, that MODE was designed to
handle
> > accumulated precip and needs input from pcp_combine. How can I
used
> > observed composite dBZ as input and where can I obtain the file
with this
> > data in the correct format ?
> >
> > The obs and WRF output data are initially not on the same grid +
the WRF
> > data is staggered.
> >
> > 1) I assume that UPP de-staggers the data when converting to GRB1
> correct ?
> > 2) How do I interpolate the composite dBZ obs data onto the GRIB1-
derived
> > grids or vice versa ?
> > 3) Would you have a sample namelist available for me to run MODE
once
> I'll
> > succeed in obtaining WRF and OBS data on the same regular grid ?.
> >
> > NB: Would there be any plans in the future to make all the above
process
> > more user friendly ? Aka a self-contained intuitive GUI package
(like
> > Matlab) that reads in data directly from WRF or any other model,
figures
> > out the computational grid the output data it is on, then reads in
any
> > matching standard Level-II observations, figures out the format,
> > interpolate and destaggers the data and provide the desired plots
and
> stats
> > to the user ? I have friends in many other fields (petroleum,
chemistry,
> > biology, medecine) and we (meteorologists) are perhaps the only
one
> having
> > to deal with those intermediate extra-curricular tedious tasks
related to
> > installation of complicated packages, shell scripts, cumbersome
binary
> file
> > formats (Especially GRIB which I despise) and programming in 10
different
> > languages. For instance, when my friend in bio-engineering
received a new
> > apparatus designed to gather X/Y data on a given assay
experiments, a
> > computer + GUI software came along with it to make all the stats
and
> > required plots to him/her with a a single mouse click - No
specific
> > computing skills were required other than basic Windows. Why isn't
it the
> > same for meteorologists I wonder ? I am sure I am speaking for
many
> > (similarly 'frustrated') individuals here as in the end, what
matters to
> > everyone are the results-
> >
> > Cheers and best,
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Thu May 30 16:11:57 2013
Hi John:
As you might have expected I ran into some issues running copygb.
We run WRF on CONUS at 4-km grid spacing on a Lambert conformal grid-
When I
run:
cat > itag <<EOF
/raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
netcdf
${SY}-${SM}-${SD}_03:00:00
${tag}
EOF
echo 'FILE TO BE PROCESSED'
/raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out 2>&1
mv WRFPRS03.tm00 WRFPRS_d01_03
# this stuff interp to a regular grid
read nav < 'copygb_gridnav.txt'
export nav
${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
I get:
copygb: unsupported output grid
I tried to change it to:
read nav < 'copygb_hwrf.txt'
but got the same error
Any clues on how I can get this program to destagger my WRF output in
the
GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
Cheers and thanks,
PS: I am using METV4.0 and the model outout is from WRFV3.4.1
On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
> Dear John:
>
> Many thanks for your prompt and detailed reply.
>
> I definitely blame the lack of funding in our field to hire software
> engineers (at the level of the individuals working for MathWorks,
Google,
> Facebook etc) to develop user friendly GUIs for meteorological use.
I truly
> hope your team will get the funding it deserves to further enhance
this
> very complex tool, which has a lot of potential and could definitely
be of
> relevant use for routine forecasters.
>
> I will give it a try using the precip data you specified for now -
I'll
> let you know if I run into some issues.
>
> South side of Norman and Purcell are in a tornado warning at the
moment -
> my attention is now 'detoured' towards the sky.
>
> Cheers and best,
>
> Alexandre-
>
>
> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> Here's a link to the MET website for some sources of observation
data:
>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>
>> MET can basically handle gridded data in GRIB1 or GRIB2 format.
The only
>> other gridded data formats it can handle are the NetCDF output of
the
>> pinterp utility, and the internal NetCDF format used by
>> MET. We'd like to more generally support CF-compliant NetCDF data,
but
>> we haven't gotten that done yet.
>>
>> MODE can be used to compare two different gridded data files. They
can
>> be any of the gridded data files that MET supports - GRIB1, GRIB2,
NetCDF
>> output of pcp_combine, and so on. MODE was developed
>> using accumulated precipitation data, but we have applied it to
other
>> fields, including radar reflectivity. We just had to adjust the
>> convolution radius and threshold, and think about the other
settings.
>>
>> As for a source of gridded reflectivity data, I'm really not sure.
We've
>> used RTMA data from NCEP in the past, and there's a link to that on
the
>> observation data page. We've used Q2 data from NSSL
>> in the past, but we first had to get it into GRIB format. I see
the Q2
>> website (http://www.nssl.noaa.gov/projects/q2/) but can see how to
>> access the data directly.
>>
>> Regarding UPP, yes, it destaggers the grid. We suggest using the
copygb
>> utility for regridding GRIB1 data. copygb only handles GRIB1, not
GRIB2.
>> To regrid GRIB2 data, you can use the cnvgrib
>> utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2
>> tool does some regridding, but it's pretty limited. Here's a
portion of
>> the MET online tutorial that discussed copygb:
>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>
>> For examples of running MODE, please take a look in
>> METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running
>> MODE. I'd also suggest reading through the MODE section of the
online
>> tutorial:
>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>
>> Generally speaking, you should start by playing around with the
>> convolution radius and threshold to define objects that capture
your areas
>> of interest.
>>
>> Regarding future enhancements, at this point our funding is limited
to
>> only support - no additional development. Hopefully, that will
change in
>> the future. We have submitted a proposal that would
>> include development to support automated regridding of data. So
you
>> could skip the copygb step, for example, before running grid_stat
and MODE.
>> As for why the tools for petroleum, chemistry,
>> biology, and medicine are more sophisticated than those for
meteorology,
>> I suspect there's more money driving the other disciplines.
>>
>> Thanks,
>> John
>>
>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>> >
>> > Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>> > Transaction: Ticket created by alexandre.o.fierro at gmail.com
>> > Queue: met_help
>> > Subject: Obs data to feed in MET tools.
>> > Owner: Nobody
>> > Requestors: alexandre.o.fierro at gmail.com
>> > Status: new
>> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>> >
>> >
>> > Hi John:
>> >
>> > I have been reading the MET Users Guide for data formats and
remained a
>> bit
>> > daunted by this constant interplay between all sorts of file
formats -
>> At
>> > the moment my goal is rather succinct, I would like to be able to
>> compare
>> > my WRF forecast (lets say composite dBZ) with observations (from
e.g,
>> NMQ,
>> > NCEP or another source).
>> >
>> > Where can I obtain the observation file with formats compliant
with MET
>> as
>> > the Users Guide does not point to any specific URL? Note that I
am now
>> able
>> > to convert the WRF.NC files into GRIB1 files via UPP.
>> >
>> > I would be interested in using the MODE tool for compiste dBZ
during a
>> > single model time. I have read, however, that MODE was designed
to
>> handle
>> > accumulated precip and needs input from pcp_combine. How can I
used
>> > observed composite dBZ as input and where can I obtain the file
with
>> this
>> > data in the correct format ?
>> >
>> > The obs and WRF output data are initially not on the same grid +
the WRF
>> > data is staggered.
>> >
>> > 1) I assume that UPP de-staggers the data when converting to GRB1
>> correct ?
>> > 2) How do I interpolate the composite dBZ obs data onto the
>> GRIB1-derived
>> > grids or vice versa ?
>> > 3) Would you have a sample namelist available for me to run MODE
once
>> I'll
>> > succeed in obtaining WRF and OBS data on the same regular grid ?.
>> >
>> > NB: Would there be any plans in the future to make all the above
process
>> > more user friendly ? Aka a self-contained intuitive GUI package
(like
>> > Matlab) that reads in data directly from WRF or any other model,
figures
>> > out the computational grid the output data it is on, then reads
in any
>> > matching standard Level-II observations, figures out the format,
>> > interpolate and destaggers the data and provide the desired plots
and
>> stats
>> > to the user ? I have friends in many other fields (petroleum,
chemistry,
>> > biology, medecine) and we (meteorologists) are perhaps the only
one
>> having
>> > to deal with those intermediate extra-curricular tedious tasks
related
>> to
>> > installation of complicated packages, shell scripts, cumbersome
binary
>> file
>> > formats (Especially GRIB which I despise) and programming in 10
>> different
>> > languages. For instance, when my friend in bio-engineering
received a
>> new
>> > apparatus designed to gather X/Y data on a given assay
experiments, a
>> > computer + GUI software came along with it to make all the stats
and
>> > required plots to him/her with a a single mouse click - No
specific
>> > computing skills were required other than basic Windows. Why
isn't it
>> the
>> > same for meteorologists I wonder ? I am sure I am speaking for
many
>> > (similarly 'frustrated') individuals here as in the end, what
matters to
>> > everyone are the results-
>> >
>> > Cheers and best,
>> >
>>
>>
>
>
> --
> -------------------------------------------------------------
> Alexandre Fierro, PhD
> Research Scientist-
> National Severe Storms Laboratory (NSSL/NOAA)
> *The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>
> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
> why it is called the Present"
>
> "There are only 10 types of people in the world:
> Those who understand binary, and those who don't"
>
> "My opinions are my own and not representative of OU, NSSL,
> AOML, HRD, LANL or any affiliates."
> ^.^
> (o o)
> /( V )\
> ---m---m----
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Fri May 31 10:21:50 2013
Alex,
So you have a GRIB file that's output by unipost, named
"WRFPRS_d01_03". And you're running it through copygb using the grid
defined by the contents of "copygb_gridnav.txt" or "copygb_hwrf.txt".
So
what do those copygb_gridnav.txt and copygb_hwrf.txt files contain?
Also, try running the following:
wgrib -V -d 1 WRFPRS_d01_03
That'll give a 'V'erbose description of the first record in that file,
including the current grid definition.
Can you send me that output?
Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the output
of unipost should already be unstaggered. If it's WRF-NMM, the output
of unipost will be staggered, and you need to run it
through copygb to de-stagger it.
Thanks,
John
On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> Hi John:
>
> As you might have expected I ran into some issues running copygb.
>
> We run WRF on CONUS at 4-km grid spacing on a Lambert conformal
grid-When I
> run:
>
> cat > itag <<EOF
> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> netcdf
> ${SY}-${SM}-${SD}_03:00:00
> ${tag}
> EOF
> echo 'FILE TO BE PROCESSED'
> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out 2>&1
> mv WRFPRS03.tm00 WRFPRS_d01_03
>
> # this stuff interp to a regular grid
> read nav < 'copygb_gridnav.txt'
> export nav
> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
>
> I get:
>
> copygb: unsupported output grid
>
> I tried to change it to:
>
> read nav < 'copygb_hwrf.txt'
>
> but got the same error
>
> Any clues on how I can get this program to destagger my WRF output
in the
> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
>
> Cheers and thanks,
>
> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
>
> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> <alexandre.o.fierro at gmail.com>wrote:
>
>> Dear John:
>>
>> Many thanks for your prompt and detailed reply.
>>
>> I definitely blame the lack of funding in our field to hire
software
>> engineers (at the level of the individuals working for MathWorks,
Google,
>> Facebook etc) to develop user friendly GUIs for meteorological use.
I truly
>> hope your team will get the funding it deserves to further enhance
this
>> very complex tool, which has a lot of potential and could
definitely be of
>> relevant use for routine forecasters.
>>
>> I will give it a try using the precip data you specified for now -
I'll
>> let you know if I run into some issues.
>>
>> South side of Norman and Purcell are in a tornado warning at the
moment -
>> my attention is now 'detoured' towards the sky.
>>
>> Cheers and best,
>>
>> Alexandre-
>>
>>
>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>>
>>> Alex,
>>>
>>> Here's a link to the MET website for some sources of observation
data:
>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>
>>> MET can basically handle gridded data in GRIB1 or GRIB2 format.
The only
>>> other gridded data formats it can handle are the NetCDF output of
the
>>> pinterp utility, and the internal NetCDF format used by
>>> MET. We'd like to more generally support CF-compliant NetCDF
data, but
>>> we haven't gotten that done yet.
>>>
>>> MODE can be used to compare two different gridded data files.
They can
>>> be any of the gridded data files that MET supports - GRIB1, GRIB2,
NetCDF
>>> output of pcp_combine, and so on. MODE was developed
>>> using accumulated precipitation data, but we have applied it to
other
>>> fields, including radar reflectivity. We just had to adjust the
>>> convolution radius and threshold, and think about the other
settings.
>>>
>>> As for a source of gridded reflectivity data, I'm really not sure.
We've
>>> used RTMA data from NCEP in the past, and there's a link to that
on the
>>> observation data page. We've used Q2 data from NSSL
>>> in the past, but we first had to get it into GRIB format. I see
the Q2
>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see how to
>>> access the data directly.
>>>
>>> Regarding UPP, yes, it destaggers the grid. We suggest using the
copygb
>>> utility for regridding GRIB1 data. copygb only handles GRIB1, not
GRIB2.
>>> To regrid GRIB2 data, you can use the cnvgrib
>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2
>>> tool does some regridding, but it's pretty limited. Here's a
portion of
>>> the MET online tutorial that discussed copygb:
>>>
>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>
>>> For examples of running MODE, please take a look in
>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running
>>> MODE. I'd also suggest reading through the MODE section of the
online
>>> tutorial:
>>>
>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>
>>> Generally speaking, you should start by playing around with the
>>> convolution radius and threshold to define objects that capture
your areas
>>> of interest.
>>>
>>> Regarding future enhancements, at this point our funding is
limited to
>>> only support - no additional development. Hopefully, that will
change in
>>> the future. We have submitted a proposal that would
>>> include development to support automated regridding of data. So
you
>>> could skip the copygb step, for example, before running grid_stat
and MODE.
>>> As for why the tools for petroleum, chemistry,
>>> biology, and medicine are more sophisticated than those for
meteorology,
>>> I suspect there's more money driving the other disciplines.
>>>
>>> Thanks,
>>> John
>>>
>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>
>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
>>>> Queue: met_help
>>>> Subject: Obs data to feed in MET tools.
>>>> Owner: Nobody
>>>> Requestors: alexandre.o.fierro at gmail.com
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>
>>>>
>>>> Hi John:
>>>>
>>>> I have been reading the MET Users Guide for data formats and
remained a
>>> bit
>>>> daunted by this constant interplay between all sorts of file
formats -
>>> At
>>>> the moment my goal is rather succinct, I would like to be able to
>>> compare
>>>> my WRF forecast (lets say composite dBZ) with observations (from
e.g,
>>> NMQ,
>>>> NCEP or another source).
>>>>
>>>> Where can I obtain the observation file with formats compliant
with MET
>>> as
>>>> the Users Guide does not point to any specific URL? Note that I
am now
>>> able
>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>
>>>> I would be interested in using the MODE tool for compiste dBZ
during a
>>>> single model time. I have read, however, that MODE was designed
to
>>> handle
>>>> accumulated precip and needs input from pcp_combine. How can I
used
>>>> observed composite dBZ as input and where can I obtain the file
with
>>> this
>>>> data in the correct format ?
>>>>
>>>> The obs and WRF output data are initially not on the same grid +
the WRF
>>>> data is staggered.
>>>>
>>>> 1) I assume that UPP de-staggers the data when converting to GRB1
>>> correct ?
>>>> 2) How do I interpolate the composite dBZ obs data onto the
>>> GRIB1-derived
>>>> grids or vice versa ?
>>>> 3) Would you have a sample namelist available for me to run MODE
once
>>> I'll
>>>> succeed in obtaining WRF and OBS data on the same regular grid ?.
>>>>
>>>> NB: Would there be any plans in the future to make all the above
process
>>>> more user friendly ? Aka a self-contained intuitive GUI package
(like
>>>> Matlab) that reads in data directly from WRF or any other model,
figures
>>>> out the computational grid the output data it is on, then reads
in any
>>>> matching standard Level-II observations, figures out the format,
>>>> interpolate and destaggers the data and provide the desired plots
and
>>> stats
>>>> to the user ? I have friends in many other fields (petroleum,
chemistry,
>>>> biology, medecine) and we (meteorologists) are perhaps the only
one
>>> having
>>>> to deal with those intermediate extra-curricular tedious tasks
related
>>> to
>>>> installation of complicated packages, shell scripts, cumbersome
binary
>>> file
>>>> formats (Especially GRIB which I despise) and programming in 10
>>> different
>>>> languages. For instance, when my friend in bio-engineering
received a
>>> new
>>>> apparatus designed to gather X/Y data on a given assay
experiments, a
>>>> computer + GUI software came along with it to make all the stats
and
>>>> required plots to him/her with a a single mouse click - No
specific
>>>> computing skills were required other than basic Windows. Why
isn't it
>>> the
>>>> same for meteorologists I wonder ? I am sure I am speaking for
many
>>>> (similarly 'frustrated') individuals here as in the end, what
matters to
>>>> everyone are the results-
>>>>
>>>> Cheers and best,
>>>>
>>>
>>>
>>
>>
>> --
>> -------------------------------------------------------------
>> Alexandre Fierro, PhD
>> Research Scientist-
>> National Severe Storms Laboratory (NSSL/NOAA)
>> *The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>
>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
>> why it is called the Present"
>>
>> "There are only 10 types of people in the world:
>> Those who understand binary, and those who don't"
>>
>> "My opinions are my own and not representative of OU, NSSL,
>> AOML, HRD, LANL or any affiliates."
>> ^.^
>> (o o)
>> /( V )\
>> ---m---m----
>>
>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Fri May 31 13:58:05 2013
Hi John:
I use ARW so seems like UNIPOST already de-staggers the data.
I have:
/home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1 WRFPRS_d01_03
rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0 levels=(0,0)
grid=255 MSL 3hr fcst:
PRMSL=Pressure reduced to MSL [Pa]
timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3 num_in_ave
0
missing 0
center 7 subcenter 0 process 125 Table 2 scan: WE:SN winds(grid)
Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov -98.000000
Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP 0.000000
North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64 mode 136
min/max data 99016.4 102768 num bits 16 BDS_Ref 9.90164e+06
DecScale 2
BinScale 3
The next step I guess would be to produce accumulated precip from
several
of those WRFPRS_d01_0FHR files correct (where FHR=forecast hour)?
Cheers,
Alex-
On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> So you have a GRIB file that's output by unipost, named
"WRFPRS_d01_03".
> And you're running it through copygb using the grid defined by the
> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
> what do those copygb_gridnav.txt and copygb_hwrf.txt files contain?
>
> Also, try running the following:
> wgrib -V -d 1 WRFPRS_d01_03
>
> That'll give a 'V'erbose description of the first record in that
file,
> including the current grid definition.
>
> Can you send me that output?
>
> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output of
> unipost should already be unstaggered. If it's WRF-NMM, the output
of
> unipost will be staggered, and you need to run it
> through copygb to de-stagger it.
>
> Thanks,
> John
>
> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > Hi John:
> >
> > As you might have expected I ran into some issues running copygb.
> >
> > We run WRF on CONUS at 4-km grid spacing on a Lambert conformal
> grid-When I
> > run:
> >
> > cat > itag <<EOF
> > /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> > netcdf
> > ${SY}-${SM}-${SD}_03:00:00
> > ${tag}
> > EOF
> > echo 'FILE TO BE PROCESSED'
> > /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> > mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
> > mv WRFPRS03.tm00 WRFPRS_d01_03
> >
> > # this stuff interp to a regular grid
> > read nav < 'copygb_gridnav.txt'
> > export nav
> > ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
> >
> > I get:
> >
> > copygb: unsupported output grid
> >
> > I tried to change it to:
> >
> > read nav < 'copygb_hwrf.txt'
> >
> > but got the same error
> >
> > Any clues on how I can get this program to destagger my WRF output
in the
> > GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
> >
> > Cheers and thanks,
> >
> > PS: I am using METV4.0 and the model outout is from WRFV3.4.1
> >
> > On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> > <alexandre.o.fierro at gmail.com>wrote:
> >
> >> Dear John:
> >>
> >> Many thanks for your prompt and detailed reply.
> >>
> >> I definitely blame the lack of funding in our field to hire
software
> >> engineers (at the level of the individuals working for MathWorks,
> Google,
> >> Facebook etc) to develop user friendly GUIs for meteorological
use. I
> truly
> >> hope your team will get the funding it deserves to further
enhance this
> >> very complex tool, which has a lot of potential and could
definitely be
> of
> >> relevant use for routine forecasters.
> >>
> >> I will give it a try using the precip data you specified for now
- I'll
> >> let you know if I run into some issues.
> >>
> >> South side of Norman and Purcell are in a tornado warning at the
moment
> -
> >> my attention is now 'detoured' towards the sky.
> >>
> >> Cheers and best,
> >>
> >> Alexandre-
> >>
> >>
> >> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >>> Alex,
> >>>
> >>> Here's a link to the MET website for some sources of observation
data:
> >>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>
> >>> MET can basically handle gridded data in GRIB1 or GRIB2 format.
The
> only
> >>> other gridded data formats it can handle are the NetCDF output
of the
> >>> pinterp utility, and the internal NetCDF format used by
> >>> MET. We'd like to more generally support CF-compliant NetCDF
data, but
> >>> we haven't gotten that done yet.
> >>>
> >>> MODE can be used to compare two different gridded data files.
They can
> >>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
> NetCDF
> >>> output of pcp_combine, and so on. MODE was developed
> >>> using accumulated precipitation data, but we have applied it to
other
> >>> fields, including radar reflectivity. We just had to adjust the
> >>> convolution radius and threshold, and think about the other
settings.
> >>>
> >>> As for a source of gridded reflectivity data, I'm really not
sure.
> We've
> >>> used RTMA data from NCEP in the past, and there's a link to that
on the
> >>> observation data page. We've used Q2 data from NSSL
> >>> in the past, but we first had to get it into GRIB format. I see
the Q2
> >>> website (http://www.nssl.noaa.gov/projects/q2/) but can see how
to
> >>> access the data directly.
> >>>
> >>> Regarding UPP, yes, it destaggers the grid. We suggest using
the
> copygb
> >>> utility for regridding GRIB1 data. copygb only handles GRIB1,
not
> GRIB2.
> >>> To regrid GRIB2 data, you can use the cnvgrib
> >>> utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2
> >>> tool does some regridding, but it's pretty limited. Here's a
portion
> of
> >>> the MET online tutorial that discussed copygb:
> >>>
> >>>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>
> >>> For examples of running MODE, please take a look in
> >>> METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running
> >>> MODE. I'd also suggest reading through the MODE section of the
online
> >>> tutorial:
> >>>
> >>>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>
> >>> Generally speaking, you should start by playing around with the
> >>> convolution radius and threshold to define objects that capture
your
> areas
> >>> of interest.
> >>>
> >>> Regarding future enhancements, at this point our funding is
limited to
> >>> only support - no additional development. Hopefully, that will
change
> in
> >>> the future. We have submitted a proposal that would
> >>> include development to support automated regridding of data. So
you
> >>> could skip the copygb step, for example, before running
grid_stat and
> MODE.
> >>> As for why the tools for petroleum, chemistry,
> >>> biology, and medicine are more sophisticated than those for
> meteorology,
> >>> I suspect there's more money driving the other disciplines.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>
> >>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> >>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
> >>>> Queue: met_help
> >>>> Subject: Obs data to feed in MET tools.
> >>>> Owner: Nobody
> >>>> Requestors: alexandre.o.fierro at gmail.com
> >>>> Status: new
> >>>> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>
> >>>>
> >>>> Hi John:
> >>>>
> >>>> I have been reading the MET Users Guide for data formats and
remained
> a
> >>> bit
> >>>> daunted by this constant interplay between all sorts of file
formats -
> >>> At
> >>>> the moment my goal is rather succinct, I would like to be able
to
> >>> compare
> >>>> my WRF forecast (lets say composite dBZ) with observations
(from e.g,
> >>> NMQ,
> >>>> NCEP or another source).
> >>>>
> >>>> Where can I obtain the observation file with formats compliant
with
> MET
> >>> as
> >>>> the Users Guide does not point to any specific URL? Note that I
am now
> >>> able
> >>>> to convert the WRF.NC files into GRIB1 files via UPP.
> >>>>
> >>>> I would be interested in using the MODE tool for compiste dBZ
during a
> >>>> single model time. I have read, however, that MODE was designed
to
> >>> handle
> >>>> accumulated precip and needs input from pcp_combine. How can I
used
> >>>> observed composite dBZ as input and where can I obtain the file
with
> >>> this
> >>>> data in the correct format ?
> >>>>
> >>>> The obs and WRF output data are initially not on the same grid
+ the
> WRF
> >>>> data is staggered.
> >>>>
> >>>> 1) I assume that UPP de-staggers the data when converting to
GRB1
> >>> correct ?
> >>>> 2) How do I interpolate the composite dBZ obs data onto the
> >>> GRIB1-derived
> >>>> grids or vice versa ?
> >>>> 3) Would you have a sample namelist available for me to run
MODE once
> >>> I'll
> >>>> succeed in obtaining WRF and OBS data on the same regular grid
?.
> >>>>
> >>>> NB: Would there be any plans in the future to make all the
above
> process
> >>>> more user friendly ? Aka a self-contained intuitive GUI
package (like
> >>>> Matlab) that reads in data directly from WRF or any other
model,
> figures
> >>>> out the computational grid the output data it is on, then reads
in any
> >>>> matching standard Level-II observations, figures out the
format,
> >>>> interpolate and destaggers the data and provide the desired
plots and
> >>> stats
> >>>> to the user ? I have friends in many other fields (petroleum,
> chemistry,
> >>>> biology, medecine) and we (meteorologists) are perhaps the only
one
> >>> having
> >>>> to deal with those intermediate extra-curricular tedious tasks
related
> >>> to
> >>>> installation of complicated packages, shell scripts, cumbersome
binary
> >>> file
> >>>> formats (Especially GRIB which I despise) and programming in 10
> >>> different
> >>>> languages. For instance, when my friend in bio-engineering
received a
> >>> new
> >>>> apparatus designed to gather X/Y data on a given assay
experiments, a
> >>>> computer + GUI software came along with it to make all the
stats and
> >>>> required plots to him/her with a a single mouse click - No
specific
> >>>> computing skills were required other than basic Windows. Why
isn't it
> >>> the
> >>>> same for meteorologists I wonder ? I am sure I am speaking for
many
> >>>> (similarly 'frustrated') individuals here as in the end, what
matters
> to
> >>>> everyone are the results-
> >>>>
> >>>> Cheers and best,
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >> -------------------------------------------------------------
> >> Alexandre Fierro, PhD
> >> Research Scientist-
> >> National Severe Storms Laboratory (NSSL/NOAA)
> >> *The Cooperative Institute for Mesoscale Meteorological Studies*
> (OU/NOAA)
> >> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>
> >> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That
> is
> >> why it is called the Present"
> >>
> >> "There are only 10 types of people in the world:
> >> Those who understand binary, and those who don't"
> >>
> >> "My opinions are my own and not representative of OU, NSSL,
> >> AOML, HRD, LANL or any affiliates."
> >> ^.^
> >> (o o)
> >> /( V )\
> >> ---m---m----
> >>
> >
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Fri May 31 14:11:00 2013
Alex,
Yep, by default WRF-ARW dumps out it's precipitation accumulated over
the entire model run. So you'll need to adjust your forecast
accumulation intervals to match the observation accumulation
intervals. For example, to get the 6-hour accumulation between
forecast hours 24 and 30, you'd do the following:
METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30 WRFPRS_d01_24 24
WRFPRS_d01_APCP_06_24_to_30.nc
That will grab the 30 hours of precip from the first file and the 24
hours of precip from the second file and subtract them. The last
argument is the name of the NetCDF file to be used.
You might also want to run the plot_data_plane utility just to make
sure that your data looks good:
METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
'name="APCP"; level="A30";'
That will select the field we've described (precip accumulated over 30
hours) from the file you've passed it and create a postscript image of
it.
Hope that helps.
Thanks,
John
On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> Hi John:
>
> I use ARW so seems like UNIPOST already de-staggers the data.
>
> I have:
>
> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1 WRFPRS_d01_03
> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0 levels=(0,0)
> grid=255 MSL 3hr fcst:
> PRMSL=Pressure reduced to MSL [Pa]
> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
num_in_ave 0
> missing 0
> center 7 subcenter 0 process 125 Table 2 scan: WE:SN winds(grid)
> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov -98.000000
> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP
0.000000
> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64 mode
136
> min/max data 99016.4 102768 num bits 16 BDS_Ref 9.90164e+06
DecScale 2
> BinScale 3
>
> The next step I guess would be to produce accumulated precip from
several
> of those WRFPRS_d01_0FHR files correct (where FHR=forecast hour)?
>
> Cheers,
>
> Alex-
>
> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> So you have a GRIB file that's output by unipost, named
"WRFPRS_d01_03".
>> And you're running it through copygb using the grid defined by
the
>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>> what do those copygb_gridnav.txt and copygb_hwrf.txt files contain?
>>
>> Also, try running the following:
>> wgrib -V -d 1 WRFPRS_d01_03
>>
>> That'll give a 'V'erbose description of the first record in that
file,
>> including the current grid definition.
>>
>> Can you send me that output?
>>
>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output of
>> unipost should already be unstaggered. If it's WRF-NMM, the output
of
>> unipost will be staggered, and you need to run it
>> through copygb to de-stagger it.
>>
>> Thanks,
>> John
>>
>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>
>>> Hi John:
>>>
>>> As you might have expected I ran into some issues running copygb.
>>>
>>> We run WRF on CONUS at 4-km grid spacing on a Lambert conformal
>> grid-When I
>>> run:
>>>
>>> cat > itag <<EOF
>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>> netcdf
>>> ${SY}-${SM}-${SD}_03:00:00
>>> ${tag}
>>> EOF
>>> echo 'FILE TO BE PROCESSED'
>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>>
>>> # this stuff interp to a regular grid
>>> read nav < 'copygb_gridnav.txt'
>>> export nav
>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
>>>
>>> I get:
>>>
>>> copygb: unsupported output grid
>>>
>>> I tried to change it to:
>>>
>>> read nav < 'copygb_hwrf.txt'
>>>
>>> but got the same error
>>>
>>> Any clues on how I can get this program to destagger my WRF output
in the
>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
>>>
>>> Cheers and thanks,
>>>
>>> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
>>>
>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>> <alexandre.o.fierro at gmail.com>wrote:
>>>
>>>> Dear John:
>>>>
>>>> Many thanks for your prompt and detailed reply.
>>>>
>>>> I definitely blame the lack of funding in our field to hire
software
>>>> engineers (at the level of the individuals working for MathWorks,
>> Google,
>>>> Facebook etc) to develop user friendly GUIs for meteorological
use. I
>> truly
>>>> hope your team will get the funding it deserves to further
enhance this
>>>> very complex tool, which has a lot of potential and could
definitely be
>> of
>>>> relevant use for routine forecasters.
>>>>
>>>> I will give it a try using the precip data you specified for now
- I'll
>>>> let you know if I run into some issues.
>>>>
>>>> South side of Norman and Purcell are in a tornado warning at the
moment
>> -
>>>> my attention is now 'detoured' towards the sky.
>>>>
>>>> Cheers and best,
>>>>
>>>> Alexandre-
>>>>
>>>>
>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
>>>> met_help at ucar.edu> wrote:
>>>>
>>>>> Alex,
>>>>>
>>>>> Here's a link to the MET website for some sources of observation
data:
>>>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>>>
>>>>> MET can basically handle gridded data in GRIB1 or GRIB2 format.
The
>> only
>>>>> other gridded data formats it can handle are the NetCDF output
of the
>>>>> pinterp utility, and the internal NetCDF format used by
>>>>> MET. We'd like to more generally support CF-compliant NetCDF
data, but
>>>>> we haven't gotten that done yet.
>>>>>
>>>>> MODE can be used to compare two different gridded data files.
They can
>>>>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
>> NetCDF
>>>>> output of pcp_combine, and so on. MODE was developed
>>>>> using accumulated precipitation data, but we have applied it to
other
>>>>> fields, including radar reflectivity. We just had to adjust the
>>>>> convolution radius and threshold, and think about the other
settings.
>>>>>
>>>>> As for a source of gridded reflectivity data, I'm really not
sure.
>> We've
>>>>> used RTMA data from NCEP in the past, and there's a link to that
on the
>>>>> observation data page. We've used Q2 data from NSSL
>>>>> in the past, but we first had to get it into GRIB format. I see
the Q2
>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see how
to
>>>>> access the data directly.
>>>>>
>>>>> Regarding UPP, yes, it destaggers the grid. We suggest using
the
>> copygb
>>>>> utility for regridding GRIB1 data. copygb only handles GRIB1,
not
>> GRIB2.
>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively, the
wgrib2
>>>>> tool does some regridding, but it's pretty limited. Here's a
portion
>> of
>>>>> the MET online tutorial that discussed copygb:
>>>>>
>>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>>>
>>>>> For examples of running MODE, please take a look in
>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there of
running
>>>>> MODE. I'd also suggest reading through the MODE section of the
online
>>>>> tutorial:
>>>>>
>>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>>>
>>>>> Generally speaking, you should start by playing around with the
>>>>> convolution radius and threshold to define objects that capture
your
>> areas
>>>>> of interest.
>>>>>
>>>>> Regarding future enhancements, at this point our funding is
limited to
>>>>> only support - no additional development. Hopefully, that will
change
>> in
>>>>> the future. We have submitted a proposal that would
>>>>> include development to support automated regridding of data. So
you
>>>>> could skip the copygb step, for example, before running
grid_stat and
>> MODE.
>>>>> As for why the tools for petroleum, chemistry,
>>>>> biology, and medicine are more sophisticated than those for
>> meteorology,
>>>>> I suspect there's more money driving the other disciplines.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>>>
>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
>>>>>> Queue: met_help
>>>>>> Subject: Obs data to feed in MET tools.
>>>>>> Owner: Nobody
>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>>>>> Status: new
>>>>>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>
>>>>>>
>>>>>> Hi John:
>>>>>>
>>>>>> I have been reading the MET Users Guide for data formats and
remained
>> a
>>>>> bit
>>>>>> daunted by this constant interplay between all sorts of file
formats -
>>>>> At
>>>>>> the moment my goal is rather succinct, I would like to be able
to
>>>>> compare
>>>>>> my WRF forecast (lets say composite dBZ) with observations
(from e.g,
>>>>> NMQ,
>>>>>> NCEP or another source).
>>>>>>
>>>>>> Where can I obtain the observation file with formats compliant
with
>> MET
>>>>> as
>>>>>> the Users Guide does not point to any specific URL? Note that I
am now
>>>>> able
>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>>>
>>>>>> I would be interested in using the MODE tool for compiste dBZ
during a
>>>>>> single model time. I have read, however, that MODE was designed
to
>>>>> handle
>>>>>> accumulated precip and needs input from pcp_combine. How can I
used
>>>>>> observed composite dBZ as input and where can I obtain the file
with
>>>>> this
>>>>>> data in the correct format ?
>>>>>>
>>>>>> The obs and WRF output data are initially not on the same grid
+ the
>> WRF
>>>>>> data is staggered.
>>>>>>
>>>>>> 1) I assume that UPP de-staggers the data when converting to
GRB1
>>>>> correct ?
>>>>>> 2) How do I interpolate the composite dBZ obs data onto the
>>>>> GRIB1-derived
>>>>>> grids or vice versa ?
>>>>>> 3) Would you have a sample namelist available for me to run
MODE once
>>>>> I'll
>>>>>> succeed in obtaining WRF and OBS data on the same regular grid
?.
>>>>>>
>>>>>> NB: Would there be any plans in the future to make all the
above
>> process
>>>>>> more user friendly ? Aka a self-contained intuitive GUI
package (like
>>>>>> Matlab) that reads in data directly from WRF or any other
model,
>> figures
>>>>>> out the computational grid the output data it is on, then reads
in any
>>>>>> matching standard Level-II observations, figures out the
format,
>>>>>> interpolate and destaggers the data and provide the desired
plots and
>>>>> stats
>>>>>> to the user ? I have friends in many other fields (petroleum,
>> chemistry,
>>>>>> biology, medecine) and we (meteorologists) are perhaps the only
one
>>>>> having
>>>>>> to deal with those intermediate extra-curricular tedious tasks
related
>>>>> to
>>>>>> installation of complicated packages, shell scripts, cumbersome
binary
>>>>> file
>>>>>> formats (Especially GRIB which I despise) and programming in 10
>>>>> different
>>>>>> languages. For instance, when my friend in bio-engineering
received a
>>>>> new
>>>>>> apparatus designed to gather X/Y data on a given assay
experiments, a
>>>>>> computer + GUI software came along with it to make all the
stats and
>>>>>> required plots to him/her with a a single mouse click - No
specific
>>>>>> computing skills were required other than basic Windows. Why
isn't it
>>>>> the
>>>>>> same for meteorologists I wonder ? I am sure I am speaking for
many
>>>>>> (similarly 'frustrated') individuals here as in the end, what
matters
>> to
>>>>>> everyone are the results-
>>>>>>
>>>>>> Cheers and best,
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> -------------------------------------------------------------
>>>> Alexandre Fierro, PhD
>>>> Research Scientist-
>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>> *The Cooperative Institute for Mesoscale Meteorological Studies*
>> (OU/NOAA)
>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>
>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That
>> is
>>>> why it is called the Present"
>>>>
>>>> "There are only 10 types of people in the world:
>>>> Those who understand binary, and those who don't"
>>>>
>>>> "My opinions are my own and not representative of OU, NSSL,
>>>> AOML, HRD, LANL or any affiliates."
>>>> ^.^
>>>> (o o)
>>>> /( V )\
>>>> ---m---m----
>>>>
>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Fri May 31 15:12:31 2013
John:
I have tried the following with 6 separate GRIB files each containing
1-h
accum precip but ran into this problem:
/home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05 WRFPRS_d01_06 06
WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
WRFPRS_d01_APCP_06_03_to_09.nc
DEBUG 1: Reading input file: WRFPRS_d01_03
DEBUG 1: Reading input file: WRFPRS_d01_04
WARNING:
WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
"APCP/A3" in GRIB file "WRFPRS_d01_04".
WARNING:
ERROR :
ERROR : get_field() -> can't get data plane from file "WRFPRS_d01_04"
ERROR :
What are the double digit numbers ahed of the filename ?
The original WRF OUT Files have:
ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
...
928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
PRECIPITATION" ;
935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
PRECIPITATION" ;
942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
PRECIPITATION" ;
...
Cheers and thanks,
Alex-
On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> Yep, by default WRF-ARW dumps out it's precipitation accumulated
over the
> entire model run. So you'll need to adjust your forecast
accumulation
> intervals to match the observation accumulation
> intervals. For example, to get the 6-hour accumulation between
forecast
> hours 24 and 30, you'd do the following:
>
> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30 WRFPRS_d01_24
24
> WRFPRS_d01_APCP_06_24_to_30.nc
>
> That will grab the 30 hours of precip from the first file and the 24
hours
> of precip from the second file and subtract them. The last argument
is the
> name of the NetCDF file to be used.
>
> You might also want to run the plot_data_plane utility just to make
sure
> that your data looks good:
>
> METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
> 'name="APCP"; level="A30";'
>
> That will select the field we've described (precip accumulated over
30
> hours) from the file you've passed it and create a postscript image
of it.
>
> Hope that helps.
>
> Thanks,
> John
>
> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > Hi John:
> >
> > I use ARW so seems like UNIPOST already de-staggers the data.
> >
> > I have:
> >
> > /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1 WRFPRS_d01_03
> > rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
levels=(0,0)
> > grid=255 MSL 3hr fcst:
> > PRMSL=Pressure reduced to MSL [Pa]
> > timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
num_in_ave 0
> > missing 0
> > center 7 subcenter 0 process 125 Table 2 scan: WE:SN
winds(grid)
> > Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov -98.000000
> > Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP
0.000000
> > North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64
mode 136
> > min/max data 99016.4 102768 num bits 16 BDS_Ref 9.90164e+06
> DecScale 2
> > BinScale 3
> >
> > The next step I guess would be to produce accumulated precip from
several
> > of those WRFPRS_d01_0FHR files correct (where FHR=forecast hour)?
> >
> > Cheers,
> >
> > Alex-
> >
> > On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Alex,
> >>
> >> So you have a GRIB file that's output by unipost, named
"WRFPRS_d01_03".
> >> And you're running it through copygb using the grid defined by
the
> >> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
> >> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
> >>
> >> Also, try running the following:
> >> wgrib -V -d 1 WRFPRS_d01_03
> >>
> >> That'll give a 'V'erbose description of the first record in that
file,
> >> including the current grid definition.
> >>
> >> Can you send me that output?
> >>
> >> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output
> of
> >> unipost should already be unstaggered. If it's WRF-NMM, the
output of
> >> unipost will be staggered, and you need to run it
> >> through copygb to de-stagger it.
> >>
> >> Thanks,
> >> John
> >>
> >> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>
> >>> Hi John:
> >>>
> >>> As you might have expected I ran into some issues running
copygb.
> >>>
> >>> We run WRF on CONUS at 4-km grid spacing on a Lambert conformal
> >> grid-When I
> >>> run:
> >>>
> >>> cat > itag <<EOF
> >>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>> netcdf
> >>> ${SY}-${SM}-${SD}_03:00:00
> >>> ${tag}
> >>> EOF
> >>> echo 'FILE TO BE PROCESSED'
> >>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
> >>> mv WRFPRS03.tm00 WRFPRS_d01_03
> >>>
> >>> # this stuff interp to a regular grid
> >>> read nav < 'copygb_gridnav.txt'
> >>> export nav
> >>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
> >>>
> >>> I get:
> >>>
> >>> copygb: unsupported output grid
> >>>
> >>> I tried to change it to:
> >>>
> >>> read nav < 'copygb_hwrf.txt'
> >>>
> >>> but got the same error
> >>>
> >>> Any clues on how I can get this program to destagger my WRF
output in
> the
> >>> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
> >>>
> >>> Cheers and thanks,
> >>>
> >>> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
> >>>
> >>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> >>> <alexandre.o.fierro at gmail.com>wrote:
> >>>
> >>>> Dear John:
> >>>>
> >>>> Many thanks for your prompt and detailed reply.
> >>>>
> >>>> I definitely blame the lack of funding in our field to hire
software
> >>>> engineers (at the level of the individuals working for
MathWorks,
> >> Google,
> >>>> Facebook etc) to develop user friendly GUIs for meteorological
use. I
> >> truly
> >>>> hope your team will get the funding it deserves to further
enhance
> this
> >>>> very complex tool, which has a lot of potential and could
definitely
> be
> >> of
> >>>> relevant use for routine forecasters.
> >>>>
> >>>> I will give it a try using the precip data you specified for
now -
> I'll
> >>>> let you know if I run into some issues.
> >>>>
> >>>> South side of Norman and Purcell are in a tornado warning at
the
> moment
> >> -
> >>>> my attention is now 'detoured' towards the sky.
> >>>>
> >>>> Cheers and best,
> >>>>
> >>>> Alexandre-
> >>>>
> >>>>
> >>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
> >>>> met_help at ucar.edu> wrote:
> >>>>
> >>>>> Alex,
> >>>>>
> >>>>> Here's a link to the MET website for some sources of
observation
> data:
> >>>>>
> http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>>>
> >>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format. The
> >> only
> >>>>> other gridded data formats it can handle are the NetCDF output
of the
> >>>>> pinterp utility, and the internal NetCDF format used by
> >>>>> MET. We'd like to more generally support CF-compliant NetCDF
data,
> but
> >>>>> we haven't gotten that done yet.
> >>>>>
> >>>>> MODE can be used to compare two different gridded data files.
They
> can
> >>>>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
> >> NetCDF
> >>>>> output of pcp_combine, and so on. MODE was developed
> >>>>> using accumulated precipitation data, but we have applied it
to other
> >>>>> fields, including radar reflectivity. We just had to adjust
the
> >>>>> convolution radius and threshold, and think about the other
settings.
> >>>>>
> >>>>> As for a source of gridded reflectivity data, I'm really not
sure.
> >> We've
> >>>>> used RTMA data from NCEP in the past, and there's a link to
that on
> the
> >>>>> observation data page. We've used Q2 data from NSSL
> >>>>> in the past, but we first had to get it into GRIB format. I
see the
> Q2
> >>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see
how to
> >>>>> access the data directly.
> >>>>>
> >>>>> Regarding UPP, yes, it destaggers the grid. We suggest using
the
> >> copygb
> >>>>> utility for regridding GRIB1 data. copygb only handles GRIB1,
not
> >> GRIB2.
> >>>>> To regrid GRIB2 data, you can use the cnvgrib
> >>>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively,
the
> wgrib2
> >>>>> tool does some regridding, but it's pretty limited. Here's a
portion
> >> of
> >>>>> the MET online tutorial that discussed copygb:
> >>>>>
> >>>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>>>
> >>>>> For examples of running MODE, please take a look in
> >>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there
of
> running
> >>>>> MODE. I'd also suggest reading through the MODE section of
the
> online
> >>>>> tutorial:
> >>>>>
> >>>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>>>
> >>>>> Generally speaking, you should start by playing around with
the
> >>>>> convolution radius and threshold to define objects that
capture your
> >> areas
> >>>>> of interest.
> >>>>>
> >>>>> Regarding future enhancements, at this point our funding is
limited
> to
> >>>>> only support - no additional development. Hopefully, that
will
> change
> >> in
> >>>>> the future. We have submitted a proposal that would
> >>>>> include development to support automated regridding of data.
So you
> >>>>> could skip the copygb step, for example, before running
grid_stat and
> >> MODE.
> >>>>> As for why the tools for petroleum, chemistry,
> >>>>> biology, and medicine are more sophisticated than those for
> >> meteorology,
> >>>>> I suspect there's more money driving the other disciplines.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>>>
> >>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> >>>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
> >>>>>> Queue: met_help
> >>>>>> Subject: Obs data to feed in MET tools.
> >>>>>> Owner: Nobody
> >>>>>> Requestors: alexandre.o.fierro at gmail.com
> >>>>>> Status: new
> >>>>>> Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>
> >>>>>>
> >>>>>> Hi John:
> >>>>>>
> >>>>>> I have been reading the MET Users Guide for data formats and
> remained
> >> a
> >>>>> bit
> >>>>>> daunted by this constant interplay between all sorts of file
> formats -
> >>>>> At
> >>>>>> the moment my goal is rather succinct, I would like to be
able to
> >>>>> compare
> >>>>>> my WRF forecast (lets say composite dBZ) with observations
(from
> e.g,
> >>>>> NMQ,
> >>>>>> NCEP or another source).
> >>>>>>
> >>>>>> Where can I obtain the observation file with formats
compliant with
> >> MET
> >>>>> as
> >>>>>> the Users Guide does not point to any specific URL? Note that
I am
> now
> >>>>> able
> >>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
> >>>>>>
> >>>>>> I would be interested in using the MODE tool for compiste dBZ
> during a
> >>>>>> single model time. I have read, however, that MODE was
designed to
> >>>>> handle
> >>>>>> accumulated precip and needs input from pcp_combine. How can
I used
> >>>>>> observed composite dBZ as input and where can I obtain the
file with
> >>>>> this
> >>>>>> data in the correct format ?
> >>>>>>
> >>>>>> The obs and WRF output data are initially not on the same
grid + the
> >> WRF
> >>>>>> data is staggered.
> >>>>>>
> >>>>>> 1) I assume that UPP de-staggers the data when converting to
GRB1
> >>>>> correct ?
> >>>>>> 2) How do I interpolate the composite dBZ obs data onto the
> >>>>> GRIB1-derived
> >>>>>> grids or vice versa ?
> >>>>>> 3) Would you have a sample namelist available for me to run
MODE
> once
> >>>>> I'll
> >>>>>> succeed in obtaining WRF and OBS data on the same regular
grid ?.
> >>>>>>
> >>>>>> NB: Would there be any plans in the future to make all the
above
> >> process
> >>>>>> more user friendly ? Aka a self-contained intuitive GUI
package
> (like
> >>>>>> Matlab) that reads in data directly from WRF or any other
model,
> >> figures
> >>>>>> out the computational grid the output data it is on, then
reads in
> any
> >>>>>> matching standard Level-II observations, figures out the
format,
> >>>>>> interpolate and destaggers the data and provide the desired
plots
> and
> >>>>> stats
> >>>>>> to the user ? I have friends in many other fields (petroleum,
> >> chemistry,
> >>>>>> biology, medecine) and we (meteorologists) are perhaps the
only one
> >>>>> having
> >>>>>> to deal with those intermediate extra-curricular tedious
tasks
> related
> >>>>> to
> >>>>>> installation of complicated packages, shell scripts,
cumbersome
> binary
> >>>>> file
> >>>>>> formats (Especially GRIB which I despise) and programming in
10
> >>>>> different
> >>>>>> languages. For instance, when my friend in bio-engineering
received
> a
> >>>>> new
> >>>>>> apparatus designed to gather X/Y data on a given assay
experiments,
> a
> >>>>>> computer + GUI software came along with it to make all the
stats and
> >>>>>> required plots to him/her with a a single mouse click - No
specific
> >>>>>> computing skills were required other than basic Windows. Why
isn't
> it
> >>>>> the
> >>>>>> same for meteorologists I wonder ? I am sure I am speaking
for many
> >>>>>> (similarly 'frustrated') individuals here as in the end, what
> matters
> >> to
> >>>>>> everyone are the results-
> >>>>>>
> >>>>>> Cheers and best,
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -------------------------------------------------------------
> >>>> Alexandre Fierro, PhD
> >>>> Research Scientist-
> >>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
> >> (OU/NOAA)
> >>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>
> >>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift; That
> >> is
> >>>> why it is called the Present"
> >>>>
> >>>> "There are only 10 types of people in the world:
> >>>> Those who understand binary, and those who don't"
> >>>>
> >>>> "My opinions are my own and not representative of OU, NSSL,
> >>>> AOML, HRD, LANL or any affiliates."
> >>>> ^.^
> >>>> (o o)
> >>>> /( V )\
> >>>> ---m---m----
> >>>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Mon Jun 03 09:30:09 2013
Alex,
The pcp_combine tool is telling you that it can't find 4-hour
accumulated precipitation in the file named WRFPRS_d01_04. So what
does that file contain? If you have the wgrib utility available on
your system, try running the following:
wgrib WRFPRS_d01_04 | grep APCP
The output should tell you what accumulation interval(s) are in there.
You've said that it contains 1-hour accumulated precip in your
message, so I suspect that wgrib will confirm that. But your
call to pcp_combine is requesting 4-hours of accumulated precip with
"WRFPRS_d01_04 04".
Here's what I think you want:
../bin/pcp_combine -add \
WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
WRFPRS_d01_APCP_06_03_to_09.nc
Note the following:
(1) I've selecting the "01" hour accumulation from each of the input
files and am adding them together.
(2) I've omitted the first argument you used, for "WRFPRS_d01_03".
GRIB file contain an accumulation of precipitation *ending* at the
file's time. So WRFPRS_d01_03 contains precip between hours 2
and 3. If you want a total accumulation from 3 to 6, you should use
the six files listed in the command above.
Make sense?
Thanks,
John
On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> John:
>
> I have tried the following with 6 separate GRIB files each
containing 1-h
> accum precip but ran into this problem:
>
> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05 WRFPRS_d01_06 06
> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
> WRFPRS_d01_APCP_06_03_to_09.nc
> DEBUG 1: Reading input file: WRFPRS_d01_03
> DEBUG 1: Reading input file: WRFPRS_d01_04
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
> "APCP/A3" in GRIB file "WRFPRS_d01_04".
> WARNING:
> ERROR :
> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
> ERROR :
>
> What are the double digit numbers ahed of the filename ?
>
> The original WRF OUT Files have:
>
> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>
> ...
> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
PRECIPITATION" ;
> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
> PRECIPITATION" ;
> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
> PRECIPITATION" ;
> ...
>
> Cheers and thanks,
>
> Alex-
>
> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> Yep, by default WRF-ARW dumps out it's precipitation accumulated
over the
>> entire model run. So you'll need to adjust your forecast
accumulation
>> intervals to match the observation accumulation
>> intervals. For example, to get the 6-hour accumulation between
forecast
>> hours 24 and 30, you'd do the following:
>>
>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
WRFPRS_d01_24 24
>> WRFPRS_d01_APCP_06_24_to_30.nc
>>
>> That will grab the 30 hours of precip from the first file and the
24 hours
>> of precip from the second file and subtract them. The last
argument is the
>> name of the NetCDF file to be used.
>>
>> You might also want to run the plot_data_plane utility just to make
sure
>> that your data looks good:
>>
>> METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
>> 'name="APCP"; level="A30";'
>>
>> That will select the field we've described (precip accumulated over
30
>> hours) from the file you've passed it and create a postscript image
of it.
>>
>> Hope that helps.
>>
>> Thanks,
>> John
>>
>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>
>>> Hi John:
>>>
>>> I use ARW so seems like UNIPOST already de-staggers the data.
>>>
>>> I have:
>>>
>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1 WRFPRS_d01_03
>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
levels=(0,0)
>>> grid=255 MSL 3hr fcst:
>>> PRMSL=Pressure reduced to MSL [Pa]
>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
num_in_ave 0
>>> missing 0
>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
winds(grid)
>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov -98.000000
>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP
0.000000
>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64
mode 136
>>> min/max data 99016.4 102768 num bits 16 BDS_Ref 9.90164e+06
>> DecScale 2
>>> BinScale 3
>>>
>>> The next step I guess would be to produce accumulated precip from
several
>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast hour)?
>>>
>>> Cheers,
>>>
>>> Alex-
>>>
>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Alex,
>>>>
>>>> So you have a GRIB file that's output by unipost, named
"WRFPRS_d01_03".
>>>> And you're running it through copygb using the grid defined by
the
>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
>>>>
>>>> Also, try running the following:
>>>> wgrib -V -d 1 WRFPRS_d01_03
>>>>
>>>> That'll give a 'V'erbose description of the first record in that
file,
>>>> including the current grid definition.
>>>>
>>>> Can you send me that output?
>>>>
>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output
>> of
>>>> unipost should already be unstaggered. If it's WRF-NMM, the
output of
>>>> unipost will be staggered, and you need to run it
>>>> through copygb to de-stagger it.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>
>>>>> Hi John:
>>>>>
>>>>> As you might have expected I ran into some issues running
copygb.
>>>>>
>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert conformal
>>>> grid-When I
>>>>> run:
>>>>>
>>>>> cat > itag <<EOF
>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>>>> netcdf
>>>>> ${SY}-${SM}-${SD}_03:00:00
>>>>> ${tag}
>>>>> EOF
>>>>> echo 'FILE TO BE PROCESSED'
>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>>>>
>>>>> # this stuff interp to a regular grid
>>>>> read nav < 'copygb_gridnav.txt'
>>>>> export nav
>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03 wrfprs_d01_03
>>>>>
>>>>> I get:
>>>>>
>>>>> copygb: unsupported output grid
>>>>>
>>>>> I tried to change it to:
>>>>>
>>>>> read nav < 'copygb_hwrf.txt'
>>>>>
>>>>> but got the same error
>>>>>
>>>>> Any clues on how I can get this program to destagger my WRF
output in
>> the
>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
>>>>>
>>>>> Cheers and thanks,
>>>>>
>>>>> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
>>>>>
>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>>>> <alexandre.o.fierro at gmail.com>wrote:
>>>>>
>>>>>> Dear John:
>>>>>>
>>>>>> Many thanks for your prompt and detailed reply.
>>>>>>
>>>>>> I definitely blame the lack of funding in our field to hire
software
>>>>>> engineers (at the level of the individuals working for
MathWorks,
>>>> Google,
>>>>>> Facebook etc) to develop user friendly GUIs for meteorological
use. I
>>>> truly
>>>>>> hope your team will get the funding it deserves to further
enhance
>> this
>>>>>> very complex tool, which has a lot of potential and could
definitely
>> be
>>>> of
>>>>>> relevant use for routine forecasters.
>>>>>>
>>>>>> I will give it a try using the precip data you specified for
now -
>> I'll
>>>>>> let you know if I run into some issues.
>>>>>>
>>>>>> South side of Norman and Purcell are in a tornado warning at
the
>> moment
>>>> -
>>>>>> my attention is now 'detoured' towards the sky.
>>>>>>
>>>>>> Cheers and best,
>>>>>>
>>>>>> Alexandre-
>>>>>>
>>>>>>
>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
>>>>>> met_help at ucar.edu> wrote:
>>>>>>
>>>>>>> Alex,
>>>>>>>
>>>>>>> Here's a link to the MET website for some sources of
observation
>> data:
>>>>>>>
>> http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>>>>>
>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format. The
>>>> only
>>>>>>> other gridded data formats it can handle are the NetCDF output
of the
>>>>>>> pinterp utility, and the internal NetCDF format used by
>>>>>>> MET. We'd like to more generally support CF-compliant NetCDF
data,
>> but
>>>>>>> we haven't gotten that done yet.
>>>>>>>
>>>>>>> MODE can be used to compare two different gridded data files.
They
>> can
>>>>>>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
>>>> NetCDF
>>>>>>> output of pcp_combine, and so on. MODE was developed
>>>>>>> using accumulated precipitation data, but we have applied it
to other
>>>>>>> fields, including radar reflectivity. We just had to adjust
the
>>>>>>> convolution radius and threshold, and think about the other
settings.
>>>>>>>
>>>>>>> As for a source of gridded reflectivity data, I'm really not
sure.
>>>> We've
>>>>>>> used RTMA data from NCEP in the past, and there's a link to
that on
>> the
>>>>>>> observation data page. We've used Q2 data from NSSL
>>>>>>> in the past, but we first had to get it into GRIB format. I
see the
>> Q2
>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see
how to
>>>>>>> access the data directly.
>>>>>>>
>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest using
the
>>>> copygb
>>>>>>> utility for regridding GRIB1 data. copygb only handles GRIB1,
not
>>>> GRIB2.
>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>>>>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively,
the
>> wgrib2
>>>>>>> tool does some regridding, but it's pretty limited. Here's a
portion
>>>> of
>>>>>>> the MET online tutorial that discussed copygb:
>>>>>>>
>>>>>>>
>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>>>>>
>>>>>>> For examples of running MODE, please take a look in
>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there
of
>> running
>>>>>>> MODE. I'd also suggest reading through the MODE section of
the
>> online
>>>>>>> tutorial:
>>>>>>>
>>>>>>>
>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>>>>>
>>>>>>> Generally speaking, you should start by playing around with
the
>>>>>>> convolution radius and threshold to define objects that
capture your
>>>> areas
>>>>>>> of interest.
>>>>>>>
>>>>>>> Regarding future enhancements, at this point our funding is
limited
>> to
>>>>>>> only support - no additional development. Hopefully, that
will
>> change
>>>> in
>>>>>>> the future. We have submitted a proposal that would
>>>>>>> include development to support automated regridding of data.
So you
>>>>>>> could skip the copygb step, for example, before running
grid_stat and
>>>> MODE.
>>>>>>> As for why the tools for petroleum, chemistry,
>>>>>>> biology, and medicine are more sophisticated than those for
>>>> meteorology,
>>>>>>> I suspect there's more money driving the other disciplines.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>>>>>
>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>>>>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
>>>>>>>> Queue: met_help
>>>>>>>> Subject: Obs data to feed in MET tools.
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>>>>>>> Status: new
>>>>>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi John:
>>>>>>>>
>>>>>>>> I have been reading the MET Users Guide for data formats and
>> remained
>>>> a
>>>>>>> bit
>>>>>>>> daunted by this constant interplay between all sorts of file
>> formats -
>>>>>>> At
>>>>>>>> the moment my goal is rather succinct, I would like to be
able to
>>>>>>> compare
>>>>>>>> my WRF forecast (lets say composite dBZ) with observations
(from
>> e.g,
>>>>>>> NMQ,
>>>>>>>> NCEP or another source).
>>>>>>>>
>>>>>>>> Where can I obtain the observation file with formats
compliant with
>>>> MET
>>>>>>> as
>>>>>>>> the Users Guide does not point to any specific URL? Note that
I am
>> now
>>>>>>> able
>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>>>>>
>>>>>>>> I would be interested in using the MODE tool for compiste dBZ
>> during a
>>>>>>>> single model time. I have read, however, that MODE was
designed to
>>>>>>> handle
>>>>>>>> accumulated precip and needs input from pcp_combine. How can
I used
>>>>>>>> observed composite dBZ as input and where can I obtain the
file with
>>>>>>> this
>>>>>>>> data in the correct format ?
>>>>>>>>
>>>>>>>> The obs and WRF output data are initially not on the same
grid + the
>>>> WRF
>>>>>>>> data is staggered.
>>>>>>>>
>>>>>>>> 1) I assume that UPP de-staggers the data when converting to
GRB1
>>>>>>> correct ?
>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto the
>>>>>>> GRIB1-derived
>>>>>>>> grids or vice versa ?
>>>>>>>> 3) Would you have a sample namelist available for me to run
MODE
>> once
>>>>>>> I'll
>>>>>>>> succeed in obtaining WRF and OBS data on the same regular
grid ?.
>>>>>>>>
>>>>>>>> NB: Would there be any plans in the future to make all the
above
>>>> process
>>>>>>>> more user friendly ? Aka a self-contained intuitive GUI
package
>> (like
>>>>>>>> Matlab) that reads in data directly from WRF or any other
model,
>>>> figures
>>>>>>>> out the computational grid the output data it is on, then
reads in
>> any
>>>>>>>> matching standard Level-II observations, figures out the
format,
>>>>>>>> interpolate and destaggers the data and provide the desired
plots
>> and
>>>>>>> stats
>>>>>>>> to the user ? I have friends in many other fields (petroleum,
>>>> chemistry,
>>>>>>>> biology, medecine) and we (meteorologists) are perhaps the
only one
>>>>>>> having
>>>>>>>> to deal with those intermediate extra-curricular tedious
tasks
>> related
>>>>>>> to
>>>>>>>> installation of complicated packages, shell scripts,
cumbersome
>> binary
>>>>>>> file
>>>>>>>> formats (Especially GRIB which I despise) and programming in
10
>>>>>>> different
>>>>>>>> languages. For instance, when my friend in bio-engineering
received
>> a
>>>>>>> new
>>>>>>>> apparatus designed to gather X/Y data on a given assay
experiments,
>> a
>>>>>>>> computer + GUI software came along with it to make all the
stats and
>>>>>>>> required plots to him/her with a a single mouse click - No
specific
>>>>>>>> computing skills were required other than basic Windows. Why
isn't
>> it
>>>>>>> the
>>>>>>>> same for meteorologists I wonder ? I am sure I am speaking
for many
>>>>>>>> (similarly 'frustrated') individuals here as in the end, what
>> matters
>>>> to
>>>>>>>> everyone are the results-
>>>>>>>>
>>>>>>>> Cheers and best,
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -------------------------------------------------------------
>>>>>> Alexandre Fierro, PhD
>>>>>> Research Scientist-
>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
>>>> (OU/NOAA)
>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>>>
>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift; That
>>>> is
>>>>>> why it is called the Present"
>>>>>>
>>>>>> "There are only 10 types of people in the world:
>>>>>> Those who understand binary, and those who don't"
>>>>>>
>>>>>> "My opinions are my own and not representative of OU, NSSL,
>>>>>> AOML, HRD, LANL or any affiliates."
>>>>>> ^.^
>>>>>> (o o)
>>>>>> /( V )\
>>>>>> ---m---m----
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Mon Jun 03 09:51:57 2013
Hi John:
Makes perfect sense.
I have:
/home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 | grep APCP
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
acc:NAve=0
So seems like I already have 0-4h accum precip (?) - This would
explain why
I have the same error as before:
/home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07 01
WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
DEBUG 1: Reading input file: WRFPRS_d01_04
WARNING:
WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
"APCP/A1" in GRIB file "WRFPRS_d01_04".
WARNING:
ERROR :
ERROR : get_field() -> can't get data plane from file "WRFPRS_d01_04"
ERROR :
The netcdf-equivalent array that *should* be read for this is (are):
float RAINC(Time, south_north, west_east)
;
RAINC:FieldType = 104
;
RAINC:MemoryOrder = "XY "
;
RAINC:description = "ACCUMULATED TOTAL CUMULUS
PRECIPITATION"
;
RAINC:units = "mm"
;
RAINC:stagger = ""
;
RAINC:coordinates = "XLONG XLAT"
;
float RAINSH(Time, south_north, west_east)
;
RAINSH:FieldType = 104
;
RAINSH:MemoryOrder = "XY "
;
RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
PRECIPITATION"
;
RAINSH:units = "mm"
;
RAINSH:stagger = ""
;
RAINSH:coordinates = "XLONG XLAT"
;
float RAINNC(Time, south_north, west_east)
;
RAINNC:FieldType = 104
;
RAINNC:MemoryOrder = "XY "
;
RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
PRECIPITATION"
;
RAINNC:units = "mm"
;
RAINNC:stagger = ""
;
RAINNC:coordinates = "XLONG XLAT" ;
Cheers and thank you for your help/guidance,
Alex-
On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> The pcp_combine tool is telling you that it can't find 4-hour
accumulated
> precipitation in the file named WRFPRS_d01_04. So what does that
file
> contain? If you have the wgrib utility available on
> your system, try running the following:
> wgrib WRFPRS_d01_04 | grep APCP
>
> The output should tell you what accumulation interval(s) are in
there.
> You've said that it contains 1-hour accumulated precip in your
message, so
> I suspect that wgrib will confirm that. But your
> call to pcp_combine is requesting 4-hours of accumulated precip with
> "WRFPRS_d01_04 04".
>
> Here's what I think you want:
>
> ../bin/pcp_combine -add \
> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
> WRFPRS_d01_APCP_06_03_to_09.nc
>
> Note the following:
> (1) I've selecting the "01" hour accumulation from each of the input
files
> and am adding them together.
> (2) I've omitted the first argument you used, for "WRFPRS_d01_03".
GRIB
> file contain an accumulation of precipitation *ending* at the file's
time.
> So WRFPRS_d01_03 contains precip between hours 2
> and 3. If you want a total accumulation from 3 to 6, you should use
the
> six files listed in the command above.
>
> Make sense?
>
> Thanks,
> John
>
>
>
> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > John:
> >
> > I have tried the following with 6 separate GRIB files each
containing 1-h
> > accum precip but ran into this problem:
> >
> > /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
> > WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05 WRFPRS_d01_06
06
> > WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
> > WRFPRS_d01_APCP_06_03_to_09.nc
> > DEBUG 1: Reading input file: WRFPRS_d01_03
> > DEBUG 1: Reading input file: WRFPRS_d01_04
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> VarInfo
> > "APCP/A3" in GRIB file "WRFPRS_d01_04".
> > WARNING:
> > ERROR :
> > ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
> > ERROR :
> >
> > What are the double digit numbers ahed of the filename ?
> >
> > The original WRF OUT Files have:
> >
> > ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
> >
> > ...
> > 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
> PRECIPITATION" ;
> > 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
> > PRECIPITATION" ;
> > 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
> > PRECIPITATION" ;
> > ...
> >
> > Cheers and thanks,
> >
> > Alex-
> >
> > On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Alex,
> >>
> >> Yep, by default WRF-ARW dumps out it's precipitation accumulated
over
> the
> >> entire model run. So you'll need to adjust your forecast
accumulation
> >> intervals to match the observation accumulation
> >> intervals. For example, to get the 6-hour accumulation between
forecast
> >> hours 24 and 30, you'd do the following:
> >>
> >> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
WRFPRS_d01_24 24
> >> WRFPRS_d01_APCP_06_24_to_30.nc
> >>
> >> That will grab the 30 hours of precip from the first file and the
24
> hours
> >> of precip from the second file and subtract them. The last
argument is
> the
> >> name of the NetCDF file to be used.
> >>
> >> You might also want to run the plot_data_plane utility just to
make sure
> >> that your data looks good:
> >>
> >> METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
> >> 'name="APCP"; level="A30";'
> >>
> >> That will select the field we've described (precip accumulated
over 30
> >> hours) from the file you've passed it and create a postscript
image of
> it.
> >>
> >> Hope that helps.
> >>
> >> Thanks,
> >> John
> >>
> >> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>
> >>> Hi John:
> >>>
> >>> I use ARW so seems like UNIPOST already de-staggers the data.
> >>>
> >>> I have:
> >>>
> >>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
> >>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
levels=(0,0)
> >>> grid=255 MSL 3hr fcst:
> >>> PRMSL=Pressure reduced to MSL [Pa]
> >>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
> num_in_ave 0
> >>> missing 0
> >>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
winds(grid)
> >>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov -98.000000
> >>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP
0.000000
> >>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64
mode
> 136
> >>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
> >> DecScale 2
> >>> BinScale 3
> >>>
> >>> The next step I guess would be to produce accumulated precip
from
> several
> >>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
> >>>
> >>> Cheers,
> >>>
> >>> Alex-
> >>>
> >>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> Alex,
> >>>>
> >>>> So you have a GRIB file that's output by unipost, named
> "WRFPRS_d01_03".
> >>>> And you're running it through copygb using the grid defined
by the
> >>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
> >>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
> >>>>
> >>>> Also, try running the following:
> >>>> wgrib -V -d 1 WRFPRS_d01_03
> >>>>
> >>>> That'll give a 'V'erbose description of the first record in
that file,
> >>>> including the current grid definition.
> >>>>
> >>>> Can you send me that output?
> >>>>
> >>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output
> >> of
> >>>> unipost should already be unstaggered. If it's WRF-NMM, the
output of
> >>>> unipost will be staggered, and you need to run it
> >>>> through copygb to de-stagger it.
> >>>>
> >>>> Thanks,
> >>>> John
> >>>>
> >>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >>>>>
> >>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
> >>>>>
> >>>>> Hi John:
> >>>>>
> >>>>> As you might have expected I ran into some issues running
copygb.
> >>>>>
> >>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
> >>>> grid-When I
> >>>>> run:
> >>>>>
> >>>>> cat > itag <<EOF
> >>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>>>> netcdf
> >>>>> ${SY}-${SM}-${SD}_03:00:00
> >>>>> ${tag}
> >>>>> EOF
> >>>>> echo 'FILE TO BE PROCESSED'
> >>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
> >>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
> >>>>>
> >>>>> # this stuff interp to a regular grid
> >>>>> read nav < 'copygb_gridnav.txt'
> >>>>> export nav
> >>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
> >>>>>
> >>>>> I get:
> >>>>>
> >>>>> copygb: unsupported output grid
> >>>>>
> >>>>> I tried to change it to:
> >>>>>
> >>>>> read nav < 'copygb_hwrf.txt'
> >>>>>
> >>>>> but got the same error
> >>>>>
> >>>>> Any clues on how I can get this program to destagger my WRF
output in
> >> the
> >>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
> >>>>>
> >>>>> Cheers and thanks,
> >>>>>
> >>>>> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
> >>>>>
> >>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> >>>>> <alexandre.o.fierro at gmail.com>wrote:
> >>>>>
> >>>>>> Dear John:
> >>>>>>
> >>>>>> Many thanks for your prompt and detailed reply.
> >>>>>>
> >>>>>> I definitely blame the lack of funding in our field to hire
software
> >>>>>> engineers (at the level of the individuals working for
MathWorks,
> >>>> Google,
> >>>>>> Facebook etc) to develop user friendly GUIs for
meteorological use.
> I
> >>>> truly
> >>>>>> hope your team will get the funding it deserves to further
enhance
> >> this
> >>>>>> very complex tool, which has a lot of potential and could
definitely
> >> be
> >>>> of
> >>>>>> relevant use for routine forecasters.
> >>>>>>
> >>>>>> I will give it a try using the precip data you specified for
now -
> >> I'll
> >>>>>> let you know if I run into some issues.
> >>>>>>
> >>>>>> South side of Norman and Purcell are in a tornado warning at
the
> >> moment
> >>>> -
> >>>>>> my attention is now 'detoured' towards the sky.
> >>>>>>
> >>>>>> Cheers and best,
> >>>>>>
> >>>>>> Alexandre-
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
> >>>>>> met_help at ucar.edu> wrote:
> >>>>>>
> >>>>>>> Alex,
> >>>>>>>
> >>>>>>> Here's a link to the MET website for some sources of
observation
> >> data:
> >>>>>>>
> >> http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>>>>>
> >>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
> The
> >>>> only
> >>>>>>> other gridded data formats it can handle are the NetCDF
output of
> the
> >>>>>>> pinterp utility, and the internal NetCDF format used by
> >>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF data,
> >> but
> >>>>>>> we haven't gotten that done yet.
> >>>>>>>
> >>>>>>> MODE can be used to compare two different gridded data
files. They
> >> can
> >>>>>>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
> >>>> NetCDF
> >>>>>>> output of pcp_combine, and so on. MODE was developed
> >>>>>>> using accumulated precipitation data, but we have applied it
to
> other
> >>>>>>> fields, including radar reflectivity. We just had to adjust
the
> >>>>>>> convolution radius and threshold, and think about the other
> settings.
> >>>>>>>
> >>>>>>> As for a source of gridded reflectivity data, I'm really not
sure.
> >>>> We've
> >>>>>>> used RTMA data from NCEP in the past, and there's a link to
that on
> >> the
> >>>>>>> observation data page. We've used Q2 data from NSSL
> >>>>>>> in the past, but we first had to get it into GRIB format. I
see
> the
> >> Q2
> >>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see
how to
> >>>>>>> access the data directly.
> >>>>>>>
> >>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using the
> >>>> copygb
> >>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1, not
> >>>> GRIB2.
> >>>>>>> To regrid GRIB2 data, you can use the cnvgrib
> >>>>>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively,
the
> >> wgrib2
> >>>>>>> tool does some regridding, but it's pretty limited. Here's
a
> portion
> >>>> of
> >>>>>>> the MET online tutorial that discussed copygb:
> >>>>>>>
> >>>>>>>
> >>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>>>>>
> >>>>>>> For examples of running MODE, please take a look in
> >>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there
of
> >> running
> >>>>>>> MODE. I'd also suggest reading through the MODE section of
the
> >> online
> >>>>>>> tutorial:
> >>>>>>>
> >>>>>>>
> >>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>>>>>
> >>>>>>> Generally speaking, you should start by playing around with
the
> >>>>>>> convolution radius and threshold to define objects that
capture
> your
> >>>> areas
> >>>>>>> of interest.
> >>>>>>>
> >>>>>>> Regarding future enhancements, at this point our funding is
limited
> >> to
> >>>>>>> only support - no additional development. Hopefully, that
will
> >> change
> >>>> in
> >>>>>>> the future. We have submitted a proposal that would
> >>>>>>> include development to support automated regridding of data.
So
> you
> >>>>>>> could skip the copygb step, for example, before running
grid_stat
> and
> >>>> MODE.
> >>>>>>> As for why the tools for petroleum, chemistry,
> >>>>>>> biology, and medicine are more sophisticated than those for
> >>>> meteorology,
> >>>>>>> I suspect there's more money driving the other disciplines.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> John
> >>>>>>>
> >>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>>>>>
> >>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> >>>>>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
> >>>>>>>> Queue: met_help
> >>>>>>>> Subject: Obs data to feed in MET tools.
> >>>>>>>> Owner: Nobody
> >>>>>>>> Requestors: alexandre.o.fierro at gmail.com
> >>>>>>>> Status: new
> >>>>>>>> Ticket <URL:
> >>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Hi John:
> >>>>>>>>
> >>>>>>>> I have been reading the MET Users Guide for data formats
and
> >> remained
> >>>> a
> >>>>>>> bit
> >>>>>>>> daunted by this constant interplay between all sorts of
file
> >> formats -
> >>>>>>> At
> >>>>>>>> the moment my goal is rather succinct, I would like to be
able to
> >>>>>>> compare
> >>>>>>>> my WRF forecast (lets say composite dBZ) with observations
(from
> >> e.g,
> >>>>>>> NMQ,
> >>>>>>>> NCEP or another source).
> >>>>>>>>
> >>>>>>>> Where can I obtain the observation file with formats
compliant
> with
> >>>> MET
> >>>>>>> as
> >>>>>>>> the Users Guide does not point to any specific URL? Note
that I am
> >> now
> >>>>>>> able
> >>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
> >>>>>>>>
> >>>>>>>> I would be interested in using the MODE tool for compiste
dBZ
> >> during a
> >>>>>>>> single model time. I have read, however, that MODE was
designed to
> >>>>>>> handle
> >>>>>>>> accumulated precip and needs input from pcp_combine. How
can I
> used
> >>>>>>>> observed composite dBZ as input and where can I obtain the
file
> with
> >>>>>>> this
> >>>>>>>> data in the correct format ?
> >>>>>>>>
> >>>>>>>> The obs and WRF output data are initially not on the same
grid +
> the
> >>>> WRF
> >>>>>>>> data is staggered.
> >>>>>>>>
> >>>>>>>> 1) I assume that UPP de-staggers the data when converting
to GRB1
> >>>>>>> correct ?
> >>>>>>>> 2) How do I interpolate the composite dBZ obs data onto the
> >>>>>>> GRIB1-derived
> >>>>>>>> grids or vice versa ?
> >>>>>>>> 3) Would you have a sample namelist available for me to run
MODE
> >> once
> >>>>>>> I'll
> >>>>>>>> succeed in obtaining WRF and OBS data on the same regular
grid ?.
> >>>>>>>>
> >>>>>>>> NB: Would there be any plans in the future to make all the
above
> >>>> process
> >>>>>>>> more user friendly ? Aka a self-contained intuitive GUI
package
> >> (like
> >>>>>>>> Matlab) that reads in data directly from WRF or any other
model,
> >>>> figures
> >>>>>>>> out the computational grid the output data it is on, then
reads in
> >> any
> >>>>>>>> matching standard Level-II observations, figures out the
format,
> >>>>>>>> interpolate and destaggers the data and provide the desired
plots
> >> and
> >>>>>>> stats
> >>>>>>>> to the user ? I have friends in many other fields
(petroleum,
> >>>> chemistry,
> >>>>>>>> biology, medecine) and we (meteorologists) are perhaps the
only
> one
> >>>>>>> having
> >>>>>>>> to deal with those intermediate extra-curricular tedious
tasks
> >> related
> >>>>>>> to
> >>>>>>>> installation of complicated packages, shell scripts,
cumbersome
> >> binary
> >>>>>>> file
> >>>>>>>> formats (Especially GRIB which I despise) and programming
in 10
> >>>>>>> different
> >>>>>>>> languages. For instance, when my friend in bio-engineering
> received
> >> a
> >>>>>>> new
> >>>>>>>> apparatus designed to gather X/Y data on a given assay
> experiments,
> >> a
> >>>>>>>> computer + GUI software came along with it to make all the
stats
> and
> >>>>>>>> required plots to him/her with a a single mouse click - No
> specific
> >>>>>>>> computing skills were required other than basic Windows.
Why isn't
> >> it
> >>>>>>> the
> >>>>>>>> same for meteorologists I wonder ? I am sure I am speaking
for
> many
> >>>>>>>> (similarly 'frustrated') individuals here as in the end,
what
> >> matters
> >>>> to
> >>>>>>>> everyone are the results-
> >>>>>>>>
> >>>>>>>> Cheers and best,
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> -------------------------------------------------------------
> >>>>>> Alexandre Fierro, PhD
> >>>>>> Research Scientist-
> >>>>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
> >>>> (OU/NOAA)
> >>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>>>
> >>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift;
> That
> >>>> is
> >>>>>> why it is called the Present"
> >>>>>>
> >>>>>> "There are only 10 types of people in the world:
> >>>>>> Those who understand binary, and those who don't"
> >>>>>>
> >>>>>> "My opinions are my own and not representative of OU, NSSL,
> >>>>>> AOML, HRD, LANL or any affiliates."
> >>>>>> ^.^
> >>>>>> (o o)
> >>>>>> /( V )\
> >>>>>> ---m---m----
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Mon Jun 03 10:50:05 2013
Alex,
I see that you're using METv4.0. There was a bugfix posted on
10/16/2012 that I believe is related to the problem you're seeing.
Please follow the instructions at the top of this page to download
and apply all of the latest METv4.0 patches:
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
Sorry for not catching that one sooner.
Thanks,
John
On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> Hi John:
>
> Makes perfect sense.
>
> I have:
>
> /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 | grep
APCP
>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
> acc:NAve=0
>
> So seems like I already have 0-4h accum precip (?) - This would
explain why
> I have the same error as before:
>
> /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07 01
> WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
> DEBUG 1: Reading input file: WRFPRS_d01_04
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
> "APCP/A1" in GRIB file "WRFPRS_d01_04".
> WARNING:
> ERROR :
> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
> ERROR :
>
> The netcdf-equivalent array that *should* be read for this is (are):
>
> float RAINC(Time, south_north, west_east)
> ;
>
> RAINC:FieldType = 104
> ;
>
> RAINC:MemoryOrder = "XY "
> ;
>
> RAINC:description = "ACCUMULATED TOTAL CUMULUS
> PRECIPITATION"
> ;
> RAINC:units = "mm"
> ;
>
> RAINC:stagger = ""
> ;
>
> RAINC:coordinates = "XLONG XLAT"
> ;
>
> float RAINSH(Time, south_north, west_east)
> ;
>
> RAINSH:FieldType = 104
> ;
>
> RAINSH:MemoryOrder = "XY "
> ;
>
> RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
> PRECIPITATION"
> ;
> RAINSH:units = "mm"
> ;
>
> RAINSH:stagger = ""
> ;
>
> RAINSH:coordinates = "XLONG XLAT"
> ;
>
> float RAINNC(Time, south_north, west_east)
> ;
>
> RAINNC:FieldType = 104
> ;
>
> RAINNC:MemoryOrder = "XY "
> ;
>
> RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
> PRECIPITATION"
> ;
> RAINNC:units = "mm"
> ;
>
> RAINNC:stagger = ""
> ;
>
> RAINNC:coordinates = "XLONG XLAT" ;
>
>
> Cheers and thank you for your help/guidance,
>
> Alex-
>
> On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> The pcp_combine tool is telling you that it can't find 4-hour
accumulated
>> precipitation in the file named WRFPRS_d01_04. So what does that
file
>> contain? If you have the wgrib utility available on
>> your system, try running the following:
>> wgrib WRFPRS_d01_04 | grep APCP
>>
>> The output should tell you what accumulation interval(s) are in
there.
>> You've said that it contains 1-hour accumulated precip in your
message, so
>> I suspect that wgrib will confirm that. But your
>> call to pcp_combine is requesting 4-hours of accumulated precip
with
>> "WRFPRS_d01_04 04".
>>
>> Here's what I think you want:
>>
>> ../bin/pcp_combine -add \
>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
>> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
>> WRFPRS_d01_APCP_06_03_to_09.nc
>>
>> Note the following:
>> (1) I've selecting the "01" hour accumulation from each of the
input files
>> and am adding them together.
>> (2) I've omitted the first argument you used, for "WRFPRS_d01_03".
GRIB
>> file contain an accumulation of precipitation *ending* at the
file's time.
>> So WRFPRS_d01_03 contains precip between hours 2
>> and 3. If you want a total accumulation from 3 to 6, you should
use the
>> six files listed in the command above.
>>
>> Make sense?
>>
>> Thanks,
>> John
>>
>>
>>
>> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>
>>> John:
>>>
>>> I have tried the following with 6 separate GRIB files each
containing 1-h
>>> accum precip but ran into this problem:
>>>
>>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
>>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05 WRFPRS_d01_06
06
>>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
>>> WRFPRS_d01_APCP_06_03_to_09.nc
>>> DEBUG 1: Reading input file: WRFPRS_d01_03
>>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>> WARNING:
>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
>> VarInfo
>>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
>>> WARNING:
>>> ERROR :
>>> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
>>> ERROR :
>>>
>>> What are the double digit numbers ahed of the filename ?
>>>
>>> The original WRF OUT Files have:
>>>
>>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>>>
>>> ...
>>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
>> PRECIPITATION" ;
>>> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
>>> PRECIPITATION" ;
>>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
>>> PRECIPITATION" ;
>>> ...
>>>
>>> Cheers and thanks,
>>>
>>> Alex-
>>>
>>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Alex,
>>>>
>>>> Yep, by default WRF-ARW dumps out it's precipitation accumulated
over
>> the
>>>> entire model run. So you'll need to adjust your forecast
accumulation
>>>> intervals to match the observation accumulation
>>>> intervals. For example, to get the 6-hour accumulation between
forecast
>>>> hours 24 and 30, you'd do the following:
>>>>
>>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
WRFPRS_d01_24 24
>>>> WRFPRS_d01_APCP_06_24_to_30.nc
>>>>
>>>> That will grab the 30 hours of precip from the first file and the
24
>> hours
>>>> of precip from the second file and subtract them. The last
argument is
>> the
>>>> name of the NetCDF file to be used.
>>>>
>>>> You might also want to run the plot_data_plane utility just to
make sure
>>>> that your data looks good:
>>>>
>>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
>>>> 'name="APCP"; level="A30";'
>>>>
>>>> That will select the field we've described (precip accumulated
over 30
>>>> hours) from the file you've passed it and create a postscript
image of
>> it.
>>>>
>>>> Hope that helps.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>
>>>>> Hi John:
>>>>>
>>>>> I use ARW so seems like UNIPOST already de-staggers the data.
>>>>>
>>>>> I have:
>>>>>
>>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
>>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
levels=(0,0)
>>>>> grid=255 MSL 3hr fcst:
>>>>> PRMSL=Pressure reduced to MSL [Pa]
>>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
>> num_in_ave 0
>>>>> missing 0
>>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
winds(grid)
>>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
-98.000000
>>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000 LonSP
0.000000
>>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan 64
mode
>> 136
>>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
>>>> DecScale 2
>>>>> BinScale 3
>>>>>
>>>>> The next step I guess would be to produce accumulated precip
from
>> several
>>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Alex-
>>>>>
>>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>> Alex,
>>>>>>
>>>>>> So you have a GRIB file that's output by unipost, named
>> "WRFPRS_d01_03".
>>>>>> And you're running it through copygb using the grid defined
by the
>>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
>>>>>>
>>>>>> Also, try running the following:
>>>>>> wgrib -V -d 1 WRFPRS_d01_03
>>>>>>
>>>>>> That'll give a 'V'erbose description of the first record in
that file,
>>>>>> including the current grid definition.
>>>>>>
>>>>>> Can you send me that output?
>>>>>>
>>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW, the
output
>>>> of
>>>>>> unipost should already be unstaggered. If it's WRF-NMM, the
output of
>>>>>> unipost will be staggered, and you need to run it
>>>>>> through copygb to de-stagger it.
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>>>>>>
>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
>>>>>>>
>>>>>>> Hi John:
>>>>>>>
>>>>>>> As you might have expected I ran into some issues running
copygb.
>>>>>>>
>>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
>>>>>> grid-When I
>>>>>>> run:
>>>>>>>
>>>>>>> cat > itag <<EOF
>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>>>>>> netcdf
>>>>>>> ${SY}-${SM}-${SD}_03:00:00
>>>>>>> ${tag}
>>>>>>> EOF
>>>>>>> echo 'FILE TO BE PROCESSED'
>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe > unipost_ctrl_d01.03.out
2>&1
>>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>>>>>>
>>>>>>> # this stuff interp to a regular grid
>>>>>>> read nav < 'copygb_gridnav.txt'
>>>>>>> export nav
>>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
>>>>>>>
>>>>>>> I get:
>>>>>>>
>>>>>>> copygb: unsupported output grid
>>>>>>>
>>>>>>> I tried to change it to:
>>>>>>>
>>>>>>> read nav < 'copygb_hwrf.txt'
>>>>>>>
>>>>>>> but got the same error
>>>>>>>
>>>>>>> Any clues on how I can get this program to destagger my WRF
output in
>>>> the
>>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran fine)?
>>>>>>>
>>>>>>> Cheers and thanks,
>>>>>>>
>>>>>>> PS: I am using METV4.0 and the model outout is from WRFV3.4.1
>>>>>>>
>>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>>>>>> <alexandre.o.fierro at gmail.com>wrote:
>>>>>>>
>>>>>>>> Dear John:
>>>>>>>>
>>>>>>>> Many thanks for your prompt and detailed reply.
>>>>>>>>
>>>>>>>> I definitely blame the lack of funding in our field to hire
software
>>>>>>>> engineers (at the level of the individuals working for
MathWorks,
>>>>>> Google,
>>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological use.
>> I
>>>>>> truly
>>>>>>>> hope your team will get the funding it deserves to further
enhance
>>>> this
>>>>>>>> very complex tool, which has a lot of potential and could
definitely
>>>> be
>>>>>> of
>>>>>>>> relevant use for routine forecasters.
>>>>>>>>
>>>>>>>> I will give it a try using the precip data you specified for
now -
>>>> I'll
>>>>>>>> let you know if I run into some issues.
>>>>>>>>
>>>>>>>> South side of Norman and Purcell are in a tornado warning at
the
>>>> moment
>>>>>> -
>>>>>>>> my attention is now 'detoured' towards the sky.
>>>>>>>>
>>>>>>>> Cheers and best,
>>>>>>>>
>>>>>>>> Alexandre-
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT <
>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>
>>>>>>>>> Alex,
>>>>>>>>>
>>>>>>>>> Here's a link to the MET website for some sources of
observation
>>>> data:
>>>>>>>>>
>>>> http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>>>>>>>
>>>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
>> The
>>>>>> only
>>>>>>>>> other gridded data formats it can handle are the NetCDF
output of
>> the
>>>>>>>>> pinterp utility, and the internal NetCDF format used by
>>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF data,
>>>> but
>>>>>>>>> we haven't gotten that done yet.
>>>>>>>>>
>>>>>>>>> MODE can be used to compare two different gridded data
files. They
>>>> can
>>>>>>>>> be any of the gridded data files that MET supports - GRIB1,
GRIB2,
>>>>>> NetCDF
>>>>>>>>> output of pcp_combine, and so on. MODE was developed
>>>>>>>>> using accumulated precipitation data, but we have applied it
to
>> other
>>>>>>>>> fields, including radar reflectivity. We just had to adjust
the
>>>>>>>>> convolution radius and threshold, and think about the other
>> settings.
>>>>>>>>>
>>>>>>>>> As for a source of gridded reflectivity data, I'm really not
sure.
>>>>>> We've
>>>>>>>>> used RTMA data from NCEP in the past, and there's a link to
that on
>>>> the
>>>>>>>>> observation data page. We've used Q2 data from NSSL
>>>>>>>>> in the past, but we first had to get it into GRIB format. I
see
>> the
>>>> Q2
>>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can see
how to
>>>>>>>>> access the data directly.
>>>>>>>>>
>>>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using the
>>>>>> copygb
>>>>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1, not
>>>>>> GRIB2.
>>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>>>>>>>> utility to regrid from GRIB2 to GRIB1 first. Alternatively,
the
>>>> wgrib2
>>>>>>>>> tool does some regridding, but it's pretty limited. Here's
a
>> portion
>>>>>> of
>>>>>>>>> the MET online tutorial that discussed copygb:
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>>>>>>>
>>>>>>>>> For examples of running MODE, please take a look in
>>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in there
of
>>>> running
>>>>>>>>> MODE. I'd also suggest reading through the MODE section of
the
>>>> online
>>>>>>>>> tutorial:
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>>>>>>>
>>>>>>>>> Generally speaking, you should start by playing around with
the
>>>>>>>>> convolution radius and threshold to define objects that
capture
>> your
>>>>>> areas
>>>>>>>>> of interest.
>>>>>>>>>
>>>>>>>>> Regarding future enhancements, at this point our funding is
limited
>>>> to
>>>>>>>>> only support - no additional development. Hopefully, that
will
>>>> change
>>>>>> in
>>>>>>>>> the future. We have submitted a proposal that would
>>>>>>>>> include development to support automated regridding of data.
So
>> you
>>>>>>>>> could skip the copygb step, for example, before running
grid_stat
>> and
>>>>>> MODE.
>>>>>>>>> As for why the tools for petroleum, chemistry,
>>>>>>>>> biology, and medicine are more sophisticated than those for
>>>>>> meteorology,
>>>>>>>>> I suspect there's more money driving the other disciplines.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>>>>>>>
>>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>>>>>>>>> Transaction: Ticket created by alexandre.o.fierro at gmail.com
>>>>>>>>>> Queue: met_help
>>>>>>>>>> Subject: Obs data to feed in MET tools.
>>>>>>>>>> Owner: Nobody
>>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>>>>>>>>> Status: new
>>>>>>>>>> Ticket <URL:
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi John:
>>>>>>>>>>
>>>>>>>>>> I have been reading the MET Users Guide for data formats
and
>>>> remained
>>>>>> a
>>>>>>>>> bit
>>>>>>>>>> daunted by this constant interplay between all sorts of
file
>>>> formats -
>>>>>>>>> At
>>>>>>>>>> the moment my goal is rather succinct, I would like to be
able to
>>>>>>>>> compare
>>>>>>>>>> my WRF forecast (lets say composite dBZ) with observations
(from
>>>> e.g,
>>>>>>>>> NMQ,
>>>>>>>>>> NCEP or another source).
>>>>>>>>>>
>>>>>>>>>> Where can I obtain the observation file with formats
compliant
>> with
>>>>>> MET
>>>>>>>>> as
>>>>>>>>>> the Users Guide does not point to any specific URL? Note
that I am
>>>> now
>>>>>>>>> able
>>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>>>>>>>
>>>>>>>>>> I would be interested in using the MODE tool for compiste
dBZ
>>>> during a
>>>>>>>>>> single model time. I have read, however, that MODE was
designed to
>>>>>>>>> handle
>>>>>>>>>> accumulated precip and needs input from pcp_combine. How
can I
>> used
>>>>>>>>>> observed composite dBZ as input and where can I obtain the
file
>> with
>>>>>>>>> this
>>>>>>>>>> data in the correct format ?
>>>>>>>>>>
>>>>>>>>>> The obs and WRF output data are initially not on the same
grid +
>> the
>>>>>> WRF
>>>>>>>>>> data is staggered.
>>>>>>>>>>
>>>>>>>>>> 1) I assume that UPP de-staggers the data when converting
to GRB1
>>>>>>>>> correct ?
>>>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto the
>>>>>>>>> GRIB1-derived
>>>>>>>>>> grids or vice versa ?
>>>>>>>>>> 3) Would you have a sample namelist available for me to run
MODE
>>>> once
>>>>>>>>> I'll
>>>>>>>>>> succeed in obtaining WRF and OBS data on the same regular
grid ?.
>>>>>>>>>>
>>>>>>>>>> NB: Would there be any plans in the future to make all the
above
>>>>>> process
>>>>>>>>>> more user friendly ? Aka a self-contained intuitive GUI
package
>>>> (like
>>>>>>>>>> Matlab) that reads in data directly from WRF or any other
model,
>>>>>> figures
>>>>>>>>>> out the computational grid the output data it is on, then
reads in
>>>> any
>>>>>>>>>> matching standard Level-II observations, figures out the
format,
>>>>>>>>>> interpolate and destaggers the data and provide the desired
plots
>>>> and
>>>>>>>>> stats
>>>>>>>>>> to the user ? I have friends in many other fields
(petroleum,
>>>>>> chemistry,
>>>>>>>>>> biology, medecine) and we (meteorologists) are perhaps the
only
>> one
>>>>>>>>> having
>>>>>>>>>> to deal with those intermediate extra-curricular tedious
tasks
>>>> related
>>>>>>>>> to
>>>>>>>>>> installation of complicated packages, shell scripts,
cumbersome
>>>> binary
>>>>>>>>> file
>>>>>>>>>> formats (Especially GRIB which I despise) and programming
in 10
>>>>>>>>> different
>>>>>>>>>> languages. For instance, when my friend in bio-engineering
>> received
>>>> a
>>>>>>>>> new
>>>>>>>>>> apparatus designed to gather X/Y data on a given assay
>> experiments,
>>>> a
>>>>>>>>>> computer + GUI software came along with it to make all the
stats
>> and
>>>>>>>>>> required plots to him/her with a a single mouse click - No
>> specific
>>>>>>>>>> computing skills were required other than basic Windows.
Why isn't
>>>> it
>>>>>>>>> the
>>>>>>>>>> same for meteorologists I wonder ? I am sure I am speaking
for
>> many
>>>>>>>>>> (similarly 'frustrated') individuals here as in the end,
what
>>>> matters
>>>>>> to
>>>>>>>>>> everyone are the results-
>>>>>>>>>>
>>>>>>>>>> Cheers and best,
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -------------------------------------------------------------
>>>>>>>> Alexandre Fierro, PhD
>>>>>>>> Research Scientist-
>>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
>>>>>> (OU/NOAA)
>>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>>>>>
>>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift;
>> That
>>>>>> is
>>>>>>>> why it is called the Present"
>>>>>>>>
>>>>>>>> "There are only 10 types of people in the world:
>>>>>>>> Those who understand binary, and those who don't"
>>>>>>>>
>>>>>>>> "My opinions are my own and not representative of OU, NSSL,
>>>>>>>> AOML, HRD, LANL or any affiliates."
>>>>>>>> ^.^
>>>>>>>> (o o)
>>>>>>>> /( V )\
>>>>>>>> ---m---m----
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Fri Jun 07 13:48:01 2013
Hi John:
The patch did not fix the problem: After looking at the NC files in
more
detail, I realized that the ACCUM precip is for the entire period up
to the
file dump time and not for hourly periods.
Knowing this, I then tried to run:
../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc 'name="APCP";
level="A06";'
and got a NC file that cannot be viewed by ncview or analyzed by
ncdump. Is
there a ncview equivalent for grib ?
I then assumed that my grib files produced by UPP were OK and tried to
run
mode as follows:
../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir ./ -v
2
but the command came back with usage errors.
Cheers and thanks for your help,
Alex-
On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> I see that you're using METv4.0. There was a bugfix posted on
10/16/2012
> that I believe is related to the problem you're seeing. Please
follow the
> instructions at the top of this page to download
> and apply all of the latest METv4.0 patches:
>
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>
> Sorry for not catching that one sooner.
>
> Thanks,
> John
>
>
> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > Hi John:
> >
> > Makes perfect sense.
> >
> > I have:
> >
> > /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 | grep
APCP
> >
>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
> > acc:NAve=0
> >
> > So seems like I already have 0-4h accum precip (?) - This would
explain
> why
> > I have the same error as before:
> >
> > /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
> > WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07
01
> > WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
> > DEBUG 1: Reading input file: WRFPRS_d01_04
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> VarInfo
> > "APCP/A1" in GRIB file "WRFPRS_d01_04".
> > WARNING:
> > ERROR :
> > ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
> > ERROR :
> >
> > The netcdf-equivalent array that *should* be read for this is
(are):
> >
> > float RAINC(Time, south_north, west_east)
> > ;
> >
> > RAINC:FieldType = 104
> > ;
> >
> > RAINC:MemoryOrder = "XY "
> > ;
> >
> > RAINC:description = "ACCUMULATED TOTAL CUMULUS
> > PRECIPITATION"
> > ;
> > RAINC:units = "mm"
> > ;
> >
> > RAINC:stagger = ""
> > ;
> >
> > RAINC:coordinates = "XLONG XLAT"
> > ;
> >
> > float RAINSH(Time, south_north, west_east)
> > ;
> >
> > RAINSH:FieldType = 104
> > ;
> >
> > RAINSH:MemoryOrder = "XY "
> > ;
> >
> > RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
> > PRECIPITATION"
> > ;
> > RAINSH:units = "mm"
> > ;
> >
> > RAINSH:stagger = ""
> > ;
> >
> > RAINSH:coordinates = "XLONG XLAT"
> > ;
> >
> > float RAINNC(Time, south_north, west_east)
> > ;
> >
> > RAINNC:FieldType = 104
> > ;
> >
> > RAINNC:MemoryOrder = "XY "
> > ;
> >
> > RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
> > PRECIPITATION"
> > ;
> > RAINNC:units = "mm"
> > ;
> >
> > RAINNC:stagger = ""
> > ;
> >
> > RAINNC:coordinates = "XLONG XLAT" ;
> >
> >
> > Cheers and thank you for your help/guidance,
> >
> > Alex-
> >
> > On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Alex,
> >>
> >> The pcp_combine tool is telling you that it can't find 4-hour
> accumulated
> >> precipitation in the file named WRFPRS_d01_04. So what does that
file
> >> contain? If you have the wgrib utility available on
> >> your system, try running the following:
> >> wgrib WRFPRS_d01_04 | grep APCP
> >>
> >> The output should tell you what accumulation interval(s) are in
there.
> >> You've said that it contains 1-hour accumulated precip in your
> message, so
> >> I suspect that wgrib will confirm that. But your
> >> call to pcp_combine is requesting 4-hours of accumulated precip
with
> >> "WRFPRS_d01_04 04".
> >>
> >> Here's what I think you want:
> >>
> >> ../bin/pcp_combine -add \
> >> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
> >> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
> >> WRFPRS_d01_APCP_06_03_to_09.nc
> >>
> >> Note the following:
> >> (1) I've selecting the "01" hour accumulation from each of the
input
> files
> >> and am adding them together.
> >> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03". GRIB
> >> file contain an accumulation of precipitation *ending* at the
file's
> time.
> >> So WRFPRS_d01_03 contains precip between hours 2
> >> and 3. If you want a total accumulation from 3 to 6, you should
use the
> >> six files listed in the command above.
> >>
> >> Make sense?
> >>
> >> Thanks,
> >> John
> >>
> >>
> >>
> >> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>
> >>> John:
> >>>
> >>> I have tried the following with 6 separate GRIB files each
containing
> 1-h
> >>> accum precip but ran into this problem:
> >>>
> >>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
> >>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05 WRFPRS_d01_06
06
> >>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
> >>> WRFPRS_d01_APCP_06_03_to_09.nc
> >>> DEBUG 1: Reading input file: WRFPRS_d01_03
> >>> DEBUG 1: Reading input file: WRFPRS_d01_04
> >>> WARNING:
> >>> WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> >> VarInfo
> >>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
> >>> WARNING:
> >>> ERROR :
> >>> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
> >>> ERROR :
> >>>
> >>> What are the double digit numbers ahed of the filename ?
> >>>
> >>> The original WRF OUT Files have:
> >>>
> >>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
> >>>
> >>> ...
> >>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
> >> PRECIPITATION" ;
> >>> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
> >>> PRECIPITATION" ;
> >>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
> >>> PRECIPITATION" ;
> >>> ...
> >>>
> >>> Cheers and thanks,
> >>>
> >>> Alex-
> >>>
> >>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> Alex,
> >>>>
> >>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated over
> >> the
> >>>> entire model run. So you'll need to adjust your forecast
accumulation
> >>>> intervals to match the observation accumulation
> >>>> intervals. For example, to get the 6-hour accumulation between
> forecast
> >>>> hours 24 and 30, you'd do the following:
> >>>>
> >>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
WRFPRS_d01_24
> 24
> >>>> WRFPRS_d01_APCP_06_24_to_30.nc
> >>>>
> >>>> That will grab the 30 hours of precip from the first file and
the 24
> >> hours
> >>>> of precip from the second file and subtract them. The last
argument
> is
> >> the
> >>>> name of the NetCDF file to be used.
> >>>>
> >>>> You might also want to run the plot_data_plane utility just to
make
> sure
> >>>> that your data looks good:
> >>>>
> >>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30 WRFPRS_d01_30.nc
> >>>> 'name="APCP"; level="A30";'
> >>>>
> >>>> That will select the field we've described (precip accumulated
over 30
> >>>> hours) from the file you've passed it and create a postscript
image of
> >> it.
> >>>>
> >>>> Hope that helps.
> >>>>
> >>>> Thanks,
> >>>> John
> >>>>
> >>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
> >>>>>
> >>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
> >>>>>
> >>>>> Hi John:
> >>>>>
> >>>>> I use ARW so seems like UNIPOST already de-staggers the data.
> >>>>>
> >>>>> I have:
> >>>>>
> >>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
> >>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
levels=(0,0)
> >>>>> grid=255 MSL 3hr fcst:
> >>>>> PRMSL=Pressure reduced to MSL [Pa]
> >>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
> >> num_in_ave 0
> >>>>> missing 0
> >>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
winds(grid)
> >>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
-98.000000
> >>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000
LonSP
> 0.000000
> >>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan
64 mode
> >> 136
> >>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
> >>>> DecScale 2
> >>>>> BinScale 3
> >>>>>
> >>>>> The next step I guess would be to produce accumulated precip
from
> >> several
> >>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Alex-
> >>>>>
> >>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
> >>>>> met_help at ucar.edu> wrote:
> >>>>>
> >>>>>> Alex,
> >>>>>>
> >>>>>> So you have a GRIB file that's output by unipost, named
> >> "WRFPRS_d01_03".
> >>>>>> And you're running it through copygb using the grid
defined by
> the
> >>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
> >>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
> >>>>>>
> >>>>>> Also, try running the following:
> >>>>>> wgrib -V -d 1 WRFPRS_d01_03
> >>>>>>
> >>>>>> That'll give a 'V'erbose description of the first record in
that
> file,
> >>>>>> including the current grid definition.
> >>>>>>
> >>>>>> Can you send me that output?
> >>>>>>
> >>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW,
the
> output
> >>>> of
> >>>>>> unipost should already be unstaggered. If it's WRF-NMM, the
output
> of
> >>>>>> unipost will be staggered, and you need to run it
> >>>>>> through copygb to de-stagger it.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> John
> >>>>>>
> >>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >>>>>>>
> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>>>>>
> >>>>>>> Hi John:
> >>>>>>>
> >>>>>>> As you might have expected I ran into some issues running
copygb.
> >>>>>>>
> >>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
> >>>>>> grid-When I
> >>>>>>> run:
> >>>>>>>
> >>>>>>> cat > itag <<EOF
> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>>>>>> netcdf
> >>>>>>> ${SY}-${SM}-${SD}_03:00:00
> >>>>>>> ${tag}
> >>>>>>> EOF
> >>>>>>> echo 'FILE TO BE PROCESSED'
> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
> >>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out 2>&1
> >>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
> >>>>>>>
> >>>>>>> # this stuff interp to a regular grid
> >>>>>>> read nav < 'copygb_gridnav.txt'
> >>>>>>> export nav
> >>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
> >>>>>>>
> >>>>>>> I get:
> >>>>>>>
> >>>>>>> copygb: unsupported output grid
> >>>>>>>
> >>>>>>> I tried to change it to:
> >>>>>>>
> >>>>>>> read nav < 'copygb_hwrf.txt'
> >>>>>>>
> >>>>>>> but got the same error
> >>>>>>>
> >>>>>>> Any clues on how I can get this program to destagger my WRF
output
> in
> >>>> the
> >>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
> >>>>>>>
> >>>>>>> Cheers and thanks,
> >>>>>>>
> >>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
> >>>>>>>
> >>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> >>>>>>> <alexandre.o.fierro at gmail.com>wrote:
> >>>>>>>
> >>>>>>>> Dear John:
> >>>>>>>>
> >>>>>>>> Many thanks for your prompt and detailed reply.
> >>>>>>>>
> >>>>>>>> I definitely blame the lack of funding in our field to hire
> software
> >>>>>>>> engineers (at the level of the individuals working for
MathWorks,
> >>>>>> Google,
> >>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
> use.
> >> I
> >>>>>> truly
> >>>>>>>> hope your team will get the funding it deserves to further
enhance
> >>>> this
> >>>>>>>> very complex tool, which has a lot of potential and could
> definitely
> >>>> be
> >>>>>> of
> >>>>>>>> relevant use for routine forecasters.
> >>>>>>>>
> >>>>>>>> I will give it a try using the precip data you specified
for now -
> >>>> I'll
> >>>>>>>> let you know if I run into some issues.
> >>>>>>>>
> >>>>>>>> South side of Norman and Purcell are in a tornado warning
at the
> >>>> moment
> >>>>>> -
> >>>>>>>> my attention is now 'detoured' towards the sky.
> >>>>>>>>
> >>>>>>>> Cheers and best,
> >>>>>>>>
> >>>>>>>> Alexandre-
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT
<
> >>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>
> >>>>>>>>> Alex,
> >>>>>>>>>
> >>>>>>>>> Here's a link to the MET website for some sources of
observation
> >>>> data:
> >>>>>>>>>
> >>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>>>>>>>
> >>>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
> >> The
> >>>>>> only
> >>>>>>>>> other gridded data formats it can handle are the NetCDF
output of
> >> the
> >>>>>>>>> pinterp utility, and the internal NetCDF format used by
> >>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
> data,
> >>>> but
> >>>>>>>>> we haven't gotten that done yet.
> >>>>>>>>>
> >>>>>>>>> MODE can be used to compare two different gridded data
files.
> They
> >>>> can
> >>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
> GRIB2,
> >>>>>> NetCDF
> >>>>>>>>> output of pcp_combine, and so on. MODE was developed
> >>>>>>>>> using accumulated precipitation data, but we have applied
it to
> >> other
> >>>>>>>>> fields, including radar reflectivity. We just had to
adjust the
> >>>>>>>>> convolution radius and threshold, and think about the
other
> >> settings.
> >>>>>>>>>
> >>>>>>>>> As for a source of gridded reflectivity data, I'm really
not
> sure.
> >>>>>> We've
> >>>>>>>>> used RTMA data from NCEP in the past, and there's a link
to that
> on
> >>>> the
> >>>>>>>>> observation data page. We've used Q2 data from NSSL
> >>>>>>>>> in the past, but we first had to get it into GRIB format.
I see
> >> the
> >>>> Q2
> >>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can
see how
> to
> >>>>>>>>> access the data directly.
> >>>>>>>>>
> >>>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using the
> >>>>>> copygb
> >>>>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1,
> not
> >>>>>> GRIB2.
> >>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
> >>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively, the
> >>>> wgrib2
> >>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
> >> portion
> >>>>>> of
> >>>>>>>>> the MET online tutorial that discussed copygb:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>>>>>>>
> >>>>>>>>> For examples of running MODE, please take a look in
> >>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there of
> >>>> running
> >>>>>>>>> MODE. I'd also suggest reading through the MODE section
of the
> >>>> online
> >>>>>>>>> tutorial:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>>>>>>>
> >>>>>>>>> Generally speaking, you should start by playing around
with the
> >>>>>>>>> convolution radius and threshold to define objects that
capture
> >> your
> >>>>>> areas
> >>>>>>>>> of interest.
> >>>>>>>>>
> >>>>>>>>> Regarding future enhancements, at this point our funding
is
> limited
> >>>> to
> >>>>>>>>> only support - no additional development. Hopefully, that
will
> >>>> change
> >>>>>> in
> >>>>>>>>> the future. We have submitted a proposal that would
> >>>>>>>>> include development to support automated regridding of
data. So
> >> you
> >>>>>>>>> could skip the copygb step, for example, before running
grid_stat
> >> and
> >>>>>> MODE.
> >>>>>>>>> As for why the tools for petroleum, chemistry,
> >>>>>>>>> biology, and medicine are more sophisticated than those
for
> >>>>>> meteorology,
> >>>>>>>>> I suspect there's more money driving the other
disciplines.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> John
> >>>>>>>>>
> >>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
> >>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
> >>>>>>>>>> Queue: met_help
> >>>>>>>>>> Subject: Obs data to feed in MET tools.
> >>>>>>>>>> Owner: Nobody
> >>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
> >>>>>>>>>> Status: new
> >>>>>>>>>> Ticket <URL:
> >>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Hi John:
> >>>>>>>>>>
> >>>>>>>>>> I have been reading the MET Users Guide for data formats
and
> >>>> remained
> >>>>>> a
> >>>>>>>>> bit
> >>>>>>>>>> daunted by this constant interplay between all sorts of
file
> >>>> formats -
> >>>>>>>>> At
> >>>>>>>>>> the moment my goal is rather succinct, I would like to be
able
> to
> >>>>>>>>> compare
> >>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations (from
> >>>> e.g,
> >>>>>>>>> NMQ,
> >>>>>>>>>> NCEP or another source).
> >>>>>>>>>>
> >>>>>>>>>> Where can I obtain the observation file with formats
compliant
> >> with
> >>>>>> MET
> >>>>>>>>> as
> >>>>>>>>>> the Users Guide does not point to any specific URL? Note
that I
> am
> >>>> now
> >>>>>>>>> able
> >>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
> >>>>>>>>>>
> >>>>>>>>>> I would be interested in using the MODE tool for compiste
dBZ
> >>>> during a
> >>>>>>>>>> single model time. I have read, however, that MODE was
designed
> to
> >>>>>>>>> handle
> >>>>>>>>>> accumulated precip and needs input from pcp_combine. How
can I
> >> used
> >>>>>>>>>> observed composite dBZ as input and where can I obtain
the file
> >> with
> >>>>>>>>> this
> >>>>>>>>>> data in the correct format ?
> >>>>>>>>>>
> >>>>>>>>>> The obs and WRF output data are initially not on the same
grid +
> >> the
> >>>>>> WRF
> >>>>>>>>>> data is staggered.
> >>>>>>>>>>
> >>>>>>>>>> 1) I assume that UPP de-staggers the data when converting
to
> GRB1
> >>>>>>>>> correct ?
> >>>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto
the
> >>>>>>>>> GRIB1-derived
> >>>>>>>>>> grids or vice versa ?
> >>>>>>>>>> 3) Would you have a sample namelist available for me to
run MODE
> >>>> once
> >>>>>>>>> I'll
> >>>>>>>>>> succeed in obtaining WRF and OBS data on the same regular
grid
> ?.
> >>>>>>>>>>
> >>>>>>>>>> NB: Would there be any plans in the future to make all
the above
> >>>>>> process
> >>>>>>>>>> more user friendly ? Aka a self-contained intuitive GUI
package
> >>>> (like
> >>>>>>>>>> Matlab) that reads in data directly from WRF or any other
model,
> >>>>>> figures
> >>>>>>>>>> out the computational grid the output data it is on, then
reads
> in
> >>>> any
> >>>>>>>>>> matching standard Level-II observations, figures out the
format,
> >>>>>>>>>> interpolate and destaggers the data and provide the
desired
> plots
> >>>> and
> >>>>>>>>> stats
> >>>>>>>>>> to the user ? I have friends in many other fields
(petroleum,
> >>>>>> chemistry,
> >>>>>>>>>> biology, medecine) and we (meteorologists) are perhaps
the only
> >> one
> >>>>>>>>> having
> >>>>>>>>>> to deal with those intermediate extra-curricular tedious
tasks
> >>>> related
> >>>>>>>>> to
> >>>>>>>>>> installation of complicated packages, shell scripts,
cumbersome
> >>>> binary
> >>>>>>>>> file
> >>>>>>>>>> formats (Especially GRIB which I despise) and programming
in 10
> >>>>>>>>> different
> >>>>>>>>>> languages. For instance, when my friend in bio-
engineering
> >> received
> >>>> a
> >>>>>>>>> new
> >>>>>>>>>> apparatus designed to gather X/Y data on a given assay
> >> experiments,
> >>>> a
> >>>>>>>>>> computer + GUI software came along with it to make all
the stats
> >> and
> >>>>>>>>>> required plots to him/her with a a single mouse click -
No
> >> specific
> >>>>>>>>>> computing skills were required other than basic Windows.
Why
> isn't
> >>>> it
> >>>>>>>>> the
> >>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking for
> >> many
> >>>>>>>>>> (similarly 'frustrated') individuals here as in the end,
what
> >>>> matters
> >>>>>> to
> >>>>>>>>>> everyone are the results-
> >>>>>>>>>>
> >>>>>>>>>> Cheers and best,
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>>
-------------------------------------------------------------
> >>>>>>>> Alexandre Fierro, PhD
> >>>>>>>> Research Scientist-
> >>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
> >>>>>> (OU/NOAA)
> >>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>>>>>
> >>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift;
> >> That
> >>>>>> is
> >>>>>>>> why it is called the Present"
> >>>>>>>>
> >>>>>>>> "There are only 10 types of people in the world:
> >>>>>>>> Those who understand binary, and those who don't"
> >>>>>>>>
> >>>>>>>> "My opinions are my own and not representative of OU, NSSL,
> >>>>>>>> AOML, HRD, LANL or any affiliates."
> >>>>>>>> ^.^
> >>>>>>>> (o o)
> >>>>>>>> /( V )\
> >>>>>>>> ---m---m----
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Fri Jun 07 14:00:00 2013
I realized MODE needed a config file (some sort of namelist).
I used:
../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
./config/MODEConfig_APCP_06 -outdir ./ -v 2
but got:
DEBUG 1: Default Config File:
/home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
ERROR :
ERROR : Trouble reading observation file
"./3B42RT.2013.05.29.06z.bin"
ERROR :
I got those obs files at:
ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
and assumed these were GRIB ? but neither wgrib2 nor wgrib work in
reading
the file.
Cheers and thanks ! perhaps I'll manage to get this stuff to work
before
2015...
On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
> Hi John:
>
> The patch did not fix the problem: After looking at the NC files in
more
> detail, I realized that the ACCUM precip is for the entire period up
to the
> file dump time and not for hourly periods.
>
> Knowing this, I then tried to run:
>
> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc 'name="APCP";
> level="A06";'
>
> and got a NC file that cannot be viewed by ncview or analyzed by
ncdump.
> Is there a ncview equivalent for grib ?
>
> I then assumed that my grib files produced by UPP were OK and tried
to run
> mode as follows:
>
> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir ./
-v 2
>
> but the command came back with usage errors.
>
> Cheers and thanks for your help,
>
> Alex-
>
>
> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> I see that you're using METv4.0. There was a bugfix posted on
10/16/2012
>> that I believe is related to the problem you're seeing. Please
follow the
>> instructions at the top of this page to download
>> and apply all of the latest METv4.0 patches:
>>
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>>
>> Sorry for not catching that one sooner.
>>
>> Thanks,
>> John
>>
>>
>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>> >
>> > Hi John:
>> >
>> > Makes perfect sense.
>> >
>> > I have:
>> >
>> > /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 | grep
APCP
>> >
>>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
>> > acc:NAve=0
>> >
>> > So seems like I already have 0-4h accum precip (?) - This would
explain
>> why
>> > I have the same error as before:
>> >
>> > /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
>> > WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07
01
>> > WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
>> > DEBUG 1: Reading input file: WRFPRS_d01_04
>> > WARNING:
>> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
>> VarInfo
>> > "APCP/A1" in GRIB file "WRFPRS_d01_04".
>> > WARNING:
>> > ERROR :
>> > ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
>> > ERROR :
>> >
>> > The netcdf-equivalent array that *should* be read for this is
(are):
>> >
>> > float RAINC(Time, south_north, west_east)
>> > ;
>> >
>> > RAINC:FieldType = 104
>> > ;
>> >
>> > RAINC:MemoryOrder = "XY "
>> > ;
>> >
>> > RAINC:description = "ACCUMULATED TOTAL CUMULUS
>> > PRECIPITATION"
>> > ;
>> > RAINC:units = "mm"
>> > ;
>> >
>> > RAINC:stagger = ""
>> > ;
>> >
>> > RAINC:coordinates = "XLONG XLAT"
>> > ;
>> >
>> > float RAINSH(Time, south_north, west_east)
>> > ;
>> >
>> > RAINSH:FieldType = 104
>> > ;
>> >
>> > RAINSH:MemoryOrder = "XY "
>> > ;
>> >
>> > RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
>> > PRECIPITATION"
>> > ;
>> > RAINSH:units = "mm"
>> > ;
>> >
>> > RAINSH:stagger = ""
>> > ;
>> >
>> > RAINSH:coordinates = "XLONG XLAT"
>> > ;
>> >
>> > float RAINNC(Time, south_north, west_east)
>> > ;
>> >
>> > RAINNC:FieldType = 104
>> > ;
>> >
>> > RAINNC:MemoryOrder = "XY "
>> > ;
>> >
>> > RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
>> > PRECIPITATION"
>> > ;
>> > RAINNC:units = "mm"
>> > ;
>> >
>> > RAINNC:stagger = ""
>> > ;
>> >
>> > RAINNC:coordinates = "XLONG XLAT" ;
>> >
>> >
>> > Cheers and thank you for your help/guidance,
>> >
>> > Alex-
>> >
>> > On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
>> > met_help at ucar.edu> wrote:
>> >
>> >> Alex,
>> >>
>> >> The pcp_combine tool is telling you that it can't find 4-hour
>> accumulated
>> >> precipitation in the file named WRFPRS_d01_04. So what does
that file
>> >> contain? If you have the wgrib utility available on
>> >> your system, try running the following:
>> >> wgrib WRFPRS_d01_04 | grep APCP
>> >>
>> >> The output should tell you what accumulation interval(s) are in
there.
>> >> You've said that it contains 1-hour accumulated precip in your
>> message, so
>> >> I suspect that wgrib will confirm that. But your
>> >> call to pcp_combine is requesting 4-hours of accumulated precip
with
>> >> "WRFPRS_d01_04 04".
>> >>
>> >> Here's what I think you want:
>> >>
>> >> ../bin/pcp_combine -add \
>> >> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
>> >> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
>> >> WRFPRS_d01_APCP_06_03_to_09.nc
>> >>
>> >> Note the following:
>> >> (1) I've selecting the "01" hour accumulation from each of the
input
>> files
>> >> and am adding them together.
>> >> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
>> GRIB
>> >> file contain an accumulation of precipitation *ending* at the
file's
>> time.
>> >> So WRFPRS_d01_03 contains precip between hours 2
>> >> and 3. If you want a total accumulation from 3 to 6, you should
use
>> the
>> >> six files listed in the command above.
>> >>
>> >> Make sense?
>> >>
>> >> Thanks,
>> >> John
>> >>
>> >>
>> >>
>> >> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>> >>>
>> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>> >>>
>> >>> John:
>> >>>
>> >>> I have tried the following with 6 separate GRIB files each
containing
>> 1-h
>> >>> accum precip but ran into this problem:
>> >>>
>> >>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
>> >>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06 06
>> >>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
>> >>> WRFPRS_d01_APCP_06_03_to_09.nc
>> >>> DEBUG 1: Reading input file: WRFPRS_d01_03
>> >>> DEBUG 1: Reading input file: WRFPRS_d01_04
>> >>> WARNING:
>> >>> WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
>> >> VarInfo
>> >>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
>> >>> WARNING:
>> >>> ERROR :
>> >>> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
>> >>> ERROR :
>> >>>
>> >>> What are the double digit numbers ahed of the filename ?
>> >>>
>> >>> The original WRF OUT Files have:
>> >>>
>> >>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>> >>>
>> >>> ...
>> >>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
>> >> PRECIPITATION" ;
>> >>> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
>> >>> PRECIPITATION" ;
>> >>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
>> >>> PRECIPITATION" ;
>> >>> ...
>> >>>
>> >>> Cheers and thanks,
>> >>>
>> >>> Alex-
>> >>>
>> >>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
>> >>> met_help at ucar.edu> wrote:
>> >>>
>> >>>> Alex,
>> >>>>
>> >>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated over
>> >> the
>> >>>> entire model run. So you'll need to adjust your forecast
>> accumulation
>> >>>> intervals to match the observation accumulation
>> >>>> intervals. For example, to get the 6-hour accumulation
between
>> forecast
>> >>>> hours 24 and 30, you'd do the following:
>> >>>>
>> >>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
>> WRFPRS_d01_24 24
>> >>>> WRFPRS_d01_APCP_06_24_to_30.nc
>> >>>>
>> >>>> That will grab the 30 hours of precip from the first file and
the 24
>> >> hours
>> >>>> of precip from the second file and subtract them. The last
argument
>> is
>> >> the
>> >>>> name of the NetCDF file to be used.
>> >>>>
>> >>>> You might also want to run the plot_data_plane utility just to
make
>> sure
>> >>>> that your data looks good:
>> >>>>
>> >>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
WRFPRS_d01_30.nc
>> >>>> 'name="APCP"; level="A30";'
>> >>>>
>> >>>> That will select the field we've described (precip accumulated
over
>> 30
>> >>>> hours) from the file you've passed it and create a postscript
image
>> of
>> >> it.
>> >>>>
>> >>>> Hope that helps.
>> >>>>
>> >>>> Thanks,
>> >>>> John
>> >>>>
>> >>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>> >>>>>
>> >>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
>> >>>>>
>> >>>>> Hi John:
>> >>>>>
>> >>>>> I use ARW so seems like UNIPOST already de-staggers the data.
>> >>>>>
>> >>>>> I have:
>> >>>>>
>> >>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
>> >>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
>> levels=(0,0)
>> >>>>> grid=255 MSL 3hr fcst:
>> >>>>> PRMSL=Pressure reduced to MSL [Pa]
>> >>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid 3
>> >> num_in_ave 0
>> >>>>> missing 0
>> >>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
>> winds(grid)
>> >>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
-98.000000
>> >>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000
LonSP
>> 0.000000
>> >>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000 scan
64
>> mode
>> >> 136
>> >>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
>> >>>> DecScale 2
>> >>>>> BinScale 3
>> >>>>>
>> >>>>> The next step I guess would be to produce accumulated precip
from
>> >> several
>> >>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
>> >>>>>
>> >>>>> Cheers,
>> >>>>>
>> >>>>> Alex-
>> >>>>>
>> >>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT <
>> >>>>> met_help at ucar.edu> wrote:
>> >>>>>
>> >>>>>> Alex,
>> >>>>>>
>> >>>>>> So you have a GRIB file that's output by unipost, named
>> >> "WRFPRS_d01_03".
>> >>>>>> And you're running it through copygb using the grid
defined by
>> the
>> >>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>> >>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
contain?
>> >>>>>>
>> >>>>>> Also, try running the following:
>> >>>>>> wgrib -V -d 1 WRFPRS_d01_03
>> >>>>>>
>> >>>>>> That'll give a 'V'erbose description of the first record in
that
>> file,
>> >>>>>> including the current grid definition.
>> >>>>>>
>> >>>>>> Can you send me that output?
>> >>>>>>
>> >>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW,
the
>> output
>> >>>> of
>> >>>>>> unipost should already be unstaggered. If it's WRF-NMM, the
>> output of
>> >>>>>> unipost will be staggered, and you need to run it
>> >>>>>> through copygb to de-stagger it.
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>> John
>> >>>>>>
>> >>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>> >>>>>>>
>> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>> >>>>>>>
>> >>>>>>> Hi John:
>> >>>>>>>
>> >>>>>>> As you might have expected I ran into some issues running
copygb.
>> >>>>>>>
>> >>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
>> >>>>>> grid-When I
>> >>>>>>> run:
>> >>>>>>>
>> >>>>>>> cat > itag <<EOF
>> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>> >>>>>>> netcdf
>> >>>>>>> ${SY}-${SM}-${SD}_03:00:00
>> >>>>>>> ${tag}
>> >>>>>>> EOF
>> >>>>>>> echo 'FILE TO BE PROCESSED'
>> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-${SD}_03:00:00
>> >>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out
>> 2>&1
>> >>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>> >>>>>>>
>> >>>>>>> # this stuff interp to a regular grid
>> >>>>>>> read nav < 'copygb_gridnav.txt'
>> >>>>>>> export nav
>> >>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
>> >>>>>>>
>> >>>>>>> I get:
>> >>>>>>>
>> >>>>>>> copygb: unsupported output grid
>> >>>>>>>
>> >>>>>>> I tried to change it to:
>> >>>>>>>
>> >>>>>>> read nav < 'copygb_hwrf.txt'
>> >>>>>>>
>> >>>>>>> but got the same error
>> >>>>>>>
>> >>>>>>> Any clues on how I can get this program to destagger my WRF
>> output in
>> >>>> the
>> >>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
>> >>>>>>>
>> >>>>>>> Cheers and thanks,
>> >>>>>>>
>> >>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
>> >>>>>>>
>> >>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>> >>>>>>> <alexandre.o.fierro at gmail.com>wrote:
>> >>>>>>>
>> >>>>>>>> Dear John:
>> >>>>>>>>
>> >>>>>>>> Many thanks for your prompt and detailed reply.
>> >>>>>>>>
>> >>>>>>>> I definitely blame the lack of funding in our field to
hire
>> software
>> >>>>>>>> engineers (at the level of the individuals working for
MathWorks,
>> >>>>>> Google,
>> >>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
>> use.
>> >> I
>> >>>>>> truly
>> >>>>>>>> hope your team will get the funding it deserves to further
>> enhance
>> >>>> this
>> >>>>>>>> very complex tool, which has a lot of potential and could
>> definitely
>> >>>> be
>> >>>>>> of
>> >>>>>>>> relevant use for routine forecasters.
>> >>>>>>>>
>> >>>>>>>> I will give it a try using the precip data you specified
for now
>> -
>> >>>> I'll
>> >>>>>>>> let you know if I run into some issues.
>> >>>>>>>>
>> >>>>>>>> South side of Norman and Purcell are in a tornado warning
at the
>> >>>> moment
>> >>>>>> -
>> >>>>>>>> my attention is now 'detoured' towards the sky.
>> >>>>>>>>
>> >>>>>>>> Cheers and best,
>> >>>>>>>>
>> >>>>>>>> Alexandre-
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via RT
<
>> >>>>>>>> met_help at ucar.edu> wrote:
>> >>>>>>>>
>> >>>>>>>>> Alex,
>> >>>>>>>>>
>> >>>>>>>>> Here's a link to the MET website for some sources of
observation
>> >>>> data:
>> >>>>>>>>>
>> >>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>> >>>>>>>>>
>> >>>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
>> >> The
>> >>>>>> only
>> >>>>>>>>> other gridded data formats it can handle are the NetCDF
output
>> of
>> >> the
>> >>>>>>>>> pinterp utility, and the internal NetCDF format used by
>> >>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
>> data,
>> >>>> but
>> >>>>>>>>> we haven't gotten that done yet.
>> >>>>>>>>>
>> >>>>>>>>> MODE can be used to compare two different gridded data
files.
>> They
>> >>>> can
>> >>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
>> GRIB2,
>> >>>>>> NetCDF
>> >>>>>>>>> output of pcp_combine, and so on. MODE was developed
>> >>>>>>>>> using accumulated precipitation data, but we have applied
it to
>> >> other
>> >>>>>>>>> fields, including radar reflectivity. We just had to
adjust the
>> >>>>>>>>> convolution radius and threshold, and think about the
other
>> >> settings.
>> >>>>>>>>>
>> >>>>>>>>> As for a source of gridded reflectivity data, I'm really
not
>> sure.
>> >>>>>> We've
>> >>>>>>>>> used RTMA data from NCEP in the past, and there's a link
to
>> that on
>> >>>> the
>> >>>>>>>>> observation data page. We've used Q2 data from NSSL
>> >>>>>>>>> in the past, but we first had to get it into GRIB format.
I see
>> >> the
>> >>>> Q2
>> >>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can
see
>> how to
>> >>>>>>>>> access the data directly.
>> >>>>>>>>>
>> >>>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using
>> the
>> >>>>>> copygb
>> >>>>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1,
>> not
>> >>>>>> GRIB2.
>> >>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>> >>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively, the
>> >>>> wgrib2
>> >>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
>> >> portion
>> >>>>>> of
>> >>>>>>>>> the MET online tutorial that discussed copygb:
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>> >>>>>>>>>
>> >>>>>>>>> For examples of running MODE, please take a look in
>> >>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there of
>> >>>> running
>> >>>>>>>>> MODE. I'd also suggest reading through the MODE section
of the
>> >>>> online
>> >>>>>>>>> tutorial:
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>> >>>>>>>>>
>> >>>>>>>>> Generally speaking, you should start by playing around
with the
>> >>>>>>>>> convolution radius and threshold to define objects that
capture
>> >> your
>> >>>>>> areas
>> >>>>>>>>> of interest.
>> >>>>>>>>>
>> >>>>>>>>> Regarding future enhancements, at this point our funding
is
>> limited
>> >>>> to
>> >>>>>>>>> only support - no additional development. Hopefully,
that will
>> >>>> change
>> >>>>>> in
>> >>>>>>>>> the future. We have submitted a proposal that would
>> >>>>>>>>> include development to support automated regridding of
data. So
>> >> you
>> >>>>>>>>> could skip the copygb step, for example, before running
>> grid_stat
>> >> and
>> >>>>>> MODE.
>> >>>>>>>>> As for why the tools for petroleum, chemistry,
>> >>>>>>>>> biology, and medicine are more sophisticated than those
for
>> >>>>>> meteorology,
>> >>>>>>>>> I suspect there's more money driving the other
disciplines.
>> >>>>>>>>>
>> >>>>>>>>> Thanks,
>> >>>>>>>>> John
>> >>>>>>>>>
>> >>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>> >>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
>> >>>>>>>>>> Queue: met_help
>> >>>>>>>>>> Subject: Obs data to feed in MET tools.
>> >>>>>>>>>> Owner: Nobody
>> >>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>> >>>>>>>>>> Status: new
>> >>>>>>>>>> Ticket <URL:
>> >>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> Hi John:
>> >>>>>>>>>>
>> >>>>>>>>>> I have been reading the MET Users Guide for data formats
and
>> >>>> remained
>> >>>>>> a
>> >>>>>>>>> bit
>> >>>>>>>>>> daunted by this constant interplay between all sorts of
file
>> >>>> formats -
>> >>>>>>>>> At
>> >>>>>>>>>> the moment my goal is rather succinct, I would like to
be able
>> to
>> >>>>>>>>> compare
>> >>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
>> (from
>> >>>> e.g,
>> >>>>>>>>> NMQ,
>> >>>>>>>>>> NCEP or another source).
>> >>>>>>>>>>
>> >>>>>>>>>> Where can I obtain the observation file with formats
compliant
>> >> with
>> >>>>>> MET
>> >>>>>>>>> as
>> >>>>>>>>>> the Users Guide does not point to any specific URL? Note
that
>> I am
>> >>>> now
>> >>>>>>>>> able
>> >>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>> >>>>>>>>>>
>> >>>>>>>>>> I would be interested in using the MODE tool for
compiste dBZ
>> >>>> during a
>> >>>>>>>>>> single model time. I have read, however, that MODE was
>> designed to
>> >>>>>>>>> handle
>> >>>>>>>>>> accumulated precip and needs input from pcp_combine. How
can I
>> >> used
>> >>>>>>>>>> observed composite dBZ as input and where can I obtain
the file
>> >> with
>> >>>>>>>>> this
>> >>>>>>>>>> data in the correct format ?
>> >>>>>>>>>>
>> >>>>>>>>>> The obs and WRF output data are initially not on the
same grid
>> +
>> >> the
>> >>>>>> WRF
>> >>>>>>>>>> data is staggered.
>> >>>>>>>>>>
>> >>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting to
>> GRB1
>> >>>>>>>>> correct ?
>> >>>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto
the
>> >>>>>>>>> GRIB1-derived
>> >>>>>>>>>> grids or vice versa ?
>> >>>>>>>>>> 3) Would you have a sample namelist available for me to
run
>> MODE
>> >>>> once
>> >>>>>>>>> I'll
>> >>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular grid
>> ?.
>> >>>>>>>>>>
>> >>>>>>>>>> NB: Would there be any plans in the future to make all
the
>> above
>> >>>>>> process
>> >>>>>>>>>> more user friendly ? Aka a self-contained intuitive GUI
>> package
>> >>>> (like
>> >>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
>> model,
>> >>>>>> figures
>> >>>>>>>>>> out the computational grid the output data it is on,
then
>> reads in
>> >>>> any
>> >>>>>>>>>> matching standard Level-II observations, figures out the
>> format,
>> >>>>>>>>>> interpolate and destaggers the data and provide the
desired
>> plots
>> >>>> and
>> >>>>>>>>> stats
>> >>>>>>>>>> to the user ? I have friends in many other fields
(petroleum,
>> >>>>>> chemistry,
>> >>>>>>>>>> biology, medecine) and we (meteorologists) are perhaps
the only
>> >> one
>> >>>>>>>>> having
>> >>>>>>>>>> to deal with those intermediate extra-curricular tedious
tasks
>> >>>> related
>> >>>>>>>>> to
>> >>>>>>>>>> installation of complicated packages, shell scripts,
cumbersome
>> >>>> binary
>> >>>>>>>>> file
>> >>>>>>>>>> formats (Especially GRIB which I despise) and
programming in 10
>> >>>>>>>>> different
>> >>>>>>>>>> languages. For instance, when my friend in bio-
engineering
>> >> received
>> >>>> a
>> >>>>>>>>> new
>> >>>>>>>>>> apparatus designed to gather X/Y data on a given assay
>> >> experiments,
>> >>>> a
>> >>>>>>>>>> computer + GUI software came along with it to make all
the
>> stats
>> >> and
>> >>>>>>>>>> required plots to him/her with a a single mouse click -
No
>> >> specific
>> >>>>>>>>>> computing skills were required other than basic Windows.
Why
>> isn't
>> >>>> it
>> >>>>>>>>> the
>> >>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking for
>> >> many
>> >>>>>>>>>> (similarly 'frustrated') individuals here as in the end,
what
>> >>>> matters
>> >>>>>> to
>> >>>>>>>>>> everyone are the results-
>> >>>>>>>>>>
>> >>>>>>>>>> Cheers and best,
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>>
-------------------------------------------------------------
>> >>>>>>>> Alexandre Fierro, PhD
>> >>>>>>>> Research Scientist-
>> >>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>> >>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
>> >>>>>> (OU/NOAA)
>> >>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>> >>>>>>>>
>> >>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is
a Gift;
>> >> That
>> >>>>>> is
>> >>>>>>>> why it is called the Present"
>> >>>>>>>>
>> >>>>>>>> "There are only 10 types of people in the world:
>> >>>>>>>> Those who understand binary, and those who don't"
>> >>>>>>>>
>> >>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
>> >>>>>>>> AOML, HRD, LANL or any affiliates."
>> >>>>>>>> ^.^
>> >>>>>>>> (o o)
>> >>>>>>>> /( V )\
>> >>>>>>>> ---m---m----
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>
>
> --
> -------------------------------------------------------------
> Alexandre Fierro, PhD
> Research Scientist-
> National Severe Storms Laboratory (NSSL/NOAA)
> *The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
>
> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>
> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
> why it is called the Present"
>
> "There are only 10 types of people in the world:
> Those who understand binary, and those who don't"
>
> "My opinions are my own and not representative of OU, NSSL,
> AOML, HRD, LANL or any affiliates."
> ^.^
> (o o)
> /( V )\
> ---m---m----
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Fri Jun 07 14:30:28 2013
John:
I have tried to make a test by running MODE on the same two files as
follows:
../bin/mode ./WRFPRS_d01_06 .//WRFPRS_d01_06
./config/MODEConfig_APCP_06
-outdir ./ -v 2
and it seems to run fine. My issue nwo is *where* to obtain gridded
files
in GRIB or NC format?
I tried most datasets abvailable here:
http://www.dtcenter.org/met/users/downloads/observation_data.php
but none can be read by either wgrib, wgrib2 or ncview- The datasets
reside
on rather clunky web page interfaces with no real info on what the
files
format are and what is meant by "gridded". Perhaps you can help me
obtain
some obs files of accum precip in NC or GRIB1,2 format compliant with
MET.
Once I get these files, how does one re-grid the observed data onto
the WRF
de-staggered grid of WRFPRS_d01_06 ? Does MODE handle this step or is
there
yet another step to re-grid the observations before running MODE?
Cheers and thanks,
On Fri, Jun 7, 2013 at 2:59 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
> I realized MODE needed a config file (some sort of namelist).
>
> I used:
>
> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
> ./config/MODEConfig_APCP_06 -outdir ./ -v 2
>
> but got:
>
> DEBUG 1: Default Config File:
> /home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
> DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
> DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
> ERROR :
> ERROR : Trouble reading observation file
"./3B42RT.2013.05.29.06z.bin"
> ERROR :
>
> I got those obs files at:
>
> ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
>
> and assumed these were GRIB ? but neither wgrib2 nor wgrib work in
reading
> the file.
>
> Cheers and thanks ! perhaps I'll manage to get this stuff to work
before
> 2015...
>
>
> On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
>
>> Hi John:
>>
>> The patch did not fix the problem: After looking at the NC files in
more
>> detail, I realized that the ACCUM precip is for the entire period
up to the
>> file dump time and not for hourly periods.
>>
>> Knowing this, I then tried to run:
>>
>> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc 'name="APCP";
>> level="A06";'
>>
>> and got a NC file that cannot be viewed by ncview or analyzed by
ncdump.
>> Is there a ncview equivalent for grib ?
>>
>> I then assumed that my grib files produced by UPP were OK and tried
to
>> run mode as follows:
>>
>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir ./
-v 2
>>
>> but the command came back with usage errors.
>>
>> Cheers and thanks for your help,
>>
>> Alex-
>>
>>
>> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>>
>>> Alex,
>>>
>>> I see that you're using METv4.0. There was a bugfix posted on
>>> 10/16/2012 that I believe is related to the problem you're seeing.
Please
>>> follow the instructions at the top of this page to download
>>> and apply all of the latest METv4.0 patches:
>>>
>>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>>>
>>> Sorry for not catching that one sooner.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
>>> >
>>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>> >
>>> > Hi John:
>>> >
>>> > Makes perfect sense.
>>> >
>>> > I have:
>>> >
>>> > /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 |
grep APCP
>>> >
>>>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
>>> > acc:NAve=0
>>> >
>>> > So seems like I already have 0-4h accum precip (?) - This would
>>> explain why
>>> > I have the same error as before:
>>> >
>>> > /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
>>> > WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07
01
>>> > WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
>>> > DEBUG 1: Reading input file: WRFPRS_d01_04
>>> > WARNING:
>>> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
>>> VarInfo
>>> > "APCP/A1" in GRIB file "WRFPRS_d01_04".
>>> > WARNING:
>>> > ERROR :
>>> > ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
>>> > ERROR :
>>> >
>>> > The netcdf-equivalent array that *should* be read for this is
(are):
>>> >
>>> > float RAINC(Time, south_north, west_east)
>>> > ;
>>> >
>>> > RAINC:FieldType = 104
>>> > ;
>>> >
>>> > RAINC:MemoryOrder = "XY "
>>> > ;
>>> >
>>> > RAINC:description = "ACCUMULATED TOTAL CUMULUS
>>> > PRECIPITATION"
>>> > ;
>>> > RAINC:units = "mm"
>>> > ;
>>> >
>>> > RAINC:stagger = ""
>>> > ;
>>> >
>>> > RAINC:coordinates = "XLONG XLAT"
>>> > ;
>>> >
>>> > float RAINSH(Time, south_north, west_east)
>>> > ;
>>> >
>>> > RAINSH:FieldType = 104
>>> > ;
>>> >
>>> > RAINSH:MemoryOrder = "XY "
>>> > ;
>>> >
>>> > RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
>>> > PRECIPITATION"
>>> > ;
>>> > RAINSH:units = "mm"
>>> > ;
>>> >
>>> > RAINSH:stagger = ""
>>> > ;
>>> >
>>> > RAINSH:coordinates = "XLONG XLAT"
>>> > ;
>>> >
>>> > float RAINNC(Time, south_north, west_east)
>>> > ;
>>> >
>>> > RAINNC:FieldType = 104
>>> > ;
>>> >
>>> > RAINNC:MemoryOrder = "XY "
>>> > ;
>>> >
>>> > RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
>>> > PRECIPITATION"
>>> > ;
>>> > RAINNC:units = "mm"
>>> > ;
>>> >
>>> > RAINNC:stagger = ""
>>> > ;
>>> >
>>> > RAINNC:coordinates = "XLONG XLAT" ;
>>> >
>>> >
>>> > Cheers and thank you for your help/guidance,
>>> >
>>> > Alex-
>>> >
>>> > On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
>>> > met_help at ucar.edu> wrote:
>>> >
>>> >> Alex,
>>> >>
>>> >> The pcp_combine tool is telling you that it can't find 4-hour
>>> accumulated
>>> >> precipitation in the file named WRFPRS_d01_04. So what does
that file
>>> >> contain? If you have the wgrib utility available on
>>> >> your system, try running the following:
>>> >> wgrib WRFPRS_d01_04 | grep APCP
>>> >>
>>> >> The output should tell you what accumulation interval(s) are in
there.
>>> >> You've said that it contains 1-hour accumulated precip in
your
>>> message, so
>>> >> I suspect that wgrib will confirm that. But your
>>> >> call to pcp_combine is requesting 4-hours of accumulated precip
with
>>> >> "WRFPRS_d01_04 04".
>>> >>
>>> >> Here's what I think you want:
>>> >>
>>> >> ../bin/pcp_combine -add \
>>> >> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
>>> >> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
>>> >> WRFPRS_d01_APCP_06_03_to_09.nc
>>> >>
>>> >> Note the following:
>>> >> (1) I've selecting the "01" hour accumulation from each of the
input
>>> files
>>> >> and am adding them together.
>>> >> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
>>> GRIB
>>> >> file contain an accumulation of precipitation *ending* at the
file's
>>> time.
>>> >> So WRFPRS_d01_03 contains precip between hours 2
>>> >> and 3. If you want a total accumulation from 3 to 6, you
should use
>>> the
>>> >> six files listed in the command above.
>>> >>
>>> >> Make sense?
>>> >>
>>> >> Thanks,
>>> >> John
>>> >>
>>> >>
>>> >>
>>> >> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>>> >>>
>>> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
>>> >>>
>>> >>> John:
>>> >>>
>>> >>> I have tried the following with 6 separate GRIB files each
>>> containing 1-h
>>> >>> accum precip but ran into this problem:
>>> >>>
>>> >>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
>>> >>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06 06
>>> >>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
>>> >>> WRFPRS_d01_APCP_06_03_to_09.nc
>>> >>> DEBUG 1: Reading input file: WRFPRS_d01_03
>>> >>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>> >>> WARNING:
>>> >>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
>>> >> VarInfo
>>> >>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
>>> >>> WARNING:
>>> >>> ERROR :
>>> >>> ERROR : get_field() -> can't get data plane from file
>>> "WRFPRS_d01_04"
>>> >>> ERROR :
>>> >>>
>>> >>> What are the double digit numbers ahed of the filename ?
>>> >>>
>>> >>> The original WRF OUT Files have:
>>> >>>
>>> >>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>>> >>>
>>> >>> ...
>>> >>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
>>> >> PRECIPITATION" ;
>>> >>> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
>>> >>> PRECIPITATION" ;
>>> >>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
>>> >>> PRECIPITATION" ;
>>> >>> ...
>>> >>>
>>> >>> Cheers and thanks,
>>> >>>
>>> >>> Alex-
>>> >>>
>>> >>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
>>> >>> met_help at ucar.edu> wrote:
>>> >>>
>>> >>>> Alex,
>>> >>>>
>>> >>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated
>>> over
>>> >> the
>>> >>>> entire model run. So you'll need to adjust your forecast
>>> accumulation
>>> >>>> intervals to match the observation accumulation
>>> >>>> intervals. For example, to get the 6-hour accumulation
between
>>> forecast
>>> >>>> hours 24 and 30, you'd do the following:
>>> >>>>
>>> >>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
>>> WRFPRS_d01_24 24
>>> >>>> WRFPRS_d01_APCP_06_24_to_30.nc
>>> >>>>
>>> >>>> That will grab the 30 hours of precip from the first file and
the 24
>>> >> hours
>>> >>>> of precip from the second file and subtract them. The last
>>> argument is
>>> >> the
>>> >>>> name of the NetCDF file to be used.
>>> >>>>
>>> >>>> You might also want to run the plot_data_plane utility just
to make
>>> sure
>>> >>>> that your data looks good:
>>> >>>>
>>> >>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
WRFPRS_d01_30.nc
>>> >>>> 'name="APCP"; level="A30";'
>>> >>>>
>>> >>>> That will select the field we've described (precip
accumulated over
>>> 30
>>> >>>> hours) from the file you've passed it and create a postscript
image
>>> of
>>> >> it.
>>> >>>>
>>> >>>> Hope that helps.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> John
>>> >>>>
>>> >>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>>> >>>>>
>>> >>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>> >>>>>
>>> >>>>> Hi John:
>>> >>>>>
>>> >>>>> I use ARW so seems like UNIPOST already de-staggers the
data.
>>> >>>>>
>>> >>>>> I have:
>>> >>>>>
>>> >>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
>>> >>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
>>> levels=(0,0)
>>> >>>>> grid=255 MSL 3hr fcst:
>>> >>>>> PRMSL=Pressure reduced to MSL [Pa]
>>> >>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid
3
>>> >> num_in_ave 0
>>> >>>>> missing 0
>>> >>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
>>> winds(grid)
>>> >>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
-98.000000
>>> >>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000
LonSP
>>> 0.000000
>>> >>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000
scan 64
>>> mode
>>> >> 136
>>> >>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
>>> >>>> DecScale 2
>>> >>>>> BinScale 3
>>> >>>>>
>>> >>>>> The next step I guess would be to produce accumulated precip
from
>>> >> several
>>> >>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>>
>>> >>>>> Alex-
>>> >>>>>
>>> >>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT
<
>>> >>>>> met_help at ucar.edu> wrote:
>>> >>>>>
>>> >>>>>> Alex,
>>> >>>>>>
>>> >>>>>> So you have a GRIB file that's output by unipost, named
>>> >> "WRFPRS_d01_03".
>>> >>>>>> And you're running it through copygb using the grid
defined
>>> by the
>>> >>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>>> >>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
>>> contain?
>>> >>>>>>
>>> >>>>>> Also, try running the following:
>>> >>>>>> wgrib -V -d 1 WRFPRS_d01_03
>>> >>>>>>
>>> >>>>>> That'll give a 'V'erbose description of the first record in
that
>>> file,
>>> >>>>>> including the current grid definition.
>>> >>>>>>
>>> >>>>>> Can you send me that output?
>>> >>>>>>
>>> >>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW,
the
>>> output
>>> >>>> of
>>> >>>>>> unipost should already be unstaggered. If it's WRF-NMM,
the
>>> output of
>>> >>>>>> unipost will be staggered, and you need to run it
>>> >>>>>> through copygb to de-stagger it.
>>> >>>>>>
>>> >>>>>> Thanks,
>>> >>>>>> John
>>> >>>>>>
>>> >>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>> >>>>>>>
>>> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>> >>>>>>>
>>> >>>>>>> Hi John:
>>> >>>>>>>
>>> >>>>>>> As you might have expected I ran into some issues running
copygb.
>>> >>>>>>>
>>> >>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
>>> >>>>>> grid-When I
>>> >>>>>>> run:
>>> >>>>>>>
>>> >>>>>>> cat > itag <<EOF
>>> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>> >>>>>>> netcdf
>>> >>>>>>> ${SY}-${SM}-${SD}_03:00:00
>>> >>>>>>> ${tag}
>>> >>>>>>> EOF
>>> >>>>>>> echo 'FILE TO BE PROCESSED'
>>> >>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>> >>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out
>>> 2>&1
>>> >>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>> >>>>>>>
>>> >>>>>>> # this stuff interp to a regular grid
>>> >>>>>>> read nav < 'copygb_gridnav.txt'
>>> >>>>>>> export nav
>>> >>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
>>> >>>>>>>
>>> >>>>>>> I get:
>>> >>>>>>>
>>> >>>>>>> copygb: unsupported output grid
>>> >>>>>>>
>>> >>>>>>> I tried to change it to:
>>> >>>>>>>
>>> >>>>>>> read nav < 'copygb_hwrf.txt'
>>> >>>>>>>
>>> >>>>>>> but got the same error
>>> >>>>>>>
>>> >>>>>>> Any clues on how I can get this program to destagger my
WRF
>>> output in
>>> >>>> the
>>> >>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
>>> >>>>>>>
>>> >>>>>>> Cheers and thanks,
>>> >>>>>>>
>>> >>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
>>> >>>>>>>
>>> >>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>> >>>>>>> <alexandre.o.fierro at gmail.com>wrote:
>>> >>>>>>>
>>> >>>>>>>> Dear John:
>>> >>>>>>>>
>>> >>>>>>>> Many thanks for your prompt and detailed reply.
>>> >>>>>>>>
>>> >>>>>>>> I definitely blame the lack of funding in our field to
hire
>>> software
>>> >>>>>>>> engineers (at the level of the individuals working for
>>> MathWorks,
>>> >>>>>> Google,
>>> >>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
>>> use.
>>> >> I
>>> >>>>>> truly
>>> >>>>>>>> hope your team will get the funding it deserves to
further
>>> enhance
>>> >>>> this
>>> >>>>>>>> very complex tool, which has a lot of potential and could
>>> definitely
>>> >>>> be
>>> >>>>>> of
>>> >>>>>>>> relevant use for routine forecasters.
>>> >>>>>>>>
>>> >>>>>>>> I will give it a try using the precip data you specified
for
>>> now -
>>> >>>> I'll
>>> >>>>>>>> let you know if I run into some issues.
>>> >>>>>>>>
>>> >>>>>>>> South side of Norman and Purcell are in a tornado warning
at the
>>> >>>> moment
>>> >>>>>> -
>>> >>>>>>>> my attention is now 'detoured' towards the sky.
>>> >>>>>>>>
>>> >>>>>>>> Cheers and best,
>>> >>>>>>>>
>>> >>>>>>>> Alexandre-
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via
RT <
>>> >>>>>>>> met_help at ucar.edu> wrote:
>>> >>>>>>>>
>>> >>>>>>>>> Alex,
>>> >>>>>>>>>
>>> >>>>>>>>> Here's a link to the MET website for some sources of
>>> observation
>>> >>>> data:
>>> >>>>>>>>>
>>> >>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>> >>>>>>>>>
>>> >>>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
>>> >> The
>>> >>>>>> only
>>> >>>>>>>>> other gridded data formats it can handle are the NetCDF
output
>>> of
>>> >> the
>>> >>>>>>>>> pinterp utility, and the internal NetCDF format used by
>>> >>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
>>> data,
>>> >>>> but
>>> >>>>>>>>> we haven't gotten that done yet.
>>> >>>>>>>>>
>>> >>>>>>>>> MODE can be used to compare two different gridded data
files.
>>> They
>>> >>>> can
>>> >>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
>>> GRIB2,
>>> >>>>>> NetCDF
>>> >>>>>>>>> output of pcp_combine, and so on. MODE was developed
>>> >>>>>>>>> using accumulated precipitation data, but we have
applied it to
>>> >> other
>>> >>>>>>>>> fields, including radar reflectivity. We just had to
adjust
>>> the
>>> >>>>>>>>> convolution radius and threshold, and think about the
other
>>> >> settings.
>>> >>>>>>>>>
>>> >>>>>>>>> As for a source of gridded reflectivity data, I'm really
not
>>> sure.
>>> >>>>>> We've
>>> >>>>>>>>> used RTMA data from NCEP in the past, and there's a link
to
>>> that on
>>> >>>> the
>>> >>>>>>>>> observation data page. We've used Q2 data from NSSL
>>> >>>>>>>>> in the past, but we first had to get it into GRIB
format. I
>>> see
>>> >> the
>>> >>>> Q2
>>> >>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can
see
>>> how to
>>> >>>>>>>>> access the data directly.
>>> >>>>>>>>>
>>> >>>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using
>>> the
>>> >>>>>> copygb
>>> >>>>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1,
>>> not
>>> >>>>>> GRIB2.
>>> >>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>> >>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively,
>>> the
>>> >>>> wgrib2
>>> >>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
>>> >> portion
>>> >>>>>> of
>>> >>>>>>>>> the MET online tutorial that discussed copygb:
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>
>>> >>>>
>>> >>
>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>> >>>>>>>>>
>>> >>>>>>>>> For examples of running MODE, please take a look in
>>> >>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there of
>>> >>>> running
>>> >>>>>>>>> MODE. I'd also suggest reading through the MODE section
of the
>>> >>>> online
>>> >>>>>>>>> tutorial:
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>
>>> >>>>
>>> >>
>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>> >>>>>>>>>
>>> >>>>>>>>> Generally speaking, you should start by playing around
with the
>>> >>>>>>>>> convolution radius and threshold to define objects that
capture
>>> >> your
>>> >>>>>> areas
>>> >>>>>>>>> of interest.
>>> >>>>>>>>>
>>> >>>>>>>>> Regarding future enhancements, at this point our funding
is
>>> limited
>>> >>>> to
>>> >>>>>>>>> only support - no additional development. Hopefully,
that will
>>> >>>> change
>>> >>>>>> in
>>> >>>>>>>>> the future. We have submitted a proposal that would
>>> >>>>>>>>> include development to support automated regridding of
data.
>>> So
>>> >> you
>>> >>>>>>>>> could skip the copygb step, for example, before running
>>> grid_stat
>>> >> and
>>> >>>>>> MODE.
>>> >>>>>>>>> As for why the tools for petroleum, chemistry,
>>> >>>>>>>>> biology, and medicine are more sophisticated than those
for
>>> >>>>>> meteorology,
>>> >>>>>>>>> I suspect there's more money driving the other
disciplines.
>>> >>>>>>>>>
>>> >>>>>>>>> Thanks,
>>> >>>>>>>>> John
>>> >>>>>>>>>
>>> >>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>> >>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
>>> >>>>>>>>>> Queue: met_help
>>> >>>>>>>>>> Subject: Obs data to feed in MET tools.
>>> >>>>>>>>>> Owner: Nobody
>>> >>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>> >>>>>>>>>> Status: new
>>> >>>>>>>>>> Ticket <URL:
>>> >>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>> Hi John:
>>> >>>>>>>>>>
>>> >>>>>>>>>> I have been reading the MET Users Guide for data
formats and
>>> >>>> remained
>>> >>>>>> a
>>> >>>>>>>>> bit
>>> >>>>>>>>>> daunted by this constant interplay between all sorts of
file
>>> >>>> formats -
>>> >>>>>>>>> At
>>> >>>>>>>>>> the moment my goal is rather succinct, I would like to
be
>>> able to
>>> >>>>>>>>> compare
>>> >>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
>>> (from
>>> >>>> e.g,
>>> >>>>>>>>> NMQ,
>>> >>>>>>>>>> NCEP or another source).
>>> >>>>>>>>>>
>>> >>>>>>>>>> Where can I obtain the observation file with formats
compliant
>>> >> with
>>> >>>>>> MET
>>> >>>>>>>>> as
>>> >>>>>>>>>> the Users Guide does not point to any specific URL?
Note that
>>> I am
>>> >>>> now
>>> >>>>>>>>> able
>>> >>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>> >>>>>>>>>>
>>> >>>>>>>>>> I would be interested in using the MODE tool for
compiste dBZ
>>> >>>> during a
>>> >>>>>>>>>> single model time. I have read, however, that MODE was
>>> designed to
>>> >>>>>>>>> handle
>>> >>>>>>>>>> accumulated precip and needs input from pcp_combine.
How can I
>>> >> used
>>> >>>>>>>>>> observed composite dBZ as input and where can I obtain
the
>>> file
>>> >> with
>>> >>>>>>>>> this
>>> >>>>>>>>>> data in the correct format ?
>>> >>>>>>>>>>
>>> >>>>>>>>>> The obs and WRF output data are initially not on the
same
>>> grid +
>>> >> the
>>> >>>>>> WRF
>>> >>>>>>>>>> data is staggered.
>>> >>>>>>>>>>
>>> >>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting to
>>> GRB1
>>> >>>>>>>>> correct ?
>>> >>>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto
the
>>> >>>>>>>>> GRIB1-derived
>>> >>>>>>>>>> grids or vice versa ?
>>> >>>>>>>>>> 3) Would you have a sample namelist available for me to
run
>>> MODE
>>> >>>> once
>>> >>>>>>>>> I'll
>>> >>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular
>>> grid ?.
>>> >>>>>>>>>>
>>> >>>>>>>>>> NB: Would there be any plans in the future to make all
the
>>> above
>>> >>>>>> process
>>> >>>>>>>>>> more user friendly ? Aka a self-contained intuitive
GUI
>>> package
>>> >>>> (like
>>> >>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
>>> model,
>>> >>>>>> figures
>>> >>>>>>>>>> out the computational grid the output data it is on,
then
>>> reads in
>>> >>>> any
>>> >>>>>>>>>> matching standard Level-II observations, figures out
the
>>> format,
>>> >>>>>>>>>> interpolate and destaggers the data and provide the
desired
>>> plots
>>> >>>> and
>>> >>>>>>>>> stats
>>> >>>>>>>>>> to the user ? I have friends in many other fields
(petroleum,
>>> >>>>>> chemistry,
>>> >>>>>>>>>> biology, medecine) and we (meteorologists) are perhaps
the
>>> only
>>> >> one
>>> >>>>>>>>> having
>>> >>>>>>>>>> to deal with those intermediate extra-curricular
tedious tasks
>>> >>>> related
>>> >>>>>>>>> to
>>> >>>>>>>>>> installation of complicated packages, shell scripts,
>>> cumbersome
>>> >>>> binary
>>> >>>>>>>>> file
>>> >>>>>>>>>> formats (Especially GRIB which I despise) and
programming in
>>> 10
>>> >>>>>>>>> different
>>> >>>>>>>>>> languages. For instance, when my friend in bio-
engineering
>>> >> received
>>> >>>> a
>>> >>>>>>>>> new
>>> >>>>>>>>>> apparatus designed to gather X/Y data on a given assay
>>> >> experiments,
>>> >>>> a
>>> >>>>>>>>>> computer + GUI software came along with it to make all
the
>>> stats
>>> >> and
>>> >>>>>>>>>> required plots to him/her with a a single mouse click -
No
>>> >> specific
>>> >>>>>>>>>> computing skills were required other than basic
Windows. Why
>>> isn't
>>> >>>> it
>>> >>>>>>>>> the
>>> >>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking for
>>> >> many
>>> >>>>>>>>>> (similarly 'frustrated') individuals here as in the
end, what
>>> >>>> matters
>>> >>>>>> to
>>> >>>>>>>>>> everyone are the results-
>>> >>>>>>>>>>
>>> >>>>>>>>>> Cheers and best,
>>> >>>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>> --
>>> >>>>>>>>
-------------------------------------------------------------
>>> >>>>>>>> Alexandre Fierro, PhD
>>> >>>>>>>> Research Scientist-
>>> >>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>> >>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
>>> >>>>>> (OU/NOAA)
>>> >>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>> >>>>>>>>
>>> >>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is
a
>>> Gift;
>>> >> That
>>> >>>>>> is
>>> >>>>>>>> why it is called the Present"
>>> >>>>>>>>
>>> >>>>>>>> "There are only 10 types of people in the world:
>>> >>>>>>>> Those who understand binary, and those who don't"
>>> >>>>>>>>
>>> >>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
>>> >>>>>>>> AOML, HRD, LANL or any affiliates."
>>> >>>>>>>> ^.^
>>> >>>>>>>> (o o)
>>> >>>>>>>> /( V )\
>>> >>>>>>>> ---m---m----
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>> --
>> -------------------------------------------------------------
>> Alexandre Fierro, PhD
>> Research Scientist-
>> National Severe Storms Laboratory (NSSL/NOAA)
>> *The Cooperative Institute for Mesoscale Meteorological
Studies*(OU/NOAA)
>>
>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>
>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
>> why it is called the Present"
>>
>> "There are only 10 types of people in the world:
>> Those who understand binary, and those who don't"
>>
>> "My opinions are my own and not representative of OU, NSSL,
>> AOML, HRD, LANL or any affiliates."
>> ^.^
>> (o o)
>> /( V )\
>> ---m---m----
>>
>
>
>
> --
> -------------------------------------------------------------
> Alexandre Fierro, PhD
> Research Scientist-
> National Severe Storms Laboratory (NSSL/NOAA)
> *The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>
> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
> why it is called the Present"
>
> "There are only 10 types of people in the world:
> Those who understand binary, and those who don't"
>
> "My opinions are my own and not representative of OU, NSSL,
> AOML, HRD, LANL or any affiliates."
> ^.^
> (o o)
> /( V )\
> ---m---m----
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #61600] Obs data to feed in MET tools.
From: John Halley Gotway
Time: Mon Jun 10 13:29:40 2013
Alex,
The grid-to-grid tools in MET require that the two input files already
be on the same grid. The copygb utility is useful for regridding GRIB
files.
Perhaps it'd be easiest to just have you send me one of your output
GRIB files. I can take a look at the location of the domain and see
if there's any observation data sources I could recommend.
You can post it to our anonymous ftp site by following these
instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
If you send me some data, please send me an email letting me know it's
there.
Thanks,
John
On 06/07/2013 02:30 PM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> John:
>
> I have tried to make a test by running MODE on the same two files as
> follows:
>
> ../bin/mode ./WRFPRS_d01_06 .//WRFPRS_d01_06
./config/MODEConfig_APCP_06
> -outdir ./ -v 2
>
> and it seems to run fine. My issue nwo is *where* to obtain gridded
files
> in GRIB or NC format?
>
> I tried most datasets abvailable here:
>
> http://www.dtcenter.org/met/users/downloads/observation_data.php
>
> but none can be read by either wgrib, wgrib2 or ncview- The datasets
reside
> on rather clunky web page interfaces with no real info on what the
files
> format are and what is meant by "gridded". Perhaps you can help me
obtain
> some obs files of accum precip in NC or GRIB1,2 format compliant
with MET.
> Once I get these files, how does one re-grid the observed data onto
the WRF
> de-staggered grid of WRFPRS_d01_06 ? Does MODE handle this step or
is there
> yet another step to re-grid the observations before running MODE?
>
> Cheers and thanks,
>
> On Fri, Jun 7, 2013 at 2:59 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
>
>> I realized MODE needed a config file (some sort of namelist).
>>
>> I used:
>>
>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
>> ./config/MODEConfig_APCP_06 -outdir ./ -v 2
>>
>> but got:
>>
>> DEBUG 1: Default Config File:
>> /home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
>> DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
>> DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
>> ERROR :
>> ERROR : Trouble reading observation file
"./3B42RT.2013.05.29.06z.bin"
>> ERROR :
>>
>> I got those obs files at:
>>
>> ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
>>
>> and assumed these were GRIB ? but neither wgrib2 nor wgrib work in
reading
>> the file.
>>
>> Cheers and thanks ! perhaps I'll manage to get this stuff to work
before
>> 2015...
>>
>>
>> On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro
<alexandre.o.fierro at gmail.com>wrote:
>>
>>> Hi John:
>>>
>>> The patch did not fix the problem: After looking at the NC files
in more
>>> detail, I realized that the ACCUM precip is for the entire period
up to the
>>> file dump time and not for hourly periods.
>>>
>>> Knowing this, I then tried to run:
>>>
>>> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc
'name="APCP";
>>> level="A06";'
>>>
>>> and got a NC file that cannot be viewed by ncview or analyzed by
ncdump.
>>> Is there a ncview equivalent for grib ?
>>>
>>> I then assumed that my grib files produced by UPP were OK and
tried to
>>> run mode as follows:
>>>
>>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir ./
-v 2
>>>
>>> but the command came back with usage errors.
>>>
>>> Cheers and thanks for your help,
>>>
>>> Alex-
>>>
>>>
>>> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Alex,
>>>>
>>>> I see that you're using METv4.0. There was a bugfix posted on
>>>> 10/16/2012 that I believe is related to the problem you're
seeing. Please
>>>> follow the instructions at the top of this page to download
>>>> and apply all of the latest METv4.0 patches:
>>>>
>>>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>>>>
>>>> Sorry for not catching that one sooner.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>>
>>>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>
>>>>> Hi John:
>>>>>
>>>>> Makes perfect sense.
>>>>>
>>>>> I have:
>>>>>
>>>>> /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 |
grep APCP
>>>>>
>>>>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
>>>>> acc:NAve=0
>>>>>
>>>>> So seems like I already have 0-4h accum precip (?) - This would
>>>> explain why
>>>>> I have the same error as before:
>>>>>
>>>>> /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 WRFPRS_d01_07
01
>>>>> WRFPRS_d01_08 01 WRFPRS_d01_09 01 WRFPRS_d01_APCP_06_03_to_09.nc
>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>>>> WARNING:
>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
>>>> VarInfo
>>>>> "APCP/A1" in GRIB file "WRFPRS_d01_04".
>>>>> WARNING:
>>>>> ERROR :
>>>>> ERROR : get_field() -> can't get data plane from file
"WRFPRS_d01_04"
>>>>> ERROR :
>>>>>
>>>>> The netcdf-equivalent array that *should* be read for this is
(are):
>>>>>
>>>>> float RAINC(Time, south_north, west_east)
>>>>> ;
>>>>>
>>>>> RAINC:FieldType = 104
>>>>> ;
>>>>>
>>>>> RAINC:MemoryOrder = "XY "
>>>>> ;
>>>>>
>>>>> RAINC:description = "ACCUMULATED TOTAL CUMULUS
>>>>> PRECIPITATION"
>>>>> ;
>>>>> RAINC:units = "mm"
>>>>> ;
>>>>>
>>>>> RAINC:stagger = ""
>>>>> ;
>>>>>
>>>>> RAINC:coordinates = "XLONG XLAT"
>>>>> ;
>>>>>
>>>>> float RAINSH(Time, south_north, west_east)
>>>>> ;
>>>>>
>>>>> RAINSH:FieldType = 104
>>>>> ;
>>>>>
>>>>> RAINSH:MemoryOrder = "XY "
>>>>> ;
>>>>>
>>>>> RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
>>>>> PRECIPITATION"
>>>>> ;
>>>>> RAINSH:units = "mm"
>>>>> ;
>>>>>
>>>>> RAINSH:stagger = ""
>>>>> ;
>>>>>
>>>>> RAINSH:coordinates = "XLONG XLAT"
>>>>> ;
>>>>>
>>>>> float RAINNC(Time, south_north, west_east)
>>>>> ;
>>>>>
>>>>> RAINNC:FieldType = 104
>>>>> ;
>>>>>
>>>>> RAINNC:MemoryOrder = "XY "
>>>>> ;
>>>>>
>>>>> RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
>>>>> PRECIPITATION"
>>>>> ;
>>>>> RAINNC:units = "mm"
>>>>> ;
>>>>>
>>>>> RAINNC:stagger = ""
>>>>> ;
>>>>>
>>>>> RAINNC:coordinates = "XLONG XLAT" ;
>>>>>
>>>>>
>>>>> Cheers and thank you for your help/guidance,
>>>>>
>>>>> Alex-
>>>>>
>>>>> On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>> Alex,
>>>>>>
>>>>>> The pcp_combine tool is telling you that it can't find 4-hour
>>>> accumulated
>>>>>> precipitation in the file named WRFPRS_d01_04. So what does
that file
>>>>>> contain? If you have the wgrib utility available on
>>>>>> your system, try running the following:
>>>>>> wgrib WRFPRS_d01_04 | grep APCP
>>>>>>
>>>>>> The output should tell you what accumulation interval(s) are in
there.
>>>>>> You've said that it contains 1-hour accumulated precip in
your
>>>> message, so
>>>>>> I suspect that wgrib will confirm that. But your
>>>>>> call to pcp_combine is requesting 4-hours of accumulated precip
with
>>>>>> "WRFPRS_d01_04 04".
>>>>>>
>>>>>> Here's what I think you want:
>>>>>>
>>>>>> ../bin/pcp_combine -add \
>>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
>>>>>> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
>>>>>>
>>>>>> Note the following:
>>>>>> (1) I've selecting the "01" hour accumulation from each of the
input
>>>> files
>>>>>> and am adding them together.
>>>>>> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
>>>> GRIB
>>>>>> file contain an accumulation of precipitation *ending* at the
file's
>>>> time.
>>>>>> So WRFPRS_d01_03 contains precip between hours 2
>>>>>> and 3. If you want a total accumulation from 3 to 6, you
should use
>>>> the
>>>>>> six files listed in the command above.
>>>>>>
>>>>>> Make sense?
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>>>>>>>
>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
>>>>>>>
>>>>>>> John:
>>>>>>>
>>>>>>> I have tried the following with 6 separate GRIB files each
>>>> containing 1-h
>>>>>>> accum precip but ran into this problem:
>>>>>>>
>>>>>>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine -add
>>>>>>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06 06
>>>>>>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
>>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_03
>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>>>>>> WARNING:
>>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
>>>>>> VarInfo
>>>>>>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
>>>>>>> WARNING:
>>>>>>> ERROR :
>>>>>>> ERROR : get_field() -> can't get data plane from file
>>>> "WRFPRS_d01_04"
>>>>>>> ERROR :
>>>>>>>
>>>>>>> What are the double digit numbers ahed of the filename ?
>>>>>>>
>>>>>>> The original WRF OUT Files have:
>>>>>>>
>>>>>>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>>>>>>>
>>>>>>> ...
>>>>>>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
>>>>>> PRECIPITATION" ;
>>>>>>> 935: RAINSH:description = "ACCUMULATED SHALLOW CUMULUS
>>>>>>> PRECIPITATION" ;
>>>>>>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID SCALE
>>>>>>> PRECIPITATION" ;
>>>>>>> ...
>>>>>>>
>>>>>>> Cheers and thanks,
>>>>>>>
>>>>>>> Alex-
>>>>>>>
>>>>>>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>
>>>>>>>> Alex,
>>>>>>>>
>>>>>>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated
>>>> over
>>>>>> the
>>>>>>>> entire model run. So you'll need to adjust your forecast
>>>> accumulation
>>>>>>>> intervals to match the observation accumulation
>>>>>>>> intervals. For example, to get the 6-hour accumulation
between
>>>> forecast
>>>>>>>> hours 24 and 30, you'd do the following:
>>>>>>>>
>>>>>>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
>>>> WRFPRS_d01_24 24
>>>>>>>> WRFPRS_d01_APCP_06_24_to_30.nc
>>>>>>>>
>>>>>>>> That will grab the 30 hours of precip from the first file and
the 24
>>>>>> hours
>>>>>>>> of precip from the second file and subtract them. The last
>>>> argument is
>>>>>> the
>>>>>>>> name of the NetCDF file to be used.
>>>>>>>>
>>>>>>>> You might also want to run the plot_data_plane utility just
to make
>>>> sure
>>>>>>>> that your data looks good:
>>>>>>>>
>>>>>>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
WRFPRS_d01_30.nc
>>>>>>>> 'name="APCP"; level="A30";'
>>>>>>>>
>>>>>>>> That will select the field we've described (precip
accumulated over
>>>> 30
>>>>>>>> hours) from the file you've passed it and create a postscript
image
>>>> of
>>>>>> it.
>>>>>>>>
>>>>>>>> Hope that helps.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> John
>>>>>>>>
>>>>>>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>>>>>>>>>
>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>>>>>
>>>>>>>>> Hi John:
>>>>>>>>>
>>>>>>>>> I use ARW so seems like UNIPOST already de-staggers the
data.
>>>>>>>>>
>>>>>>>>> I have:
>>>>>>>>>
>>>>>>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
WRFPRS_d01_03
>>>>>>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
>>>> levels=(0,0)
>>>>>>>>> grid=255 MSL 3hr fcst:
>>>>>>>>> PRMSL=Pressure reduced to MSL [Pa]
>>>>>>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS grid
3
>>>>>> num_in_ave 0
>>>>>>>>> missing 0
>>>>>>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
>>>> winds(grid)
>>>>>>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
-98.000000
>>>>>>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000
LonSP
>>>> 0.000000
>>>>>>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000
scan 64
>>>> mode
>>>>>> 136
>>>>>>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
9.90164e+06
>>>>>>>> DecScale 2
>>>>>>>>> BinScale 3
>>>>>>>>>
>>>>>>>>> The next step I guess would be to produce accumulated precip
from
>>>>>> several
>>>>>>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Alex-
>>>>>>>>>
>>>>>>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via RT
<
>>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Alex,
>>>>>>>>>>
>>>>>>>>>> So you have a GRIB file that's output by unipost, named
>>>>>> "WRFPRS_d01_03".
>>>>>>>>>> And you're running it through copygb using the grid
defined
>>>> by the
>>>>>>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt". So
>>>>>>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt files
>>>> contain?
>>>>>>>>>>
>>>>>>>>>> Also, try running the following:
>>>>>>>>>> wgrib -V -d 1 WRFPRS_d01_03
>>>>>>>>>>
>>>>>>>>>> That'll give a 'V'erbose description of the first record in
that
>>>> file,
>>>>>>>>>> including the current grid definition.
>>>>>>>>>>
>>>>>>>>>> Can you send me that output?
>>>>>>>>>>
>>>>>>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-ARW,
the
>>>> output
>>>>>>>> of
>>>>>>>>>> unipost should already be unstaggered. If it's WRF-NMM,
the
>>>> output of
>>>>>>>>>> unipost will be staggered, and you need to run it
>>>>>>>>>> through copygb to de-stagger it.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>>>>>>>>>>
>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>>>>>>>
>>>>>>>>>>> Hi John:
>>>>>>>>>>>
>>>>>>>>>>> As you might have expected I ran into some issues running
copygb.
>>>>>>>>>>>
>>>>>>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
>>>>>>>>>> grid-When I
>>>>>>>>>>> run:
>>>>>>>>>>>
>>>>>>>>>>> cat > itag <<EOF
>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>>>>>>>>>> netcdf
>>>>>>>>>>> ${SY}-${SM}-${SD}_03:00:00
>>>>>>>>>>> ${tag}
>>>>>>>>>>> EOF
>>>>>>>>>>> echo 'FILE TO BE PROCESSED'
>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>>>>>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out
>>>> 2>&1
>>>>>>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>>>>>>>>>>
>>>>>>>>>>> # this stuff interp to a regular grid
>>>>>>>>>>> read nav < 'copygb_gridnav.txt'
>>>>>>>>>>> export nav
>>>>>>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
>>>>>>>>>>>
>>>>>>>>>>> I get:
>>>>>>>>>>>
>>>>>>>>>>> copygb: unsupported output grid
>>>>>>>>>>>
>>>>>>>>>>> I tried to change it to:
>>>>>>>>>>>
>>>>>>>>>>> read nav < 'copygb_hwrf.txt'
>>>>>>>>>>>
>>>>>>>>>>> but got the same error
>>>>>>>>>>>
>>>>>>>>>>> Any clues on how I can get this program to destagger my
WRF
>>>> output in
>>>>>>>> the
>>>>>>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
>>>>>>>>>>>
>>>>>>>>>>> Cheers and thanks,
>>>>>>>>>>>
>>>>>>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
>>>>>>>>>>>
>>>>>>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>>>>>>>>>> <alexandre.o.fierro at gmail.com>wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Dear John:
>>>>>>>>>>>>
>>>>>>>>>>>> Many thanks for your prompt and detailed reply.
>>>>>>>>>>>>
>>>>>>>>>>>> I definitely blame the lack of funding in our field to
hire
>>>> software
>>>>>>>>>>>> engineers (at the level of the individuals working for
>>>> MathWorks,
>>>>>>>>>> Google,
>>>>>>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
>>>> use.
>>>>>> I
>>>>>>>>>> truly
>>>>>>>>>>>> hope your team will get the funding it deserves to
further
>>>> enhance
>>>>>>>> this
>>>>>>>>>>>> very complex tool, which has a lot of potential and could
>>>> definitely
>>>>>>>> be
>>>>>>>>>> of
>>>>>>>>>>>> relevant use for routine forecasters.
>>>>>>>>>>>>
>>>>>>>>>>>> I will give it a try using the precip data you specified
for
>>>> now -
>>>>>>>> I'll
>>>>>>>>>>>> let you know if I run into some issues.
>>>>>>>>>>>>
>>>>>>>>>>>> South side of Norman and Purcell are in a tornado warning
at the
>>>>>>>> moment
>>>>>>>>>> -
>>>>>>>>>>>> my attention is now 'detoured' towards the sky.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers and best,
>>>>>>>>>>>>
>>>>>>>>>>>> Alexandre-
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via
RT <
>>>>>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Alex,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here's a link to the MET website for some sources of
>>>> observation
>>>>>>>> data:
>>>>>>>>>>>>>
>>>>>>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>>>>>>>>>>>
>>>>>>>>>>>>> MET can basically handle gridded data in GRIB1 or GRIB2
format.
>>>>>> The
>>>>>>>>>> only
>>>>>>>>>>>>> other gridded data formats it can handle are the NetCDF
output
>>>> of
>>>>>> the
>>>>>>>>>>>>> pinterp utility, and the internal NetCDF format used by
>>>>>>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
>>>> data,
>>>>>>>> but
>>>>>>>>>>>>> we haven't gotten that done yet.
>>>>>>>>>>>>>
>>>>>>>>>>>>> MODE can be used to compare two different gridded data
files.
>>>> They
>>>>>>>> can
>>>>>>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
>>>> GRIB2,
>>>>>>>>>> NetCDF
>>>>>>>>>>>>> output of pcp_combine, and so on. MODE was developed
>>>>>>>>>>>>> using accumulated precipitation data, but we have
applied it to
>>>>>> other
>>>>>>>>>>>>> fields, including radar reflectivity. We just had to
adjust
>>>> the
>>>>>>>>>>>>> convolution radius and threshold, and think about the
other
>>>>>> settings.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As for a source of gridded reflectivity data, I'm really
not
>>>> sure.
>>>>>>>>>> We've
>>>>>>>>>>>>> used RTMA data from NCEP in the past, and there's a link
to
>>>> that on
>>>>>>>> the
>>>>>>>>>>>>> observation data page. We've used Q2 data from NSSL
>>>>>>>>>>>>> in the past, but we first had to get it into GRIB
format. I
>>>> see
>>>>>> the
>>>>>>>> Q2
>>>>>>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but can
see
>>>> how to
>>>>>>>>>>>>> access the data directly.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regarding UPP, yes, it destaggers the grid. We suggest
using
>>>> the
>>>>>>>>>> copygb
>>>>>>>>>>>>> utility for regridding GRIB1 data. copygb only handles
GRIB1,
>>>> not
>>>>>>>>>> GRIB2.
>>>>>>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>>>>>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively,
>>>> the
>>>>>>>> wgrib2
>>>>>>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
>>>>>> portion
>>>>>>>>>> of
>>>>>>>>>>>>> the MET online tutorial that discussed copygb:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>>>>>>>>>>>
>>>>>>>>>>>>> For examples of running MODE, please take a look in
>>>>>>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there of
>>>>>>>> running
>>>>>>>>>>>>> MODE. I'd also suggest reading through the MODE section
of the
>>>>>>>> online
>>>>>>>>>>>>> tutorial:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>>>>>>>>>>>
>>>>>>>>>>>>> Generally speaking, you should start by playing around
with the
>>>>>>>>>>>>> convolution radius and threshold to define objects that
capture
>>>>>> your
>>>>>>>>>> areas
>>>>>>>>>>>>> of interest.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regarding future enhancements, at this point our funding
is
>>>> limited
>>>>>>>> to
>>>>>>>>>>>>> only support - no additional development. Hopefully,
that will
>>>>>>>> change
>>>>>>>>>> in
>>>>>>>>>>>>> the future. We have submitted a proposal that would
>>>>>>>>>>>>> include development to support automated regridding of
data.
>>>> So
>>>>>> you
>>>>>>>>>>>>> could skip the copygb step, for example, before running
>>>> grid_stat
>>>>>> and
>>>>>>>>>> MODE.
>>>>>>>>>>>>> As for why the tools for petroleum, chemistry,
>>>>>>>>>>>>> biology, and medicine are more sophisticated than those
for
>>>>>>>>>> meteorology,
>>>>>>>>>>>>> I suspect there's more money driving the other
disciplines.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> John
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted upon.
>>>>>>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
>>>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>>>> Subject: Obs data to feed in MET tools.
>>>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>>>>>>>>>>>>> Status: new
>>>>>>>>>>>>>> Ticket <URL:
>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi John:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have been reading the MET Users Guide for data
formats and
>>>>>>>> remained
>>>>>>>>>> a
>>>>>>>>>>>>> bit
>>>>>>>>>>>>>> daunted by this constant interplay between all sorts of
file
>>>>>>>> formats -
>>>>>>>>>>>>> At
>>>>>>>>>>>>>> the moment my goal is rather succinct, I would like to
be
>>>> able to
>>>>>>>>>>>>> compare
>>>>>>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
>>>> (from
>>>>>>>> e.g,
>>>>>>>>>>>>> NMQ,
>>>>>>>>>>>>>> NCEP or another source).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Where can I obtain the observation file with formats
compliant
>>>>>> with
>>>>>>>>>> MET
>>>>>>>>>>>>> as
>>>>>>>>>>>>>> the Users Guide does not point to any specific URL?
Note that
>>>> I am
>>>>>>>> now
>>>>>>>>>>>>> able
>>>>>>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I would be interested in using the MODE tool for
compiste dBZ
>>>>>>>> during a
>>>>>>>>>>>>>> single model time. I have read, however, that MODE was
>>>> designed to
>>>>>>>>>>>>> handle
>>>>>>>>>>>>>> accumulated precip and needs input from pcp_combine.
How can I
>>>>>> used
>>>>>>>>>>>>>> observed composite dBZ as input and where can I obtain
the
>>>> file
>>>>>> with
>>>>>>>>>>>>> this
>>>>>>>>>>>>>> data in the correct format ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The obs and WRF output data are initially not on the
same
>>>> grid +
>>>>>> the
>>>>>>>>>> WRF
>>>>>>>>>>>>>> data is staggered.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting to
>>>> GRB1
>>>>>>>>>>>>> correct ?
>>>>>>>>>>>>>> 2) How do I interpolate the composite dBZ obs data onto
the
>>>>>>>>>>>>> GRIB1-derived
>>>>>>>>>>>>>> grids or vice versa ?
>>>>>>>>>>>>>> 3) Would you have a sample namelist available for me to
run
>>>> MODE
>>>>>>>> once
>>>>>>>>>>>>> I'll
>>>>>>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular
>>>> grid ?.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> NB: Would there be any plans in the future to make all
the
>>>> above
>>>>>>>>>> process
>>>>>>>>>>>>>> more user friendly ? Aka a self-contained intuitive
GUI
>>>> package
>>>>>>>> (like
>>>>>>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
>>>> model,
>>>>>>>>>> figures
>>>>>>>>>>>>>> out the computational grid the output data it is on,
then
>>>> reads in
>>>>>>>> any
>>>>>>>>>>>>>> matching standard Level-II observations, figures out
the
>>>> format,
>>>>>>>>>>>>>> interpolate and destaggers the data and provide the
desired
>>>> plots
>>>>>>>> and
>>>>>>>>>>>>> stats
>>>>>>>>>>>>>> to the user ? I have friends in many other fields
(petroleum,
>>>>>>>>>> chemistry,
>>>>>>>>>>>>>> biology, medecine) and we (meteorologists) are perhaps
the
>>>> only
>>>>>> one
>>>>>>>>>>>>> having
>>>>>>>>>>>>>> to deal with those intermediate extra-curricular
tedious tasks
>>>>>>>> related
>>>>>>>>>>>>> to
>>>>>>>>>>>>>> installation of complicated packages, shell scripts,
>>>> cumbersome
>>>>>>>> binary
>>>>>>>>>>>>> file
>>>>>>>>>>>>>> formats (Especially GRIB which I despise) and
programming in
>>>> 10
>>>>>>>>>>>>> different
>>>>>>>>>>>>>> languages. For instance, when my friend in bio-
engineering
>>>>>> received
>>>>>>>> a
>>>>>>>>>>>>> new
>>>>>>>>>>>>>> apparatus designed to gather X/Y data on a given assay
>>>>>> experiments,
>>>>>>>> a
>>>>>>>>>>>>>> computer + GUI software came along with it to make all
the
>>>> stats
>>>>>> and
>>>>>>>>>>>>>> required plots to him/her with a a single mouse click -
No
>>>>>> specific
>>>>>>>>>>>>>> computing skills were required other than basic
Windows. Why
>>>> isn't
>>>>>>>> it
>>>>>>>>>>>>> the
>>>>>>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking for
>>>>>> many
>>>>>>>>>>>>>> (similarly 'frustrated') individuals here as in the
end, what
>>>>>>>> matters
>>>>>>>>>> to
>>>>>>>>>>>>>> everyone are the results-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers and best,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
-------------------------------------------------------------
>>>>>>>>>>>> Alexandre Fierro, PhD
>>>>>>>>>>>> Research Scientist-
>>>>>>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>>>>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
>>>>>>>>>> (OU/NOAA)
>>>>>>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>>>>>>>>>
>>>>>>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is
a
>>>> Gift;
>>>>>> That
>>>>>>>>>> is
>>>>>>>>>>>> why it is called the Present"
>>>>>>>>>>>>
>>>>>>>>>>>> "There are only 10 types of people in the world:
>>>>>>>>>>>> Those who understand binary, and those who don't"
>>>>>>>>>>>>
>>>>>>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
>>>>>>>>>>>> AOML, HRD, LANL or any affiliates."
>>>>>>>>>>>> ^.^
>>>>>>>>>>>> (o o)
>>>>>>>>>>>> /( V )\
>>>>>>>>>>>> ---m---m----
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> -------------------------------------------------------------
>>> Alexandre Fierro, PhD
>>> Research Scientist-
>>> National Severe Storms Laboratory (NSSL/NOAA)
>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*(OU/NOAA)
>>>
>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>
>>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
>>> why it is called the Present"
>>>
>>> "There are only 10 types of people in the world:
>>> Those who understand binary, and those who don't"
>>>
>>> "My opinions are my own and not representative of OU, NSSL,
>>> AOML, HRD, LANL or any affiliates."
>>> ^.^
>>> (o o)
>>> /( V )\
>>> ---m---m----
>>>
>>
>>
>>
>> --
>> -------------------------------------------------------------
>> Alexandre Fierro, PhD
>> Research Scientist-
>> National Severe Storms Laboratory (NSSL/NOAA)
>> *The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>
>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That is
>> why it is called the Present"
>>
>> "There are only 10 types of people in the world:
>> Those who understand binary, and those who don't"
>>
>> "My opinions are my own and not representative of OU, NSSL,
>> AOML, HRD, LANL or any affiliates."
>> ^.^
>> (o o)
>> /( V )\
>> ---m---m----
>>
>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Mon Jun 10 13:52:52 2013
Hi John:
GRIB files created by running UPP on the WRF(ARW) output are available
here
(WRFPRS_d01_03 and WRFPRS_d01_04):
/incoming/irap/met_help/FIERRO_DATA
I just placed two files for you to see as the transfer is quite slow.
The
WRF data is on a 4-km dd-staggered grid over CONUS.
Cheers and thanks !
Alex-
On Mon, Jun 10, 2013 at 2:29 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> The grid-to-grid tools in MET require that the two input files
already be
> on the same grid. The copygb utility is useful for regridding GRIB
files.
>
> Perhaps it'd be easiest to just have you send me one of your output
GRIB
> files. I can take a look at the location of the domain and see if
there's
> any observation data sources I could recommend.
>
> You can post it to our anonymous ftp site by following these
instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> If you send me some data, please send me an email letting me know
it's
> there.
>
> Thanks,
> John
>
> On 06/07/2013 02:30 PM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > John:
> >
> > I have tried to make a test by running MODE on the same two files
as
> > follows:
> >
> > ../bin/mode ./WRFPRS_d01_06 .//WRFPRS_d01_06
./config/MODEConfig_APCP_06
> > -outdir ./ -v 2
> >
> > and it seems to run fine. My issue nwo is *where* to obtain
gridded files
> > in GRIB or NC format?
> >
> > I tried most datasets abvailable here:
> >
> > http://www.dtcenter.org/met/users/downloads/observation_data.php
> >
> > but none can be read by either wgrib, wgrib2 or ncview- The
datasets
> reside
> > on rather clunky web page interfaces with no real info on what the
files
> > format are and what is meant by "gridded". Perhaps you can help me
obtain
> > some obs files of accum precip in NC or GRIB1,2 format compliant
with
> MET.
> > Once I get these files, how does one re-grid the observed data
onto the
> WRF
> > de-staggered grid of WRFPRS_d01_06 ? Does MODE handle this step or
is
> there
> > yet another step to re-grid the observations before running MODE?
> >
> > Cheers and thanks,
> >
> > On Fri, Jun 7, 2013 at 2:59 PM, Alex Fierro <
> alexandre.o.fierro at gmail.com>wrote:
> >
> >> I realized MODE needed a config file (some sort of namelist).
> >>
> >> I used:
> >>
> >> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
> >> ./config/MODEConfig_APCP_06 -outdir ./ -v 2
> >>
> >> but got:
> >>
> >> DEBUG 1: Default Config File:
> >> /home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
> >> DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
> >> DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
> >> ERROR :
> >> ERROR : Trouble reading observation file
"./3B42RT.2013.05.29.06z.bin"
> >> ERROR :
> >>
> >> I got those obs files at:
> >>
> >> ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
> >>
> >> and assumed these were GRIB ? but neither wgrib2 nor wgrib work
in
> reading
> >> the file.
> >>
> >> Cheers and thanks ! perhaps I'll manage to get this stuff to work
before
> >> 2015...
> >>
> >>
> >> On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro <
> alexandre.o.fierro at gmail.com>wrote:
> >>
> >>> Hi John:
> >>>
> >>> The patch did not fix the problem: After looking at the NC files
in
> more
> >>> detail, I realized that the ACCUM precip is for the entire
period up
> to the
> >>> file dump time and not for hourly periods.
> >>>
> >>> Knowing this, I then tried to run:
> >>>
> >>> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc
'name="APCP";
> >>> level="A06";'
> >>>
> >>> and got a NC file that cannot be viewed by ncview or analyzed by
> ncdump.
> >>> Is there a ncview equivalent for grib ?
> >>>
> >>> I then assumed that my grib files produced by UPP were OK and
tried to
> >>> run mode as follows:
> >>>
> >>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir
./ -v 2
> >>>
> >>> but the command came back with usage errors.
> >>>
> >>> Cheers and thanks for your help,
> >>>
> >>> Alex-
> >>>
> >>>
> >>> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> Alex,
> >>>>
> >>>> I see that you're using METv4.0. There was a bugfix posted on
> >>>> 10/16/2012 that I believe is related to the problem you're
seeing.
> Please
> >>>> follow the instructions at the top of this page to download
> >>>> and apply all of the latest METv4.0 patches:
> >>>>
> >>>>
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> >>>>
> >>>> Sorry for not catching that one sooner.
> >>>>
> >>>> Thanks,
> >>>> John
> >>>>
> >>>>
> >>>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
> >>>>>
> >>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
> >>>>>
> >>>>> Hi John:
> >>>>>
> >>>>> Makes perfect sense.
> >>>>>
> >>>>> I have:
> >>>>>
> >>>>> /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 |
grep
> APCP
> >>>>>
> >>>>
>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
> >>>>> acc:NAve=0
> >>>>>
> >>>>> So seems like I already have 0-4h accum precip (?) - This
would
> >>>> explain why
> >>>>> I have the same error as before:
> >>>>>
> >>>>> /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
> >>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01
WRFPRS_d01_07 01
> >>>>> WRFPRS_d01_08 01 WRFPRS_d01_09 01
WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
> >>>>> WARNING:
> >>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
> >>>> VarInfo
> >>>>> "APCP/A1" in GRIB file "WRFPRS_d01_04".
> >>>>> WARNING:
> >>>>> ERROR :
> >>>>> ERROR : get_field() -> can't get data plane from file
> "WRFPRS_d01_04"
> >>>>> ERROR :
> >>>>>
> >>>>> The netcdf-equivalent array that *should* be read for this is
(are):
> >>>>>
> >>>>> float RAINC(Time, south_north, west_east)
> >>>>> ;
> >>>>>
> >>>>> RAINC:FieldType = 104
> >>>>> ;
> >>>>>
> >>>>> RAINC:MemoryOrder = "XY "
> >>>>> ;
> >>>>>
> >>>>> RAINC:description = "ACCUMULATED TOTAL
CUMULUS
> >>>>> PRECIPITATION"
> >>>>> ;
> >>>>> RAINC:units = "mm"
> >>>>> ;
> >>>>>
> >>>>> RAINC:stagger = ""
> >>>>> ;
> >>>>>
> >>>>> RAINC:coordinates = "XLONG XLAT"
> >>>>> ;
> >>>>>
> >>>>> float RAINSH(Time, south_north, west_east)
> >>>>> ;
> >>>>>
> >>>>> RAINSH:FieldType = 104
> >>>>> ;
> >>>>>
> >>>>> RAINSH:MemoryOrder = "XY "
> >>>>> ;
> >>>>>
> >>>>> RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
> >>>>> PRECIPITATION"
> >>>>> ;
> >>>>> RAINSH:units = "mm"
> >>>>> ;
> >>>>>
> >>>>> RAINSH:stagger = ""
> >>>>> ;
> >>>>>
> >>>>> RAINSH:coordinates = "XLONG XLAT"
> >>>>> ;
> >>>>>
> >>>>> float RAINNC(Time, south_north, west_east)
> >>>>> ;
> >>>>>
> >>>>> RAINNC:FieldType = 104
> >>>>> ;
> >>>>>
> >>>>> RAINNC:MemoryOrder = "XY "
> >>>>> ;
> >>>>>
> >>>>> RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
> >>>>> PRECIPITATION"
> >>>>> ;
> >>>>> RAINNC:units = "mm"
> >>>>> ;
> >>>>>
> >>>>> RAINNC:stagger = ""
> >>>>> ;
> >>>>>
> >>>>> RAINNC:coordinates = "XLONG XLAT" ;
> >>>>>
> >>>>>
> >>>>> Cheers and thank you for your help/guidance,
> >>>>>
> >>>>> Alex-
> >>>>>
> >>>>> On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
> >>>>> met_help at ucar.edu> wrote:
> >>>>>
> >>>>>> Alex,
> >>>>>>
> >>>>>> The pcp_combine tool is telling you that it can't find 4-hour
> >>>> accumulated
> >>>>>> precipitation in the file named WRFPRS_d01_04. So what does
that
> file
> >>>>>> contain? If you have the wgrib utility available on
> >>>>>> your system, try running the following:
> >>>>>> wgrib WRFPRS_d01_04 | grep APCP
> >>>>>>
> >>>>>> The output should tell you what accumulation interval(s) are
in
> there.
> >>>>>> You've said that it contains 1-hour accumulated precip in
your
> >>>> message, so
> >>>>>> I suspect that wgrib will confirm that. But your
> >>>>>> call to pcp_combine is requesting 4-hours of accumulated
precip with
> >>>>>> "WRFPRS_d01_04 04".
> >>>>>>
> >>>>>> Here's what I think you want:
> >>>>>>
> >>>>>> ../bin/pcp_combine -add \
> >>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
> >>>>>> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
> >>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>>>
> >>>>>> Note the following:
> >>>>>> (1) I've selecting the "01" hour accumulation from each of
the input
> >>>> files
> >>>>>> and am adding them together.
> >>>>>> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
> >>>> GRIB
> >>>>>> file contain an accumulation of precipitation *ending* at the
file's
> >>>> time.
> >>>>>> So WRFPRS_d01_03 contains precip between hours 2
> >>>>>> and 3. If you want a total accumulation from 3 to 6, you
should use
> >>>> the
> >>>>>> six files listed in the command above.
> >>>>>>
> >>>>>> Make sense?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> John
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
> >>>>>>>
> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>>>>>
> >>>>>>> John:
> >>>>>>>
> >>>>>>> I have tried the following with 6 separate GRIB files each
> >>>> containing 1-h
> >>>>>>> accum precip but ran into this problem:
> >>>>>>>
> >>>>>>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine
-add
> >>>>>>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06 06
> >>>>>>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
> >>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_03
> >>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
> >>>>>>> WARNING:
> >>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
> >>>>>> VarInfo
> >>>>>>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
> >>>>>>> WARNING:
> >>>>>>> ERROR :
> >>>>>>> ERROR : get_field() -> can't get data plane from file
> >>>> "WRFPRS_d01_04"
> >>>>>>> ERROR :
> >>>>>>>
> >>>>>>> What are the double digit numbers ahed of the filename ?
> >>>>>>>
> >>>>>>> The original WRF OUT Files have:
> >>>>>>>
> >>>>>>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
> >>>>>>>
> >>>>>>> ...
> >>>>>>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
> >>>>>> PRECIPITATION" ;
> >>>>>>> 935: RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
> >>>>>>> PRECIPITATION" ;
> >>>>>>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
> >>>>>>> PRECIPITATION" ;
> >>>>>>> ...
> >>>>>>>
> >>>>>>> Cheers and thanks,
> >>>>>>>
> >>>>>>> Alex-
> >>>>>>>
> >>>>>>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
> >>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>
> >>>>>>>> Alex,
> >>>>>>>>
> >>>>>>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated
> >>>> over
> >>>>>> the
> >>>>>>>> entire model run. So you'll need to adjust your forecast
> >>>> accumulation
> >>>>>>>> intervals to match the observation accumulation
> >>>>>>>> intervals. For example, to get the 6-hour accumulation
between
> >>>> forecast
> >>>>>>>> hours 24 and 30, you'd do the following:
> >>>>>>>>
> >>>>>>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
> >>>> WRFPRS_d01_24 24
> >>>>>>>> WRFPRS_d01_APCP_06_24_to_30.nc
> >>>>>>>>
> >>>>>>>> That will grab the 30 hours of precip from the first file
and the
> 24
> >>>>>> hours
> >>>>>>>> of precip from the second file and subtract them. The last
> >>>> argument is
> >>>>>> the
> >>>>>>>> name of the NetCDF file to be used.
> >>>>>>>>
> >>>>>>>> You might also want to run the plot_data_plane utility just
to
> make
> >>>> sure
> >>>>>>>> that your data looks good:
> >>>>>>>>
> >>>>>>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
WRFPRS_d01_30.nc
> >>>>>>>> 'name="APCP"; level="A30";'
> >>>>>>>>
> >>>>>>>> That will select the field we've described (precip
accumulated
> over
> >>>> 30
> >>>>>>>> hours) from the file you've passed it and create a
postscript
> image
> >>>> of
> >>>>>> it.
> >>>>>>>>
> >>>>>>>> Hope that helps.
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> John
> >>>>>>>>
> >>>>>>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
> >>>>>>>>>
> >>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>>>>>>>
> >>>>>>>>> Hi John:
> >>>>>>>>>
> >>>>>>>>> I use ARW so seems like UNIPOST already de-staggers the
data.
> >>>>>>>>>
> >>>>>>>>> I have:
> >>>>>>>>>
> >>>>>>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
> WRFPRS_d01_03
> >>>>>>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
> >>>> levels=(0,0)
> >>>>>>>>> grid=255 MSL 3hr fcst:
> >>>>>>>>> PRMSL=Pressure reduced to MSL [Pa]
> >>>>>>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS
grid 3
> >>>>>> num_in_ave 0
> >>>>>>>>> missing 0
> >>>>>>>>> center 7 subcenter 0 process 125 Table 2 scan: WE:SN
> >>>> winds(grid)
> >>>>>>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
> -98.000000
> >>>>>>>>> Latin1 60.000000 Latin2 30.000000 LatSP 0.000000
LonSP
> >>>> 0.000000
> >>>>>>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000
scan 64
> >>>> mode
> >>>>>> 136
> >>>>>>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
> 9.90164e+06
> >>>>>>>> DecScale 2
> >>>>>>>>> BinScale 3
> >>>>>>>>>
> >>>>>>>>> The next step I guess would be to produce accumulated
precip from
> >>>>>> several
> >>>>>>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>>
> >>>>>>>>> Alex-
> >>>>>>>>>
> >>>>>>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via
RT <
> >>>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>>
> >>>>>>>>>> Alex,
> >>>>>>>>>>
> >>>>>>>>>> So you have a GRIB file that's output by unipost, named
> >>>>>> "WRFPRS_d01_03".
> >>>>>>>>>> And you're running it through copygb using the grid
defined
> >>>> by the
> >>>>>>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt".
So
> >>>>>>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt
files
> >>>> contain?
> >>>>>>>>>>
> >>>>>>>>>> Also, try running the following:
> >>>>>>>>>> wgrib -V -d 1 WRFPRS_d01_03
> >>>>>>>>>>
> >>>>>>>>>> That'll give a 'V'erbose description of the first record
in that
> >>>> file,
> >>>>>>>>>> including the current grid definition.
> >>>>>>>>>>
> >>>>>>>>>> Can you send me that output?
> >>>>>>>>>>
> >>>>>>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-
ARW, the
> >>>> output
> >>>>>>>> of
> >>>>>>>>>> unipost should already be unstaggered. If it's WRF-NMM,
the
> >>>> output of
> >>>>>>>>>> unipost will be staggered, and you need to run it
> >>>>>>>>>> through copygb to de-stagger it.
> >>>>>>>>>>
> >>>>>>>>>> Thanks,
> >>>>>>>>>> John
> >>>>>>>>>>
> >>>>>>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>>
> >>>>>>>>>>> Hi John:
> >>>>>>>>>>>
> >>>>>>>>>>> As you might have expected I ran into some issues
running
> copygb.
> >>>>>>>>>>>
> >>>>>>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
> >>>>>>>>>> grid-When I
> >>>>>>>>>>> run:
> >>>>>>>>>>>
> >>>>>>>>>>> cat > itag <<EOF
> >>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
> >>>>>>>>>>> netcdf
> >>>>>>>>>>> ${SY}-${SM}-${SD}_03:00:00
> >>>>>>>>>>> ${tag}
> >>>>>>>>>>> EOF
> >>>>>>>>>>> echo 'FILE TO BE PROCESSED'
> >>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
> >>>>>>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out
> >>>> 2>&1
> >>>>>>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
> >>>>>>>>>>>
> >>>>>>>>>>> # this stuff interp to a regular grid
> >>>>>>>>>>> read nav < 'copygb_gridnav.txt'
> >>>>>>>>>>> export nav
> >>>>>>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
> >>>>>>>>>>>
> >>>>>>>>>>> I get:
> >>>>>>>>>>>
> >>>>>>>>>>> copygb: unsupported output grid
> >>>>>>>>>>>
> >>>>>>>>>>> I tried to change it to:
> >>>>>>>>>>>
> >>>>>>>>>>> read nav < 'copygb_hwrf.txt'
> >>>>>>>>>>>
> >>>>>>>>>>> but got the same error
> >>>>>>>>>>>
> >>>>>>>>>>> Any clues on how I can get this program to destagger my
WRF
> >>>> output in
> >>>>>>>> the
> >>>>>>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
> >>>>>>>>>>>
> >>>>>>>>>>> Cheers and thanks,
> >>>>>>>>>>>
> >>>>>>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
> >>>>>>>>>>>
> >>>>>>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> >>>>>>>>>>> <alexandre.o.fierro at gmail.com>wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Dear John:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Many thanks for your prompt and detailed reply.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I definitely blame the lack of funding in our field to
hire
> >>>> software
> >>>>>>>>>>>> engineers (at the level of the individuals working for
> >>>> MathWorks,
> >>>>>>>>>> Google,
> >>>>>>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
> >>>> use.
> >>>>>> I
> >>>>>>>>>> truly
> >>>>>>>>>>>> hope your team will get the funding it deserves to
further
> >>>> enhance
> >>>>>>>> this
> >>>>>>>>>>>> very complex tool, which has a lot of potential and
could
> >>>> definitely
> >>>>>>>> be
> >>>>>>>>>> of
> >>>>>>>>>>>> relevant use for routine forecasters.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I will give it a try using the precip data you
specified for
> >>>> now -
> >>>>>>>> I'll
> >>>>>>>>>>>> let you know if I run into some issues.
> >>>>>>>>>>>>
> >>>>>>>>>>>> South side of Norman and Purcell are in a tornado
warning at
> the
> >>>>>>>> moment
> >>>>>>>>>> -
> >>>>>>>>>>>> my attention is now 'detoured' towards the sky.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers and best,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Alexandre-
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via
RT <
> >>>>>>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Alex,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Here's a link to the MET website for some sources of
> >>>> observation
> >>>>>>>> data:
> >>>>>>>>>>>>>
> >>>>>>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> MET can basically handle gridded data in GRIB1 or
GRIB2
> format.
> >>>>>> The
> >>>>>>>>>> only
> >>>>>>>>>>>>> other gridded data formats it can handle are the
NetCDF
> output
> >>>> of
> >>>>>> the
> >>>>>>>>>>>>> pinterp utility, and the internal NetCDF format used
by
> >>>>>>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
> >>>> data,
> >>>>>>>> but
> >>>>>>>>>>>>> we haven't gotten that done yet.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> MODE can be used to compare two different gridded data
files.
> >>>> They
> >>>>>>>> can
> >>>>>>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
> >>>> GRIB2,
> >>>>>>>>>> NetCDF
> >>>>>>>>>>>>> output of pcp_combine, and so on. MODE was developed
> >>>>>>>>>>>>> using accumulated precipitation data, but we have
applied it
> to
> >>>>>> other
> >>>>>>>>>>>>> fields, including radar reflectivity. We just had to
adjust
> >>>> the
> >>>>>>>>>>>>> convolution radius and threshold, and think about the
other
> >>>>>> settings.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> As for a source of gridded reflectivity data, I'm
really not
> >>>> sure.
> >>>>>>>>>> We've
> >>>>>>>>>>>>> used RTMA data from NCEP in the past, and there's a
link to
> >>>> that on
> >>>>>>>> the
> >>>>>>>>>>>>> observation data page. We've used Q2 data from NSSL
> >>>>>>>>>>>>> in the past, but we first had to get it into GRIB
format. I
> >>>> see
> >>>>>> the
> >>>>>>>> Q2
> >>>>>>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but
can see
> >>>> how to
> >>>>>>>>>>>>> access the data directly.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Regarding UPP, yes, it destaggers the grid. We
suggest using
> >>>> the
> >>>>>>>>>> copygb
> >>>>>>>>>>>>> utility for regridding GRIB1 data. copygb only
handles
> GRIB1,
> >>>> not
> >>>>>>>>>> GRIB2.
> >>>>>>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
> >>>>>>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively,
> >>>> the
> >>>>>>>> wgrib2
> >>>>>>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
> >>>>>> portion
> >>>>>>>>>> of
> >>>>>>>>>>>>> the MET online tutorial that discussed copygb:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> For examples of running MODE, please take a look in
> >>>>>>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there
> of
> >>>>>>>> running
> >>>>>>>>>>>>> MODE. I'd also suggest reading through the MODE
section of
> the
> >>>>>>>> online
> >>>>>>>>>>>>> tutorial:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Generally speaking, you should start by playing around
with
> the
> >>>>>>>>>>>>> convolution radius and threshold to define objects
that
> capture
> >>>>>> your
> >>>>>>>>>> areas
> >>>>>>>>>>>>> of interest.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Regarding future enhancements, at this point our
funding is
> >>>> limited
> >>>>>>>> to
> >>>>>>>>>>>>> only support - no additional development. Hopefully,
that
> will
> >>>>>>>> change
> >>>>>>>>>> in
> >>>>>>>>>>>>> the future. We have submitted a proposal that would
> >>>>>>>>>>>>> include development to support automated regridding of
data.
> >>>> So
> >>>>>> you
> >>>>>>>>>>>>> could skip the copygb step, for example, before
running
> >>>> grid_stat
> >>>>>> and
> >>>>>>>>>> MODE.
> >>>>>>>>>>>>> As for why the tools for petroleum, chemistry,
> >>>>>>>>>>>>> biology, and medicine are more sophisticated than
those for
> >>>>>>>>>> meteorology,
> >>>>>>>>>>>>> I suspect there's more money driving the other
disciplines.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>> John
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted
upon.
> >>>>>>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
> >>>>>>>>>>>>>> Queue: met_help
> >>>>>>>>>>>>>> Subject: Obs data to feed in MET tools.
> >>>>>>>>>>>>>> Owner: Nobody
> >>>>>>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
> >>>>>>>>>>>>>> Status: new
> >>>>>>>>>>>>>> Ticket <URL:
> >>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi John:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I have been reading the MET Users Guide for data
formats and
> >>>>>>>> remained
> >>>>>>>>>> a
> >>>>>>>>>>>>> bit
> >>>>>>>>>>>>>> daunted by this constant interplay between all sorts
of file
> >>>>>>>> formats -
> >>>>>>>>>>>>> At
> >>>>>>>>>>>>>> the moment my goal is rather succinct, I would like
to be
> >>>> able to
> >>>>>>>>>>>>> compare
> >>>>>>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
> >>>> (from
> >>>>>>>> e.g,
> >>>>>>>>>>>>> NMQ,
> >>>>>>>>>>>>>> NCEP or another source).
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Where can I obtain the observation file with formats
> compliant
> >>>>>> with
> >>>>>>>>>> MET
> >>>>>>>>>>>>> as
> >>>>>>>>>>>>>> the Users Guide does not point to any specific URL?
Note
> that
> >>>> I am
> >>>>>>>> now
> >>>>>>>>>>>>> able
> >>>>>>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I would be interested in using the MODE tool for
compiste
> dBZ
> >>>>>>>> during a
> >>>>>>>>>>>>>> single model time. I have read, however, that MODE
was
> >>>> designed to
> >>>>>>>>>>>>> handle
> >>>>>>>>>>>>>> accumulated precip and needs input from pcp_combine.
How
> can I
> >>>>>> used
> >>>>>>>>>>>>>> observed composite dBZ as input and where can I
obtain the
> >>>> file
> >>>>>> with
> >>>>>>>>>>>>> this
> >>>>>>>>>>>>>> data in the correct format ?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The obs and WRF output data are initially not on the
same
> >>>> grid +
> >>>>>> the
> >>>>>>>>>> WRF
> >>>>>>>>>>>>>> data is staggered.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting to
> >>>> GRB1
> >>>>>>>>>>>>> correct ?
> >>>>>>>>>>>>>> 2) How do I interpolate the composite dBZ obs data
onto the
> >>>>>>>>>>>>> GRIB1-derived
> >>>>>>>>>>>>>> grids or vice versa ?
> >>>>>>>>>>>>>> 3) Would you have a sample namelist available for me
to run
> >>>> MODE
> >>>>>>>> once
> >>>>>>>>>>>>> I'll
> >>>>>>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular
> >>>> grid ?.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> NB: Would there be any plans in the future to make
all the
> >>>> above
> >>>>>>>>>> process
> >>>>>>>>>>>>>> more user friendly ? Aka a self-contained intuitive
GUI
> >>>> package
> >>>>>>>> (like
> >>>>>>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
> >>>> model,
> >>>>>>>>>> figures
> >>>>>>>>>>>>>> out the computational grid the output data it is on,
then
> >>>> reads in
> >>>>>>>> any
> >>>>>>>>>>>>>> matching standard Level-II observations, figures out
the
> >>>> format,
> >>>>>>>>>>>>>> interpolate and destaggers the data and provide the
desired
> >>>> plots
> >>>>>>>> and
> >>>>>>>>>>>>> stats
> >>>>>>>>>>>>>> to the user ? I have friends in many other fields
> (petroleum,
> >>>>>>>>>> chemistry,
> >>>>>>>>>>>>>> biology, medecine) and we (meteorologists) are
perhaps the
> >>>> only
> >>>>>> one
> >>>>>>>>>>>>> having
> >>>>>>>>>>>>>> to deal with those intermediate extra-curricular
tedious
> tasks
> >>>>>>>> related
> >>>>>>>>>>>>> to
> >>>>>>>>>>>>>> installation of complicated packages, shell scripts,
> >>>> cumbersome
> >>>>>>>> binary
> >>>>>>>>>>>>> file
> >>>>>>>>>>>>>> formats (Especially GRIB which I despise) and
programming in
> >>>> 10
> >>>>>>>>>>>>> different
> >>>>>>>>>>>>>> languages. For instance, when my friend in bio-
engineering
> >>>>>> received
> >>>>>>>> a
> >>>>>>>>>>>>> new
> >>>>>>>>>>>>>> apparatus designed to gather X/Y data on a given
assay
> >>>>>> experiments,
> >>>>>>>> a
> >>>>>>>>>>>>>> computer + GUI software came along with it to make
all the
> >>>> stats
> >>>>>> and
> >>>>>>>>>>>>>> required plots to him/her with a a single mouse click
- No
> >>>>>> specific
> >>>>>>>>>>>>>> computing skills were required other than basic
Windows. Why
> >>>> isn't
> >>>>>>>> it
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking
> for
> >>>>>> many
> >>>>>>>>>>>>>> (similarly 'frustrated') individuals here as in the
end,
> what
> >>>>>>>> matters
> >>>>>>>>>> to
> >>>>>>>>>>>>>> everyone are the results-
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Cheers and best,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>>
-------------------------------------------------------------
> >>>>>>>>>>>> Alexandre Fierro, PhD
> >>>>>>>>>>>> Research Scientist-
> >>>>>>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>>>>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
> Studies*
> >>>>>>>>>> (OU/NOAA)
> >>>>>>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>>>>>>>>>
> >>>>>>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today
is a
> >>>> Gift;
> >>>>>> That
> >>>>>>>>>> is
> >>>>>>>>>>>> why it is called the Present"
> >>>>>>>>>>>>
> >>>>>>>>>>>> "There are only 10 types of people in the world:
> >>>>>>>>>>>> Those who understand binary, and those who don't"
> >>>>>>>>>>>>
> >>>>>>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
> >>>>>>>>>>>> AOML, HRD, LANL or any affiliates."
> >>>>>>>>>>>> ^.^
> >>>>>>>>>>>> (o o)
> >>>>>>>>>>>> /( V )\
> >>>>>>>>>>>> ---m---m----
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> -------------------------------------------------------------
> >>> Alexandre Fierro, PhD
> >>> Research Scientist-
> >>> National Severe Storms Laboratory (NSSL/NOAA)
> >>> *The Cooperative Institute for Mesoscale Meteorological
> Studies*(OU/NOAA)
> >>>
> >>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>
> >>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift; That
> is
> >>> why it is called the Present"
> >>>
> >>> "There are only 10 types of people in the world:
> >>> Those who understand binary, and those who don't"
> >>>
> >>> "My opinions are my own and not representative of OU, NSSL,
> >>> AOML, HRD, LANL or any affiliates."
> >>> ^.^
> >>> (o o)
> >>> /( V )\
> >>> ---m---m----
> >>>
> >>
> >>
> >>
> >> --
> >> -------------------------------------------------------------
> >> Alexandre Fierro, PhD
> >> Research Scientist-
> >> National Severe Storms Laboratory (NSSL/NOAA)
> >> *The Cooperative Institute for Mesoscale Meteorological Studies*
> (OU/NOAA)
> >> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>
> >> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That
> is
> >> why it is called the Present"
> >>
> >> "There are only 10 types of people in the world:
> >> Those who understand binary, and those who don't"
> >>
> >> "My opinions are my own and not representative of OU, NSSL,
> >> AOML, HRD, LANL or any affiliates."
> >> ^.^
> >> (o o)
> >> /( V )\
> >> ---m---m----
> >>
> >
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: John Halley Gotway
Time: Mon Jun 10 15:16:13 2013
Alex,
Here's a list of several things you might do with your data:
(1) Use plot_data_plane to plot it:
METv4.1/bin/plot_data_plane WRFPRS_d01_03 WRFPRS_d01_03_APCP.ps
'name="APCP"; level="A3";'
(2) Retrieve and process corresponding StageIV precip analysis data:
# Run wgrib to find out the model initialization and lead time
wgrib -d 1 -V WRFPRS_d01_03
# It's a 3-hour forecast for the 2013052900 initialization. So we
want observation data valid at 2013052903.
# Pull StageIV data:
wget
ftp://ftp.emc.ncep.noaa.gov/mmb/precip/st2n4.arch/201305/ST4.20130529
# Untar it:
tar -xvf ST4.20130529
# Unzip all the files
gunzip *.Z
# Run pcp_combine to compute a 3-hour accumulation valid at
2013052903:
METv4.1/bin/pcp_combine -add ST4.2013052903.01h 1
ST4.2013052902.01h 1 ST4.2013052901.01h 1 ST4.2013052903.03h.nc
# Figure out the StageIV grid definition.
wgrib -d 1 -V ST4.2013052900.01h
# StageIV grid ->
# polar stereo: Lat1 23.117000 Long1 -119.023000 Orient
-105.000000
# north pole (1121 x 881) Dx 4763 Dy 4763 scan 64 mode 8
# Use copygb to regrid your model precip to the StageIV domain,
using budget interpolation.
# Refer to example here:
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/run4.php
copygb -i3 -k'4*-1 61' -xg"255 5 1121 881 23117 -119023 8 -105000
4763 4763 0 64" WRFPRS_d01_03 WRFPRS_d01_03_APCP_03_st4
(3) Use MODE to compare your GRIB forecast file to the NetCDF
observation file:
# See attached config file
METv4.1/bin/mode WRFPRS_d01_03_APCP_03_st4 ST4.2013052903.03h.nc
MODEConfig_APCP_03
Hopefully that helps get you going.
Thanks,
John
On 06/10/2013 01:52 PM, Alex Fierro via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>
> Hi John:
>
> GRIB files created by running UPP on the WRF(ARW) output are
available here
> (WRFPRS_d01_03 and WRFPRS_d01_04):
>
> /incoming/irap/met_help/FIERRO_DATA
>
> I just placed two files for you to see as the transfer is quite
slow. The
> WRF data is on a 4-km dd-staggered grid over CONUS.
>
> Cheers and thanks !
>
> Alex-
>
>
> On Mon, Jun 10, 2013 at 2:29 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Alex,
>>
>> The grid-to-grid tools in MET require that the two input files
already be
>> on the same grid. The copygb utility is useful for regridding GRIB
files.
>>
>> Perhaps it'd be easiest to just have you send me one of your output
GRIB
>> files. I can take a look at the location of the domain and see if
there's
>> any observation data sources I could recommend.
>>
>> You can post it to our anonymous ftp site by following these
instructions:
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>
>> If you send me some data, please send me an email letting me know
it's
>> there.
>>
>> Thanks,
>> John
>>
>> On 06/07/2013 02:30 PM, Alex Fierro via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>
>>> John:
>>>
>>> I have tried to make a test by running MODE on the same two files
as
>>> follows:
>>>
>>> ../bin/mode ./WRFPRS_d01_06 .//WRFPRS_d01_06
./config/MODEConfig_APCP_06
>>> -outdir ./ -v 2
>>>
>>> and it seems to run fine. My issue nwo is *where* to obtain
gridded files
>>> in GRIB or NC format?
>>>
>>> I tried most datasets abvailable here:
>>>
>>> http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>
>>> but none can be read by either wgrib, wgrib2 or ncview- The
datasets
>> reside
>>> on rather clunky web page interfaces with no real info on what the
files
>>> format are and what is meant by "gridded". Perhaps you can help me
obtain
>>> some obs files of accum precip in NC or GRIB1,2 format compliant
with
>> MET.
>>> Once I get these files, how does one re-grid the observed data
onto the
>> WRF
>>> de-staggered grid of WRFPRS_d01_06 ? Does MODE handle this step or
is
>> there
>>> yet another step to re-grid the observations before running MODE?
>>>
>>> Cheers and thanks,
>>>
>>> On Fri, Jun 7, 2013 at 2:59 PM, Alex Fierro <
>> alexandre.o.fierro at gmail.com>wrote:
>>>
>>>> I realized MODE needed a config file (some sort of namelist).
>>>>
>>>> I used:
>>>>
>>>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
>>>> ./config/MODEConfig_APCP_06 -outdir ./ -v 2
>>>>
>>>> but got:
>>>>
>>>> DEBUG 1: Default Config File:
>>>> /home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
>>>> DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
>>>> DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
>>>> ERROR :
>>>> ERROR : Trouble reading observation file
"./3B42RT.2013.05.29.06z.bin"
>>>> ERROR :
>>>>
>>>> I got those obs files at:
>>>>
>>>> ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
>>>>
>>>> and assumed these were GRIB ? but neither wgrib2 nor wgrib work
in
>> reading
>>>> the file.
>>>>
>>>> Cheers and thanks ! perhaps I'll manage to get this stuff to work
before
>>>> 2015...
>>>>
>>>>
>>>> On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro <
>> alexandre.o.fierro at gmail.com>wrote:
>>>>
>>>>> Hi John:
>>>>>
>>>>> The patch did not fix the problem: After looking at the NC files
in
>> more
>>>>> detail, I realized that the ACCUM precip is for the entire
period up
>> to the
>>>>> file dump time and not for hourly periods.
>>>>>
>>>>> Knowing this, I then tried to run:
>>>>>
>>>>> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc
'name="APCP";
>>>>> level="A06";'
>>>>>
>>>>> and got a NC file that cannot be viewed by ncview or analyzed by
>> ncdump.
>>>>> Is there a ncview equivalent for grib ?
>>>>>
>>>>> I then assumed that my grib files produced by UPP were OK and
tried to
>>>>> run mode as follows:
>>>>>
>>>>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin -outdir
./ -v 2
>>>>>
>>>>> but the command came back with usage errors.
>>>>>
>>>>> Cheers and thanks for your help,
>>>>>
>>>>> Alex-
>>>>>
>>>>>
>>>>> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>> Alex,
>>>>>>
>>>>>> I see that you're using METv4.0. There was a bugfix posted on
>>>>>> 10/16/2012 that I believe is related to the problem you're
seeing.
>> Please
>>>>>> follow the instructions at the top of this page to download
>>>>>> and apply all of the latest METv4.0 patches:
>>>>>>
>>>>>>
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
>>>>>>
>>>>>> Sorry for not catching that one sooner.
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>>
>>>>>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
>>>>>>>
>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600
>
>>>>>>>
>>>>>>> Hi John:
>>>>>>>
>>>>>>> Makes perfect sense.
>>>>>>>
>>>>>>> I have:
>>>>>>>
>>>>>>> /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 |
grep
>> APCP
>>>>>>>
>>>>>>
>>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
>>>>>>> acc:NAve=0
>>>>>>>
>>>>>>> So seems like I already have 0-4h accum precip (?) - This
would
>>>>>> explain why
>>>>>>> I have the same error as before:
>>>>>>>
>>>>>>> /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine -add
>>>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01
WRFPRS_d01_07 01
>>>>>>> WRFPRS_d01_08 01 WRFPRS_d01_09 01
WRFPRS_d01_APCP_06_03_to_09.nc
>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>>>>>> WARNING:
>>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
>>>>>> VarInfo
>>>>>>> "APCP/A1" in GRIB file "WRFPRS_d01_04".
>>>>>>> WARNING:
>>>>>>> ERROR :
>>>>>>> ERROR : get_field() -> can't get data plane from file
>> "WRFPRS_d01_04"
>>>>>>> ERROR :
>>>>>>>
>>>>>>> The netcdf-equivalent array that *should* be read for this is
(are):
>>>>>>>
>>>>>>> float RAINC(Time, south_north, west_east)
>>>>>>> ;
>>>>>>>
>>>>>>> RAINC:FieldType = 104
>>>>>>> ;
>>>>>>>
>>>>>>> RAINC:MemoryOrder = "XY "
>>>>>>> ;
>>>>>>>
>>>>>>> RAINC:description = "ACCUMULATED TOTAL
CUMULUS
>>>>>>> PRECIPITATION"
>>>>>>> ;
>>>>>>> RAINC:units = "mm"
>>>>>>> ;
>>>>>>>
>>>>>>> RAINC:stagger = ""
>>>>>>> ;
>>>>>>>
>>>>>>> RAINC:coordinates = "XLONG XLAT"
>>>>>>> ;
>>>>>>>
>>>>>>> float RAINSH(Time, south_north, west_east)
>>>>>>> ;
>>>>>>>
>>>>>>> RAINSH:FieldType = 104
>>>>>>> ;
>>>>>>>
>>>>>>> RAINSH:MemoryOrder = "XY "
>>>>>>> ;
>>>>>>>
>>>>>>> RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
>>>>>>> PRECIPITATION"
>>>>>>> ;
>>>>>>> RAINSH:units = "mm"
>>>>>>> ;
>>>>>>>
>>>>>>> RAINSH:stagger = ""
>>>>>>> ;
>>>>>>>
>>>>>>> RAINSH:coordinates = "XLONG XLAT"
>>>>>>> ;
>>>>>>>
>>>>>>> float RAINNC(Time, south_north, west_east)
>>>>>>> ;
>>>>>>>
>>>>>>> RAINNC:FieldType = 104
>>>>>>> ;
>>>>>>>
>>>>>>> RAINNC:MemoryOrder = "XY "
>>>>>>> ;
>>>>>>>
>>>>>>> RAINNC:description = "ACCUMULATED TOTAL
GRID SCALE
>>>>>>> PRECIPITATION"
>>>>>>> ;
>>>>>>> RAINNC:units = "mm"
>>>>>>> ;
>>>>>>>
>>>>>>> RAINNC:stagger = ""
>>>>>>> ;
>>>>>>>
>>>>>>> RAINNC:coordinates = "XLONG XLAT" ;
>>>>>>>
>>>>>>>
>>>>>>> Cheers and thank you for your help/guidance,
>>>>>>>
>>>>>>> Alex-
>>>>>>>
>>>>>>> On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>
>>>>>>>> Alex,
>>>>>>>>
>>>>>>>> The pcp_combine tool is telling you that it can't find 4-hour
>>>>>> accumulated
>>>>>>>> precipitation in the file named WRFPRS_d01_04. So what does
that
>> file
>>>>>>>> contain? If you have the wgrib utility available on
>>>>>>>> your system, try running the following:
>>>>>>>> wgrib WRFPRS_d01_04 | grep APCP
>>>>>>>>
>>>>>>>> The output should tell you what accumulation interval(s) are
in
>> there.
>>>>>>>> You've said that it contains 1-hour accumulated precip in
your
>>>>>> message, so
>>>>>>>> I suspect that wgrib will confirm that. But your
>>>>>>>> call to pcp_combine is requesting 4-hours of accumulated
precip with
>>>>>>>> "WRFPRS_d01_04 04".
>>>>>>>>
>>>>>>>> Here's what I think you want:
>>>>>>>>
>>>>>>>> ../bin/pcp_combine -add \
>>>>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
>>>>>>>> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
>>>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
>>>>>>>>
>>>>>>>> Note the following:
>>>>>>>> (1) I've selecting the "01" hour accumulation from each of
the input
>>>>>> files
>>>>>>>> and am adding them together.
>>>>>>>> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
>>>>>> GRIB
>>>>>>>> file contain an accumulation of precipitation *ending* at the
file's
>>>>>> time.
>>>>>>>> So WRFPRS_d01_03 contains precip between hours 2
>>>>>>>> and 3. If you want a total accumulation from 3 to 6, you
should use
>>>>>> the
>>>>>>>> six files listed in the command above.
>>>>>>>>
>>>>>>>> Make sense?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> John
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
>>>>>>>>>
>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>>>>>
>>>>>>>>> John:
>>>>>>>>>
>>>>>>>>> I have tried the following with 6 separate GRIB files each
>>>>>> containing 1-h
>>>>>>>>> accum precip but ran into this problem:
>>>>>>>>>
>>>>>>>>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine
-add
>>>>>>>>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06 06
>>>>>>>>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
>>>>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
>>>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_03
>>>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
>>>>>>>>> WARNING:
>>>>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
>>>>>>>> VarInfo
>>>>>>>>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
>>>>>>>>> WARNING:
>>>>>>>>> ERROR :
>>>>>>>>> ERROR : get_field() -> can't get data plane from file
>>>>>> "WRFPRS_d01_04"
>>>>>>>>> ERROR :
>>>>>>>>>
>>>>>>>>> What are the double digit numbers ahed of the filename ?
>>>>>>>>>
>>>>>>>>> The original WRF OUT Files have:
>>>>>>>>>
>>>>>>>>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
>>>>>>>>>
>>>>>>>>> ...
>>>>>>>>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
>>>>>>>> PRECIPITATION" ;
>>>>>>>>> 935: RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
>>>>>>>>> PRECIPITATION" ;
>>>>>>>>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
>>>>>>>>> PRECIPITATION" ;
>>>>>>>>> ...
>>>>>>>>>
>>>>>>>>> Cheers and thanks,
>>>>>>>>>
>>>>>>>>> Alex-
>>>>>>>>>
>>>>>>>>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT <
>>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Alex,
>>>>>>>>>>
>>>>>>>>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated
>>>>>> over
>>>>>>>> the
>>>>>>>>>> entire model run. So you'll need to adjust your forecast
>>>>>> accumulation
>>>>>>>>>> intervals to match the observation accumulation
>>>>>>>>>> intervals. For example, to get the 6-hour accumulation
between
>>>>>> forecast
>>>>>>>>>> hours 24 and 30, you'd do the following:
>>>>>>>>>>
>>>>>>>>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
>>>>>> WRFPRS_d01_24 24
>>>>>>>>>> WRFPRS_d01_APCP_06_24_to_30.nc
>>>>>>>>>>
>>>>>>>>>> That will grab the 30 hours of precip from the first file
and the
>> 24
>>>>>>>> hours
>>>>>>>>>> of precip from the second file and subtract them. The last
>>>>>> argument is
>>>>>>>> the
>>>>>>>>>> name of the NetCDF file to be used.
>>>>>>>>>>
>>>>>>>>>> You might also want to run the plot_data_plane utility just
to
>> make
>>>>>> sure
>>>>>>>>>> that your data looks good:
>>>>>>>>>>
>>>>>>>>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
WRFPRS_d01_30.nc
>>>>>>>>>> 'name="APCP"; level="A30";'
>>>>>>>>>>
>>>>>>>>>> That will select the field we've described (precip
accumulated
>> over
>>>>>> 30
>>>>>>>>>> hours) from the file you've passed it and create a
postscript
>> image
>>>>>> of
>>>>>>>> it.
>>>>>>>>>>
>>>>>>>>>> Hope that helps.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
>>>>>>>>>>>
>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
>>>>>>>>>>>
>>>>>>>>>>> Hi John:
>>>>>>>>>>>
>>>>>>>>>>> I use ARW so seems like UNIPOST already de-staggers the
data.
>>>>>>>>>>>
>>>>>>>>>>> I have:
>>>>>>>>>>>
>>>>>>>>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
>> WRFPRS_d01_03
>>>>>>>>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
>>>>>> levels=(0,0)
>>>>>>>>>>> grid=255 MSL 3hr fcst:
>>>>>>>>>>> PRMSL=Pressure reduced to MSL [Pa]
>>>>>>>>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS
grid 3
>>>>>>>> num_in_ave 0
>>>>>>>>>>> missing 0
>>>>>>>>>>> center 7 subcenter 0 process 125 Table 2 scan:
WE:SN
>>>>>> winds(grid)
>>>>>>>>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
>> -98.000000
>>>>>>>>>>> Latin1 60.000000 Latin2 30.000000 LatSP
0.000000 LonSP
>>>>>> 0.000000
>>>>>>>>>>> North Pole (1199 x 799) Dx 4.000000 Dy 4.000000
scan 64
>>>>>> mode
>>>>>>>> 136
>>>>>>>>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
>> 9.90164e+06
>>>>>>>>>> DecScale 2
>>>>>>>>>>> BinScale 3
>>>>>>>>>>>
>>>>>>>>>>> The next step I guess would be to produce accumulated
precip from
>>>>>>>> several
>>>>>>>>>>> of those WRFPRS_d01_0FHR files correct (where FHR=forecast
hour)?
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> Alex-
>>>>>>>>>>>
>>>>>>>>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via
RT <
>>>>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Alex,
>>>>>>>>>>>>
>>>>>>>>>>>> So you have a GRIB file that's output by unipost, named
>>>>>>>> "WRFPRS_d01_03".
>>>>>>>>>>>> And you're running it through copygb using the grid
defined
>>>>>> by the
>>>>>>>>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt".
So
>>>>>>>>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt
files
>>>>>> contain?
>>>>>>>>>>>>
>>>>>>>>>>>> Also, try running the following:
>>>>>>>>>>>> wgrib -V -d 1 WRFPRS_d01_03
>>>>>>>>>>>>
>>>>>>>>>>>> That'll give a 'V'erbose description of the first record
in that
>>>>>> file,
>>>>>>>>>>>> including the current grid definition.
>>>>>>>>>>>>
>>>>>>>>>>>> Can you send me that output?
>>>>>>>>>>>>
>>>>>>>>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-
ARW, the
>>>>>> output
>>>>>>>>>> of
>>>>>>>>>>>> unipost should already be unstaggered. If it's WRF-NMM,
the
>>>>>> output of
>>>>>>>>>>>> unipost will be staggered, and you need to run it
>>>>>>>>>>>> through copygb to de-stagger it.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> John
>>>>>>>>>>>>
>>>>>>>>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi John:
>>>>>>>>>>>>>
>>>>>>>>>>>>> As you might have expected I ran into some issues
running
>> copygb.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
conformal
>>>>>>>>>>>> grid-When I
>>>>>>>>>>>>> run:
>>>>>>>>>>>>>
>>>>>>>>>>>>> cat > itag <<EOF
>>>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>>>>>>>>>>>> netcdf
>>>>>>>>>>>>> ${SY}-${SM}-${SD}_03:00:00
>>>>>>>>>>>>> ${tag}
>>>>>>>>>>>>> EOF
>>>>>>>>>>>>> echo 'FILE TO BE PROCESSED'
>>>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
>>>>>>>>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
unipost_ctrl_d01.03.out
>>>>>> 2>&1
>>>>>>>>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
>>>>>>>>>>>>>
>>>>>>>>>>>>> # this stuff interp to a regular grid
>>>>>>>>>>>>> read nav < 'copygb_gridnav.txt'
>>>>>>>>>>>>> export nav
>>>>>>>>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
wrfprs_d01_03
>>>>>>>>>>>>>
>>>>>>>>>>>>> I get:
>>>>>>>>>>>>>
>>>>>>>>>>>>> copygb: unsupported output grid
>>>>>>>>>>>>>
>>>>>>>>>>>>> I tried to change it to:
>>>>>>>>>>>>>
>>>>>>>>>>>>> read nav < 'copygb_hwrf.txt'
>>>>>>>>>>>>>
>>>>>>>>>>>>> but got the same error
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any clues on how I can get this program to destagger my
WRF
>>>>>> output in
>>>>>>>>>> the
>>>>>>>>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which ran
fine)?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers and thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
>>>>>>>>>>>>> <alexandre.o.fierro at gmail.com>wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Dear John:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Many thanks for your prompt and detailed reply.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I definitely blame the lack of funding in our field to
hire
>>>>>> software
>>>>>>>>>>>>>> engineers (at the level of the individuals working for
>>>>>> MathWorks,
>>>>>>>>>>>> Google,
>>>>>>>>>>>>>> Facebook etc) to develop user friendly GUIs for
meteorological
>>>>>> use.
>>>>>>>> I
>>>>>>>>>>>> truly
>>>>>>>>>>>>>> hope your team will get the funding it deserves to
further
>>>>>> enhance
>>>>>>>>>> this
>>>>>>>>>>>>>> very complex tool, which has a lot of potential and
could
>>>>>> definitely
>>>>>>>>>> be
>>>>>>>>>>>> of
>>>>>>>>>>>>>> relevant use for routine forecasters.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I will give it a try using the precip data you
specified for
>>>>>> now -
>>>>>>>>>> I'll
>>>>>>>>>>>>>> let you know if I run into some issues.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> South side of Norman and Purcell are in a tornado
warning at
>> the
>>>>>>>>>> moment
>>>>>>>>>>>> -
>>>>>>>>>>>>>> my attention is now 'detoured' towards the sky.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers and best,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Alexandre-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway via
RT <
>>>>>>>>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Alex,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Here's a link to the MET website for some sources of
>>>>>> observation
>>>>>>>>>> data:
>>>>>>>>>>>>>>>
>>>>>>>>>>
http://www.dtcenter.org/met/users/downloads/observation_data.php
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> MET can basically handle gridded data in GRIB1 or
GRIB2
>> format.
>>>>>>>> The
>>>>>>>>>>>> only
>>>>>>>>>>>>>>> other gridded data formats it can handle are the
NetCDF
>> output
>>>>>> of
>>>>>>>> the
>>>>>>>>>>>>>>> pinterp utility, and the internal NetCDF format used
by
>>>>>>>>>>>>>>> MET. We'd like to more generally support CF-compliant
NetCDF
>>>>>> data,
>>>>>>>>>> but
>>>>>>>>>>>>>>> we haven't gotten that done yet.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> MODE can be used to compare two different gridded data
files.
>>>>>> They
>>>>>>>>>> can
>>>>>>>>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
>>>>>> GRIB2,
>>>>>>>>>>>> NetCDF
>>>>>>>>>>>>>>> output of pcp_combine, and so on. MODE was developed
>>>>>>>>>>>>>>> using accumulated precipitation data, but we have
applied it
>> to
>>>>>>>> other
>>>>>>>>>>>>>>> fields, including radar reflectivity. We just had to
adjust
>>>>>> the
>>>>>>>>>>>>>>> convolution radius and threshold, and think about the
other
>>>>>>>> settings.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As for a source of gridded reflectivity data, I'm
really not
>>>>>> sure.
>>>>>>>>>>>> We've
>>>>>>>>>>>>>>> used RTMA data from NCEP in the past, and there's a
link to
>>>>>> that on
>>>>>>>>>> the
>>>>>>>>>>>>>>> observation data page. We've used Q2 data from NSSL
>>>>>>>>>>>>>>> in the past, but we first had to get it into GRIB
format. I
>>>>>> see
>>>>>>>> the
>>>>>>>>>> Q2
>>>>>>>>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but
can see
>>>>>> how to
>>>>>>>>>>>>>>> access the data directly.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regarding UPP, yes, it destaggers the grid. We
suggest using
>>>>>> the
>>>>>>>>>>>> copygb
>>>>>>>>>>>>>>> utility for regridding GRIB1 data. copygb only
handles
>> GRIB1,
>>>>>> not
>>>>>>>>>>>> GRIB2.
>>>>>>>>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
>>>>>>>>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
Alternatively,
>>>>>> the
>>>>>>>>>> wgrib2
>>>>>>>>>>>>>>> tool does some regridding, but it's pretty limited.
Here's a
>>>>>>>> portion
>>>>>>>>>>>> of
>>>>>>>>>>>>>>> the MET online tutorial that discussed copygb:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> For examples of running MODE, please take a look in
>>>>>>>>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples in
there
>> of
>>>>>>>>>> running
>>>>>>>>>>>>>>> MODE. I'd also suggest reading through the MODE
section of
>> the
>>>>>>>>>> online
>>>>>>>>>>>>>>> tutorial:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Generally speaking, you should start by playing around
with
>> the
>>>>>>>>>>>>>>> convolution radius and threshold to define objects
that
>> capture
>>>>>>>> your
>>>>>>>>>>>> areas
>>>>>>>>>>>>>>> of interest.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regarding future enhancements, at this point our
funding is
>>>>>> limited
>>>>>>>>>> to
>>>>>>>>>>>>>>> only support - no additional development. Hopefully,
that
>> will
>>>>>>>>>> change
>>>>>>>>>>>> in
>>>>>>>>>>>>>>> the future. We have submitted a proposal that would
>>>>>>>>>>>>>>> include development to support automated regridding of
data.
>>>>>> So
>>>>>>>> you
>>>>>>>>>>>>>>> could skip the copygb step, for example, before
running
>>>>>> grid_stat
>>>>>>>> and
>>>>>>>>>>>> MODE.
>>>>>>>>>>>>>>> As for why the tools for petroleum, chemistry,
>>>>>>>>>>>>>>> biology, and medicine are more sophisticated than
those for
>>>>>>>>>>>> meteorology,
>>>>>>>>>>>>>>> I suspect there's more money driving the other
disciplines.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> John
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted
upon.
>>>>>>>>>>>>>>>> Transaction: Ticket created by
alexandre.o.fierro at gmail.com
>>>>>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>>>>>> Subject: Obs data to feed in MET tools.
>>>>>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
>>>>>>>>>>>>>>>> Status: new
>>>>>>>>>>>>>>>> Ticket <URL:
>>>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi John:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have been reading the MET Users Guide for data
formats and
>>>>>>>>>> remained
>>>>>>>>>>>> a
>>>>>>>>>>>>>>> bit
>>>>>>>>>>>>>>>> daunted by this constant interplay between all sorts
of file
>>>>>>>>>> formats -
>>>>>>>>>>>>>>> At
>>>>>>>>>>>>>>>> the moment my goal is rather succinct, I would like
to be
>>>>>> able to
>>>>>>>>>>>>>>> compare
>>>>>>>>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
>>>>>> (from
>>>>>>>>>> e.g,
>>>>>>>>>>>>>>> NMQ,
>>>>>>>>>>>>>>>> NCEP or another source).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Where can I obtain the observation file with formats
>> compliant
>>>>>>>> with
>>>>>>>>>>>> MET
>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>> the Users Guide does not point to any specific URL?
Note
>> that
>>>>>> I am
>>>>>>>>>> now
>>>>>>>>>>>>>>> able
>>>>>>>>>>>>>>>> to convert the WRF.NC files into GRIB1 files via UPP.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I would be interested in using the MODE tool for
compiste
>> dBZ
>>>>>>>>>> during a
>>>>>>>>>>>>>>>> single model time. I have read, however, that MODE
was
>>>>>> designed to
>>>>>>>>>>>>>>> handle
>>>>>>>>>>>>>>>> accumulated precip and needs input from pcp_combine.
How
>> can I
>>>>>>>> used
>>>>>>>>>>>>>>>> observed composite dBZ as input and where can I
obtain the
>>>>>> file
>>>>>>>> with
>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>> data in the correct format ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The obs and WRF output data are initially not on the
same
>>>>>> grid +
>>>>>>>> the
>>>>>>>>>>>> WRF
>>>>>>>>>>>>>>>> data is staggered.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting to
>>>>>> GRB1
>>>>>>>>>>>>>>> correct ?
>>>>>>>>>>>>>>>> 2) How do I interpolate the composite dBZ obs data
onto the
>>>>>>>>>>>>>>> GRIB1-derived
>>>>>>>>>>>>>>>> grids or vice versa ?
>>>>>>>>>>>>>>>> 3) Would you have a sample namelist available for me
to run
>>>>>> MODE
>>>>>>>>>> once
>>>>>>>>>>>>>>> I'll
>>>>>>>>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular
>>>>>> grid ?.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> NB: Would there be any plans in the future to make
all the
>>>>>> above
>>>>>>>>>>>> process
>>>>>>>>>>>>>>>> more user friendly ? Aka a self-contained intuitive
GUI
>>>>>> package
>>>>>>>>>> (like
>>>>>>>>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
>>>>>> model,
>>>>>>>>>>>> figures
>>>>>>>>>>>>>>>> out the computational grid the output data it is on,
then
>>>>>> reads in
>>>>>>>>>> any
>>>>>>>>>>>>>>>> matching standard Level-II observations, figures out
the
>>>>>> format,
>>>>>>>>>>>>>>>> interpolate and destaggers the data and provide the
desired
>>>>>> plots
>>>>>>>>>> and
>>>>>>>>>>>>>>> stats
>>>>>>>>>>>>>>>> to the user ? I have friends in many other fields
>> (petroleum,
>>>>>>>>>>>> chemistry,
>>>>>>>>>>>>>>>> biology, medecine) and we (meteorologists) are
perhaps the
>>>>>> only
>>>>>>>> one
>>>>>>>>>>>>>>> having
>>>>>>>>>>>>>>>> to deal with those intermediate extra-curricular
tedious
>> tasks
>>>>>>>>>> related
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> installation of complicated packages, shell scripts,
>>>>>> cumbersome
>>>>>>>>>> binary
>>>>>>>>>>>>>>> file
>>>>>>>>>>>>>>>> formats (Especially GRIB which I despise) and
programming in
>>>>>> 10
>>>>>>>>>>>>>>> different
>>>>>>>>>>>>>>>> languages. For instance, when my friend in bio-
engineering
>>>>>>>> received
>>>>>>>>>> a
>>>>>>>>>>>>>>> new
>>>>>>>>>>>>>>>> apparatus designed to gather X/Y data on a given
assay
>>>>>>>> experiments,
>>>>>>>>>> a
>>>>>>>>>>>>>>>> computer + GUI software came along with it to make
all the
>>>>>> stats
>>>>>>>> and
>>>>>>>>>>>>>>>> required plots to him/her with a a single mouse click
- No
>>>>>>>> specific
>>>>>>>>>>>>>>>> computing skills were required other than basic
Windows. Why
>>>>>> isn't
>>>>>>>>>> it
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking
>> for
>>>>>>>> many
>>>>>>>>>>>>>>>> (similarly 'frustrated') individuals here as in the
end,
>> what
>>>>>>>>>> matters
>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> everyone are the results-
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Cheers and best,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>
-------------------------------------------------------------
>>>>>>>>>>>>>> Alexandre Fierro, PhD
>>>>>>>>>>>>>> Research Scientist-
>>>>>>>>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>>>>>>>>>>>> *The Cooperative Institute for Mesoscale Meteorological
>> Studies*
>>>>>>>>>>>> (OU/NOAA)
>>>>>>>>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Yesterday is History, Tomorrow is a Mystery and Today
is a
>>>>>> Gift;
>>>>>>>> That
>>>>>>>>>>>> is
>>>>>>>>>>>>>> why it is called the Present"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "There are only 10 types of people in the world:
>>>>>>>>>>>>>> Those who understand binary, and those who don't"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
>>>>>>>>>>>>>> AOML, HRD, LANL or any affiliates."
>>>>>>>>>>>>>> ^.^
>>>>>>>>>>>>>> (o o)
>>>>>>>>>>>>>> /( V )\
>>>>>>>>>>>>>> ---m---m----
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -------------------------------------------------------------
>>>>> Alexandre Fierro, PhD
>>>>> Research Scientist-
>>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>>> *The Cooperative Institute for Mesoscale Meteorological
>> Studies*(OU/NOAA)
>>>>>
>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>>
>>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift; That
>> is
>>>>> why it is called the Present"
>>>>>
>>>>> "There are only 10 types of people in the world:
>>>>> Those who understand binary, and those who don't"
>>>>>
>>>>> "My opinions are my own and not representative of OU, NSSL,
>>>>> AOML, HRD, LANL or any affiliates."
>>>>> ^.^
>>>>> (o o)
>>>>> /( V )\
>>>>> ---m---m----
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -------------------------------------------------------------
>>>> Alexandre Fierro, PhD
>>>> Research Scientist-
>>>> National Severe Storms Laboratory (NSSL/NOAA)
>>>> *The Cooperative Institute for Mesoscale Meteorological Studies*
>> (OU/NOAA)
>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
>>>>
>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a Gift;
That
>> is
>>>> why it is called the Present"
>>>>
>>>> "There are only 10 types of people in the world:
>>>> Those who understand binary, and those who don't"
>>>>
>>>> "My opinions are my own and not representative of OU, NSSL,
>>>> AOML, HRD, LANL or any affiliates."
>>>> ^.^
>>>> (o o)
>>>> /( V )\
>>>> ---m---m----
>>>>
>>>
>>>
>>>
>>
>>
>
>
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: John Halley Gotway
Time: Mon Jun 10 15:16:13 2013
////////////////////////////////////////////////////////////////////////////////
//
// MODE configuration file.
//
// For additional information, see the MET_BASE/data/config/README
file.
//
////////////////////////////////////////////////////////////////////////////////
//
// Output model name to be written
//
model = "WRF";
////////////////////////////////////////////////////////////////////////////////
//
// Approximate grid resolution (km)
//
grid_res = 4;
////////////////////////////////////////////////////////////////////////////////
//
// Forecast and observation fields to be verified
//
fcst = {
field = {
name = "APCP";
level = "A03";
};
raw_thresh = >=0.0;
conv_radius = 15; // in grid squares
conv_thresh = >=5.0;
vld_thresh = 0.5;
area_thresh = >=0.0;
inten_perc_value = 100;
inten_perc_thresh = >=0.0;
merge_thresh = >=1.25;
merge_flag = THRESH;
};
obs = {
field = {
name = "APCP_03";
level = "(*,*)";
};
raw_thresh = >=0.0;
conv_radius = 15; // in grid squares
conv_thresh = >=5.0;
vld_thresh = 0.5;
area_thresh = >=0.0;
inten_perc_value = 100;
inten_perc_thresh = >=0.0;
merge_thresh = >=1.25;
merge_flag = THRESH;
};
////////////////////////////////////////////////////////////////////////////////
//
// Handle missing data
//
mask_missing_flag = NONE;
//
// Match objects between the forecast and observation fields
//
match_flag = MERGE_BOTH;
//
// Maximum centroid distance for objects to be compared
//
max_centroid_dist = 800.0/grid_res;
////////////////////////////////////////////////////////////////////////////////
//
// Verification masking regions
//
mask = {
grid = "";
grid_flag = NONE; // Apply to NONE, FCST, OBS, or BOTH
poly = "";
poly_flag = NONE; // Apply to NONE, FCST, OBS, or BOTH
};
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine weights
//
weight = {
centroid_dist = 2.0;
boundary_dist = 4.0;
convex_hull_dist = 0.0;
angle_diff = 1.0;
area_ratio = 1.0;
int_area_ratio = 2.0;
complexity_ratio = 0.0;
inten_perc_ratio = 0.0;
inten_perc_value = 50;
}
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine interest functions
//
interest_function = {
centroid_dist = (
( 0.0, 1.0 )
( 60.0/grid_res, 1.0 )
( 600.0/grid_res, 0.0 )
);
boundary_dist = (
( 0.0, 1.0 )
( 400.0/grid_res, 0.0 )
);
convex_hull_dist = (
( 0.0, 1.0 )
( 400.0/grid_res, 0.0 )
);
angle_diff = (
( 0.0, 1.0 )
( 30.0, 1.0 )
( 90.0, 0.0 )
);
corner = 0.8;
ratio_if = (
( 0.0, 0.0 )
( corner, 1.0 )
( 1.0, 1.0 )
);
area_ratio = ratio_if;
int_area_ratio = (
( 0.00, 0.00 )
( 0.10, 0.50 )
( 0.25, 1.00 )
( 1.00, 1.00 )
);
complexity_ratio = ratio_if;
inten_perc_ratio = ratio_if;
}
////////////////////////////////////////////////////////////////////////////////
//
// Total interest threshold for determining matches
//
total_interest_thresh = 0.7;
//
// Interest threshold for printing output pair information
//
print_interest_thresh = 0.0;
////////////////////////////////////////////////////////////////////////////////
//
// Plotting information
//
met_data_dir = "MET_BASE/data";
fcst_raw_plot = {
color_table = "MET_BASE/data/colortables/met_default.ctable";
plot_min = 0.0;
plot_max = 0.0;
colorbar_spacing = 1;
};
obs_raw_plot = {
color_table = "MET_BASE/data/colortables/met_default.ctable";
plot_min = 0.0;
plot_max = 0.0;
colorbar_spacing = 1;
};
object_plot = {
color_table = "MET_BASE/data/colortables/mode_obj.ctable";
};
//
// Number of grid boxes to fill with bad data values along the edge of
the field
// to avoid edge effects.
//
zero_border_size = 1;
//
// Boolean for plotting on the region of valid data within the domain
//
plot_valid_flag = FALSE;
//
// Plot polyline edges using great circle arcs instead of straight
lines
//
plot_gcarc_flag = FALSE;
////////////////////////////////////////////////////////////////////////////////
//
// NetCDF matched pairs, PostScript, and contingency table output
files
//
ps_plot_flag = TRUE;
nc_pairs_flag = TRUE;
ct_stats_flag = TRUE;
////////////////////////////////////////////////////////////////////////////////
output_prefix = "";
version = "V4.1";
////////////////////////////////////////////////////////////////////////////////
------------------------------------------------
Subject: Obs data to feed in MET tools.
From: Alex Fierro
Time: Mon Jun 10 16:01:26 2013
Hi John:
Many thanks for providing all the details behind the commands that
must be
entered prior to running MODE -I must say I was way off in my initial
attempts. The final results are remarkable and very impressive. I
would
like to thank you very much for your patience and for your step by
step
guidance towards the successful completion of running this complex
code.
I'll go ahead now and write a script that will plot those daily.
Perhaps one could include your email below in the MET Tutorial/Users
Guide
as an example in the end. For Lambda users such as me, it is always
easier
to start with something one is familiar with (WRF-ARW ouput) and most
importantly with a list of instructions that works.
Cheers and best,
Alex-
On Mon, Jun 10, 2013 at 4:16 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Alex,
>
> Here's a list of several things you might do with your data:
>
> (1) Use plot_data_plane to plot it:
> METv4.1/bin/plot_data_plane WRFPRS_d01_03 WRFPRS_d01_03_APCP.ps
> 'name="APCP"; level="A3";'
>
> (2) Retrieve and process corresponding StageIV precip analysis data:
> # Run wgrib to find out the model initialization and lead time
> wgrib -d 1 -V WRFPRS_d01_03
>
> # It's a 3-hour forecast for the 2013052900 initialization. So
we want
> observation data valid at 2013052903.
> # Pull StageIV data:
> wget
>
ftp://ftp.emc.ncep.noaa.gov/mmb/precip/st2n4.arch/201305/ST4.20130529
>
> # Untar it:
> tar -xvf ST4.20130529
>
> # Unzip all the files
> gunzip *.Z
>
> # Run pcp_combine to compute a 3-hour accumulation valid at
2013052903:
> METv4.1/bin/pcp_combine -add ST4.2013052903.01h 1
ST4.2013052902.01h 1
> ST4.2013052901.01h 1 ST4.2013052903.03h.nc
>
> # Figure out the StageIV grid definition.
> wgrib -d 1 -V ST4.2013052900.01h
>
> # StageIV grid ->
> # polar stereo: Lat1 23.117000 Long1 -119.023000 Orient
-105.000000
> # north pole (1121 x 881) Dx 4763 Dy 4763 scan 64 mode 8
>
> # Use copygb to regrid your model precip to the StageIV domain,
using
> budget interpolation.
> # Refer to example here:
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/run4.php
> copygb -i3 -k'4*-1 61' -xg"255 5 1121 881 23117 -119023 8 -105000
4763
> 4763 0 64" WRFPRS_d01_03 WRFPRS_d01_03_APCP_03_st4
>
> (3) Use MODE to compare your GRIB forecast file to the NetCDF
observation
> file:
> # See attached config file
> METv4.1/bin/mode WRFPRS_d01_03_APCP_03_st4
ST4.2013052903.03h.ncMODEConfig_APCP_03
>
> Hopefully that helps get you going.
>
> Thanks,
> John
>
>
> On 06/10/2013 01:52 PM, Alex Fierro via RT wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >
> > Hi John:
> >
> > GRIB files created by running UPP on the WRF(ARW) output are
available
> here
> > (WRFPRS_d01_03 and WRFPRS_d01_04):
> >
> > /incoming/irap/met_help/FIERRO_DATA
> >
> > I just placed two files for you to see as the transfer is quite
slow. The
> > WRF data is on a 4-km dd-staggered grid over CONUS.
> >
> > Cheers and thanks !
> >
> > Alex-
> >
> >
> > On Mon, Jun 10, 2013 at 2:29 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Alex,
> >>
> >> The grid-to-grid tools in MET require that the two input files
already
> be
> >> on the same grid. The copygb utility is useful for regridding
GRIB
> files.
> >>
> >> Perhaps it'd be easiest to just have you send me one of your
output GRIB
> >> files. I can take a look at the location of the domain and see
if
> there's
> >> any observation data sources I could recommend.
> >>
> >> You can post it to our anonymous ftp site by following these
> instructions:
> >> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>
> >> If you send me some data, please send me an email letting me know
it's
> >> there.
> >>
> >> Thanks,
> >> John
> >>
> >> On 06/07/2013 02:30 PM, Alex Fierro via RT wrote:
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>
> >>> John:
> >>>
> >>> I have tried to make a test by running MODE on the same two
files as
> >>> follows:
> >>>
> >>> ../bin/mode ./WRFPRS_d01_06 .//WRFPRS_d01_06
> ./config/MODEConfig_APCP_06
> >>> -outdir ./ -v 2
> >>>
> >>> and it seems to run fine. My issue nwo is *where* to obtain
gridded
> files
> >>> in GRIB or NC format?
> >>>
> >>> I tried most datasets abvailable here:
> >>>
> >>> http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>
> >>> but none can be read by either wgrib, wgrib2 or ncview- The
datasets
> >> reside
> >>> on rather clunky web page interfaces with no real info on what
the
> files
> >>> format are and what is meant by "gridded". Perhaps you can help
me
> obtain
> >>> some obs files of accum precip in NC or GRIB1,2 format compliant
with
> >> MET.
> >>> Once I get these files, how does one re-grid the observed data
onto the
> >> WRF
> >>> de-staggered grid of WRFPRS_d01_06 ? Does MODE handle this step
or is
> >> there
> >>> yet another step to re-grid the observations before running
MODE?
> >>>
> >>> Cheers and thanks,
> >>>
> >>> On Fri, Jun 7, 2013 at 2:59 PM, Alex Fierro <
> >> alexandre.o.fierro at gmail.com>wrote:
> >>>
> >>>> I realized MODE needed a config file (some sort of namelist).
> >>>>
> >>>> I used:
> >>>>
> >>>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
> >>>> ./config/MODEConfig_APCP_06 -outdir ./ -v 2
> >>>>
> >>>> but got:
> >>>>
> >>>> DEBUG 1: Default Config File:
> >>>> /home/Alex.Fierro/METv4.0/data/config/MODEConfig_default
> >>>> DEBUG 1: Match Config File: ./config/MODEConfig_APCP_06
> >>>> DEBUG 1: Merge Config File: ./config/MODEConfig_APCP_06
> >>>> ERROR :
> >>>> ERROR : Trouble reading observation file
> "./3B42RT.2013.05.29.06z.bin"
> >>>> ERROR :
> >>>>
> >>>> I got those obs files at:
> >>>>
> >>>> ftp://disc2.nascom.nasa.gov/data/TRMM/Gridded/3B42RT/201305/
> >>>>
> >>>> and assumed these were GRIB ? but neither wgrib2 nor wgrib work
in
> >> reading
> >>>> the file.
> >>>>
> >>>> Cheers and thanks ! perhaps I'll manage to get this stuff to
work
> before
> >>>> 2015...
> >>>>
> >>>>
> >>>> On Fri, Jun 7, 2013 at 2:47 PM, Alex Fierro <
> >> alexandre.o.fierro at gmail.com>wrote:
> >>>>
> >>>>> Hi John:
> >>>>>
> >>>>> The patch did not fix the problem: After looking at the NC
files in
> >> more
> >>>>> detail, I realized that the ACCUM precip is for the entire
period up
> >> to the
> >>>>> file dump time and not for hourly periods.
> >>>>>
> >>>>> Knowing this, I then tried to run:
> >>>>>
> >>>>> ../bin/plot_data_plane WRFPRS_d01_06 WRFPRS_d01_06.nc
'name="APCP";
> >>>>> level="A06";'
> >>>>>
> >>>>> and got a NC file that cannot be viewed by ncview or analyzed
by
> >> ncdump.
> >>>>> Is there a ncview equivalent for grib ?
> >>>>>
> >>>>> I then assumed that my grib files produced by UPP were OK and
tried
> to
> >>>>> run mode as follows:
> >>>>>
> >>>>> ../bin/mode ./WRFPRS_d01_06 ./3B42RT.2013.05.29.06z.bin
-outdir ./
> -v 2
> >>>>>
> >>>>> but the command came back with usage errors.
> >>>>>
> >>>>> Cheers and thanks for your help,
> >>>>>
> >>>>> Alex-
> >>>>>
> >>>>>
> >>>>> On Mon, Jun 3, 2013 at 11:50 AM, John Halley Gotway via RT <
> >>>>> met_help at ucar.edu> wrote:
> >>>>>
> >>>>>> Alex,
> >>>>>>
> >>>>>> I see that you're using METv4.0. There was a bugfix posted
on
> >>>>>> 10/16/2012 that I believe is related to the problem you're
seeing.
> >> Please
> >>>>>> follow the instructions at the top of this page to download
> >>>>>> and apply all of the latest METv4.0 patches:
> >>>>>>
> >>>>>>
> >>
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.0/index.php
> >>>>>>
> >>>>>> Sorry for not catching that one sooner.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> John
> >>>>>>
> >>>>>>
> >>>>>> On 06/03/2013 09:51 AM, Alex Fierro via RT wrote:
> >>>>>>>
> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>>>>>
> >>>>>>> Hi John:
> >>>>>>>
> >>>>>>> Makes perfect sense.
> >>>>>>>
> >>>>>>> I have:
> >>>>>>>
> >>>>>>> /home/Alex.Fierro/METv4.0/scripts(205)>wgrib WRFPRS_d01_04 |
grep
> >> APCP
> >>>>>>>
> >>>>>>
> >>
>
281:424304284:d=13052900:APCP:kpds5=61:kpds6=1:kpds7=0:TR=4:P1=0:P2=4:TimeU=1:sfc:0-
4hr
> >>>>>>> acc:NAve=0
> >>>>>>>
> >>>>>>> So seems like I already have 0-4h accum precip (?) - This
would
> >>>>>> explain why
> >>>>>>> I have the same error as before:
> >>>>>>>
> >>>>>>> /home/Alex.Fierro/METv4.0/scripts(204)>../bin/pcp_combine
-add
> >>>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01
WRFPRS_d01_07 01
> >>>>>>> WRFPRS_d01_08 01 WRFPRS_d01_09 01
WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
> >>>>>>> WARNING:
> >>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found for
> >>>>>> VarInfo
> >>>>>>> "APCP/A1" in GRIB file "WRFPRS_d01_04".
> >>>>>>> WARNING:
> >>>>>>> ERROR :
> >>>>>>> ERROR : get_field() -> can't get data plane from file
> >> "WRFPRS_d01_04"
> >>>>>>> ERROR :
> >>>>>>>
> >>>>>>> The netcdf-equivalent array that *should* be read for this
is
> (are):
> >>>>>>>
> >>>>>>> float RAINC(Time, south_north, west_east)
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINC:FieldType = 104
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINC:MemoryOrder = "XY "
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINC:description = "ACCUMULATED TOTAL
CUMULUS
> >>>>>>> PRECIPITATION"
> >>>>>>> ;
> >>>>>>> RAINC:units = "mm"
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINC:stagger = ""
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINC:coordinates = "XLONG XLAT"
> >>>>>>> ;
> >>>>>>>
> >>>>>>> float RAINSH(Time, south_north, west_east)
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINSH:FieldType = 104
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINSH:MemoryOrder = "XY "
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINSH:description = "ACCUMULATED SHALLOW
> CUMULUS
> >>>>>>> PRECIPITATION"
> >>>>>>> ;
> >>>>>>> RAINSH:units = "mm"
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINSH:stagger = ""
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINSH:coordinates = "XLONG XLAT"
> >>>>>>> ;
> >>>>>>>
> >>>>>>> float RAINNC(Time, south_north, west_east)
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINNC:FieldType = 104
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINNC:MemoryOrder = "XY "
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINNC:description = "ACCUMULATED TOTAL
GRID
> SCALE
> >>>>>>> PRECIPITATION"
> >>>>>>> ;
> >>>>>>> RAINNC:units = "mm"
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINNC:stagger = ""
> >>>>>>> ;
> >>>>>>>
> >>>>>>> RAINNC:coordinates = "XLONG XLAT" ;
> >>>>>>>
> >>>>>>>
> >>>>>>> Cheers and thank you for your help/guidance,
> >>>>>>>
> >>>>>>> Alex-
> >>>>>>>
> >>>>>>> On Mon, Jun 3, 2013 at 10:30 AM, John Halley Gotway via RT <
> >>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>
> >>>>>>>> Alex,
> >>>>>>>>
> >>>>>>>> The pcp_combine tool is telling you that it can't find 4-
hour
> >>>>>> accumulated
> >>>>>>>> precipitation in the file named WRFPRS_d01_04. So what
does that
> >> file
> >>>>>>>> contain? If you have the wgrib utility available on
> >>>>>>>> your system, try running the following:
> >>>>>>>> wgrib WRFPRS_d01_04 | grep APCP
> >>>>>>>>
> >>>>>>>> The output should tell you what accumulation interval(s)
are in
> >> there.
> >>>>>>>> You've said that it contains 1-hour accumulated precip
in your
> >>>>>> message, so
> >>>>>>>> I suspect that wgrib will confirm that. But your
> >>>>>>>> call to pcp_combine is requesting 4-hours of accumulated
precip
> with
> >>>>>>>> "WRFPRS_d01_04 04".
> >>>>>>>>
> >>>>>>>> Here's what I think you want:
> >>>>>>>>
> >>>>>>>> ../bin/pcp_combine -add \
> >>>>>>>> WRFPRS_d01_04 01 WRFPRS_d01_05 01 WRFPRS_d01_06 01 \
> >>>>>>>> WRFPRS_d01_07 01 WRFPRS_d01_08 01 WRFPRS_d01_09 01 \
> >>>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>>>>>
> >>>>>>>> Note the following:
> >>>>>>>> (1) I've selecting the "01" hour accumulation from each of
the
> input
> >>>>>> files
> >>>>>>>> and am adding them together.
> >>>>>>>> (2) I've omitted the first argument you used, for
"WRFPRS_d01_03".
> >>>>>> GRIB
> >>>>>>>> file contain an accumulation of precipitation *ending* at
the
> file's
> >>>>>> time.
> >>>>>>>> So WRFPRS_d01_03 contains precip between hours 2
> >>>>>>>> and 3. If you want a total accumulation from 3 to 6, you
should
> use
> >>>>>> the
> >>>>>>>> six files listed in the command above.
> >>>>>>>>
> >>>>>>>> Make sense?
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> John
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 05/31/2013 03:12 PM, Alex Fierro via RT wrote:
> >>>>>>>>>
> >>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600 >
> >>>>>>>>>
> >>>>>>>>> John:
> >>>>>>>>>
> >>>>>>>>> I have tried the following with 6 separate GRIB files each
> >>>>>> containing 1-h
> >>>>>>>>> accum precip but ran into this problem:
> >>>>>>>>>
> >>>>>>>>> /home/Alex.Fierro/METv4.0/scripts(211)>../bin/pcp_combine
-add
> >>>>>>>>> WRFPRS_d01_03 03 WRFPRS_d01_04 04 WRFPRS_d01_05 05
WRFPRS_d01_06
> 06
> >>>>>>>>> WRFPRS_d01_07 07 WRFPRS_d01_08 08 WRFPRS_d01_09 09
> >>>>>>>>> WRFPRS_d01_APCP_06_03_to_09.nc
> >>>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_03
> >>>>>>>>> DEBUG 1: Reading input file: WRFPRS_d01_04
> >>>>>>>>> WARNING:
> >>>>>>>>> WARNING: MetGrib1DataFile::data_plane() -> No exact match
found
> for
> >>>>>>>> VarInfo
> >>>>>>>>> "APCP/A3" in GRIB file "WRFPRS_d01_04".
> >>>>>>>>> WARNING:
> >>>>>>>>> ERROR :
> >>>>>>>>> ERROR : get_field() -> can't get data plane from file
> >>>>>> "WRFPRS_d01_04"
> >>>>>>>>> ERROR :
> >>>>>>>>>
> >>>>>>>>> What are the double digit numbers ahed of the filename ?
> >>>>>>>>>
> >>>>>>>>> The original WRF OUT Files have:
> >>>>>>>>>
> >>>>>>>>> ncdump -h wrfout_d01_2013-05-29_00:00:00 | grep -in ACC
> >>>>>>>>>
> >>>>>>>>> ...
> >>>>>>>>> 928: RAINC:description = "ACCUMULATED TOTAL CUMULUS
> >>>>>>>> PRECIPITATION" ;
> >>>>>>>>> 935: RAINSH:description = "ACCUMULATED SHALLOW
CUMULUS
> >>>>>>>>> PRECIPITATION" ;
> >>>>>>>>> 942: RAINNC:description = "ACCUMULATED TOTAL GRID
SCALE
> >>>>>>>>> PRECIPITATION" ;
> >>>>>>>>> ...
> >>>>>>>>>
> >>>>>>>>> Cheers and thanks,
> >>>>>>>>>
> >>>>>>>>> Alex-
> >>>>>>>>>
> >>>>>>>>> On Fri, May 31, 2013 at 3:11 PM, John Halley Gotway via RT
<
> >>>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>>
> >>>>>>>>>> Alex,
> >>>>>>>>>>
> >>>>>>>>>> Yep, by default WRF-ARW dumps out it's precipitation
accumulated
> >>>>>> over
> >>>>>>>> the
> >>>>>>>>>> entire model run. So you'll need to adjust your forecast
> >>>>>> accumulation
> >>>>>>>>>> intervals to match the observation accumulation
> >>>>>>>>>> intervals. For example, to get the 6-hour accumulation
between
> >>>>>> forecast
> >>>>>>>>>> hours 24 and 30, you'd do the following:
> >>>>>>>>>>
> >>>>>>>>>> METv4.1/bin/pcp_combine -subtract WRFPRS_d01_30 30
> >>>>>> WRFPRS_d01_24 24
> >>>>>>>>>> WRFPRS_d01_APCP_06_24_to_30.nc
> >>>>>>>>>>
> >>>>>>>>>> That will grab the 30 hours of precip from the first file
and
> the
> >> 24
> >>>>>>>> hours
> >>>>>>>>>> of precip from the second file and subtract them. The
last
> >>>>>> argument is
> >>>>>>>> the
> >>>>>>>>>> name of the NetCDF file to be used.
> >>>>>>>>>>
> >>>>>>>>>> You might also want to run the plot_data_plane utility
just to
> >> make
> >>>>>> sure
> >>>>>>>>>> that your data looks good:
> >>>>>>>>>>
> >>>>>>>>>> METv4.1/bin/plot_data_plane WRFPRS_d01_30
> WRFPRS_d01_30.nc
> >>>>>>>>>> 'name="APCP"; level="A30";'
> >>>>>>>>>>
> >>>>>>>>>> That will select the field we've described (precip
accumulated
> >> over
> >>>>>> 30
> >>>>>>>>>> hours) from the file you've passed it and create a
postscript
> >> image
> >>>>>> of
> >>>>>>>> it.
> >>>>>>>>>>
> >>>>>>>>>> Hope that helps.
> >>>>>>>>>>
> >>>>>>>>>> Thanks,
> >>>>>>>>>> John
> >>>>>>>>>>
> >>>>>>>>>> On 05/31/2013 01:58 PM, Alex Fierro via RT wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>>
> >>>>>>>>>>> Hi John:
> >>>>>>>>>>>
> >>>>>>>>>>> I use ARW so seems like UNIPOST already de-staggers the
data.
> >>>>>>>>>>>
> >>>>>>>>>>> I have:
> >>>>>>>>>>>
> >>>>>>>>>>> /home/Alex.Fierro/UPPV2.1/scripts(208)>wgrib -V -d 1
> >> WRFPRS_d01_03
> >>>>>>>>>>> rec 1:0:date 2013052900 PRMSL kpds5=2 kpds6=102 kpds7=0
> >>>>>> levels=(0,0)
> >>>>>>>>>>> grid=255 MSL 3hr fcst:
> >>>>>>>>>>> PRMSL=Pressure reduced to MSL [Pa]
> >>>>>>>>>>> timerange 0 P1 3 P2 0 TimeU 1 nx 1199 ny 799 GDS
grid 3
> >>>>>>>> num_in_ave 0
> >>>>>>>>>>> missing 0
> >>>>>>>>>>> center 7 subcenter 0 process 125 Table 2 scan:
WE:SN
> >>>>>> winds(grid)
> >>>>>>>>>>> Lambert Conf: Lat1 21.641000 Lon1 -120.450000 Lov
> >> -98.000000
> >>>>>>>>>>> Latin1 60.000000 Latin2 30.000000 LatSP
0.000000
> LonSP
> >>>>>> 0.000000
> >>>>>>>>>>> North Pole (1199 x 799) Dx 4.000000 Dy
4.000000
> scan 64
> >>>>>> mode
> >>>>>>>> 136
> >>>>>>>>>>> min/max data 99016.4 102768 num bits 16 BDS_Ref
> >> 9.90164e+06
> >>>>>>>>>> DecScale 2
> >>>>>>>>>>> BinScale 3
> >>>>>>>>>>>
> >>>>>>>>>>> The next step I guess would be to produce accumulated
precip
> from
> >>>>>>>> several
> >>>>>>>>>>> of those WRFPRS_d01_0FHR files correct (where
FHR=forecast
> hour)?
> >>>>>>>>>>>
> >>>>>>>>>>> Cheers,
> >>>>>>>>>>>
> >>>>>>>>>>> Alex-
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, May 31, 2013 at 11:21 AM, John Halley Gotway via
RT <
> >>>>>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Alex,
> >>>>>>>>>>>>
> >>>>>>>>>>>> So you have a GRIB file that's output by unipost, named
> >>>>>>>> "WRFPRS_d01_03".
> >>>>>>>>>>>> And you're running it through copygb using the
grid
> defined
> >>>>>> by the
> >>>>>>>>>>>> contents of "copygb_gridnav.txt" or "copygb_hwrf.txt".
So
> >>>>>>>>>>>> what do those copygb_gridnav.txt and copygb_hwrf.txt
files
> >>>>>> contain?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also, try running the following:
> >>>>>>>>>>>> wgrib -V -d 1 WRFPRS_d01_03
> >>>>>>>>>>>>
> >>>>>>>>>>>> That'll give a 'V'erbose description of the first
record in
> that
> >>>>>> file,
> >>>>>>>>>>>> including the current grid definition.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Can you send me that output?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also, are you running WRF-ARW or WRF-NMM? If it's WRF-
ARW,
> the
> >>>>>> output
> >>>>>>>>>> of
> >>>>>>>>>>>> unipost should already be unstaggered. If it's WRF-
NMM, the
> >>>>>> output of
> >>>>>>>>>>>> unipost will be staggered, and you need to run it
> >>>>>>>>>>>> through copygb to de-stagger it.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> John
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 05/30/2013 04:11 PM, Alex Fierro via RT wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi John:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> As you might have expected I ran into some issues
running
> >> copygb.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> We run WRF on CONUS at 4-km grid spacing on a Lambert
> conformal
> >>>>>>>>>>>> grid-When I
> >>>>>>>>>>>>> run:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> cat > itag <<EOF
> >>>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
> >>>>>>>>>>>>> netcdf
> >>>>>>>>>>>>> ${SY}-${SM}-${SD}_03:00:00
> >>>>>>>>>>>>> ${tag}
> >>>>>>>>>>>>> EOF
> >>>>>>>>>>>>> echo 'FILE TO BE PROCESSED'
> >>>>>>>>>>>>> /raid/alex/20${YMD}00/wrfout_d01_${SY}-${SM}-
${SD}_03:00:00
> >>>>>>>>>>>>> mpirun -np 8 ${POSTEXEC}/unipost.exe >
> unipost_ctrl_d01.03.out
> >>>>>> 2>&1
> >>>>>>>>>>>>> mv WRFPRS03.tm00 WRFPRS_d01_03
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> # this stuff interp to a regular grid
> >>>>>>>>>>>>> read nav < 'copygb_gridnav.txt'
> >>>>>>>>>>>>> export nav
> >>>>>>>>>>>>> ${POSTEXEC}/copygb.exe -xg"${nav}" WRFPRS_d01_03
> wrfprs_d01_03
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I get:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> copygb: unsupported output grid
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I tried to change it to:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> read nav < 'copygb_hwrf.txt'
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> but got the same error
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Any clues on how I can get this program to destagger
my WRF
> >>>>>> output in
> >>>>>>>>>> the
> >>>>>>>>>>>>> GRIB file WRFPRS_d01_03 produced by unipost (which
ran
> fine)?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Cheers and thanks,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> PS: I am using METV4.0 and the model outout is from
WRFV3.4.1
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Thu, May 30, 2013 at 3:53 PM, Alex Fierro
> >>>>>>>>>>>>> <alexandre.o.fierro at gmail.com>wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Dear John:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Many thanks for your prompt and detailed reply.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I definitely blame the lack of funding in our field
to hire
> >>>>>> software
> >>>>>>>>>>>>>> engineers (at the level of the individuals working
for
> >>>>>> MathWorks,
> >>>>>>>>>>>> Google,
> >>>>>>>>>>>>>> Facebook etc) to develop user friendly GUIs for
> meteorological
> >>>>>> use.
> >>>>>>>> I
> >>>>>>>>>>>> truly
> >>>>>>>>>>>>>> hope your team will get the funding it deserves to
further
> >>>>>> enhance
> >>>>>>>>>> this
> >>>>>>>>>>>>>> very complex tool, which has a lot of potential and
could
> >>>>>> definitely
> >>>>>>>>>> be
> >>>>>>>>>>>> of
> >>>>>>>>>>>>>> relevant use for routine forecasters.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I will give it a try using the precip data you
specified for
> >>>>>> now -
> >>>>>>>>>> I'll
> >>>>>>>>>>>>>> let you know if I run into some issues.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> South side of Norman and Purcell are in a tornado
warning at
> >> the
> >>>>>>>>>> moment
> >>>>>>>>>>>> -
> >>>>>>>>>>>>>> my attention is now 'detoured' towards the sky.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Cheers and best,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Alexandre-
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Thu, May 30, 2013 at 2:32 PM, John Halley Gotway
via RT <
> >>>>>>>>>>>>>> met_help at ucar.edu> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Alex,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Here's a link to the MET website for some sources of
> >>>>>> observation
> >>>>>>>>>> data:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>
> http://www.dtcenter.org/met/users/downloads/observation_data.php
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> MET can basically handle gridded data in GRIB1 or
GRIB2
> >> format.
> >>>>>>>> The
> >>>>>>>>>>>> only
> >>>>>>>>>>>>>>> other gridded data formats it can handle are the
NetCDF
> >> output
> >>>>>> of
> >>>>>>>> the
> >>>>>>>>>>>>>>> pinterp utility, and the internal NetCDF format used
by
> >>>>>>>>>>>>>>> MET. We'd like to more generally support CF-
compliant
> NetCDF
> >>>>>> data,
> >>>>>>>>>> but
> >>>>>>>>>>>>>>> we haven't gotten that done yet.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> MODE can be used to compare two different gridded
data
> files.
> >>>>>> They
> >>>>>>>>>> can
> >>>>>>>>>>>>>>> be any of the gridded data files that MET supports -
GRIB1,
> >>>>>> GRIB2,
> >>>>>>>>>>>> NetCDF
> >>>>>>>>>>>>>>> output of pcp_combine, and so on. MODE was
developed
> >>>>>>>>>>>>>>> using accumulated precipitation data, but we have
applied
> it
> >> to
> >>>>>>>> other
> >>>>>>>>>>>>>>> fields, including radar reflectivity. We just had
to
> adjust
> >>>>>> the
> >>>>>>>>>>>>>>> convolution radius and threshold, and think about
the other
> >>>>>>>> settings.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> As for a source of gridded reflectivity data, I'm
really
> not
> >>>>>> sure.
> >>>>>>>>>>>> We've
> >>>>>>>>>>>>>>> used RTMA data from NCEP in the past, and there's a
link to
> >>>>>> that on
> >>>>>>>>>> the
> >>>>>>>>>>>>>>> observation data page. We've used Q2 data from NSSL
> >>>>>>>>>>>>>>> in the past, but we first had to get it into GRIB
format.
> I
> >>>>>> see
> >>>>>>>> the
> >>>>>>>>>> Q2
> >>>>>>>>>>>>>>> website (http://www.nssl.noaa.gov/projects/q2/) but
can
> see
> >>>>>> how to
> >>>>>>>>>>>>>>> access the data directly.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Regarding UPP, yes, it destaggers the grid. We
suggest
> using
> >>>>>> the
> >>>>>>>>>>>> copygb
> >>>>>>>>>>>>>>> utility for regridding GRIB1 data. copygb only
handles
> >> GRIB1,
> >>>>>> not
> >>>>>>>>>>>> GRIB2.
> >>>>>>>>>>>>>>> To regrid GRIB2 data, you can use the cnvgrib
> >>>>>>>>>>>>>>> utility to regrid from GRIB2 to GRIB1 first.
> Alternatively,
> >>>>>> the
> >>>>>>>>>> wgrib2
> >>>>>>>>>>>>>>> tool does some regridding, but it's pretty limited.
> Here's a
> >>>>>>>> portion
> >>>>>>>>>>>> of
> >>>>>>>>>>>>>>> the MET online tutorial that discussed copygb:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/copygb/index.php
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> For examples of running MODE, please take a look in
> >>>>>>>>>>>>>>> METv4.1/scripts/test_mode.sh. There are 3 examples
in
> there
> >> of
> >>>>>>>>>> running
> >>>>>>>>>>>>>>> MODE. I'd also suggest reading through the MODE
section of
> >> the
> >>>>>>>>>> online
> >>>>>>>>>>>>>>> tutorial:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>
>
http://www.dtcenter.org/met/users/support/online_tutorial/METv4.0/mode/index.php
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Generally speaking, you should start by playing
around with
> >> the
> >>>>>>>>>>>>>>> convolution radius and threshold to define objects
that
> >> capture
> >>>>>>>> your
> >>>>>>>>>>>> areas
> >>>>>>>>>>>>>>> of interest.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Regarding future enhancements, at this point our
funding is
> >>>>>> limited
> >>>>>>>>>> to
> >>>>>>>>>>>>>>> only support - no additional development.
Hopefully, that
> >> will
> >>>>>>>>>> change
> >>>>>>>>>>>> in
> >>>>>>>>>>>>>>> the future. We have submitted a proposal that would
> >>>>>>>>>>>>>>> include development to support automated regridding
of
> data.
> >>>>>> So
> >>>>>>>> you
> >>>>>>>>>>>>>>> could skip the copygb step, for example, before
running
> >>>>>> grid_stat
> >>>>>>>> and
> >>>>>>>>>>>> MODE.
> >>>>>>>>>>>>>>> As for why the tools for petroleum,
chemistry,
> >>>>>>>>>>>>>>> biology, and medicine are more sophisticated than
those for
> >>>>>>>>>>>> meteorology,
> >>>>>>>>>>>>>>> I suspect there's more money driving the other
disciplines.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>> John
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 05/30/2013 10:50 AM, Alex Fierro via RT wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thu May 30 10:50:30 2013: Request 61600 was acted
upon.
> >>>>>>>>>>>>>>>> Transaction: Ticket created by
> alexandre.o.fierro at gmail.com
> >>>>>>>>>>>>>>>> Queue: met_help
> >>>>>>>>>>>>>>>> Subject: Obs data to feed in MET tools.
> >>>>>>>>>>>>>>>> Owner: Nobody
> >>>>>>>>>>>>>>>> Requestors: alexandre.o.fierro at gmail.com
> >>>>>>>>>>>>>>>> Status: new
> >>>>>>>>>>>>>>>> Ticket <URL:
> >>>>>>>>>>>>
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=61600>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hi John:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have been reading the MET Users Guide for data
formats
> and
> >>>>>>>>>> remained
> >>>>>>>>>>>> a
> >>>>>>>>>>>>>>> bit
> >>>>>>>>>>>>>>>> daunted by this constant interplay between all
sorts of
> file
> >>>>>>>>>> formats -
> >>>>>>>>>>>>>>> At
> >>>>>>>>>>>>>>>> the moment my goal is rather succinct, I would like
to be
> >>>>>> able to
> >>>>>>>>>>>>>>> compare
> >>>>>>>>>>>>>>>> my WRF forecast (lets say composite dBZ) with
observations
> >>>>>> (from
> >>>>>>>>>> e.g,
> >>>>>>>>>>>>>>> NMQ,
> >>>>>>>>>>>>>>>> NCEP or another source).
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Where can I obtain the observation file with
formats
> >> compliant
> >>>>>>>> with
> >>>>>>>>>>>> MET
> >>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>> the Users Guide does not point to any specific URL?
Note
> >> that
> >>>>>> I am
> >>>>>>>>>> now
> >>>>>>>>>>>>>>> able
> >>>>>>>>>>>>>>>> to convert the WRF.NC files into GRIB1 files via
UPP.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I would be interested in using the MODE tool for
compiste
> >> dBZ
> >>>>>>>>>> during a
> >>>>>>>>>>>>>>>> single model time. I have read, however, that MODE
was
> >>>>>> designed to
> >>>>>>>>>>>>>>> handle
> >>>>>>>>>>>>>>>> accumulated precip and needs input from
pcp_combine. How
> >> can I
> >>>>>>>> used
> >>>>>>>>>>>>>>>> observed composite dBZ as input and where can I
obtain the
> >>>>>> file
> >>>>>>>> with
> >>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>> data in the correct format ?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> The obs and WRF output data are initially not on
the same
> >>>>>> grid +
> >>>>>>>> the
> >>>>>>>>>>>> WRF
> >>>>>>>>>>>>>>>> data is staggered.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 1) I assume that UPP de-staggers the data when
converting
> to
> >>>>>> GRB1
> >>>>>>>>>>>>>>> correct ?
> >>>>>>>>>>>>>>>> 2) How do I interpolate the composite dBZ obs data
onto
> the
> >>>>>>>>>>>>>>> GRIB1-derived
> >>>>>>>>>>>>>>>> grids or vice versa ?
> >>>>>>>>>>>>>>>> 3) Would you have a sample namelist available for
me to
> run
> >>>>>> MODE
> >>>>>>>>>> once
> >>>>>>>>>>>>>>> I'll
> >>>>>>>>>>>>>>>> succeed in obtaining WRF and OBS data on the same
regular
> >>>>>> grid ?.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> NB: Would there be any plans in the future to make
all the
> >>>>>> above
> >>>>>>>>>>>> process
> >>>>>>>>>>>>>>>> more user friendly ? Aka a self-contained
intuitive GUI
> >>>>>> package
> >>>>>>>>>> (like
> >>>>>>>>>>>>>>>> Matlab) that reads in data directly from WRF or any
other
> >>>>>> model,
> >>>>>>>>>>>> figures
> >>>>>>>>>>>>>>>> out the computational grid the output data it is
on, then
> >>>>>> reads in
> >>>>>>>>>> any
> >>>>>>>>>>>>>>>> matching standard Level-II observations, figures
out the
> >>>>>> format,
> >>>>>>>>>>>>>>>> interpolate and destaggers the data and provide the
> desired
> >>>>>> plots
> >>>>>>>>>> and
> >>>>>>>>>>>>>>> stats
> >>>>>>>>>>>>>>>> to the user ? I have friends in many other fields
> >> (petroleum,
> >>>>>>>>>>>> chemistry,
> >>>>>>>>>>>>>>>> biology, medecine) and we (meteorologists) are
perhaps the
> >>>>>> only
> >>>>>>>> one
> >>>>>>>>>>>>>>> having
> >>>>>>>>>>>>>>>> to deal with those intermediate extra-curricular
tedious
> >> tasks
> >>>>>>>>>> related
> >>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>> installation of complicated packages, shell
scripts,
> >>>>>> cumbersome
> >>>>>>>>>> binary
> >>>>>>>>>>>>>>> file
> >>>>>>>>>>>>>>>> formats (Especially GRIB which I despise) and
programming
> in
> >>>>>> 10
> >>>>>>>>>>>>>>> different
> >>>>>>>>>>>>>>>> languages. For instance, when my friend in bio-
engineering
> >>>>>>>> received
> >>>>>>>>>> a
> >>>>>>>>>>>>>>> new
> >>>>>>>>>>>>>>>> apparatus designed to gather X/Y data on a given
assay
> >>>>>>>> experiments,
> >>>>>>>>>> a
> >>>>>>>>>>>>>>>> computer + GUI software came along with it to make
all the
> >>>>>> stats
> >>>>>>>> and
> >>>>>>>>>>>>>>>> required plots to him/her with a a single mouse
click - No
> >>>>>>>> specific
> >>>>>>>>>>>>>>>> computing skills were required other than basic
Windows.
> Why
> >>>>>> isn't
> >>>>>>>>>> it
> >>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>> same for meteorologists I wonder ? I am sure I am
speaking
> >> for
> >>>>>>>> many
> >>>>>>>>>>>>>>>> (similarly 'frustrated') individuals here as in the
end,
> >> what
> >>>>>>>>>> matters
> >>>>>>>>>>>> to
> >>>>>>>>>>>>>>>> everyone are the results-
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Cheers and best,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>
> -------------------------------------------------------------
> >>>>>>>>>>>>>> Alexandre Fierro, PhD
> >>>>>>>>>>>>>> Research Scientist-
> >>>>>>>>>>>>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>>>>>>>>>>>> *The Cooperative Institute for Mesoscale
Meteorological
> >> Studies*
> >>>>>>>>>>>> (OU/NOAA)
> >>>>>>>>>>>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> "Yesterday is History, Tomorrow is a Mystery and
Today is a
> >>>>>> Gift;
> >>>>>>>> That
> >>>>>>>>>>>> is
> >>>>>>>>>>>>>> why it is called the Present"
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> "There are only 10 types of people in the world:
> >>>>>>>>>>>>>> Those who understand binary, and those who don't"
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> "My opinions are my own and not representative of OU,
NSSL,
> >>>>>>>>>>>>>> AOML, HRD, LANL or any affiliates."
> >>>>>>>>>>>>>> ^.^
> >>>>>>>>>>>>>> (o o)
> >>>>>>>>>>>>>> /( V )\
> >>>>>>>>>>>>>> ---m---m----
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> -------------------------------------------------------------
> >>>>> Alexandre Fierro, PhD
> >>>>> Research Scientist-
> >>>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>>> *The Cooperative Institute for Mesoscale Meteorological
> >> Studies*(OU/NOAA)
> >>>>>
> >>>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>>
> >>>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift;
> That
> >> is
> >>>>> why it is called the Present"
> >>>>>
> >>>>> "There are only 10 types of people in the world:
> >>>>> Those who understand binary, and those who don't"
> >>>>>
> >>>>> "My opinions are my own and not representative of OU, NSSL,
> >>>>> AOML, HRD, LANL or any affiliates."
> >>>>> ^.^
> >>>>> (o o)
> >>>>> /( V )\
> >>>>> ---m---m----
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> -------------------------------------------------------------
> >>>> Alexandre Fierro, PhD
> >>>> Research Scientist-
> >>>> National Severe Storms Laboratory (NSSL/NOAA)
> >>>> *The Cooperative Institute for Mesoscale Meteorological
Studies*
> >> (OU/NOAA)
> >>>> Los Alamos National Laboratory, Los Alamos, NM (LANL)
> >>>>
> >>>> "Yesterday is History, Tomorrow is a Mystery and Today is a
Gift; That
> >> is
> >>>> why it is called the Present"
> >>>>
> >>>> "There are only 10 types of people in the world:
> >>>> Those who understand binary, and those who don't"
> >>>>
> >>>> "My opinions are my own and not representative of OU, NSSL,
> >>>> AOML, HRD, LANL or any affiliates."
> >>>> ^.^
> >>>> (o o)
> >>>> /( V )\
> >>>> ---m---m----
> >>>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
--
-------------------------------------------------------------
Alexandre Fierro, PhD
Research Scientist-
National Severe Storms Laboratory (NSSL/NOAA)
*The Cooperative Institute for Mesoscale Meteorological Studies*
(OU/NOAA)
Los Alamos National Laboratory, Los Alamos, NM (LANL)
"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That
is
why it is called the Present"
"There are only 10 types of people in the world:
Those who understand binary, and those who don't"
"My opinions are my own and not representative of OU, NSSL,
AOML, HRD, LANL or any affiliates."
^.^
(o o)
/( V )\
---m---m----
------------------------------------------------
More information about the Met_help
mailing list