[Met_help] [rt.rap.ucar.edu #100324] History for MET update and questions
George McCabe via RT
met_help at ucar.edu
Thu Jul 1 07:45:23 MDT 2021
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi all,
I used MET/metpy to calculate the moist static energy for the Dorian (2019)
use-case. MSE may be a very useful metric in general that others may like
to try (as applied in the papers listed below). In the case of Dorian, MSE
may have had some bearing in the development of rainfall over the NE.
https://journals.ametsoc.org/view/journals/atsc/71/11/jas-d-14-0052.1.xml
https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2019GL083667
https://journals.ametsoc.org/view/journals/clim/32/18/jcli-d-18-0599.1.xml
I have a couple of questions regarding MET. First, for the series
analysis, do I really need to run a separate python script for each
diagnostic? This looks to be the case by default when looking at PV and
IVT, in which each script outputs only one variable for MET to then read.
Can I combine multiple scripts into one that outputs multiple variables?
Second, is it possible for MET to read-in variables directly from wrfout
netcdf files? For example, say I have PBL height or other model variables
on model sigma levels. Would MET know how to read these when specified in
the config files? My understanding is that MET is particular when it comes
to the level specified. It can handle pressure levels ("PXXX"), but what
about sigma levels ("???")? Thank you.
-Nick
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MET update and questions
From: Minna Win
Time: Thu Jun 24 11:31:51 2021
Hi Nick,
I will need to find someone who can answer your second question
regarding
netCDF files. I need some clarification on your first question. When
you
are asking whether you need to run multiple python scripts, are you
referring to the Python embedding scripts that MET supports?
Regards,
Minna
---------------
Minna Win
Pronouns: she/her
National Center for Atmospheric Research
Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
---------------
On Thu, Jun 24, 2021 at 10:24 AM Nicholas Leonardo via RT
<met_help at ucar.edu>
wrote:
>
> Thu Jun 24 10:24:25 2021: Request 100324 was acted upon.
> Transaction: Ticket created by nleonardo87 at gmail.com
> Queue: met_help
> Subject: MET update and questions
> Owner: Nobody
> Requestors: nleonardo87 at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100324 >
>
>
> Hi all,
> I used MET/metpy to calculate the moist static energy for the Dorian
(2019)
> use-case. MSE may be a very useful metric in general that others
may like
> to try (as applied in the papers listed below). In the case of
Dorian, MSE
> may have had some bearing in the development of rainfall over the
NE.
> https://journals.ametsoc.org/view/journals/atsc/71/11/jas-d-14-
0052.1.xml
>
https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2019GL083667
> https://journals.ametsoc.org/view/journals/clim/32/18/jcli-d-18-
0599.1.xml
>
> I have a couple of questions regarding MET. First, for the series
> analysis, do I really need to run a separate python script for each
> diagnostic? This looks to be the case by default when looking at PV
and
> IVT, in which each script outputs only one variable for MET to then
read.
> Can I combine multiple scripts into one that outputs multiple
variables?
>
> Second, is it possible for MET to read-in variables directly from
wrfout
> netcdf files? For example, say I have PBL height or other model
variables
> on model sigma levels. Would MET know how to read these when
specified in
> the config files? My understanding is that MET is particular when
it comes
> to the level specified. It can handle pressure levels ("PXXX"), but
what
> about sigma levels ("???")? Thank you.
>
> -Nick
>
>
------------------------------------------------
Subject: MET update and questions
From: Nicholas Leonardo
Time: Thu Jun 24 13:06:27 2021
Hello Mina,
Thank you and yes, I was referring to the Python embedding scripts
(e.g.,
from the Dorian feature-relative use case, condensing
gfs_pv_analysis.py,
gfs_ivt_analysis.py, gfs_pv_fcst.py, gfs_ivt_fcst.py into one).
-Nick
On Thu, Jun 24, 2021 at 1:31 PM Minna Win via RT <met_help at ucar.edu>
wrote:
> Hi Nick,
>
> I will need to find someone who can answer your second question
regarding
> netCDF files. I need some clarification on your first question.
When you
> are asking whether you need to run multiple python scripts, are you
> referring to the Python embedding scripts that MET supports?
>
> Regards,
> Minna
> ---------------
> Minna Win
> Pronouns: she/her
> National Center for Atmospheric Research
> Developmental Testbed Center
> Phone: 303-497-8423
> Fax: 303-497-8401
> ---------------
>
>
>
> On Thu, Jun 24, 2021 at 10:24 AM Nicholas Leonardo via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Thu Jun 24 10:24:25 2021: Request 100324 was acted upon.
> > Transaction: Ticket created by nleonardo87 at gmail.com
> > Queue: met_help
> > Subject: MET update and questions
> > Owner: Nobody
> > Requestors: nleonardo87 at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100324 >
> >
> >
> > Hi all,
> > I used MET/metpy to calculate the moist static energy for the
Dorian
> (2019)
> > use-case. MSE may be a very useful metric in general that others
may
> like
> > to try (as applied in the papers listed below). In the case of
Dorian,
> MSE
> > may have had some bearing in the development of rainfall over the
NE.
> >
> https://journals.ametsoc.org/view/journals/atsc/71/11/jas-d-14-
0052.1.xml
> >
https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2019GL083667
> >
> https://journals.ametsoc.org/view/journals/clim/32/18/jcli-d-18-
0599.1.xml
> >
> > I have a couple of questions regarding MET. First, for the series
> > analysis, do I really need to run a separate python script for
each
> > diagnostic? This looks to be the case by default when looking at
PV and
> > IVT, in which each script outputs only one variable for MET to
then read.
> > Can I combine multiple scripts into one that outputs multiple
variables?
> >
> > Second, is it possible for MET to read-in variables directly from
wrfout
> > netcdf files? For example, say I have PBL height or other model
> variables
> > on model sigma levels. Would MET know how to read these when
specified
> in
> > the config files? My understanding is that MET is particular when
it
> comes
> > to the level specified. It can handle pressure levels ("PXXX"),
but what
> > about sigma levels ("???")? Thank you.
> >
> > -Nick
> >
> >
>
>
------------------------------------------------
Subject: MET update and questions
From: Minna Win
Time: Thu Jun 24 13:10:47 2021
Hi Nick,
I found a response to your second question:
"We do not currently support reading variables on sigma levels in
WRFout
directly. We finally have funding to actively work towards that
capability
and are hoping it will be available in our METplus 4.1.0 beta_3
release at
the end of September."
I will ask George McCabe to answer your first question, now that I
know
that you were referring to Python embedding scripts.
Regards,
Minna
---------------
Minna Win
Pronouns: she/her
National Center for Atmospheric Research
Developmental Testbed Center
Phone: 303-497-8423
Fax: 303-497-8401
---------------
On Thu, Jun 24, 2021 at 10:24 AM Nicholas Leonardo via RT
<met_help at ucar.edu>
wrote:
>
> Thu Jun 24 10:24:25 2021: Request 100324 was acted upon.
> Transaction: Ticket created by nleonardo87 at gmail.com
> Queue: met_help
> Subject: MET update and questions
> Owner: Nobody
> Requestors: nleonardo87 at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100324 >
>
>
> Hi all,
> I used MET/metpy to calculate the moist static energy for the Dorian
(2019)
> use-case. MSE may be a very useful metric in general that others
may like
> to try (as applied in the papers listed below). In the case of
Dorian, MSE
> may have had some bearing in the development of rainfall over the
NE.
> https://journals.ametsoc.org/view/journals/atsc/71/11/jas-d-14-
0052.1.xml
>
https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2019GL083667
> https://journals.ametsoc.org/view/journals/clim/32/18/jcli-d-18-
0599.1.xml
>
> I have a couple of questions regarding MET. First, for the series
> analysis, do I really need to run a separate python script for each
> diagnostic? This looks to be the case by default when looking at PV
and
> IVT, in which each script outputs only one variable for MET to then
read.
> Can I combine multiple scripts into one that outputs multiple
variables?
>
> Second, is it possible for MET to read-in variables directly from
wrfout
> netcdf files? For example, say I have PBL height or other model
variables
> on model sigma levels. Would MET know how to read these when
specified in
> the config files? My understanding is that MET is particular when
it comes
> to the level specified. It can handle pressure levels ("PXXX"), but
what
> about sigma levels ("???")? Thank you.
>
> -Nick
>
>
------------------------------------------------
Subject: MET update and questions
From: George McCabe
Time: Mon Jun 28 10:34:10 2021
Hi Nick,
To address this question:
* First, for the series analysis, do I really need to run a separate
python
script for each diagnostic? This looks to be the case by default when
looking at PV and IVT, in which each script outputs only one variable
for
MET to then read. Can I combine multiple scripts into one that outputs
multiple variables? *
Currently, yes, you will need to call a script for each variable. The
MET
tools only read a single 2D field as gridded input and the Python
Embedding
logic was designed to use a single script call to produce a single
input to
the MET tools.
- George
On Thu, Jun 24, 2021 at 1:26 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> Thu Jun 24 13:26:02 2021: Request 100324 was acted upon.
> Transaction: Given to mccabe (George McCabe) by minnawin
> Queue: met_help
> Subject: MET update and questions
> Owner: mccabe
> Requestors: nleonardo87 at gmail.com
> Status: open
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100324 >
>
>
> This transaction appears to have no content
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
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: MET update and questions
From: Nicholas Leonardo
Time: Mon Jun 28 11:17:29 2021
I see. At least regarding the ingestion of WRF data, I figure that
the
embedded python script functionality can be used to first read-in and
convert/interpolate the data into something MET can use. Thank you
all
very much for checking.
-Nick
On Mon, Jun 28, 2021 at 12:47 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Nick,
>
> To address this question:
>
> * First, for the series analysis, do I really need to run a separate
python
> script for each diagnostic? This looks to be the case by default
when
> looking at PV and IVT, in which each script outputs only one
variable for
> MET to then read. Can I combine multiple scripts into one that
outputs
> multiple variables? *
>
> Currently, yes, you will need to call a script for each variable.
The MET
> tools only read a single 2D field as gridded input and the Python
Embedding
> logic was designed to use a single script call to produce a single
input to
> the MET tools.
>
> - George
>
> On Thu, Jun 24, 2021 at 1:26 PM Minna Win via RT <met_help at ucar.edu>
> wrote:
>
> >
> > Thu Jun 24 13:26:02 2021: Request 100324 was acted upon.
> > Transaction: Given to mccabe (George McCabe) by minnawin
> > Queue: met_help
> > Subject: MET update and questions
> > Owner: mccabe
> > Requestors: nleonardo87 at gmail.com
> > Status: open
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100324 >
> >
> >
> > This transaction appears to have no content
> >
>
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> 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.
>
>
------------------------------------------------
More information about the Met_help
mailing list