[Met_help] [rt.rap.ucar.edu #95459] History for Verification of Atmospheric Motion Vectors using PointStat
Howard Soh via RT
met_help at ucar.edu
Fri Jun 19 14:53:35 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
We generate atmospheric motion vectors (AMVs) using GEOS imagery and were hoping to use PointStat and StatAnalysis to produce some verification metrics on how well the algorithm to produce the AMVs was doing compared to RAOB and aircraft observations.
The AMVs that we are generating output the winds in u and v components in m/s as well as the vertical placement in pressure and height and are in NetCDF format. I can provide an example file of the AMVs if it would be helpful. I then obtain MADIS RAOB and aircraft data from NCEP, and using madis2nc convert this data into the format wanted by MET. I created a PointStat configuration file that is edited for the forecast and observation fields to hopefully work with the data. I then run the following command:
point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc 20200530_madis2nc.nc /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi -outdir /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
PointStat then errors indicating that it is having trouble reading the AMV file. I have attached both the configuration file as well as the output log to the email. Is there something that I need to do to the AMV NetCDF file before using PointStat that I can not aware of, or is there a better method of verification using MET to compare point motion vectors at various heights to observational data?
Thank you for any help that you can provide!
Josh Boustead
Meteorologist/Modeler
PEMDAS Technology and Innovation
Norman, OK 73069
--
CONFIDENTIALITY NOTICE: This email message and all attachments
transmitted with it may contain legally privileged and confidential
information intended solely for the use of the addressee. If the reader of
this message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, or other use of this
message or its attachments is strictly prohibited. If you have received
this message in error, please notify the sender immediately and delete this
message from your system. Thank you.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Julie Prestopnik
Time: Tue Jun 02 09:38:30 2020
Hi Josh.
Thank you for all of this information. I see that MET is having
trouble
reading your forecast file. Thank you for attaching your config file
and
your log file. Could you please also send us your forecast file and
your
observation file so that we can take a closer look? You can follow
the
instructions under the "How to Send Us Data" section on the following
page:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
Julie
On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
<met_help at ucar.edu>
wrote:
>
> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> Transaction: Ticket created by josh.boustead at pemdastech.com
> Queue: met_help
> Subject: Verification of Atmospheric Motion Vectors using
PointStat
> Owner: Nobody
> Requestors: josh.boustead at pemdastech.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459 >
>
>
> Hello,
>
> We generate atmospheric motion vectors (AMVs) using GEOS imagery and
were
> hoping to use PointStat and StatAnalysis to produce some
verification
> metrics on how well the algorithm to produce the AMVs was doing
compared to
> RAOB and aircraft observations.
>
> The AMVs that we are generating output the winds in u and v
components in
> m/s as well as the vertical placement in pressure and height and are
in
> NetCDF format. I can provide an example file of the AMVs if it would
be
> helpful. I then obtain MADIS RAOB and aircraft data from NCEP, and
using
> madis2nc convert this data into the format wanted by MET. I created
a
> PointStat configuration file that is edited for the forecast and
> observation fields to hopefully work with the data. I then run the
> following command:
>
> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
20200530_madis2nc.nc
> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
-outdir
> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
>
> PointStat then errors indicating that it is having trouble reading
the AMV
> file. I have attached both the configuration file as well as the
output log
> to the email. Is there something that I need to do to the AMV NetCDF
file
> before using PointStat that I can not aware of, or is there a better
method
> of verification using MET to compare point motion vectors at various
> heights to observational data?
>
> Thank you for any help that you can provide!
>
> Josh Boustead
>
> Meteorologist/Modeler
> PEMDAS Technology and Innovation
> Norman, OK 73069
>
>
>
>
> --
>
>
>
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE: This email message and all attachments
> transmitted with it may contain legally privileged and confidential
> information intended solely for the use of the addressee. If the
reader of
> this message is not the intended recipient, you are hereby notified
that
> any reading, dissemination, distribution, copying, or other use of
this
> message or its attachments is strictly prohibited. If you have
received
> this message in error, please notify the sender immediately and
delete
> this
> message from your system. Thank you.
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Josh Boustead
Time: Tue Jun 02 10:04:43 2020
Hi Julie,
Thanks for the quick rely! I have updated the data as per instructions
from the link in your email.
Please let me know if you need anything additional.
Thanks again,
Josh
> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
<met_help at ucar.edu> wrote:
>
> Hi Josh.
>
> Thank you for all of this information. I see that MET is having
trouble
> reading your forecast file. Thank you for attaching your config
file and
> your log file. Could you please also send us your forecast file and
your
> observation file so that we can take a closer look? You can follow
the
> instructions under the "How to Send Us Data" section on the
following page:
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk <https://dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk>
>
> Julie
>
> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
<met_help at ucar.edu <mailto:met_help at ucar.edu>>
> wrote:
>
>>
>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
>> Transaction: Ticket created by josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>
>> Queue: met_help
>> Subject: Verification of Atmospheric Motion Vectors using
PointStat
>> Owner: Nobody
>> Requestors: josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>
>>
>> Hello,
>>
>> We generate atmospheric motion vectors (AMVs) using GEOS imagery
and were
>> hoping to use PointStat and StatAnalysis to produce some
verification
>> metrics on how well the algorithm to produce the AMVs was doing
compared to
>> RAOB and aircraft observations.
>>
>> The AMVs that we are generating output the winds in u and v
components in
>> m/s as well as the vertical placement in pressure and height and
are in
>> NetCDF format. I can provide an example file of the AMVs if it
would be
>> helpful. I then obtain MADIS RAOB and aircraft data from NCEP, and
using
>> madis2nc convert this data into the format wanted by MET. I created
a
>> PointStat configuration file that is edited for the forecast and
>> observation fields to hopefully work with the data. I then run the
>> following command:
>>
>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
20200530_madis2nc.nc
>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
-outdir
>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
>>
>> PointStat then errors indicating that it is having trouble reading
the AMV
>> file. I have attached both the configuration file as well as the
output log
>> to the email. Is there something that I need to do to the AMV
NetCDF file
>> before using PointStat that I can not aware of, or is there a
better method
>> of verification using MET to compare point motion vectors at
various
>> heights to observational data?
>>
>> Thank you for any help that you can provide!
>>
>> Josh Boustead
>>
>> Meteorologist/Modeler
>> PEMDAS Technology and Innovation
>> Norman, OK 73069
>>
>>
>>
>>
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email message and all attachments
>> transmitted with it may contain legally privileged and confidential
>> information intended solely for the use of the addressee. If the
reader of
>> this message is not the intended recipient, you are hereby notified
that
>> any reading, dissemination, distribution, copying, or other use of
this
>> message or its attachments is strictly prohibited. If you have
received
>> this message in error, please notify the sender immediately and
delete
>> this
>> message from your system. Thank you.
>>
>>
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
--
CONFIDENTIALITY NOTICE: This email message and all attachments
transmitted with it may contain legally privileged and confidential
information intended solely for the use of the addressee. If the
reader of
this message is not the intended recipient, you are hereby notified
that
any reading, dissemination, distribution, copying, or other use of
this
message or its attachments is strictly prohibited. If you have
received
this message in error, please notify the sender immediately and delete
this
message from your system. Thank you.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Julie Prestopnik
Time: Tue Jun 02 11:07:32 2020
Hi Josh.
Unfortunately, this NetCDF forecast data is not in a format that MET
can
read. MET is only able to read certain flavors of NetCDF:
(1) The NetCDF output of the WRF p_interp or wrf_interp utilities
(2) The NetCDF Climate Forecast (CF) convention
(
http://cfconventions.org/Data/cf-conventions/cf-con(ventions-1.7/cf-
conventions.html
<http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html>
)
(3) The NetCDF output of other MET tools, like pcp_combine
Your options are to either (1) reformat this data into a file format
MET
understands or (2) write a python wrapper script to interpret this
data and
utilize python embedding. Examples of python embedding can be found
here:
https://dtcenter.org/community-code/model-evaluation-tools-met/sample-
analysis-scripts
I hope this helps!
Julie
On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459 >
>
> Hi Julie,
>
> Thanks for the quick rely! I have updated the data as per
instructions
> from the link in your email.
>
> Please let me know if you need anything additional.
>
> Thanks again,
>
> Josh
>
> > On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
> >
> > Hi Josh.
> >
> > Thank you for all of this information. I see that MET is having
trouble
> > reading your forecast file. Thank you for attaching your config
file and
> > your log file. Could you please also send us your forecast file
and your
> > observation file so that we can take a closer look? You can
follow the
> > instructions under the "How to Send Us Data" section on the
following
> page:
> >
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> <
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> >
> >
> > Julie
> >
> > On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
<met_help at ucar.edu
> <mailto:met_help at ucar.edu>>
> > wrote:
> >
> >>
> >> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> >> Transaction: Ticket created by josh.boustead at pemdastech.com
<mailto:
> josh.boustead at pemdastech.com>
> >> Queue: met_help
> >> Subject: Verification of Atmospheric Motion Vectors using
PointStat
> >> Owner: Nobody
> >> Requestors: josh.boustead at pemdastech.com <mailto:
> josh.boustead at pemdastech.com>
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> >>
> >>
> >> Hello,
> >>
> >> We generate atmospheric motion vectors (AMVs) using GEOS imagery
and
> were
> >> hoping to use PointStat and StatAnalysis to produce some
verification
> >> metrics on how well the algorithm to produce the AMVs was doing
> compared to
> >> RAOB and aircraft observations.
> >>
> >> The AMVs that we are generating output the winds in u and v
components
> in
> >> m/s as well as the vertical placement in pressure and height and
are in
> >> NetCDF format. I can provide an example file of the AMVs if it
would be
> >> helpful. I then obtain MADIS RAOB and aircraft data from NCEP,
and using
> >> madis2nc convert this data into the format wanted by MET. I
created a
> >> PointStat configuration file that is edited for the forecast and
> >> observation fields to hopefully work with the data. I then run
the
> >> following command:
> >>
> >> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
> 20200530_madis2nc.nc
> >> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
-outdir
> >> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
> >>
> >> PointStat then errors indicating that it is having trouble
reading the
> AMV
> >> file. I have attached both the configuration file as well as the
output
> log
> >> to the email. Is there something that I need to do to the AMV
NetCDF
> file
> >> before using PointStat that I can not aware of, or is there a
better
> method
> >> of verification using MET to compare point motion vectors at
various
> >> heights to observational data?
> >>
> >> Thank you for any help that you can provide!
> >>
> >> Josh Boustead
> >>
> >> Meteorologist/Modeler
> >> PEMDAS Technology and Innovation
> >> Norman, OK 73069
> >>
> >>
> >>
> >>
> >> --
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This email message and all attachments
> >> transmitted with it may contain legally privileged and
confidential
> >> information intended solely for the use of the addressee. If the
reader
> of
> >> this message is not the intended recipient, you are hereby
notified that
> >> any reading, dissemination, distribution, copying, or other use
of this
> >> message or its attachments is strictly prohibited. If you have
received
> >> this message in error, please notify the sender immediately and
delete
> >> this
> >> message from your system. Thank you.
> >>
> >>
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
> >
> > My working day may not be your working day. Please do not feel
obliged
> to
> > reply to this email outside of your normal working hours.
>
>
> --
>
>
>
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE: This email message and all attachments
> transmitted with it may contain legally privileged and confidential
> information intended solely for the use of the addressee. If the
reader of
> this message is not the intended recipient, you are hereby notified
that
> any reading, dissemination, distribution, copying, or other use of
this
> message or its attachments is strictly prohibited. If you have
received
> this message in error, please notify the sender immediately and
delete
> this
> message from your system. Thank you.
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Josh Boustead
Time: Wed Jun 03 08:01:55 2020
Good morning Julie,
Thanks for the information and help!
I was looking through the MET user guide and ran across the point to
grid tool that I have not used before, but it mentions taking point
observations from GOES 16/17 and creating a grid. Our AMV output files
are a subset of the GOES 16/17 in the same format. Would I be able to
use that tool to take the u and v components of the wind and create a
grid that I could then use in PointStat? The user guide and example in
the user guide use Aerosol Optical Depth and we are interested in the
wind so maybe it wouldn’t work, but it is something that caught our
eye. We also have the AMVs output into a csv. Along the same lines,
could I use a tool such as ascii2nc to take the information in those
csv files, create a NetCDF file that point2Grid could then use to
create a grid that could be used in PointStat?
Thanks again!
Josh
> On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
<met_help at ucar.edu> wrote:
>
> Hi Josh.
>
> Unfortunately, this NetCDF forecast data is not in a format that MET
can
> read. MET is only able to read certain flavors of NetCDF:
>
> (1) The NetCDF output of the WRF p_interp or wrf_interp utilities
> (2) The NetCDF Climate Forecast (CF) convention
> (
> http://cfconventions.org/Data/cf-conventions/cf-con
<http://cfconventions.org/Data/cf-conventions/cf-con>(ventions-1.7/cf-
conventions.html
> <http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html <http://cfconventions.org/Data/cf-conventions/cf-
conventions-1.7/cf-conventions.html>>
> )
> (3) The NetCDF output of other MET tools, like pcp_combine
>
> Your options are to either (1) reformat this data into a file format
MET
> understands or (2) write a python wrapper script to interpret this
data and
> utilize python embedding. Examples of python embedding can be found
here:
> https://dtcenter.org/community-code/model-evaluation-tools-
met/sample-analysis-scripts <https://dtcenter.org/community-
code/model-evaluation-tools-met/sample-analysis-scripts>
>
> I hope this helps!
>
> Julie
>
> On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
<met_help at ucar.edu <mailto:met_help at ucar.edu>>
> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>
>> Hi Julie,
>>
>> Thanks for the quick rely! I have updated the data as per
instructions
>> from the link in your email.
>>
>> Please let me know if you need anything additional.
>>
>> Thanks again,
>>
>> Josh
>>
>>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
<met_help at ucar.edu>
>> wrote:
>>>
>>> Hi Josh.
>>>
>>> Thank you for all of this information. I see that MET is having
trouble
>>> reading your forecast file. Thank you for attaching your config
file and
>>> your log file. Could you please also send us your forecast file
and your
>>> observation file so that we can take a closer look? You can
follow the
>>> instructions under the "How to Send Us Data" section on the
following
>> page:
>>>
>> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
>> <
>> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk <https://dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk>
>>>
>>>
>>> Julie
>>>
>>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
<met_help at ucar.edu <mailto:met_help at ucar.edu>
>> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
>>> wrote:
>>>
>>>>
>>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
>>>> Transaction: Ticket created by josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com> <mailto:
>> josh.boustead at pemdastech.com <mailto:josh.boustead at pemdastech.com>>
>>>> Queue: met_help
>>>> Subject: Verification of Atmospheric Motion Vectors using
PointStat
>>>> Owner: Nobody
>>>> Requestors: josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com> <mailto:
>> josh.boustead at pemdastech.com <mailto:josh.boustead at pemdastech.com>>
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>>>
>>>>
>>>> Hello,
>>>>
>>>> We generate atmospheric motion vectors (AMVs) using GEOS imagery
and
>> were
>>>> hoping to use PointStat and StatAnalysis to produce some
verification
>>>> metrics on how well the algorithm to produce the AMVs was doing
>> compared to
>>>> RAOB and aircraft observations.
>>>>
>>>> The AMVs that we are generating output the winds in u and v
components
>> in
>>>> m/s as well as the vertical placement in pressure and height and
are in
>>>> NetCDF format. I can provide an example file of the AMVs if it
would be
>>>> helpful. I then obtain MADIS RAOB and aircraft data from NCEP,
and using
>>>> madis2nc convert this data into the format wanted by MET. I
created a
>>>> PointStat configuration file that is edited for the forecast and
>>>> observation fields to hopefully work with the data. I then run
the
>>>> following command:
>>>>
>>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
>> 20200530_madis2nc.nc
>>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
-outdir
>>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
>>>>
>>>> PointStat then errors indicating that it is having trouble
reading the
>> AMV
>>>> file. I have attached both the configuration file as well as the
output
>> log
>>>> to the email. Is there something that I need to do to the AMV
NetCDF
>> file
>>>> before using PointStat that I can not aware of, or is there a
better
>> method
>>>> of verification using MET to compare point motion vectors at
various
>>>> heights to observational data?
>>>>
>>>> Thank you for any help that you can provide!
>>>>
>>>> Josh Boustead
>>>>
>>>> Meteorologist/Modeler
>>>> PEMDAS Technology and Innovation
>>>> Norman, OK 73069
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE: This email message and all attachments
>>>> transmitted with it may contain legally privileged and
confidential
>>>> information intended solely for the use of the addressee. If the
reader
>> of
>>>> this message is not the intended recipient, you are hereby
notified that
>>>> any reading, dissemination, distribution, copying, or other use
of this
>>>> message or its attachments is strictly prohibited. If you have
received
>>>> this message in error, please notify the sender immediately and
delete
>>>> this
>>>> message from your system. Thank you.
>>>>
>>>>
>>>
>>> --
>>> Julie Prestopnik
>>> Software Engineer
>>> National Center for Atmospheric Research
>>> Research Applications Laboratory
>>> Phone: 303.497.8399
>>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
<mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
>>>
>>> My working day may not be your working day. Please do not feel
obliged
>> to
>>> reply to this email outside of your normal working hours.
>>
>>
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email message and all attachments
>> transmitted with it may contain legally privileged and confidential
>> information intended solely for the use of the addressee. If the
reader of
>> this message is not the intended recipient, you are hereby notified
that
>> any reading, dissemination, distribution, copying, or other use of
this
>> message or its attachments is strictly prohibited. If you have
received
>> this message in error, please notify the sender immediately and
delete
>> this
>> message from your system. Thank you.
>>
>>
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
--
CONFIDENTIALITY NOTICE: This email message and all attachments
transmitted with it may contain legally privileged and confidential
information intended solely for the use of the addressee. If the
reader of
this message is not the intended recipient, you are hereby notified
that
any reading, dissemination, distribution, copying, or other use of
this
message or its attachments is strictly prohibited. If you have
received
this message in error, please notify the sender immediately and delete
this
message from your system. Thank you.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Julie Prestopnik
Time: Wed Jun 03 10:04:39 2020
Hi Josh.
I am reassigning this ticket to Howard Soh who should be better able
to
answer your questions after he takes a look at the file that you are
using. Please allow a few business days for a response.
Julie
On Wed, Jun 3, 2020 at 8:01 AM Josh Boustead via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459 >
>
> Good morning Julie,
>
> Thanks for the information and help!
>
> I was looking through the MET user guide and ran across the point to
grid
> tool that I have not used before, but it mentions taking point
observations
> from GOES 16/17 and creating a grid. Our AMV output files are a
subset of
> the GOES 16/17 in the same format. Would I be able to use that tool
to take
> the u and v components of the wind and create a grid that I could
then use
> in PointStat? The user guide and example in the user guide use
Aerosol
> Optical Depth and we are interested in the wind so maybe it wouldn’t
work,
> but it is something that caught our eye. We also have the AMVs
output into
> a csv. Along the same lines, could I use a tool such as ascii2nc to
take
> the information in those csv files, create a NetCDF file that
point2Grid
> could then use to create a grid that could be used in PointStat?
>
> Thanks again!
>
> Josh
>
> > On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
> >
> > Hi Josh.
> >
> > Unfortunately, this NetCDF forecast data is not in a format that
MET can
> > read. MET is only able to read certain flavors of NetCDF:
> >
> > (1) The NetCDF output of the WRF p_interp or wrf_interp utilities
> > (2) The NetCDF Climate Forecast (CF) convention
> > (
> > http://cfconventions.org/Data/cf-conventions/cf-con <
> http://cfconventions.org/Data/cf-conventions/cf-con
> >(ventions-1.7/cf-conventions.html
> > <
> http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html
> <
> http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html
> >>
> > )
> > (3) The NetCDF output of other MET tools, like pcp_combine
> >
> > Your options are to either (1) reformat this data into a file
format MET
> > understands or (2) write a python wrapper script to interpret this
data
> and
> > utilize python embedding. Examples of python embedding can be
found
> here:
> >
> https://dtcenter.org/community-code/model-evaluation-tools-
met/sample-analysis-scripts
> <
> https://dtcenter.org/community-code/model-evaluation-tools-
met/sample-analysis-scripts
> >
> >
> > I hope this helps!
> >
> > Julie
> >
> > On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
<met_help at ucar.edu
> <mailto:met_help at ucar.edu>>
> > wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> >>
> >> Hi Julie,
> >>
> >> Thanks for the quick rely! I have updated the data as per
instructions
> >> from the link in your email.
> >>
> >> Please let me know if you need anything additional.
> >>
> >> Thanks again,
> >>
> >> Josh
> >>
> >>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> >> wrote:
> >>>
> >>> Hi Josh.
> >>>
> >>> Thank you for all of this information. I see that MET is having
> trouble
> >>> reading your forecast file. Thank you for attaching your config
file
> and
> >>> your log file. Could you please also send us your forecast file
and
> your
> >>> observation file so that we can take a closer look? You can
follow the
> >>> instructions under the "How to Send Us Data" section on the
following
> >> page:
> >>>
> >>
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> >> <
> >>
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> <
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> >
> >>>
> >>>
> >>> Julie
> >>>
> >>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
<met_help at ucar.edu
> <mailto:met_help at ucar.edu>
> >> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
> >>> wrote:
> >>>
> >>>>
> >>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> >>>> Transaction: Ticket created by josh.boustead at pemdastech.com
<mailto:
> josh.boustead at pemdastech.com> <mailto:
> >> josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>>
> >>>> Queue: met_help
> >>>> Subject: Verification of Atmospheric Motion Vectors using
PointStat
> >>>> Owner: Nobody
> >>>> Requestors: josh.boustead at pemdastech.com <mailto:
> josh.boustead at pemdastech.com> <mailto:
> >> josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>>
> >>>> Status: new
> >>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> >>>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> We generate atmospheric motion vectors (AMVs) using GEOS
imagery and
> >> were
> >>>> hoping to use PointStat and StatAnalysis to produce some
verification
> >>>> metrics on how well the algorithm to produce the AMVs was doing
> >> compared to
> >>>> RAOB and aircraft observations.
> >>>>
> >>>> The AMVs that we are generating output the winds in u and v
components
> >> in
> >>>> m/s as well as the vertical placement in pressure and height
and are
> in
> >>>> NetCDF format. I can provide an example file of the AMVs if it
would
> be
> >>>> helpful. I then obtain MADIS RAOB and aircraft data from NCEP,
and
> using
> >>>> madis2nc convert this data into the format wanted by MET. I
created a
> >>>> PointStat configuration file that is edited for the forecast
and
> >>>> observation fields to hopefully work with the data. I then run
the
> >>>> following command:
> >>>>
> >>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
> >> 20200530_madis2nc.nc
> >>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
-outdir
> >>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
> >>>>
> >>>> PointStat then errors indicating that it is having trouble
reading the
> >> AMV
> >>>> file. I have attached both the configuration file as well as
the
> output
> >> log
> >>>> to the email. Is there something that I need to do to the AMV
NetCDF
> >> file
> >>>> before using PointStat that I can not aware of, or is there a
better
> >> method
> >>>> of verification using MET to compare point motion vectors at
various
> >>>> heights to observational data?
> >>>>
> >>>> Thank you for any help that you can provide!
> >>>>
> >>>> Josh Boustead
> >>>>
> >>>> Meteorologist/Modeler
> >>>> PEMDAS Technology and Innovation
> >>>> Norman, OK 73069
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> CONFIDENTIALITY NOTICE: This email message and all attachments
> >>>> transmitted with it may contain legally privileged and
confidential
> >>>> information intended solely for the use of the addressee. If
the
> reader
> >> of
> >>>> this message is not the intended recipient, you are hereby
notified
> that
> >>>> any reading, dissemination, distribution, copying, or other use
of
> this
> >>>> message or its attachments is strictly prohibited. If you have
> received
> >>>> this message in error, please notify the sender immediately and
delete
> >>>> this
> >>>> message from your system. Thank you.
> >>>>
> >>>>
> >>>
> >>> --
> >>> Julie Prestopnik
> >>> Software Engineer
> >>> National Center for Atmospheric Research
> >>> Research Applications Laboratory
> >>> Phone: 303.497.8399
> >>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu> <mailto:
> jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
> >>>
> >>> My working day may not be your working day. Please do not feel
obliged
> >> to
> >>> reply to this email outside of your normal working hours.
> >>
> >>
> >> --
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This email message and all attachments
> >> transmitted with it may contain legally privileged and
confidential
> >> information intended solely for the use of the addressee. If the
reader
> of
> >> this message is not the intended recipient, you are hereby
notified that
> >> any reading, dissemination, distribution, copying, or other use
of this
> >> message or its attachments is strictly prohibited. If you have
received
> >> this message in error, please notify the sender immediately and
delete
> >> this
> >> message from your system. Thank you.
> >>
> >>
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
obliged
> to
> > reply to this email outside of your normal working hours.
>
>
> --
>
>
>
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE: This email message and all attachments
> transmitted with it may contain legally privileged and confidential
> information intended solely for the use of the addressee. If the
reader of
> this message is not the intended recipient, you are hereby notified
that
> any reading, dissemination, distribution, copying, or other use of
this
> message or its attachments is strictly prohibited. If you have
received
> this message in error, please notify the sender immediately and
delete
> this
> message from your system. Thank you.
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Howard Soh
Time: Wed Jun 03 13:43:23 2020
You can use ascii2nc. There is workaround by modifying the AMV data
file.
point2grid supports GOES 16/17 dataset. GOES 16/17 does not have
lat/lon variables. They are computed but point2grid can read lat/lon
from the NetCDF in order to save the computing time. The AMV data file
is not supported by point2grid as is because of missing information
(meta data).
Workaround:
Step 1. Generating CF-complaints NetCDF file with lat/lon variables
- nccopy -V lat,lon amv_abi-goes16_B14BT_YU_20200530T1200Z.nc amv_abi-
goes16_lat_lon.nc
- ncrename -v lat,latitude -v lon,longitude amv_abi-goes16_lat_lon.nc
- ncatted -a Conventions,global,a,c,"CF-1.6" amv_abi-goes16_lat_lon.nc
- ncatted -a long_name,latitude,a,c,latitude amv_abi-goes16_lat_lon.nc
- ncatted -a units,latitude,a,c,degrees_south amv_abi-
goes16_lat_lon.nc
- ncatted -a units,longitude,a,c,degrees_west amv_abi-
goes16_lat_lon.nc
- ncatted -a long_name,longitude,a,c,longitude amv_abi-
goes16_lat_lon.nc
note: make sure the units are correct (degrees_south or degrees_north)
Step 2. Set environment variable to set the NetCDF file with lat/lon
- export MET_GEOSTATIONARY_DATA=amv_abi-goes16_lat_lon.nc
or
- setenv MET_GEOSTATIONARY_DATA amv_abi-goes16_lat_lon.nc
Step 3. Add metadata (two global attributes) into AMV file
+ ncatted -a scene_id,global,a,c,Mesoscale amv_abi-
goes16_B14BT_YU_20200530T1200Z.nc
+ ncatted -a Projection,global,a,c,LatLon amv_abi-
goes16_B14BT_YU_20200530T1200Z.nc
Step 4. Added NetCDF type ("file_type=NETCDF_MET;") into the "-field"
command line option
+ ./point2grid amv_abi-goes16_B14BT_YU_20200530T1200Z.nc G212
output.nc -field 'name="pressure"; level="(*,*)";
file_type=NETCDF_MET;' -v 4
Cheers,
Howard
Step 2.
On Wed Jun 03 08:01:55 2020, josh.boustead at pemdastech.com wrote:
> Good morning Julie,
>
> Thanks for the information and help!
>
> I was looking through the MET user guide and ran across the point to
> grid tool that I have not used before, but it mentions taking point
> observations from GOES 16/17 and creating a grid. Our AMV output
files
> are a subset of the GOES 16/17 in the same format. Would I be able
to
> use that tool to take the u and v components of the wind and create
a
> grid that I could then use in PointStat? The user guide and example
in
> the user guide use Aerosol Optical Depth and we are interested in
the
> wind so maybe it wouldn’t work, but it is something that caught our
> eye. We also have the AMVs output into a csv. Along the same lines,
> could I use a tool such as ascii2nc to take the information in those
> csv files, create a NetCDF file that point2Grid could then use to
> create a grid that could be used in PointStat?
>
> Thanks again!
>
> Josh
>
> > On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
> > <met_help at ucar.edu> wrote:
> >
> > Hi Josh.
> >
> > Unfortunately, this NetCDF forecast data is not in a format that
MET
> > can
> > read. MET is only able to read certain flavors of NetCDF:
> >
> > (1) The NetCDF output of the WRF p_interp or wrf_interp utilities
> > (2) The NetCDF Climate Forecast (CF) convention
> > (
> > http://cfconventions.org/Data/cf-conventions/cf-con
> > <http://cfconventions.org/Data/cf-conventions/cf-con>(ventions-
> > 1.7/cf-conventions.html
> > <http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.7/cf-
> > conventions.html <http://cfconventions.org/Data/cf-conventions/cf-
> > conventions-1.7/cf-conventions.html>>
> > )
> > (3) The NetCDF output of other MET tools, like pcp_combine
> >
> > Your options are to either (1) reformat this data into a file
format
> > MET
> > understands or (2) write a python wrapper script to interpret this
> > data and
> > utilize python embedding. Examples of python embedding can be
found
> > here:
> > https://dtcenter.org/community-code/model-evaluation-tools-
> > met/sample-analysis-scripts <https://dtcenter.org/community-
> > code/model-evaluation-tools-met/sample-analysis-scripts>
> >
> > I hope this helps!
> >
> > Julie
> >
> > On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
> > <met_help at ucar.edu <mailto:met_help at ucar.edu>>
> > wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> >> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> >>
> >> Hi Julie,
> >>
> >> Thanks for the quick rely! I have updated the data as per
> >> instructions
> >> from the link in your email.
> >>
> >> Please let me know if you need anything additional.
> >>
> >> Thanks again,
> >>
> >> Josh
> >>
> >>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
> >>> <met_help at ucar.edu>
> >> wrote:
> >>>
> >>> Hi Josh.
> >>>
> >>> Thank you for all of this information. I see that MET is having
> >>> trouble
> >>> reading your forecast file. Thank you for attaching your config
> >>> file and
> >>> your log file. Could you please also send us your forecast file
> >>> and your
> >>> observation file so that we can take a closer look? You can
follow
> >>> the
> >>> instructions under the "How to Send Us Data" section on the
> >>> following
> >> page:
> >>>
> >> https://dtcenter.org/community-code/model-evaluation-tools-
met/met-
> >> help-desk
> >> <
> >> https://dtcenter.org/community-code/model-evaluation-tools-
met/met-
> >> help-desk <https://dtcenter.org/community-code/model-evaluation-
> >> tools-met/met-help-desk>
> >>>
> >>>
> >>> Julie
> >>>
> >>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
> >>> <met_help at ucar.edu <mailto:met_help at ucar.edu>
> >> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
> >>> wrote:
> >>>
> >>>>
> >>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> >>>> Transaction: Ticket created by josh.boustead at pemdastech.com
> >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> >> josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>>
> >>>> Queue: met_help
> >>>> Subject: Verification of Atmospheric Motion Vectors using
> >>>> PointStat
> >>>> Owner: Nobody
> >>>> Requestors: josh.boustead at pemdastech.com
> >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> >> josh.boustead at pemdastech.com
<mailto:josh.boustead at pemdastech.com>>
> >>>> Status: new
> >>>> Ticket <URL:
> >>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> >>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> >>>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> We generate atmospheric motion vectors (AMVs) using GEOS
imagery
> >>>> and
> >> were
> >>>> hoping to use PointStat and StatAnalysis to produce some
> >>>> verification
> >>>> metrics on how well the algorithm to produce the AMVs was doing
> >> compared to
> >>>> RAOB and aircraft observations.
> >>>>
> >>>> The AMVs that we are generating output the winds in u and v
> >>>> components
> >> in
> >>>> m/s as well as the vertical placement in pressure and height
and
> >>>> are in
> >>>> NetCDF format. I can provide an example file of the AMVs if it
> >>>> would be
> >>>> helpful. I then obtain MADIS RAOB and aircraft data from NCEP,
and
> >>>> using
> >>>> madis2nc convert this data into the format wanted by MET. I
> >>>> created a
> >>>> PointStat configuration file that is edited for the forecast
and
> >>>> observation fields to hopefully work with the data. I then run
the
> >>>> following command:
> >>>>
> >>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
> >> 20200530_madis2nc.nc
> >>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
> >>>> -outdir
> >>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
> >>>>
> >>>> PointStat then errors indicating that it is having trouble
reading
> >>>> the
> >> AMV
> >>>> file. I have attached both the configuration file as well as
the
> >>>> output
> >> log
> >>>> to the email. Is there something that I need to do to the AMV
> >>>> NetCDF
> >> file
> >>>> before using PointStat that I can not aware of, or is there a
> >>>> better
> >> method
> >>>> of verification using MET to compare point motion vectors at
> >>>> various
> >>>> heights to observational data?
> >>>>
> >>>> Thank you for any help that you can provide!
> >>>>
> >>>> Josh Boustead
> >>>>
> >>>> Meteorologist/Modeler
> >>>> PEMDAS Technology and Innovation
> >>>> Norman, OK 73069
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> CONFIDENTIALITY NOTICE: This email message and all attachments
> >>>> transmitted with it may contain legally privileged and
> >>>> confidential
> >>>> information intended solely for the use of the addressee. If
the
> >>>> reader
> >> of
> >>>> this message is not the intended recipient, you are hereby
> >>>> notified that
> >>>> any reading, dissemination, distribution, copying, or other use
of
> >>>> this
> >>>> message or its attachments is strictly prohibited. If you have
> >>>> received
> >>>> this message in error, please notify the sender immediately and
> >>>> delete
> >>>> this
> >>>> message from your system. Thank you.
> >>>>
> >>>>
> >>>
> >>> --
> >>> Julie Prestopnik
> >>> Software Engineer
> >>> National Center for Atmospheric Research
> >>> Research Applications Laboratory
> >>> Phone: 303.497.8399
> >>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
> >>> <mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
> >>>
> >>> My working day may not be your working day. Please do not feel
> >>> obliged
> >> to
> >>> reply to this email outside of your normal working hours.
> >>
> >>
> >> --
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This email message and all attachments
> >> transmitted with it may contain legally privileged and
confidential
> >> information intended solely for the use of the addressee. If the
> >> reader of
> >> this message is not the intended recipient, you are hereby
notified
> >> that
> >> any reading, dissemination, distribution, copying, or other use
of
> >> this
> >> message or its attachments is strictly prohibited. If you have
> >> received
> >> this message in error, please notify the sender immediately and
> >> delete
> >> this
> >> message from your system. Thank you.
> >>
> >>
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
> > obliged to
> > reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Howard Soh
Time: Wed Jun 03 13:56:53 2020
Add one more global attribute into AMV file:
+ ncatted -a MET_version,global,a,c,V9.1 amv_abi-
goes16_B14BT_YU_20200530T1200Z.nc
note: Change "V9.1" to the matching MET version you are using
Cheers,
Howard
On Wed Jun 03 13:43:23 2020, hsoh wrote:
> You can use ascii2nc. There is workaround by modifying the AMV data
> file.
>
> point2grid supports GOES 16/17 dataset. GOES 16/17 does not have
> lat/lon variables. They are computed but point2grid can read lat/lon
> from the NetCDF in order to save the computing time. The AMV data
file
> is not supported by point2grid as is because of missing information
> (meta data).
>
> Workaround:
>
> Step 1. Generating CF-complaints NetCDF file with lat/lon variables
>
> - nccopy -V lat,lon amv_abi-goes16_B14BT_YU_20200530T1200Z.nc
amv_abi-
> goes16_lat_lon.nc
> - ncrename -v lat,latitude -v lon,longitude amv_abi-
goes16_lat_lon.nc
> - ncatted -a Conventions,global,a,c,"CF-1.6" amv_abi-
goes16_lat_lon.nc
> - ncatted -a long_name,latitude,a,c,latitude amv_abi-
goes16_lat_lon.nc
> - ncatted -a units,latitude,a,c,degrees_south amv_abi-
> goes16_lat_lon.nc
> - ncatted -a units,longitude,a,c,degrees_west amv_abi-
> goes16_lat_lon.nc
> - ncatted -a long_name,longitude,a,c,longitude amv_abi-
> goes16_lat_lon.nc
>
> note: make sure the units are correct (degrees_south or
degrees_north)
>
> Step 2. Set environment variable to set the NetCDF file with lat/lon
>
> - export MET_GEOSTATIONARY_DATA=amv_abi-goes16_lat_lon.nc
> or
> - setenv MET_GEOSTATIONARY_DATA amv_abi-goes16_lat_lon.nc
>
> Step 3. Add metadata (two global attributes) into AMV file
>
> + ncatted -a scene_id,global,a,c,Mesoscale amv_abi-
> goes16_B14BT_YU_20200530T1200Z.nc
> + ncatted -a Projection,global,a,c,LatLon amv_abi-
> goes16_B14BT_YU_20200530T1200Z.nc
>
> Step 4. Added NetCDF type ("file_type=NETCDF_MET;") into the "-
field"
> command line option
>
> + ./point2grid amv_abi-goes16_B14BT_YU_20200530T1200Z.nc G212
> output.nc -field 'name="pressure"; level="(*,*)";
> file_type=NETCDF_MET;' -v 4
>
> Cheers,
> Howard
>
>
>
>
> Step 2.
>
>
> On Wed Jun 03 08:01:55 2020, josh.boustead at pemdastech.com wrote:
> > Good morning Julie,
> >
> > Thanks for the information and help!
> >
> > I was looking through the MET user guide and ran across the point
to
> > grid tool that I have not used before, but it mentions taking
point
> > observations from GOES 16/17 and creating a grid. Our AMV output
> > files
> > are a subset of the GOES 16/17 in the same format. Would I be able
to
> > use that tool to take the u and v components of the wind and
create a
> > grid that I could then use in PointStat? The user guide and
example
> > in
> > the user guide use Aerosol Optical Depth and we are interested in
the
> > wind so maybe it wouldn’t work, but it is something that caught
our
> > eye. We also have the AMVs output into a csv. Along the same
lines,
> > could I use a tool such as ascii2nc to take the information in
those
> > csv files, create a NetCDF file that point2Grid could then use to
> > create a grid that could be used in PointStat?
> >
> > Thanks again!
> >
> > Josh
> >
> > > On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
> > > <met_help at ucar.edu> wrote:
> > >
> > > Hi Josh.
> > >
> > > Unfortunately, this NetCDF forecast data is not in a format that
> > > MET
> > > can
> > > read. MET is only able to read certain flavors of NetCDF:
> > >
> > > (1) The NetCDF output of the WRF p_interp or wrf_interp
utilities
> > > (2) The NetCDF Climate Forecast (CF) convention
> > > (
> > > http://cfconventions.org/Data/cf-conventions/cf-con
> > > <http://cfconventions.org/Data/cf-conventions/cf-con>(ventions-
> > > 1.7/cf-conventions.html
> > > <http://cfconventions.org/Data/cf-conventions/cf-conventions-
> > > 1.7/cf-
> > > conventions.html <http://cfconventions.org/Data/cf-
conventions/cf-
> > > conventions-1.7/cf-conventions.html>>
> > > )
> > > (3) The NetCDF output of other MET tools, like pcp_combine
> > >
> > > Your options are to either (1) reformat this data into a file
> > > format
> > > MET
> > > understands or (2) write a python wrapper script to interpret
this
> > > data and
> > > utilize python embedding. Examples of python embedding can be
> > > found
> > > here:
> > > https://dtcenter.org/community-code/model-evaluation-tools-
> > > met/sample-analysis-scripts <https://dtcenter.org/community-
> > > code/model-evaluation-tools-met/sample-analysis-scripts>
> > >
> > > I hope this helps!
> > >
> > > Julie
> > >
> > > On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
> > > <met_help at ucar.edu <mailto:met_help at ucar.edu>>
> > > wrote:
> > >
> > >>
> > >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> > >> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> > >>
> > >> Hi Julie,
> > >>
> > >> Thanks for the quick rely! I have updated the data as per
> > >> instructions
> > >> from the link in your email.
> > >>
> > >> Please let me know if you need anything additional.
> > >>
> > >> Thanks again,
> > >>
> > >> Josh
> > >>
> > >>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
> > >>> <met_help at ucar.edu>
> > >> wrote:
> > >>>
> > >>> Hi Josh.
> > >>>
> > >>> Thank you for all of this information. I see that MET is
having
> > >>> trouble
> > >>> reading your forecast file. Thank you for attaching your
config
> > >>> file and
> > >>> your log file. Could you please also send us your forecast
file
> > >>> and your
> > >>> observation file so that we can take a closer look? You can
> > >>> follow
> > >>> the
> > >>> instructions under the "How to Send Us Data" section on the
> > >>> following
> > >> page:
> > >>>
> > >> https://dtcenter.org/community-code/model-evaluation-tools-
> > >> met/met-
> > >> help-desk
> > >> <
> > >> https://dtcenter.org/community-code/model-evaluation-tools-
> > >> met/met-
> > >> help-desk <https://dtcenter.org/community-code/model-
evaluation-
> > >> tools-met/met-help-desk>
> > >>>
> > >>>
> > >>> Julie
> > >>>
> > >>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
> > >>> <met_help at ucar.edu <mailto:met_help at ucar.edu>
> > >> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
> > >>> wrote:
> > >>>
> > >>>>
> > >>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> > >>>> Transaction: Ticket created by josh.boustead at pemdastech.com
> > >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> > >> josh.boustead at pemdastech.com
> > >> <mailto:josh.boustead at pemdastech.com>>
> > >>>> Queue: met_help
> > >>>> Subject: Verification of Atmospheric Motion Vectors using
> > >>>> PointStat
> > >>>> Owner: Nobody
> > >>>> Requestors: josh.boustead at pemdastech.com
> > >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> > >> josh.boustead at pemdastech.com
> > >> <mailto:josh.boustead at pemdastech.com>>
> > >>>> Status: new
> > >>>> Ticket <URL:
> > >>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> > >>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> > >>>>
> > >>>>
> > >>>> Hello,
> > >>>>
> > >>>> We generate atmospheric motion vectors (AMVs) using GEOS
imagery
> > >>>> and
> > >> were
> > >>>> hoping to use PointStat and StatAnalysis to produce some
> > >>>> verification
> > >>>> metrics on how well the algorithm to produce the AMVs was
doing
> > >> compared to
> > >>>> RAOB and aircraft observations.
> > >>>>
> > >>>> The AMVs that we are generating output the winds in u and v
> > >>>> components
> > >> in
> > >>>> m/s as well as the vertical placement in pressure and height
and
> > >>>> are in
> > >>>> NetCDF format. I can provide an example file of the AMVs if
it
> > >>>> would be
> > >>>> helpful. I then obtain MADIS RAOB and aircraft data from
NCEP,
> > >>>> and
> > >>>> using
> > >>>> madis2nc convert this data into the format wanted by MET. I
> > >>>> created a
> > >>>> PointStat configuration file that is edited for the forecast
and
> > >>>> observation fields to hopefully work with the data. I then
run
> > >>>> the
> > >>>> following command:
> > >>>>
> > >>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
> > >> 20200530_madis2nc.nc
> > >>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
> > >>>> -outdir
> > >>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
> > >>>>
> > >>>> PointStat then errors indicating that it is having trouble
> > >>>> reading
> > >>>> the
> > >> AMV
> > >>>> file. I have attached both the configuration file as well as
the
> > >>>> output
> > >> log
> > >>>> to the email. Is there something that I need to do to the AMV
> > >>>> NetCDF
> > >> file
> > >>>> before using PointStat that I can not aware of, or is there a
> > >>>> better
> > >> method
> > >>>> of verification using MET to compare point motion vectors at
> > >>>> various
> > >>>> heights to observational data?
> > >>>>
> > >>>> Thank you for any help that you can provide!
> > >>>>
> > >>>> Josh Boustead
> > >>>>
> > >>>> Meteorologist/Modeler
> > >>>> PEMDAS Technology and Innovation
> > >>>> Norman, OK 73069
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> CONFIDENTIALITY NOTICE: This email message and all
attachments
> > >>>> transmitted with it may contain legally privileged and
> > >>>> confidential
> > >>>> information intended solely for the use of the addressee. If
the
> > >>>> reader
> > >> of
> > >>>> this message is not the intended recipient, you are hereby
> > >>>> notified that
> > >>>> any reading, dissemination, distribution, copying, or other
use
> > >>>> of
> > >>>> this
> > >>>> message or its attachments is strictly prohibited. If you
have
> > >>>> received
> > >>>> this message in error, please notify the sender immediately
and
> > >>>> delete
> > >>>> this
> > >>>> message from your system. Thank you.
> > >>>>
> > >>>>
> > >>>
> > >>> --
> > >>> Julie Prestopnik
> > >>> Software Engineer
> > >>> National Center for Atmospheric Research
> > >>> Research Applications Laboratory
> > >>> Phone: 303.497.8399
> > >>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
> > >>> <mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
> > >>>
> > >>> My working day may not be your working day. Please do not
feel
> > >>> obliged
> > >> to
> > >>> reply to this email outside of your normal working hours.
> > >>
> > >>
> > >> --
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> CONFIDENTIALITY NOTICE: This email message and all attachments
> > >> transmitted with it may contain legally privileged and
> > >> confidential
> > >> information intended solely for the use of the addressee. If
the
> > >> reader of
> > >> this message is not the intended recipient, you are hereby
> > >> notified
> > >> that
> > >> any reading, dissemination, distribution, copying, or other use
of
> > >> this
> > >> message or its attachments is strictly prohibited. If you have
> > >> received
> > >> this message in error, please notify the sender immediately and
> > >> delete
> > >> this
> > >> message from your system. Thank you.
> > >>
> > >>
> > >
> > > --
> > > Julie Prestopnik
> > > Software Engineer
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > Phone: 303.497.8399
> > > Email: jpresto at ucar.edu
> > >
> > > My working day may not be your working day. Please do not feel
> > > obliged to
> > > reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Josh Boustead
Time: Thu Jun 04 22:20:41 2020
Hello Howard,
Thank you so much for the help with the point2grid. I followed what
you did below and it appeared to work. It did generate a gridded
NetCDF file that I was able to use with PointStat. Looking at the
output from in the NetCDF for the u and v of the wind I noticed some
significant differences than what was in the original AMV NetCDF file.
I have attached the output from the point2grid took to this email. I
was wondering if you received similar values, and if you did, do you
have any theory of why the values in the gridded file is so different
than the original non CF-compliant AMV file? In your email below it
appears you processed pressure so I don’t know if you looked at the u
and v in the original AMV file or not (u_ms and v_ms), but if you
didn’t would you mind seeing if you come up with the large values for
these fields as I am?
Thanks again for all your help!
Josh
--
CONFIDENTIALITY NOTICE: This email message and all attachments
transmitted with it may contain legally privileged and confidential
information intended solely for the use of the addressee. If the
reader of
this message is not the intended recipient, you are hereby notified
that
any reading, dissemination, distribution, copying, or other use of
this
message or its attachments is strictly prohibited. If you have
received
this message in error, please notify the sender immediately and delete
this
message from your system. Thank you.
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Josh Boustead
Time: Thu Jun 04 22:20:41 2020
> On Jun 3, 2020, at 2:56 PM, Howard Soh via RT <met_help at ucar.edu>
wrote:
>
> Add one more global attribute into AMV file:
>
> + ncatted -a MET_version,global,a,c,V9.1 amv_abi-
goes16_B14BT_YU_20200530T1200Z.nc
>
> note: Change "V9.1" to the matching MET version you are using
>
> Cheers,
> Howard
>
> On Wed Jun 03 13:43:23 2020, hsoh wrote:
>> You can use ascii2nc. There is workaround by modifying the AMV data
>> file.
>>
>> point2grid supports GOES 16/17 dataset. GOES 16/17 does not have
>> lat/lon variables. They are computed but point2grid can read
lat/lon
>> from the NetCDF in order to save the computing time. The AMV data
file
>> is not supported by point2grid as is because of missing information
>> (meta data).
>>
>> Workaround:
>>
>> Step 1. Generating CF-complaints NetCDF file with lat/lon variables
>>
>> - nccopy -V lat,lon amv_abi-goes16_B14BT_YU_20200530T1200Z.nc
amv_abi-
>> goes16_lat_lon.nc
>> - ncrename -v lat,latitude -v lon,longitude amv_abi-
goes16_lat_lon.nc
>> - ncatted -a Conventions,global,a,c,"CF-1.6" amv_abi-
goes16_lat_lon.nc
>> - ncatted -a long_name,latitude,a,c,latitude amv_abi-
goes16_lat_lon.nc
>> - ncatted -a units,latitude,a,c,degrees_south amv_abi-
>> goes16_lat_lon.nc
>> - ncatted -a units,longitude,a,c,degrees_west amv_abi-
>> goes16_lat_lon.nc
>> - ncatted -a long_name,longitude,a,c,longitude amv_abi-
>> goes16_lat_lon.nc
>>
>> note: make sure the units are correct (degrees_south or
degrees_north)
>>
>> Step 2. Set environment variable to set the NetCDF file with
lat/lon
>>
>> - export MET_GEOSTATIONARY_DATA=amv_abi-goes16_lat_lon.nc
>> or
>> - setenv MET_GEOSTATIONARY_DATA amv_abi-goes16_lat_lon.nc
>>
>> Step 3. Add metadata (two global attributes) into AMV file
>>
>> + ncatted -a scene_id,global,a,c,Mesoscale amv_abi-
>> goes16_B14BT_YU_20200530T1200Z.nc
>> + ncatted -a Projection,global,a,c,LatLon amv_abi-
>> goes16_B14BT_YU_20200530T1200Z.nc
>>
>> Step 4. Added NetCDF type ("file_type=NETCDF_MET;") into the "-
field"
>> command line option
>>
>> + ./point2grid amv_abi-goes16_B14BT_YU_20200530T1200Z.nc G212
>> output.nc -field 'name="pressure"; level="(*,*)";
>> file_type=NETCDF_MET;' -v 4
>>
>> Cheers,
>> Howard
>>
>>
>>
>>
>> Step 2.
>>
>>
>> On Wed Jun 03 08:01:55 2020, josh.boustead at pemdastech.com wrote:
>>> Good morning Julie,
>>>
>>> Thanks for the information and help!
>>>
>>> I was looking through the MET user guide and ran across the point
to
>>> grid tool that I have not used before, but it mentions taking
point
>>> observations from GOES 16/17 and creating a grid. Our AMV output
>>> files
>>> are a subset of the GOES 16/17 in the same format. Would I be able
to
>>> use that tool to take the u and v components of the wind and
create a
>>> grid that I could then use in PointStat? The user guide and
example
>>> in
>>> the user guide use Aerosol Optical Depth and we are interested in
the
>>> wind so maybe it wouldn’t work, but it is something that caught
our
>>> eye. We also have the AMVs output into a csv. Along the same
lines,
>>> could I use a tool such as ascii2nc to take the information in
those
>>> csv files, create a NetCDF file that point2Grid could then use to
>>> create a grid that could be used in PointStat?
>>>
>>> Thanks again!
>>>
>>> Josh
>>>
>>>> On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
>>>> <met_help at ucar.edu> wrote:
>>>>
>>>> Hi Josh.
>>>>
>>>> Unfortunately, this NetCDF forecast data is not in a format that
>>>> MET
>>>> can
>>>> read. MET is only able to read certain flavors of NetCDF:
>>>>
>>>> (1) The NetCDF output of the WRF p_interp or wrf_interp utilities
>>>> (2) The NetCDF Climate Forecast (CF) convention
>>>> (
>>>> http://cfconventions.org/Data/cf-conventions/cf-con
>>>> <http://cfconventions.org/Data/cf-conventions/cf-con>(ventions-
>>>> 1.7/cf-conventions.html
>>>> <http://cfconventions.org/Data/cf-conventions/cf-conventions-
>>>> 1.7/cf-
>>>> conventions.html <http://cfconventions.org/Data/cf-
conventions/cf-
>>>> conventions-1.7/cf-conventions.html>>
>>>> )
>>>> (3) The NetCDF output of other MET tools, like pcp_combine
>>>>
>>>> Your options are to either (1) reformat this data into a file
>>>> format
>>>> MET
>>>> understands or (2) write a python wrapper script to interpret
this
>>>> data and
>>>> utilize python embedding. Examples of python embedding can be
>>>> found
>>>> here:
>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>> met/sample-analysis-scripts <https://dtcenter.org/community-
>>>> code/model-evaluation-tools-met/sample-analysis-scripts>
>>>>
>>>> I hope this helps!
>>>>
>>>> Julie
>>>>
>>>> On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
>>>> <met_help at ucar.edu <mailto:met_help at ucar.edu>>
>>>> wrote:
>>>>
>>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
>>>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>>>>
>>>>> Hi Julie,
>>>>>
>>>>> Thanks for the quick rely! I have updated the data as per
>>>>> instructions
>>>>> from the link in your email.
>>>>>
>>>>> Please let me know if you need anything additional.
>>>>>
>>>>> Thanks again,
>>>>>
>>>>> Josh
>>>>>
>>>>>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
>>>>>> <met_help at ucar.edu>
>>>>> wrote:
>>>>>>
>>>>>> Hi Josh.
>>>>>>
>>>>>> Thank you for all of this information. I see that MET is
having
>>>>>> trouble
>>>>>> reading your forecast file. Thank you for attaching your
config
>>>>>> file and
>>>>>> your log file. Could you please also send us your forecast
file
>>>>>> and your
>>>>>> observation file so that we can take a closer look? You can
>>>>>> follow
>>>>>> the
>>>>>> instructions under the "How to Send Us Data" section on the
>>>>>> following
>>>>> page:
>>>>>>
>>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>>> met/met-
>>>>> help-desk
>>>>> <
>>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>>> met/met-
>>>>> help-desk <https://dtcenter.org/community-code/model-evaluation-
>>>>> tools-met/met-help-desk>
>>>>>>
>>>>>>
>>>>>> Julie
>>>>>>
>>>>>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
>>>>>> <met_help at ucar.edu <mailto:met_help at ucar.edu>
>>>>> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
>>>>>>> Transaction: Ticket created by josh.boustead at pemdastech.com
>>>>>>> <mailto:josh.boustead at pemdastech.com> <mailto:
>>>>> josh.boustead at pemdastech.com
>>>>> <mailto:josh.boustead at pemdastech.com>>
>>>>>>> Queue: met_help
>>>>>>> Subject: Verification of Atmospheric Motion Vectors using
>>>>>>> PointStat
>>>>>>> Owner: Nobody
>>>>>>> Requestors: josh.boustead at pemdastech.com
>>>>>>> <mailto:josh.boustead at pemdastech.com> <mailto:
>>>>> josh.boustead at pemdastech.com
>>>>> <mailto:josh.boustead at pemdastech.com>>
>>>>>>> Status: new
>>>>>>> Ticket <URL:
>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
>>>>>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> We generate atmospheric motion vectors (AMVs) using GEOS
imagery
>>>>>>> and
>>>>> were
>>>>>>> hoping to use PointStat and StatAnalysis to produce some
>>>>>>> verification
>>>>>>> metrics on how well the algorithm to produce the AMVs was
doing
>>>>> compared to
>>>>>>> RAOB and aircraft observations.
>>>>>>>
>>>>>>> The AMVs that we are generating output the winds in u and v
>>>>>>> components
>>>>> in
>>>>>>> m/s as well as the vertical placement in pressure and height
and
>>>>>>> are in
>>>>>>> NetCDF format. I can provide an example file of the AMVs if it
>>>>>>> would be
>>>>>>> helpful. I then obtain MADIS RAOB and aircraft data from NCEP,
>>>>>>> and
>>>>>>> using
>>>>>>> madis2nc convert this data into the format wanted by MET. I
>>>>>>> created a
>>>>>>> PointStat configuration file that is edited for the forecast
and
>>>>>>> observation fields to hopefully work with the data. I then run
>>>>>>> the
>>>>>>> following command:
>>>>>>>
>>>>>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
>>>>> 20200530_madis2nc.nc
>>>>>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
>>>>>>> -outdir
>>>>>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
>>>>>>>
>>>>>>> PointStat then errors indicating that it is having trouble
>>>>>>> reading
>>>>>>> the
>>>>> AMV
>>>>>>> file. I have attached both the configuration file as well as
the
>>>>>>> output
>>>>> log
>>>>>>> to the email. Is there something that I need to do to the AMV
>>>>>>> NetCDF
>>>>> file
>>>>>>> before using PointStat that I can not aware of, or is there a
>>>>>>> better
>>>>> method
>>>>>>> of verification using MET to compare point motion vectors at
>>>>>>> various
>>>>>>> heights to observational data?
>>>>>>>
>>>>>>> Thank you for any help that you can provide!
>>>>>>>
>>>>>>> Josh Boustead
>>>>>>>
>>>>>>> Meteorologist/Modeler
>>>>>>> PEMDAS Technology and Innovation
>>>>>>> Norman, OK 73069
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> CONFIDENTIALITY NOTICE: This email message and all attachments
>>>>>>> transmitted with it may contain legally privileged and
>>>>>>> confidential
>>>>>>> information intended solely for the use of the addressee. If
the
>>>>>>> reader
>>>>> of
>>>>>>> this message is not the intended recipient, you are hereby
>>>>>>> notified that
>>>>>>> any reading, dissemination, distribution, copying, or other
use
>>>>>>> of
>>>>>>> this
>>>>>>> message or its attachments is strictly prohibited. If you have
>>>>>>> received
>>>>>>> this message in error, please notify the sender immediately
and
>>>>>>> delete
>>>>>>> this
>>>>>>> message from your system. Thank you.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Julie Prestopnik
>>>>>> Software Engineer
>>>>>> National Center for Atmospheric Research
>>>>>> Research Applications Laboratory
>>>>>> Phone: 303.497.8399
>>>>>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
>>>>>> <mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
>>>>>>
>>>>>> My working day may not be your working day. Please do not feel
>>>>>> obliged
>>>>> to
>>>>>> reply to this email outside of your normal working hours.
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> CONFIDENTIALITY NOTICE: This email message and all attachments
>>>>> transmitted with it may contain legally privileged and
>>>>> confidential
>>>>> information intended solely for the use of the addressee. If the
>>>>> reader of
>>>>> this message is not the intended recipient, you are hereby
>>>>> notified
>>>>> that
>>>>> any reading, dissemination, distribution, copying, or other use
of
>>>>> this
>>>>> message or its attachments is strictly prohibited. If you have
>>>>> received
>>>>> this message in error, please notify the sender immediately and
>>>>> delete
>>>>> this
>>>>> message from your system. Thank you.
>>>>>
>>>>>
>>>>
>>>> --
>>>> Julie Prestopnik
>>>> Software Engineer
>>>> National Center for Atmospheric Research
>>>> Research Applications Laboratory
>>>> Phone: 303.497.8399
>>>> Email: jpresto at ucar.edu
>>>>
>>>> My working day may not be your working day. Please do not feel
>>>> obliged to
>>>> reply to this email outside of your normal working hours.
>
>
>
------------------------------------------------
Subject: Verification of Atmospheric Motion Vectors using PointStat
From: Howard Soh
Time: Fri Jun 12 16:43:06 2020
I would like to close this ticket.
Do you have any more issues?
There is a github issue to support a point observation NetCDF file
(which is not generated by MET).
https://github.com/NCAR/MET/issues/1345
Cheers,
Howard
On Wed Jun 03 13:56:53 2020, hsoh wrote:
> Add one more global attribute into AMV file:
>
> + ncatted -a MET_version,global,a,c,V9.1 amv_abi-
> goes16_B14BT_YU_20200530T1200Z.nc
>
> note: Change "V9.1" to the matching MET version you are using
>
> Cheers,
> Howard
>
> On Wed Jun 03 13:43:23 2020, hsoh wrote:
> > You can use ascii2nc. There is workaround by modifying the AMV
data
> > file.
> >
> > point2grid supports GOES 16/17 dataset. GOES 16/17 does not have
> > lat/lon variables. They are computed but point2grid can read
lat/lon
> > from the NetCDF in order to save the computing time. The AMV data
> > file
> > is not supported by point2grid as is because of missing
information
> > (meta data).
> >
> > Workaround:
> >
> > Step 1. Generating CF-complaints NetCDF file with lat/lon
variables
> >
> > - nccopy -V lat,lon amv_abi-goes16_B14BT_YU_20200530T1200Z.nc
> > amv_abi-
> > goes16_lat_lon.nc
> > - ncrename -v lat,latitude -v lon,longitude amv_abi-
goes16_lat_lon.nc
> > - ncatted -a Conventions,global,a,c,"CF-1.6" amv_abi-
> > goes16_lat_lon.nc
> > - ncatted -a long_name,latitude,a,c,latitude amv_abi-
> > goes16_lat_lon.nc
> > - ncatted -a units,latitude,a,c,degrees_south amv_abi-
> > goes16_lat_lon.nc
> > - ncatted -a units,longitude,a,c,degrees_west amv_abi-
> > goes16_lat_lon.nc
> > - ncatted -a long_name,longitude,a,c,longitude amv_abi-
> > goes16_lat_lon.nc
> >
> > note: make sure the units are correct (degrees_south or
> > degrees_north)
> >
> > Step 2. Set environment variable to set the NetCDF file with
lat/lon
> >
> > - export MET_GEOSTATIONARY_DATA=amv_abi-goes16_lat_lon.nc
> > or
> > - setenv MET_GEOSTATIONARY_DATA amv_abi-goes16_lat_lon.nc
> >
> > Step 3. Add metadata (two global attributes) into AMV file
> >
> > + ncatted -a scene_id,global,a,c,Mesoscale amv_abi-
> > goes16_B14BT_YU_20200530T1200Z.nc
> > + ncatted -a Projection,global,a,c,LatLon amv_abi-
> > goes16_B14BT_YU_20200530T1200Z.nc
> >
> > Step 4. Added NetCDF type ("file_type=NETCDF_MET;") into the "-
field"
> > command line option
> >
> > + ./point2grid amv_abi-goes16_B14BT_YU_20200530T1200Z.nc G212
> > output.nc -field 'name="pressure"; level="(*,*)";
> > file_type=NETCDF_MET;' -v 4
> >
> > Cheers,
> > Howard
> >
> >
> >
> >
> > Step 2.
> >
> >
> > On Wed Jun 03 08:01:55 2020, josh.boustead at pemdastech.com wrote:
> > > Good morning Julie,
> > >
> > > Thanks for the information and help!
> > >
> > > I was looking through the MET user guide and ran across the
point
> > > to
> > > grid tool that I have not used before, but it mentions taking
point
> > > observations from GOES 16/17 and creating a grid. Our AMV output
> > > files
> > > are a subset of the GOES 16/17 in the same format. Would I be
able
> > > to
> > > use that tool to take the u and v components of the wind and
create
> > > a
> > > grid that I could then use in PointStat? The user guide and
example
> > > in
> > > the user guide use Aerosol Optical Depth and we are interested
in
> > > the
> > > wind so maybe it wouldn’t work, but it is something that caught
our
> > > eye. We also have the AMVs output into a csv. Along the same
lines,
> > > could I use a tool such as ascii2nc to take the information in
> > > those
> > > csv files, create a NetCDF file that point2Grid could then use
to
> > > create a grid that could be used in PointStat?
> > >
> > > Thanks again!
> > >
> > > Josh
> > >
> > > > On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
> > > > <met_help at ucar.edu> wrote:
> > > >
> > > > Hi Josh.
> > > >
> > > > Unfortunately, this NetCDF forecast data is not in a format
that
> > > > MET
> > > > can
> > > > read. MET is only able to read certain flavors of NetCDF:
> > > >
> > > > (1) The NetCDF output of the WRF p_interp or wrf_interp
utilities
> > > > (2) The NetCDF Climate Forecast (CF) convention
> > > > (
> > > > http://cfconventions.org/Data/cf-conventions/cf-con
> > > > <http://cfconventions.org/Data/cf-conventions/cf-
con>(ventions-
> > > > 1.7/cf-conventions.html
> > > > <http://cfconventions.org/Data/cf-conventions/cf-conventions-
> > > > 1.7/cf-
> > > > conventions.html <http://cfconventions.org/Data/cf-
> > > > conventions/cf-
> > > > conventions-1.7/cf-conventions.html>>
> > > > )
> > > > (3) The NetCDF output of other MET tools, like pcp_combine
> > > >
> > > > Your options are to either (1) reformat this data into a file
> > > > format
> > > > MET
> > > > understands or (2) write a python wrapper script to interpret
> > > > this
> > > > data and
> > > > utilize python embedding. Examples of python embedding can be
> > > > found
> > > > here:
> > > > https://dtcenter.org/community-code/model-evaluation-tools-
> > > > met/sample-analysis-scripts <https://dtcenter.org/community-
> > > > code/model-evaluation-tools-met/sample-analysis-scripts>
> > > >
> > > > I hope this helps!
> > > >
> > > > Julie
> > > >
> > > > On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
> > > > <met_help at ucar.edu <mailto:met_help at ucar.edu>>
> > > > wrote:
> > > >
> > > >>
> > > >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> > > >> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> > > >>
> > > >> Hi Julie,
> > > >>
> > > >> Thanks for the quick rely! I have updated the data as per
> > > >> instructions
> > > >> from the link in your email.
> > > >>
> > > >> Please let me know if you need anything additional.
> > > >>
> > > >> Thanks again,
> > > >>
> > > >> Josh
> > > >>
> > > >>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
> > > >>> <met_help at ucar.edu>
> > > >> wrote:
> > > >>>
> > > >>> Hi Josh.
> > > >>>
> > > >>> Thank you for all of this information. I see that MET is
> > > >>> having
> > > >>> trouble
> > > >>> reading your forecast file. Thank you for attaching your
> > > >>> config
> > > >>> file and
> > > >>> your log file. Could you please also send us your forecast
> > > >>> file
> > > >>> and your
> > > >>> observation file so that we can take a closer look? You can
> > > >>> follow
> > > >>> the
> > > >>> instructions under the "How to Send Us Data" section on the
> > > >>> following
> > > >> page:
> > > >>>
> > > >> https://dtcenter.org/community-code/model-evaluation-tools-
> > > >> met/met-
> > > >> help-desk
> > > >> <
> > > >> https://dtcenter.org/community-code/model-evaluation-tools-
> > > >> met/met-
> > > >> help-desk <https://dtcenter.org/community-code/model-
evaluation-
> > > >> tools-met/met-help-desk>
> > > >>>
> > > >>>
> > > >>> Julie
> > > >>>
> > > >>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
> > > >>> <met_help at ucar.edu <mailto:met_help at ucar.edu>
> > > >> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
> > > >>> wrote:
> > > >>>
> > > >>>>
> > > >>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
> > > >>>> Transaction: Ticket created by josh.boustead at pemdastech.com
> > > >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> > > >> josh.boustead at pemdastech.com
> > > >> <mailto:josh.boustead at pemdastech.com>>
> > > >>>> Queue: met_help
> > > >>>> Subject: Verification of Atmospheric Motion Vectors using
> > > >>>> PointStat
> > > >>>> Owner: Nobody
> > > >>>> Requestors: josh.boustead at pemdastech.com
> > > >>>> <mailto:josh.boustead at pemdastech.com> <mailto:
> > > >> josh.boustead at pemdastech.com
> > > >> <mailto:josh.boustead at pemdastech.com>>
> > > >>>> Status: new
> > > >>>> Ticket <URL:
> > > >>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
> > > >>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
> > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
> > > >>>>
> > > >>>>
> > > >>>> Hello,
> > > >>>>
> > > >>>> We generate atmospheric motion vectors (AMVs) using GEOS
> > > >>>> imagery
> > > >>>> and
> > > >> were
> > > >>>> hoping to use PointStat and StatAnalysis to produce some
> > > >>>> verification
> > > >>>> metrics on how well the algorithm to produce the AMVs was
> > > >>>> doing
> > > >> compared to
> > > >>>> RAOB and aircraft observations.
> > > >>>>
> > > >>>> The AMVs that we are generating output the winds in u and v
> > > >>>> components
> > > >> in
> > > >>>> m/s as well as the vertical placement in pressure and
height
> > > >>>> and
> > > >>>> are in
> > > >>>> NetCDF format. I can provide an example file of the AMVs if
it
> > > >>>> would be
> > > >>>> helpful. I then obtain MADIS RAOB and aircraft data from
NCEP,
> > > >>>> and
> > > >>>> using
> > > >>>> madis2nc convert this data into the format wanted by MET. I
> > > >>>> created a
> > > >>>> PointStat configuration file that is edited for the
forecast
> > > >>>> and
> > > >>>> observation fields to hopefully work with the data. I then
run
> > > >>>> the
> > > >>>> following command:
> > > >>>>
> > > >>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
> > > >> 20200530_madis2nc.nc
> > > >>>> /home/wrf/MET/met-
9.0/data/config/PointStatConfig_custom3_avi
> > > >>>> -outdir
> > > >>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
> > > >>>>
> > > >>>> PointStat then errors indicating that it is having trouble
> > > >>>> reading
> > > >>>> the
> > > >> AMV
> > > >>>> file. I have attached both the configuration file as well
as
> > > >>>> the
> > > >>>> output
> > > >> log
> > > >>>> to the email. Is there something that I need to do to the
AMV
> > > >>>> NetCDF
> > > >> file
> > > >>>> before using PointStat that I can not aware of, or is there
a
> > > >>>> better
> > > >> method
> > > >>>> of verification using MET to compare point motion vectors
at
> > > >>>> various
> > > >>>> heights to observational data?
> > > >>>>
> > > >>>> Thank you for any help that you can provide!
> > > >>>>
> > > >>>> Josh Boustead
> > > >>>>
> > > >>>> Meteorologist/Modeler
> > > >>>> PEMDAS Technology and Innovation
> > > >>>> Norman, OK 73069
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> --
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> CONFIDENTIALITY NOTICE: This email message and all
attachments
> > > >>>> transmitted with it may contain legally privileged and
> > > >>>> confidential
> > > >>>> information intended solely for the use of the addressee.
If
> > > >>>> the
> > > >>>> reader
> > > >> of
> > > >>>> this message is not the intended recipient, you are hereby
> > > >>>> notified that
> > > >>>> any reading, dissemination, distribution, copying, or other
> > > >>>> use
> > > >>>> of
> > > >>>> this
> > > >>>> message or its attachments is strictly prohibited. If you
have
> > > >>>> received
> > > >>>> this message in error, please notify the sender immediately
> > > >>>> and
> > > >>>> delete
> > > >>>> this
> > > >>>> message from your system. Thank you.
> > > >>>>
> > > >>>>
> > > >>>
> > > >>> --
> > > >>> Julie Prestopnik
> > > >>> Software Engineer
> > > >>> National Center for Atmospheric Research
> > > >>> Research Applications Laboratory
> > > >>> Phone: 303.497.8399
> > > >>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
> > > >>> <mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
> > > >>>
> > > >>> My working day may not be your working day. Please do not
feel
> > > >>> obliged
> > > >> to
> > > >>> reply to this email outside of your normal working hours.
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> CONFIDENTIALITY NOTICE: This email message and all
attachments
> > > >> transmitted with it may contain legally privileged and
> > > >> confidential
> > > >> information intended solely for the use of the addressee. If
the
> > > >> reader of
> > > >> this message is not the intended recipient, you are hereby
> > > >> notified
> > > >> that
> > > >> any reading, dissemination, distribution, copying, or other
use
> > > >> of
> > > >> this
> > > >> message or its attachments is strictly prohibited. If you
have
> > > >> received
> > > >> this message in error, please notify the sender immediately
and
> > > >> delete
> > > >> this
> > > >> message from your system. Thank you.
> > > >>
> > > >>
> > > >
> > > > --
> > > > Julie Prestopnik
> > > > Software Engineer
> > > > National Center for Atmospheric Research
> > > > Research Applications Laboratory
> > > > Phone: 303.497.8399
> > > > Email: jpresto at ucar.edu
> > > >
> > > > My working day may not be your working day. Please do not
feel
> > > > obliged to
> > > > reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #95459] Verification of Atmospheric Motion Vectors using PointStat
From: Josh Boustead
Time: Mon Jun 15 09:01:49 2020
Yes Howard that sounds fine. I really appreciate your help!!
Have a great week.
Thanks…Josh
> On Jun 12, 2020, at 5:43 PM, Howard Soh via RT <met_help at ucar.edu>
wrote:
>
> I would like to close this ticket.
> Do you have any more issues?
>
> There is a github issue to support a point observation NetCDF file
(which is not generated by MET).
https://github.com/NCAR/MET/issues/1345
>
> Cheers,
> Howard
>
> On Wed Jun 03 13:56:53 2020, hsoh wrote:
>> Add one more global attribute into AMV file:
>>
>> + ncatted -a MET_version,global,a,c,V9.1 amv_abi-
>> goes16_B14BT_YU_20200530T1200Z.nc
>>
>> note: Change "V9.1" to the matching MET version you are using
>>
>> Cheers,
>> Howard
>>
>> On Wed Jun 03 13:43:23 2020, hsoh wrote:
>>> You can use ascii2nc. There is workaround by modifying the AMV
data
>>> file.
>>>
>>> point2grid supports GOES 16/17 dataset. GOES 16/17 does not have
>>> lat/lon variables. They are computed but point2grid can read
lat/lon
>>> from the NetCDF in order to save the computing time. The AMV data
>>> file
>>> is not supported by point2grid as is because of missing
information
>>> (meta data).
>>>
>>> Workaround:
>>>
>>> Step 1. Generating CF-complaints NetCDF file with lat/lon
variables
>>>
>>> - nccopy -V lat,lon amv_abi-goes16_B14BT_YU_20200530T1200Z.nc
>>> amv_abi-
>>> goes16_lat_lon.nc
>>> - ncrename -v lat,latitude -v lon,longitude amv_abi-
goes16_lat_lon.nc
>>> - ncatted -a Conventions,global,a,c,"CF-1.6" amv_abi-
>>> goes16_lat_lon.nc
>>> - ncatted -a long_name,latitude,a,c,latitude amv_abi-
>>> goes16_lat_lon.nc
>>> - ncatted -a units,latitude,a,c,degrees_south amv_abi-
>>> goes16_lat_lon.nc
>>> - ncatted -a units,longitude,a,c,degrees_west amv_abi-
>>> goes16_lat_lon.nc
>>> - ncatted -a long_name,longitude,a,c,longitude amv_abi-
>>> goes16_lat_lon.nc
>>>
>>> note: make sure the units are correct (degrees_south or
>>> degrees_north)
>>>
>>> Step 2. Set environment variable to set the NetCDF file with
lat/lon
>>>
>>> - export MET_GEOSTATIONARY_DATA=amv_abi-goes16_lat_lon.nc
>>> or
>>> - setenv MET_GEOSTATIONARY_DATA amv_abi-goes16_lat_lon.nc
>>>
>>> Step 3. Add metadata (two global attributes) into AMV file
>>>
>>> + ncatted -a scene_id,global,a,c,Mesoscale amv_abi-
>>> goes16_B14BT_YU_20200530T1200Z.nc
>>> + ncatted -a Projection,global,a,c,LatLon amv_abi-
>>> goes16_B14BT_YU_20200530T1200Z.nc
>>>
>>> Step 4. Added NetCDF type ("file_type=NETCDF_MET;") into the "-
field"
>>> command line option
>>>
>>> + ./point2grid amv_abi-goes16_B14BT_YU_20200530T1200Z.nc G212
>>> output.nc -field 'name="pressure"; level="(*,*)";
>>> file_type=NETCDF_MET;' -v 4
>>>
>>> Cheers,
>>> Howard
>>>
>>>
>>>
>>>
>>> Step 2.
>>>
>>>
>>> On Wed Jun 03 08:01:55 2020, josh.boustead at pemdastech.com wrote:
>>>> Good morning Julie,
>>>>
>>>> Thanks for the information and help!
>>>>
>>>> I was looking through the MET user guide and ran across the point
>>>> to
>>>> grid tool that I have not used before, but it mentions taking
point
>>>> observations from GOES 16/17 and creating a grid. Our AMV output
>>>> files
>>>> are a subset of the GOES 16/17 in the same format. Would I be
able
>>>> to
>>>> use that tool to take the u and v components of the wind and
create
>>>> a
>>>> grid that I could then use in PointStat? The user guide and
example
>>>> in
>>>> the user guide use Aerosol Optical Depth and we are interested in
>>>> the
>>>> wind so maybe it wouldn’t work, but it is something that caught
our
>>>> eye. We also have the AMVs output into a csv. Along the same
lines,
>>>> could I use a tool such as ascii2nc to take the information in
>>>> those
>>>> csv files, create a NetCDF file that point2Grid could then use to
>>>> create a grid that could be used in PointStat?
>>>>
>>>> Thanks again!
>>>>
>>>> Josh
>>>>
>>>>> On Jun 2, 2020, at 12:07 PM, Julie Prestopnik via RT
>>>>> <met_help at ucar.edu> wrote:
>>>>>
>>>>> Hi Josh.
>>>>>
>>>>> Unfortunately, this NetCDF forecast data is not in a format that
>>>>> MET
>>>>> can
>>>>> read. MET is only able to read certain flavors of NetCDF:
>>>>>
>>>>> (1) The NetCDF output of the WRF p_interp or wrf_interp
utilities
>>>>> (2) The NetCDF Climate Forecast (CF) convention
>>>>> (
>>>>> http://cfconventions.org/Data/cf-conventions/cf-con
>>>>> <http://cfconventions.org/Data/cf-conventions/cf-con>(ventions-
>>>>> 1.7/cf-conventions.html
>>>>> <http://cfconventions.org/Data/cf-conventions/cf-conventions-
>>>>> 1.7/cf-
>>>>> conventions.html <http://cfconventions.org/Data/cf-
>>>>> conventions/cf-
>>>>> conventions-1.7/cf-conventions.html>>
>>>>> )
>>>>> (3) The NetCDF output of other MET tools, like pcp_combine
>>>>>
>>>>> Your options are to either (1) reformat this data into a file
>>>>> format
>>>>> MET
>>>>> understands or (2) write a python wrapper script to interpret
>>>>> this
>>>>> data and
>>>>> utilize python embedding. Examples of python embedding can be
>>>>> found
>>>>> here:
>>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>>> met/sample-analysis-scripts <https://dtcenter.org/community-
>>>>> code/model-evaluation-tools-met/sample-analysis-scripts>
>>>>>
>>>>> I hope this helps!
>>>>>
>>>>> Julie
>>>>>
>>>>> On Tue, Jun 2, 2020 at 10:04 AM Josh Boustead via RT
>>>>> <met_help at ucar.edu <mailto:met_help at ucar.edu>>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
>>>>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>>>>>
>>>>>> Hi Julie,
>>>>>>
>>>>>> Thanks for the quick rely! I have updated the data as per
>>>>>> instructions
>>>>>> from the link in your email.
>>>>>>
>>>>>> Please let me know if you need anything additional.
>>>>>>
>>>>>> Thanks again,
>>>>>>
>>>>>> Josh
>>>>>>
>>>>>>> On Jun 2, 2020, at 10:38 AM, Julie Prestopnik via RT
>>>>>>> <met_help at ucar.edu>
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Josh.
>>>>>>>
>>>>>>> Thank you for all of this information. I see that MET is
>>>>>>> having
>>>>>>> trouble
>>>>>>> reading your forecast file. Thank you for attaching your
>>>>>>> config
>>>>>>> file and
>>>>>>> your log file. Could you please also send us your forecast
>>>>>>> file
>>>>>>> and your
>>>>>>> observation file so that we can take a closer look? You can
>>>>>>> follow
>>>>>>> the
>>>>>>> instructions under the "How to Send Us Data" section on the
>>>>>>> following
>>>>>> page:
>>>>>>>
>>>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>>>> met/met-
>>>>>> help-desk
>>>>>> <
>>>>>> https://dtcenter.org/community-code/model-evaluation-tools-
>>>>>> met/met-
>>>>>> help-desk <https://dtcenter.org/community-code/model-
evaluation-
>>>>>> tools-met/met-help-desk>
>>>>>>>
>>>>>>>
>>>>>>> Julie
>>>>>>>
>>>>>>> On Tue, Jun 2, 2020 at 8:17 AM Josh Boustead via RT
>>>>>>> <met_help at ucar.edu <mailto:met_help at ucar.edu>
>>>>>> <mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Tue Jun 02 08:17:31 2020: Request 95459 was acted upon.
>>>>>>>> Transaction: Ticket created by josh.boustead at pemdastech.com
>>>>>>>> <mailto:josh.boustead at pemdastech.com> <mailto:
>>>>>> josh.boustead at pemdastech.com
>>>>>> <mailto:josh.boustead at pemdastech.com>>
>>>>>>>> Queue: met_help
>>>>>>>> Subject: Verification of Atmospheric Motion Vectors using
>>>>>>>> PointStat
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: josh.boustead at pemdastech.com
>>>>>>>> <mailto:josh.boustead at pemdastech.com> <mailto:
>>>>>> josh.boustead at pemdastech.com
>>>>>> <mailto:josh.boustead at pemdastech.com>>
>>>>>>>> Status: new
>>>>>>>> Ticket <URL:
>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459
>>>>>>>> <https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> <
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95459> >
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> We generate atmospheric motion vectors (AMVs) using GEOS
>>>>>>>> imagery
>>>>>>>> and
>>>>>> were
>>>>>>>> hoping to use PointStat and StatAnalysis to produce some
>>>>>>>> verification
>>>>>>>> metrics on how well the algorithm to produce the AMVs was
>>>>>>>> doing
>>>>>> compared to
>>>>>>>> RAOB and aircraft observations.
>>>>>>>>
>>>>>>>> The AMVs that we are generating output the winds in u and v
>>>>>>>> components
>>>>>> in
>>>>>>>> m/s as well as the vertical placement in pressure and height
>>>>>>>> and
>>>>>>>> are in
>>>>>>>> NetCDF format. I can provide an example file of the AMVs if
it
>>>>>>>> would be
>>>>>>>> helpful. I then obtain MADIS RAOB and aircraft data from
NCEP,
>>>>>>>> and
>>>>>>>> using
>>>>>>>> madis2nc convert this data into the format wanted by MET. I
>>>>>>>> created a
>>>>>>>> PointStat configuration file that is edited for the forecast
>>>>>>>> and
>>>>>>>> observation fields to hopefully work with the data. I then
run
>>>>>>>> the
>>>>>>>> following command:
>>>>>>>>
>>>>>>>> point_stat amp_abi-goes16_B14BT_YU_20200530T1200Z.nc
>>>>>> 20200530_madis2nc.nc
>>>>>>>> /home/wrf/MET/met-9.0/data/config/PointStatConfig_custom3_avi
>>>>>>>> -outdir
>>>>>>>> /home/wrf/MET/data/point_stat/ -log amp_5_30.log -v 4
>>>>>>>>
>>>>>>>> PointStat then errors indicating that it is having trouble
>>>>>>>> reading
>>>>>>>> the
>>>>>> AMV
>>>>>>>> file. I have attached both the configuration file as well as
>>>>>>>> the
>>>>>>>> output
>>>>>> log
>>>>>>>> to the email. Is there something that I need to do to the AMV
>>>>>>>> NetCDF
>>>>>> file
>>>>>>>> before using PointStat that I can not aware of, or is there a
>>>>>>>> better
>>>>>> method
>>>>>>>> of verification using MET to compare point motion vectors at
>>>>>>>> various
>>>>>>>> heights to observational data?
>>>>>>>>
>>>>>>>> Thank you for any help that you can provide!
>>>>>>>>
>>>>>>>> Josh Boustead
>>>>>>>>
>>>>>>>> Meteorologist/Modeler
>>>>>>>> PEMDAS Technology and Innovation
>>>>>>>> Norman, OK 73069
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> CONFIDENTIALITY NOTICE: This email message and all
attachments
>>>>>>>> transmitted with it may contain legally privileged and
>>>>>>>> confidential
>>>>>>>> information intended solely for the use of the addressee. If
>>>>>>>> the
>>>>>>>> reader
>>>>>> of
>>>>>>>> this message is not the intended recipient, you are hereby
>>>>>>>> notified that
>>>>>>>> any reading, dissemination, distribution, copying, or other
>>>>>>>> use
>>>>>>>> of
>>>>>>>> this
>>>>>>>> message or its attachments is strictly prohibited. If you
have
>>>>>>>> received
>>>>>>>> this message in error, please notify the sender immediately
>>>>>>>> and
>>>>>>>> delete
>>>>>>>> this
>>>>>>>> message from your system. Thank you.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Julie Prestopnik
>>>>>>> Software Engineer
>>>>>>> National Center for Atmospheric Research
>>>>>>> Research Applications Laboratory
>>>>>>> Phone: 303.497.8399
>>>>>>> Email: jpresto at ucar.edu <mailto:jpresto at ucar.edu>
>>>>>>> <mailto:jpresto at ucar.edu <mailto:jpresto at ucar.edu>>
>>>>>>>
>>>>>>> My working day may not be your working day. Please do not
feel
>>>>>>> obliged
>>>>>> to
>>>>>>> reply to this email outside of your normal working hours.
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> CONFIDENTIALITY NOTICE: This email message and all attachments
>>>>>> transmitted with it may contain legally privileged and
>>>>>> confidential
>>>>>> information intended solely for the use of the addressee. If
the
>>>>>> reader of
>>>>>> this message is not the intended recipient, you are hereby
>>>>>> notified
>>>>>> that
>>>>>> any reading, dissemination, distribution, copying, or other use
>>>>>> of
>>>>>> this
>>>>>> message or its attachments is strictly prohibited. If you have
>>>>>> received
>>>>>> this message in error, please notify the sender immediately and
>>>>>> delete
>>>>>> this
>>>>>> message from your system. Thank you.
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Julie Prestopnik
>>>>> Software Engineer
>>>>> National Center for Atmospheric Research
>>>>> Research Applications Laboratory
>>>>> Phone: 303.497.8399
>>>>> Email: jpresto at ucar.edu
>>>>>
>>>>> My working day may not be your working day. Please do not feel
>>>>> obliged to
>>>>> reply to this email outside of your normal working hours.
>
>
>
--
CONFIDENTIALITY NOTICE: This email message and all attachments
transmitted with it may contain legally privileged and confidential
information intended solely for the use of the addressee. If the
reader of
this message is not the intended recipient, you are hereby notified
that
any reading, dissemination, distribution, copying, or other use of
this
message or its attachments is strictly prohibited. If you have
received
this message in error, please notify the sender immediately and delete
this
message from your system. Thank you.
------------------------------------------------
More information about the Met_help
mailing list