[Met_help] [rt.rap.ucar.edu #80102] History for MET-Grid Stat VL1L2 Output
John Halley Gotway via RT
met_help at ucar.edu
Mon Apr 10 13:51:37 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I am having trouble getting output for the vector partial sums for the wind field at multiple pressure levels using grid stat. When I want to output the continuous and scalar partial sums, the files are filled, but turning on vl1l2 outputs nothing (blank file besides header). I tried using the u and v winds individually and together. Is there a trick to this? This seems rather simple, but I cannot seem to get the vector partial sums to work. Thanks in advance.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MET-Grid Stat VL1L2 Output
From: John Halley Gotway
Time: Mon Apr 10 12:14:33 2017
Mallory,
I see you're having trouble getting VL1L2 output from Grid-Stat.
Thanks for sending the Grid-Stat config file you're using. I see that
in there you've only requested output for the U-component of wind
(UGRD). The VL1L2 computations require both UGRD and VGRD, so you
need to put both in there.
I see from your config file that you're using MET version 5.2... which
requires that wind stats follow a certain convention. However, in MET
version 6.0 we've removed this requirement. Please take a look at the
release notes for version 6.0 and search for UGRD:
http://www.dtcenter.org/met/users/support/release_notes/METv6.0_release_notes.php
In version 5.2 version (and all previous), we required that UGRD be
immediately followed by VGRD ***AT THE SAME LEVEL*** for VL1L2 output.
This made the book-keeping in the code a lot simpler. However, when
we added support for an array of level entries, this convention made
computing VL1L2 output a lot more tedious. Look at this example:
field = [
{ name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
{ name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
];
Here we have UGRD followed by VGRD, but not at the same levels. This
gets expanded in the code to look like this:
UGRD/P1000, UGRD/P850, UGRD/P700, VGRD/P1000, VGRD/P850, VGRD/P700
So they're not in the expected order and you get no VL1L2 output.
To test, please try specifying it this long way and make sure that you
get VL1L2 output:
field = [
{ name = "UGRD"; level = [ "P1000" ]; },
{ name = "VGRD"; level = [ "P1000" ]; },
{ name = "UGRD"; level = [ "P850" ]; },
{ name = "VGRD"; level = [ "P850" ]; },
{ name = "UGRD"; level = [ "P700" ]; },
{ name = "VGRD"; level = [ "P700" ]; }
];
Once you start using version 6.0, this isn't required. We made the
code smart enough for each UGRD field to hunt around and find it's
VGRD partner, regardless of the order.
Thanks,
John
------------------------------------------------
Subject: MET-Grid Stat VL1L2 Output
From: Mallory Row - NOAA Affiliate
Time: Mon Apr 10 12:57:28 2017
Hi John,
Thanks! This makes sense. So in 6.0, if UGRD is just specified in the
config file and the VL1L2 is turned on, then it will find its
corresponding
VGRD? Or is more specified like the first example.
Mallory
On Mon, Apr 10, 2017 at 2:14 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Mallory,
>
> I see you're having trouble getting VL1L2 output from Grid-Stat.
Thanks
> for sending the Grid-Stat config file you're using. I see that in
there
> you've only requested output for the U-component of wind (UGRD).
The VL1L2
> computations require both UGRD and VGRD, so you need to put both in
there.
>
> I see from your config file that you're using MET version 5.2...
which
> requires that wind stats follow a certain convention. However, in
MET
> version 6.0 we've removed this requirement. Please take a look at
the
> release notes for version 6.0 and search for UGRD:
> http://www.dtcenter.org/met/users/support/release_notes/
> METv6.0_release_notes.php
>
> In version 5.2 version (and all previous), we required that UGRD be
> immediately followed by VGRD ***AT THE SAME LEVEL*** for VL1L2
output.
> This made the book-keeping in the code a lot simpler. However, when
we
> added support for an array of level entries, this convention made
computing
> VL1L2 output a lot more tedious. Look at this example:
>
> field = [
> { name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
> { name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
> ];
>
> Here we have UGRD followed by VGRD, but not at the same levels.
This gets
> expanded in the code to look like this:
> UGRD/P1000, UGRD/P850, UGRD/P700, VGRD/P1000, VGRD/P850,
VGRD/P700
>
> So they're not in the expected order and you get no VL1L2 output.
>
> To test, please try specifying it this long way and make sure that
you get
> VL1L2 output:
>
> field = [
> { name = "UGRD"; level = [ "P1000" ]; },
> { name = "VGRD"; level = [ "P1000" ]; },
> { name = "UGRD"; level = [ "P850" ]; },
> { name = "VGRD"; level = [ "P850" ]; },
> { name = "UGRD"; level = [ "P700" ]; },
> { name = "VGRD"; level = [ "P700" ]; }
> ];
>
> Once you start using version 6.0, this isn't required. We made the
code
> smart enough for each UGRD field to hunt around and find it's VGRD
partner,
> regardless of the order.
>
> Thanks,
> John
>
>
>
>
------------------------------------------------
Subject: MET-Grid Stat VL1L2 Output
From: John Halley Gotway
Time: Mon Apr 10 13:01:47 2017
Mallory,
In both versions, you still need to request both UGRD and VGRD to get
VL1L2
output.
The difference is...
- In 5.2, you can only list 1 level at a time since UGRD/P1000 must be
followed by VGRD/P1000... and that makes the config file longer. So
for 3
levels, you have 6 entries in the "field".
- In 6.0, you can list all the levels at once like this:
field = [
{ name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
{ name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
];
Make sense?
Thanks,
John
On Mon, Apr 10, 2017 at 12:57 PM, Mallory Row - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80102 >
>
> Hi John,
>
> Thanks! This makes sense. So in 6.0, if UGRD is just specified in
the
> config file and the VL1L2 is turned on, then it will find its
corresponding
> VGRD? Or is more specified like the first example.
>
> Mallory
>
> On Mon, Apr 10, 2017 at 2:14 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Mallory,
> >
> > I see you're having trouble getting VL1L2 output from Grid-Stat.
Thanks
> > for sending the Grid-Stat config file you're using. I see that in
there
> > you've only requested output for the U-component of wind (UGRD).
The
> VL1L2
> > computations require both UGRD and VGRD, so you need to put both
in
> there.
> >
> > I see from your config file that you're using MET version 5.2...
which
> > requires that wind stats follow a certain convention. However, in
MET
> > version 6.0 we've removed this requirement. Please take a look at
the
> > release notes for version 6.0 and search for UGRD:
> > http://www.dtcenter.org/met/users/support/release_notes/
> > METv6.0_release_notes.php
> >
> > In version 5.2 version (and all previous), we required that UGRD
be
> > immediately followed by VGRD ***AT THE SAME LEVEL*** for VL1L2
output.
> > This made the book-keeping in the code a lot simpler. However,
when we
> > added support for an array of level entries, this convention made
> computing
> > VL1L2 output a lot more tedious. Look at this example:
> >
> > field = [
> > { name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
> > { name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
> > ];
> >
> > Here we have UGRD followed by VGRD, but not at the same levels.
This
> gets
> > expanded in the code to look like this:
> > UGRD/P1000, UGRD/P850, UGRD/P700, VGRD/P1000, VGRD/P850,
VGRD/P700
> >
> > So they're not in the expected order and you get no VL1L2 output.
> >
> > To test, please try specifying it this long way and make sure that
you
> get
> > VL1L2 output:
> >
> > field = [
> > { name = "UGRD"; level = [ "P1000" ]; },
> > { name = "VGRD"; level = [ "P1000" ]; },
> > { name = "UGRD"; level = [ "P850" ]; },
> > { name = "VGRD"; level = [ "P850" ]; },
> > { name = "UGRD"; level = [ "P700" ]; },
> > { name = "VGRD"; level = [ "P700" ]; }
> > ];
> >
> > Once you start using version 6.0, this isn't required. We made
the code
> > smart enough for each UGRD field to hunt around and find it's VGRD
> partner,
> > regardless of the order.
> >
> > Thanks,
> > John
> >
> >
> >
> >
>
>
------------------------------------------------
Subject: MET-Grid Stat VL1L2 Output
From: Mallory Row - NOAA Affiliate
Time: Mon Apr 10 13:14:19 2017
Hi John,
Yes it does. Thanks for the quick help!!
Mallory
On Mon, Apr 10, 2017 at 3:01 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Mallory,
>
> In both versions, you still need to request both UGRD and VGRD to
get VL1L2
> output.
>
> The difference is...
> - In 5.2, you can only list 1 level at a time since UGRD/P1000 must
be
> followed by VGRD/P1000... and that makes the config file longer. So
for 3
> levels, you have 6 entries in the "field".
> - In 6.0, you can list all the levels at once like this:
> field = [
> { name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
> { name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
> ];
>
> Make sense?
>
> Thanks,
> John
>
> On Mon, Apr 10, 2017 at 12:57 PM, Mallory Row - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80102 >
> >
> > Hi John,
> >
> > Thanks! This makes sense. So in 6.0, if UGRD is just specified in
the
> > config file and the VL1L2 is turned on, then it will find its
> corresponding
> > VGRD? Or is more specified like the first example.
> >
> > Mallory
> >
> > On Mon, Apr 10, 2017 at 2:14 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Mallory,
> > >
> > > I see you're having trouble getting VL1L2 output from Grid-Stat.
> Thanks
> > > for sending the Grid-Stat config file you're using. I see that
in
> there
> > > you've only requested output for the U-component of wind (UGRD).
The
> > VL1L2
> > > computations require both UGRD and VGRD, so you need to put both
in
> > there.
> > >
> > > I see from your config file that you're using MET version 5.2...
which
> > > requires that wind stats follow a certain convention. However,
in MET
> > > version 6.0 we've removed this requirement. Please take a look
at the
> > > release notes for version 6.0 and search for UGRD:
> > > http://www.dtcenter.org/met/users/support/release_notes/
> > > METv6.0_release_notes.php
> > >
> > > In version 5.2 version (and all previous), we required that UGRD
be
> > > immediately followed by VGRD ***AT THE SAME LEVEL*** for VL1L2
output.
> > > This made the book-keeping in the code a lot simpler. However,
when we
> > > added support for an array of level entries, this convention
made
> > computing
> > > VL1L2 output a lot more tedious. Look at this example:
> > >
> > > field = [
> > > { name = "UGRD"; level = [ "P1000", "P850", "P700" ]; },
> > > { name = "VGRD"; level = [ "P1000", "P850", "P700" ]; }
> > > ];
> > >
> > > Here we have UGRD followed by VGRD, but not at the same levels.
This
> > gets
> > > expanded in the code to look like this:
> > > UGRD/P1000, UGRD/P850, UGRD/P700, VGRD/P1000, VGRD/P850,
VGRD/P700
> > >
> > > So they're not in the expected order and you get no VL1L2
output.
> > >
> > > To test, please try specifying it this long way and make sure
that you
> > get
> > > VL1L2 output:
> > >
> > > field = [
> > > { name = "UGRD"; level = [ "P1000" ]; },
> > > { name = "VGRD"; level = [ "P1000" ]; },
> > > { name = "UGRD"; level = [ "P850" ]; },
> > > { name = "VGRD"; level = [ "P850" ]; },
> > > { name = "UGRD"; level = [ "P700" ]; },
> > > { name = "VGRD"; level = [ "P700" ]; }
> > > ];
> > >
> > > Once you start using version 6.0, this isn't required. We made
the
> code
> > > smart enough for each UGRD field to hunt around and find it's
VGRD
> > partner,
> > > regardless of the order.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list