[Met_help] [rt.rap.ucar.edu #83032] History for verifying VIS (and other "surface" items)
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:04:06 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi, there,
New question on a new topic. I am trying to verify visibility and having
some issues. I think this is something that you might have discussed
previously but I need my memory refreshed.
In the observed BUFR file, the variable for visibility is "HOVI".
Originally in the variable obs_grib_code in PB2NC, I had VIS and visibility
was never plotted out. I surmised that this is because there is no
variable "VIS" in the observations.
I went into one of Ben's parm files and noticed that he had a line similar
to this one, which I added into my PB2NC:
obs_var_map = [
{ key = "HOVI"; val = "VIS"; },
];
To cover my bases, I added this to the point_stat config file:
fcst = {
field = [
{
name = "VIS";
level = "Z0";
cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
};
];
}
obs = [
{
name = "HOVI";
level = "Z0";
cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
};
];
I made the 2nd change above before I added the obs_var_map variable into
the PB2NC parm file. None of these combinations got me any verification of
visibility.
Questions:
1) Is Z0 the correct level for this?
2) Is this something that I can only do if using the MET 6.1 beta? To be
honest I'm not entirely positive I am linking to the MET 6.1 beta and might
need some help setting that up.
Thanks!
Perry
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: John Halley Gotway
Time: Thu Nov 16 13:06:40 2017
Perry (and Julie),
Julie, could you please forward Perry the instructions you sent out
for
running the met-6.1 beta versions on WCOSS?
One of the enhancements in met-6.1_beta2 was adding support for the
"--version" command line argument.
I'd suggest using the latest beta version... beta3. And when you do,
you
can run something like:
point_stat --version
And you'll see this type of information:
MET Version: V6.1
Repository: https://svn-met-dev.cgd.ucar.edu/tags/met/met-
6.1_beta3
Revision: 5020
Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
That'll confirm the version info.
Thanks,
John
On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: verifying VIS (and other "surface" items)
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>
>
> Hi, there,
>
> New question on a new topic. I am trying to verify visibility and
having
> some issues. I think this is something that you might have
discussed
> previously but I need my memory refreshed.
>
> In the observed BUFR file, the variable for visibility is "HOVI".
> Originally in the variable obs_grib_code in PB2NC, I had VIS and
visibility
> was never plotted out. I surmised that this is because there is no
> variable "VIS" in the observations.
>
> I went into one of Ben's parm files and noticed that he had a line
similar
> to this one, which I added into my PB2NC:
>
> obs_var_map = [
> { key = "HOVI"; val = "VIS"; },
> ];
>
> To cover my bases, I added this to the point_stat config file:
>
> fcst = {
> field = [
> {
> name = "VIS";
> level = "Z0";
> cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> };
> ];
>
> }
>
> obs = [
> {
> name = "HOVI";
> level = "Z0";
> cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> };
> ];
>
> I made the 2nd change above before I added the obs_var_map variable
into
> the PB2NC parm file. None of these combinations got me any
verification of
> visibility.
>
> Questions:
>
> 1) Is Z0 the correct level for this?
>
> 2) Is this something that I can only do if using the MET 6.1 beta?
To be
> honest I'm not entirely positive I am linking to the MET 6.1 beta
and might
> need some help setting that up.
>
> Thanks!
>
> Perry
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: Julie Prestopnik
Time: Thu Nov 16 13:15:19 2017
Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and met-6.1_beta3
on
gyre and surge. I've given instructions for the latest and greatest
here,
but you could load an earlier version if you would like to.
I'll be able to get met-6.1_beta3 installed on tide/luna once the
production switch occurs.
On gyre, please run the following to access this latest version:
module use /global/noscrub/Julie.Prestopnik/modulefiles
module load met/6.1_beta3
On surge, please run the following to access this latest version:
module use /gpfs/hps3/emc/global/noscrub/Julie.Prestopnik/modulefiles
module load met/6.1_beta3
Please let me know if you have any questions about or problems with
the
installs.
Thanks,
Julie
On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>
> Perry (and Julie),
>
> Julie, could you please forward Perry the instructions you sent out
for
> running the met-6.1 beta versions on WCOSS?
>
> One of the enhancements in met-6.1_beta2 was adding support for the
> "--version" command line argument.
>
> I'd suggest using the latest beta version... beta3. And when you
do, you
> can run something like:
>
> point_stat --version
>
> And you'll see this type of information:
>
> MET Version: V6.1
> Repository: https://svn-met-dev.cgd.ucar.edu/tags/met/met-
6.1_beta3
> Revision: 5020
> Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
>
> That'll confirm the version info.
>
> Thanks,
> John
>
> On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > Transaction: Ticket created by perry.shafran at noaa.gov
> > Queue: met_help
> > Subject: verifying VIS (and other "surface" items)
> > Owner: Nobody
> > Requestors: perry.shafran at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >
> >
> > Hi, there,
> >
> > New question on a new topic. I am trying to verify visibility and
having
> > some issues. I think this is something that you might have
discussed
> > previously but I need my memory refreshed.
> >
> > In the observed BUFR file, the variable for visibility is "HOVI".
> > Originally in the variable obs_grib_code in PB2NC, I had VIS and
> visibility
> > was never plotted out. I surmised that this is because there is
no
> > variable "VIS" in the observations.
> >
> > I went into one of Ben's parm files and noticed that he had a line
> similar
> > to this one, which I added into my PB2NC:
> >
> > obs_var_map = [
> > { key = "HOVI"; val = "VIS"; },
> > ];
> >
> > To cover my bases, I added this to the point_stat config file:
> >
> > fcst = {
> > field = [
> > {
> > name = "VIS";
> > level = "Z0";
> > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > };
> > ];
> >
> > }
> >
> > obs = [
> > {
> > name = "HOVI";
> > level = "Z0";
> > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > };
> > ];
> >
> > I made the 2nd change above before I added the obs_var_map
variable into
> > the PB2NC parm file. None of these combinations got me any
verification
> of
> > visibility.
> >
> > Questions:
> >
> > 1) Is Z0 the correct level for this?
> >
> > 2) Is this something that I can only do if using the MET 6.1
beta? To
> be
> > honest I'm not entirely positive I am linking to the MET 6.1 beta
and
> might
> > need some help setting that up.
> >
> > Thanks!
> >
> > Perry
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: perry.shafran at noaa.gov
Time: Thu Nov 16 13:17:26 2017
Hi, Julie,
Thanks! I'm sure you sent these instructions before, but somehow they
got
lost in the email threads and I guess I needed a reminder.
I think that the latest version is the best. Any reason I would want
an
older version?
Thanks!
Perry
On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and met-6.1_beta3
on
> gyre and surge. I've given instructions for the latest and greatest
here,
> but you could load an earlier version if you would like to.
>
> I'll be able to get met-6.1_beta3 installed on tide/luna once the
> production switch occurs.
>
> On gyre, please run the following to access this latest version:
>
> module use /global/noscrub/Julie.Prestopnik/modulefiles
> module load met/6.1_beta3
>
> On surge, please run the following to access this latest version:
>
> module use
/gpfs/hps3/emc/global/noscrub/Julie.Prestopnik/modulefiles
> module load met/6.1_beta3
> Please let me know if you have any questions about or problems with
the
> installs.
>
> Thanks,
> Julie
>
> On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >
> > Perry (and Julie),
> >
> > Julie, could you please forward Perry the instructions you sent
out for
> > running the met-6.1 beta versions on WCOSS?
> >
> > One of the enhancements in met-6.1_beta2 was adding support for
the
> > "--version" command line argument.
> >
> > I'd suggest using the latest beta version... beta3. And when you
do, you
> > can run something like:
> >
> > point_stat --version
> >
> > And you'll see this type of information:
> >
> > MET Version: V6.1
> > Repository: https://svn-met-dev.cgd.ucar.
> edu/tags/met/met-6.1_beta3
> > Revision: 5020
> > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
> >
> > That'll confirm the version info.
> >
> > Thanks,
> > John
> >
> > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > Queue: met_help
> > > Subject: verifying VIS (and other "surface" items)
> > > Owner: Nobody
> > > Requestors: perry.shafran at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032
> >
> > >
> > >
> > > Hi, there,
> > >
> > > New question on a new topic. I am trying to verify visibility
and
> having
> > > some issues. I think this is something that you might have
discussed
> > > previously but I need my memory refreshed.
> > >
> > > In the observed BUFR file, the variable for visibility is
"HOVI".
> > > Originally in the variable obs_grib_code in PB2NC, I had VIS and
> > visibility
> > > was never plotted out. I surmised that this is because there is
no
> > > variable "VIS" in the observations.
> > >
> > > I went into one of Ben's parm files and noticed that he had a
line
> > similar
> > > to this one, which I added into my PB2NC:
> > >
> > > obs_var_map = [
> > > { key = "HOVI"; val = "VIS"; },
> > > ];
> > >
> > > To cover my bases, I added this to the point_stat config file:
> > >
> > > fcst = {
> > > field = [
> > > {
> > > name = "VIS";
> > > level = "Z0";
> > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > };
> > > ];
> > >
> > > }
> > >
> > > obs = [
> > > {
> > > name = "HOVI";
> > > level = "Z0";
> > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > };
> > > ];
> > >
> > > I made the 2nd change above before I added the obs_var_map
variable
> into
> > > the PB2NC parm file. None of these combinations got me any
> verification
> > of
> > > visibility.
> > >
> > > Questions:
> > >
> > > 1) Is Z0 the correct level for this?
> > >
> > > 2) Is this something that I can only do if using the MET 6.1
beta? To
> > be
> > > honest I'm not entirely positive I am linking to the MET 6.1
beta and
> > might
> > > need some help setting that up.
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: Julie Prestopnik
Time: Thu Nov 16 13:21:21 2017
No worries! It was no problem to send them.
I can't think of a reason you would want an earlier version either,
but
just wanted to let you know it was an option if you wanted it for some
reason. :)
Julie
On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>
> Hi, Julie,
>
> Thanks! I'm sure you sent these instructions before, but somehow
they got
> lost in the email threads and I guess I needed a reminder.
>
> I think that the latest version is the best. Any reason I would
want an
> older version?
>
> Thanks!
>
> Perry
>
> On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and met-
6.1_beta3 on
> > gyre and surge. I've given instructions for the latest and
greatest
> here,
> > but you could load an earlier version if you would like to.
> >
> > I'll be able to get met-6.1_beta3 installed on tide/luna once the
> > production switch occurs.
> >
> > On gyre, please run the following to access this latest version:
> >
> > module use /global/noscrub/Julie.Prestopnik/modulefiles
> > module load met/6.1_beta3
> >
> > On surge, please run the following to access this latest version:
> >
> > module use
/gpfs/hps3/emc/global/noscrub/Julie.Prestopnik/modulefiles
> > module load met/6.1_beta3
> > Please let me know if you have any questions about or problems
with the
> > installs.
> >
> > Thanks,
> > Julie
> >
> > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> > >
> > > Perry (and Julie),
> > >
> > > Julie, could you please forward Perry the instructions you sent
out for
> > > running the met-6.1 beta versions on WCOSS?
> > >
> > > One of the enhancements in met-6.1_beta2 was adding support for
the
> > > "--version" command line argument.
> > >
> > > I'd suggest using the latest beta version... beta3. And when
you do,
> you
> > > can run something like:
> > >
> > > point_stat --version
> > >
> > > And you'll see this type of information:
> > >
> > > MET Version: V6.1
> > > Repository: https://svn-met-dev.cgd.ucar.
> > edu/tags/met/met-6.1_beta3
> > > Revision: 5020
> > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
> > >
> > > That'll confirm the version info.
> > >
> > > Thanks,
> > > John
> > >
> > > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > Queue: met_help
> > > > Subject: verifying VIS (and other "surface" items)
> > > > Owner: Nobody
> > > > Requestors: perry.shafran at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83032
> > >
> > > >
> > > >
> > > > Hi, there,
> > > >
> > > > New question on a new topic. I am trying to verify visibility
and
> > having
> > > > some issues. I think this is something that you might have
discussed
> > > > previously but I need my memory refreshed.
> > > >
> > > > In the observed BUFR file, the variable for visibility is
"HOVI".
> > > > Originally in the variable obs_grib_code in PB2NC, I had VIS
and
> > > visibility
> > > > was never plotted out. I surmised that this is because there
is no
> > > > variable "VIS" in the observations.
> > > >
> > > > I went into one of Ben's parm files and noticed that he had a
line
> > > similar
> > > > to this one, which I added into my PB2NC:
> > > >
> > > > obs_var_map = [
> > > > { key = "HOVI"; val = "VIS"; },
> > > > ];
> > > >
> > > > To cover my bases, I added this to the point_stat config file:
> > > >
> > > > fcst = {
> > > > field = [
> > > > {
> > > > name = "VIS";
> > > > level = "Z0";
> > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > };
> > > > ];
> > > >
> > > > }
> > > >
> > > > obs = [
> > > > {
> > > > name = "HOVI";
> > > > level = "Z0";
> > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > };
> > > > ];
> > > >
> > > > I made the 2nd change above before I added the obs_var_map
variable
> > into
> > > > the PB2NC parm file. None of these combinations got me any
> > verification
> > > of
> > > > visibility.
> > > >
> > > > Questions:
> > > >
> > > > 1) Is Z0 the correct level for this?
> > > >
> > > > 2) Is this something that I can only do if using the MET 6.1
beta?
> To
> > > be
> > > > honest I'm not entirely positive I am linking to the MET 6.1
beta and
> > > might
> > > > need some help setting that up.
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: perry.shafran at noaa.gov
Time: Thu Nov 16 13:48:54 2017
OK, we're closer but I'm still not getting any pairs for visibility.
I have this line in my PB2NC config file. This should equate HOVI
with
VIS, yes? Is there something else I am missing in either PB2NC or
point_stat?
obs_var_map = [
{ key = "HOVI"; val = "VIS"; }
];
Thanks!
Perry
On Thu, Nov 16, 2017 at 3:21 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> No worries! It was no problem to send them.
>
> I can't think of a reason you would want an earlier version either,
but
> just wanted to let you know it was an option if you wanted it for
some
> reason. :)
>
> Julie
>
> On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >
> > Hi, Julie,
> >
> > Thanks! I'm sure you sent these instructions before, but somehow
they
> got
> > lost in the email threads and I guess I needed a reminder.
> >
> > I think that the latest version is the best. Any reason I would
want an
> > older version?
> >
> > Thanks!
> >
> > Perry
> >
> > On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and met-
6.1_beta3 on
> > > gyre and surge. I've given instructions for the latest and
greatest
> > here,
> > > but you could load an earlier version if you would like to.
> > >
> > > I'll be able to get met-6.1_beta3 installed on tide/luna once
the
> > > production switch occurs.
> > >
> > > On gyre, please run the following to access this latest version:
> > >
> > > module use /global/noscrub/Julie.Prestopnik/modulefiles
> > > module load met/6.1_beta3
> > >
> > > On surge, please run the following to access this latest
version:
> > >
> > > module use
/gpfs/hps3/emc/global/noscrub/Julie.Prestopnik/modulefiles
> > > module load met/6.1_beta3
> > > Please let me know if you have any questions about or problems
with the
> > > installs.
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032
>
> > > >
> > > > Perry (and Julie),
> > > >
> > > > Julie, could you please forward Perry the instructions you
sent out
> for
> > > > running the met-6.1 beta versions on WCOSS?
> > > >
> > > > One of the enhancements in met-6.1_beta2 was adding support
for the
> > > > "--version" command line argument.
> > > >
> > > > I'd suggest using the latest beta version... beta3. And when
you do,
> > you
> > > > can run something like:
> > > >
> > > > point_stat --version
> > > >
> > > > And you'll see this type of information:
> > > >
> > > > MET Version: V6.1
> > > > Repository: https://svn-met-dev.cgd.ucar.
> > > edu/tags/met/met-6.1_beta3
> > > > Revision: 5020
> > > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
> > > >
> > > > That'll confirm the version info.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via
RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: verifying VIS (and other "surface" items)
> > > > > Owner: Nobody
> > > > > Requestors: perry.shafran at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=83032
> > > >
> > > > >
> > > > >
> > > > > Hi, there,
> > > > >
> > > > > New question on a new topic. I am trying to verify
visibility and
> > > having
> > > > > some issues. I think this is something that you might have
> discussed
> > > > > previously but I need my memory refreshed.
> > > > >
> > > > > In the observed BUFR file, the variable for visibility is
"HOVI".
> > > > > Originally in the variable obs_grib_code in PB2NC, I had VIS
and
> > > > visibility
> > > > > was never plotted out. I surmised that this is because
there is no
> > > > > variable "VIS" in the observations.
> > > > >
> > > > > I went into one of Ben's parm files and noticed that he had
a line
> > > > similar
> > > > > to this one, which I added into my PB2NC:
> > > > >
> > > > > obs_var_map = [
> > > > > { key = "HOVI"; val = "VIS"; },
> > > > > ];
> > > > >
> > > > > To cover my bases, I added this to the point_stat config
file:
> > > > >
> > > > > fcst = {
> > > > > field = [
> > > > > {
> > > > > name = "VIS";
> > > > > level = "Z0";
> > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > };
> > > > > ];
> > > > >
> > > > > }
> > > > >
> > > > > obs = [
> > > > > {
> > > > > name = "HOVI";
> > > > > level = "Z0";
> > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > };
> > > > > ];
> > > > >
> > > > > I made the 2nd change above before I added the obs_var_map
variable
> > > into
> > > > > the PB2NC parm file. None of these combinations got me any
> > > verification
> > > > of
> > > > > visibility.
> > > > >
> > > > > Questions:
> > > > >
> > > > > 1) Is Z0 the correct level for this?
> > > > >
> > > > > 2) Is this something that I can only do if using the MET
6.1 beta?
> > To
> > > > be
> > > > > honest I'm not entirely positive I am linking to the MET 6.1
beta
> and
> > > > might
> > > > > need some help setting that up.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: John Halley Gotway
Time: Thu Nov 16 14:53:47 2017
Perry,
I suspect that the name of the config file options have changed during
development and that's the source of the confusion. Looking in the
met-6.1_beta3 default config file for PB2NC, there are 2 important
settings:
"obs_bufr_var" and "obs_bufr_map"
That's different from "obs_var_map" that you're referencing.
Please try doing the following 4 things:
(1) In the PB2NC config file, add HOVI to the list of bufr variables
to be
extracted:
obs_bufr_var = [ "QOB", "TOB", "ZOB", "UOB", "VOB", "HOVI" ];
(2) In the PB2NC config file, specify the renaming that you'd like to
do:
HOVI -> VIS
obs_bufr_map = [
{ key = "HOVI"; val = "VIS"; }
];
(3) Re-run PB2NC.
(4) Run plot_point_obs to see if you have any instances of VIS showing
up
in the output file:
met-6.1_beta3/bin/plot_point_obs \
ndas.t00z.prepbufr.tm12.20070401.nc \
vis_obs.ps -obs_var VIS
I've attached a png image showing the plot_point_obs output from
running
these steps on a sample NDAS file.
Thanks,
John
On Thu, Nov 16, 2017 at 1:48 PM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>
> OK, we're closer but I'm still not getting any pairs for visibility.
>
> I have this line in my PB2NC config file. This should equate HOVI
with
> VIS, yes? Is there something else I am missing in either PB2NC or
> point_stat?
>
> obs_var_map = [
> { key = "HOVI"; val = "VIS"; }
> ];
>
> Thanks!
>
> Perry
>
> On Thu, Nov 16, 2017 at 3:21 PM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> wrote:
>
> > No worries! It was no problem to send them.
> >
> > I can't think of a reason you would want an earlier version
either, but
> > just wanted to let you know it was an option if you wanted it for
some
> > reason. :)
> >
> > Julie
> >
> > On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> > >
> > > Hi, Julie,
> > >
> > > Thanks! I'm sure you sent these instructions before, but
somehow they
> > got
> > > lost in the email threads and I guess I needed a reminder.
> > >
> > > I think that the latest version is the best. Any reason I would
want
> an
> > > older version?
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and met-
6.1_beta3
> on
> > > > gyre and surge. I've given instructions for the latest and
greatest
> > > here,
> > > > but you could load an earlier version if you would like to.
> > > >
> > > > I'll be able to get met-6.1_beta3 installed on tide/luna once
the
> > > > production switch occurs.
> > > >
> > > > On gyre, please run the following to access this latest
version:
> > > >
> > > > module use /global/noscrub/Julie.Prestopnik/modulefiles
> > > > module load met/6.1_beta3
> > > >
> > > > On surge, please run the following to access this latest
version:
> > > >
> > > > module use /gpfs/hps3/emc/global/noscrub/
> Julie.Prestopnik/modulefiles
> > > > module load met/6.1_beta3
> > > > Please let me know if you have any questions about or problems
with
> the
> > > > installs.
> > > >
> > > > Thanks,
> > > > Julie
> > > >
> > > > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> > > > >
> > > > > Perry (and Julie),
> > > > >
> > > > > Julie, could you please forward Perry the instructions you
sent out
> > for
> > > > > running the met-6.1 beta versions on WCOSS?
> > > > >
> > > > > One of the enhancements in met-6.1_beta2 was adding support
for the
> > > > > "--version" command line argument.
> > > > >
> > > > > I'd suggest using the latest beta version... beta3. And
when you
> do,
> > > you
> > > > > can run something like:
> > > > >
> > > > > point_stat --version
> > > > >
> > > > > And you'll see this type of information:
> > > > >
> > > > > MET Version: V6.1
> > > > > Repository: https://svn-met-dev.cgd.ucar.
> > > > edu/tags/met/met-6.1_beta3
> > > > > Revision: 5020
> > > > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct 2017)
> > > > >
> > > > > That'll confirm the version info.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov via
RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: verifying VIS (and other "surface" items)
> > > > > > Owner: Nobody
> > > > > > Requestors: perry.shafran at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=83032
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi, there,
> > > > > >
> > > > > > New question on a new topic. I am trying to verify
visibility
> and
> > > > having
> > > > > > some issues. I think this is something that you might
have
> > discussed
> > > > > > previously but I need my memory refreshed.
> > > > > >
> > > > > > In the observed BUFR file, the variable for visibility is
"HOVI".
> > > > > > Originally in the variable obs_grib_code in PB2NC, I had
VIS and
> > > > > visibility
> > > > > > was never plotted out. I surmised that this is because
there is
> no
> > > > > > variable "VIS" in the observations.
> > > > > >
> > > > > > I went into one of Ben's parm files and noticed that he
had a
> line
> > > > > similar
> > > > > > to this one, which I added into my PB2NC:
> > > > > >
> > > > > > obs_var_map = [
> > > > > > { key = "HOVI"; val = "VIS"; },
> > > > > > ];
> > > > > >
> > > > > > To cover my bases, I added this to the point_stat config
file:
> > > > > >
> > > > > > fcst = {
> > > > > > field = [
> > > > > > {
> > > > > > name = "VIS";
> > > > > > level = "Z0";
> > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > > };
> > > > > > ];
> > > > > >
> > > > > > }
> > > > > >
> > > > > > obs = [
> > > > > > {
> > > > > > name = "HOVI";
> > > > > > level = "Z0";
> > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > > };
> > > > > > ];
> > > > > >
> > > > > > I made the 2nd change above before I added the obs_var_map
> variable
> > > > into
> > > > > > the PB2NC parm file. None of these combinations got me
any
> > > > verification
> > > > > of
> > > > > > visibility.
> > > > > >
> > > > > > Questions:
> > > > > >
> > > > > > 1) Is Z0 the correct level for this?
> > > > > >
> > > > > > 2) Is this something that I can only do if using the MET
6.1
> beta?
> > > To
> > > > > be
> > > > > > honest I'm not entirely positive I am linking to the MET
6.1 beta
> > and
> > > > > might
> > > > > > need some help setting that up.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: perry.shafran at noaa.gov
Time: Fri Nov 17 06:41:32 2017
Hi, John,
That's the process I think I am looking for. I knew some variables
had
changed.
Thanks!
Perry
On Thu, Nov 16, 2017 at 4:53 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Perry,
>
> I suspect that the name of the config file options have changed
during
> development and that's the source of the confusion. Looking in the
> met-6.1_beta3 default config file for PB2NC, there are 2 important
> settings:
> "obs_bufr_var" and "obs_bufr_map"
>
> That's different from "obs_var_map" that you're referencing.
>
> Please try doing the following 4 things:
>
> (1) In the PB2NC config file, add HOVI to the list of bufr variables
to be
> extracted:
>
> obs_bufr_var = [ "QOB", "TOB", "ZOB", "UOB", "VOB", "HOVI" ];
>
> (2) In the PB2NC config file, specify the renaming that you'd like
to do:
> HOVI -> VIS
>
> obs_bufr_map = [
> { key = "HOVI"; val = "VIS"; }
> ];
>
> (3) Re-run PB2NC.
>
> (4) Run plot_point_obs to see if you have any instances of VIS
showing up
> in the output file:
>
> met-6.1_beta3/bin/plot_point_obs \
> ndas.t00z.prepbufr.tm12.20070401.nc \
> vis_obs.ps -obs_var VIS
>
> I've attached a png image showing the plot_point_obs output from
running
> these steps on a sample NDAS file.
>
> Thanks,
> John
>
>
> On Thu, Nov 16, 2017 at 1:48 PM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >
> > OK, we're closer but I'm still not getting any pairs for
visibility.
> >
> > I have this line in my PB2NC config file. This should equate HOVI
with
> > VIS, yes? Is there something else I am missing in either PB2NC or
> > point_stat?
> >
> > obs_var_map = [
> > { key = "HOVI"; val = "VIS"; }
> > ];
> >
> > Thanks!
> >
> > Perry
> >
> > On Thu, Nov 16, 2017 at 3:21 PM, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > No worries! It was no problem to send them.
> > >
> > > I can't think of a reason you would want an earlier version
either, but
> > > just wanted to let you know it was an option if you wanted it
for some
> > > reason. :)
> > >
> > > Julie
> > >
> > > On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032
>
> > > >
> > > > Hi, Julie,
> > > >
> > > > Thanks! I'm sure you sent these instructions before, but
somehow
> they
> > > got
> > > > lost in the email threads and I guess I needed a reminder.
> > > >
> > > > I think that the latest version is the best. Any reason I
would want
> > an
> > > > older version?
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > > On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and
> met-6.1_beta3
> > on
> > > > > gyre and surge. I've given instructions for the latest and
> greatest
> > > > here,
> > > > > but you could load an earlier version if you would like to.
> > > > >
> > > > > I'll be able to get met-6.1_beta3 installed on tide/luna
once the
> > > > > production switch occurs.
> > > > >
> > > > > On gyre, please run the following to access this latest
version:
> > > > >
> > > > > module use /global/noscrub/Julie.Prestopnik/modulefiles
> > > > > module load met/6.1_beta3
> > > > >
> > > > > On surge, please run the following to access this latest
version:
> > > > >
> > > > > module use /gpfs/hps3/emc/global/noscrub/
> > Julie.Prestopnik/modulefiles
> > > > > module load met/6.1_beta3
> > > > > Please let me know if you have any questions about or
problems with
> > the
> > > > > installs.
> > > > >
> > > > > Thanks,
> > > > > Julie
> > > > >
> > > > > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> > > > > >
> > > > > > Perry (and Julie),
> > > > > >
> > > > > > Julie, could you please forward Perry the instructions you
sent
> out
> > > for
> > > > > > running the met-6.1 beta versions on WCOSS?
> > > > > >
> > > > > > One of the enhancements in met-6.1_beta2 was adding
support for
> the
> > > > > > "--version" command line argument.
> > > > > >
> > > > > > I'd suggest using the latest beta version... beta3. And
when you
> > do,
> > > > you
> > > > > > can run something like:
> > > > > >
> > > > > > point_stat --version
> > > > > >
> > > > > > And you'll see this type of information:
> > > > > >
> > > > > > MET Version: V6.1
> > > > > > Repository: https://svn-met-dev.cgd.ucar.
> > > > > edu/tags/met/met-6.1_beta3
> > > > > > Revision: 5020
> > > > > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct
2017)
> > > > > >
> > > > > > That'll confirm the version info.
> > > > > >
> > > > > > Thanks,
> > > > > > John
> > > > > >
> > > > > > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov
via RT
> <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
> > > > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > > > Queue: met_help
> > > > > > > Subject: verifying VIS (and other "surface" items)
> > > > > > > Owner: Nobody
> > > > > > > Requestors: perry.shafran at noaa.gov
> > > > > > > Status: new
> > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > > Ticket/Display.html?id=83032
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi, there,
> > > > > > >
> > > > > > > New question on a new topic. I am trying to verify
visibility
> > and
> > > > > having
> > > > > > > some issues. I think this is something that you might
have
> > > discussed
> > > > > > > previously but I need my memory refreshed.
> > > > > > >
> > > > > > > In the observed BUFR file, the variable for visibility
is
> "HOVI".
> > > > > > > Originally in the variable obs_grib_code in PB2NC, I had
VIS
> and
> > > > > > visibility
> > > > > > > was never plotted out. I surmised that this is because
there
> is
> > no
> > > > > > > variable "VIS" in the observations.
> > > > > > >
> > > > > > > I went into one of Ben's parm files and noticed that he
had a
> > line
> > > > > > similar
> > > > > > > to this one, which I added into my PB2NC:
> > > > > > >
> > > > > > > obs_var_map = [
> > > > > > > { key = "HOVI"; val = "VIS"; },
> > > > > > > ];
> > > > > > >
> > > > > > > To cover my bases, I added this to the point_stat config
file:
> > > > > > >
> > > > > > > fcst = {
> > > > > > > field = [
> > > > > > > {
> > > > > > > name = "VIS";
> > > > > > > level = "Z0";
> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > > > };
> > > > > > > ];
> > > > > > >
> > > > > > > }
> > > > > > >
> > > > > > > obs = [
> > > > > > > {
> > > > > > > name = "HOVI";
> > > > > > > level = "Z0";
> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
> > > > > > > };
> > > > > > > ];
> > > > > > >
> > > > > > > I made the 2nd change above before I added the
obs_var_map
> > variable
> > > > > into
> > > > > > > the PB2NC parm file. None of these combinations got me
any
> > > > > verification
> > > > > > of
> > > > > > > visibility.
> > > > > > >
> > > > > > > Questions:
> > > > > > >
> > > > > > > 1) Is Z0 the correct level for this?
> > > > > > >
> > > > > > > 2) Is this something that I can only do if using the
MET 6.1
> > beta?
> > > > To
> > > > > > be
> > > > > > > honest I'm not entirely positive I am linking to the MET
6.1
> beta
> > > and
> > > > > > might
> > > > > > > need some help setting that up.
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Perry
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: perry.shafran at noaa.gov
Time: Fri Nov 17 08:40:38 2017
Ah, I finally got the visibility statistics! I think the new PB2NC
options
will be a big help going forward.
Thanks!
Perry
On Fri, Nov 17, 2017 at 8:41 AM, Perry Shafran - NOAA Affiliate <
perry.shafran at noaa.gov> wrote:
> Hi, John,
>
> That's the process I think I am looking for. I knew some variables
had
> changed.
>
> Thanks!
>
> Perry
>
> On Thu, Nov 16, 2017 at 4:53 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Perry,
>>
>> I suspect that the name of the config file options have changed
during
>> development and that's the source of the confusion. Looking in the
>> met-6.1_beta3 default config file for PB2NC, there are 2 important
>> settings:
>> "obs_bufr_var" and "obs_bufr_map"
>>
>> That's different from "obs_var_map" that you're referencing.
>>
>> Please try doing the following 4 things:
>>
>> (1) In the PB2NC config file, add HOVI to the list of bufr
variables to be
>> extracted:
>>
>> obs_bufr_var = [ "QOB", "TOB", "ZOB", "UOB", "VOB", "HOVI" ];
>>
>> (2) In the PB2NC config file, specify the renaming that you'd like
to do:
>> HOVI -> VIS
>>
>> obs_bufr_map = [
>> { key = "HOVI"; val = "VIS"; }
>> ];
>>
>> (3) Re-run PB2NC.
>>
>> (4) Run plot_point_obs to see if you have any instances of VIS
showing up
>> in the output file:
>>
>> met-6.1_beta3/bin/plot_point_obs \
>> ndas.t00z.prepbufr.tm12.20070401.nc \
>> vis_obs.ps -obs_var VIS
>>
>> I've attached a png image showing the plot_point_obs output from
running
>> these steps on a sample NDAS file.
>>
>> Thanks,
>> John
>>
>>
>> On Thu, Nov 16, 2017 at 1:48 PM, perry.shafran at noaa.gov via RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>> >
>> > OK, we're closer but I'm still not getting any pairs for
visibility.
>> >
>> > I have this line in my PB2NC config file. This should equate
HOVI with
>> > VIS, yes? Is there something else I am missing in either PB2NC
or
>> > point_stat?
>> >
>> > obs_var_map = [
>> > { key = "HOVI"; val = "VIS"; }
>> > ];
>> >
>> > Thanks!
>> >
>> > Perry
>> >
>> > On Thu, Nov 16, 2017 at 3:21 PM, Julie Prestopnik via RT <
>> > met_help at ucar.edu>
>> > wrote:
>> >
>> > > No worries! It was no problem to send them.
>> > >
>> > > I can't think of a reason you would want an earlier version
either,
>> but
>> > > just wanted to let you know it was an option if you wanted it
for some
>> > > reason. :)
>> > >
>> > > Julie
>> > >
>> > > On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via RT
<
>> > > met_help at ucar.edu> wrote:
>> > >
>> > > >
>> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032
>
>> > > >
>> > > > Hi, Julie,
>> > > >
>> > > > Thanks! I'm sure you sent these instructions before, but
somehow
>> they
>> > > got
>> > > > lost in the email threads and I guess I needed a reminder.
>> > > >
>> > > > I think that the latest version is the best. Any reason I
would
>> want
>> > an
>> > > > older version?
>> > > >
>> > > > Thanks!
>> > > >
>> > > > Perry
>> > > >
>> > > > On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
>> > > > met_help at ucar.edu>
>> > > > wrote:
>> > > >
>> > > > > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and
>> met-6.1_beta3
>> > on
>> > > > > gyre and surge. I've given instructions for the latest and
>> greatest
>> > > > here,
>> > > > > but you could load an earlier version if you would like to.
>> > > > >
>> > > > > I'll be able to get met-6.1_beta3 installed on tide/luna
once the
>> > > > > production switch occurs.
>> > > > >
>> > > > > On gyre, please run the following to access this latest
version:
>> > > > >
>> > > > > module use /global/noscrub/Julie.Prestopnik/modulefiles
>> > > > > module load met/6.1_beta3
>> > > > >
>> > > > > On surge, please run the following to access this latest
version:
>> > > > >
>> > > > > module use /gpfs/hps3/emc/global/noscrub/
>> > Julie.Prestopnik/modulefiles
>> > > > > module load met/6.1_beta3
>> > > > > Please let me know if you have any questions about or
problems
>> with
>> > the
>> > > > > installs.
>> > > > >
>> > > > > Thanks,
>> > > > > Julie
>> > > > >
>> > > > > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via RT
<
>> > > > > met_help at ucar.edu> wrote:
>> > > > >
>> > > > > >
>> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>> > > > > >
>> > > > > > Perry (and Julie),
>> > > > > >
>> > > > > > Julie, could you please forward Perry the instructions
you sent
>> out
>> > > for
>> > > > > > running the met-6.1 beta versions on WCOSS?
>> > > > > >
>> > > > > > One of the enhancements in met-6.1_beta2 was adding
support for
>> the
>> > > > > > "--version" command line argument.
>> > > > > >
>> > > > > > I'd suggest using the latest beta version... beta3. And
when
>> you
>> > do,
>> > > > you
>> > > > > > can run something like:
>> > > > > >
>> > > > > > point_stat --version
>> > > > > >
>> > > > > > And you'll see this type of information:
>> > > > > >
>> > > > > > MET Version: V6.1
>> > > > > > Repository: https://svn-met-dev.cgd.ucar.
>> > > > > edu/tags/met/met-6.1_beta3
>> > > > > > Revision: 5020
>> > > > > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct
2017)
>> > > > > >
>> > > > > > That'll confirm the version info.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > John
>> > > > > >
>> > > > > > On Wed, Nov 15, 2017 at 12:40 PM, perry.shafran at noaa.gov
via
>> RT <
>> > > > > > met_help at ucar.edu> wrote:
>> > > > > >
>> > > > > > >
>> > > > > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted upon.
>> > > > > > > Transaction: Ticket created by perry.shafran at noaa.gov
>> > > > > > > Queue: met_help
>> > > > > > > Subject: verifying VIS (and other "surface" items)
>> > > > > > > Owner: Nobody
>> > > > > > > Requestors: perry.shafran at noaa.gov
>> > > > > > > Status: new
>> > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
>> > > > Ticket/Display.html?id=83032
>> > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Hi, there,
>> > > > > > >
>> > > > > > > New question on a new topic. I am trying to verify
visibility
>> > and
>> > > > > having
>> > > > > > > some issues. I think this is something that you might
have
>> > > discussed
>> > > > > > > previously but I need my memory refreshed.
>> > > > > > >
>> > > > > > > In the observed BUFR file, the variable for visibility
is
>> "HOVI".
>> > > > > > > Originally in the variable obs_grib_code in PB2NC, I
had VIS
>> and
>> > > > > > visibility
>> > > > > > > was never plotted out. I surmised that this is because
there
>> is
>> > no
>> > > > > > > variable "VIS" in the observations.
>> > > > > > >
>> > > > > > > I went into one of Ben's parm files and noticed that he
had a
>> > line
>> > > > > > similar
>> > > > > > > to this one, which I added into my PB2NC:
>> > > > > > >
>> > > > > > > obs_var_map = [
>> > > > > > > { key = "HOVI"; val = "VIS"; },
>> > > > > > > ];
>> > > > > > >
>> > > > > > > To cover my bases, I added this to the point_stat
config file:
>> > > > > > >
>> > > > > > > fcst = {
>> > > > > > > field = [
>> > > > > > > {
>> > > > > > > name = "VIS";
>> > > > > > > level = "Z0";
>> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
>> > > > > > > };
>> > > > > > > ];
>> > > > > > >
>> > > > > > > }
>> > > > > > >
>> > > > > > > obs = [
>> > > > > > > {
>> > > > > > > name = "HOVI";
>> > > > > > > level = "Z0";
>> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090 ];
>> > > > > > > };
>> > > > > > > ];
>> > > > > > >
>> > > > > > > I made the 2nd change above before I added the
obs_var_map
>> > variable
>> > > > > into
>> > > > > > > the PB2NC parm file. None of these combinations got me
any
>> > > > > verification
>> > > > > > of
>> > > > > > > visibility.
>> > > > > > >
>> > > > > > > Questions:
>> > > > > > >
>> > > > > > > 1) Is Z0 the correct level for this?
>> > > > > > >
>> > > > > > > 2) Is this something that I can only do if using the
MET 6.1
>> > beta?
>> > > > To
>> > > > > > be
>> > > > > > > honest I'm not entirely positive I am linking to the
MET 6.1
>> beta
>> > > and
>> > > > > > might
>> > > > > > > need some help setting that up.
>> > > > > > >
>> > > > > > > Thanks!
>> > > > > > >
>> > > > > > > Perry
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>
------------------------------------------------
Subject: verifying VIS (and other "surface" items)
From: John Halley Gotway
Time: Fri Nov 17 09:18:25 2017
Great, thanks for confirming.
I'll go ahead and resolve this ticket.
John
On Fri, Nov 17, 2017 at 8:40 AM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
>
> Ah, I finally got the visibility statistics! I think the new PB2NC
options
> will be a big help going forward.
>
> Thanks!
>
> Perry
>
> On Fri, Nov 17, 2017 at 8:41 AM, Perry Shafran - NOAA Affiliate <
> perry.shafran at noaa.gov> wrote:
>
> > Hi, John,
> >
> > That's the process I think I am looking for. I knew some
variables had
> > changed.
> >
> > Thanks!
> >
> > Perry
> >
> > On Thu, Nov 16, 2017 at 4:53 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Perry,
> >>
> >> I suspect that the name of the config file options have changed
during
> >> development and that's the source of the confusion. Looking in
the
> >> met-6.1_beta3 default config file for PB2NC, there are 2
important
> >> settings:
> >> "obs_bufr_var" and "obs_bufr_map"
> >>
> >> That's different from "obs_var_map" that you're referencing.
> >>
> >> Please try doing the following 4 things:
> >>
> >> (1) In the PB2NC config file, add HOVI to the list of bufr
variables to
> be
> >> extracted:
> >>
> >> obs_bufr_var = [ "QOB", "TOB", "ZOB", "UOB", "VOB", "HOVI" ];
> >>
> >> (2) In the PB2NC config file, specify the renaming that you'd
like to
> do:
> >> HOVI -> VIS
> >>
> >> obs_bufr_map = [
> >> { key = "HOVI"; val = "VIS"; }
> >> ];
> >>
> >> (3) Re-run PB2NC.
> >>
> >> (4) Run plot_point_obs to see if you have any instances of VIS
showing
> up
> >> in the output file:
> >>
> >> met-6.1_beta3/bin/plot_point_obs \
> >> ndas.t00z.prepbufr.tm12.20070401.nc \
> >> vis_obs.ps -obs_var VIS
> >>
> >> I've attached a png image showing the plot_point_obs output from
running
> >> these steps on a sample NDAS file.
> >>
> >> Thanks,
> >> John
> >>
> >>
> >> On Thu, Nov 16, 2017 at 1:48 PM, perry.shafran at noaa.gov via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >> >
> >> > OK, we're closer but I'm still not getting any pairs for
visibility.
> >> >
> >> > I have this line in my PB2NC config file. This should equate
HOVI
> with
> >> > VIS, yes? Is there something else I am missing in either PB2NC
or
> >> > point_stat?
> >> >
> >> > obs_var_map = [
> >> > { key = "HOVI"; val = "VIS"; }
> >> > ];
> >> >
> >> > Thanks!
> >> >
> >> > Perry
> >> >
> >> > On Thu, Nov 16, 2017 at 3:21 PM, Julie Prestopnik via RT <
> >> > met_help at ucar.edu>
> >> > wrote:
> >> >
> >> > > No worries! It was no problem to send them.
> >> > >
> >> > > I can't think of a reason you would want an earlier version
either,
> >> but
> >> > > just wanted to let you know it was an option if you wanted it
for
> some
> >> > > reason. :)
> >> > >
> >> > > Julie
> >> > >
> >> > > On Thu, Nov 16, 2017 at 1:17 PM, perry.shafran at noaa.gov via
RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > > >
> >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032 >
> >> > > >
> >> > > > Hi, Julie,
> >> > > >
> >> > > > Thanks! I'm sure you sent these instructions before, but
somehow
> >> they
> >> > > got
> >> > > > lost in the email threads and I guess I needed a reminder.
> >> > > >
> >> > > > I think that the latest version is the best. Any reason I
would
> >> want
> >> > an
> >> > > > older version?
> >> > > >
> >> > > > Thanks!
> >> > > >
> >> > > > Perry
> >> > > >
> >> > > > On Thu, Nov 16, 2017 at 3:15 PM, Julie Prestopnik via RT <
> >> > > > met_help at ucar.edu>
> >> > > > wrote:
> >> > > >
> >> > > > > Hi Perry. We have met-6.1_beta1, met-6.1_beta2, and
> >> met-6.1_beta3
> >> > on
> >> > > > > gyre and surge. I've given instructions for the latest
and
> >> greatest
> >> > > > here,
> >> > > > > but you could load an earlier version if you would like
to.
> >> > > > >
> >> > > > > I'll be able to get met-6.1_beta3 installed on tide/luna
once
> the
> >> > > > > production switch occurs.
> >> > > > >
> >> > > > > On gyre, please run the following to access this latest
version:
> >> > > > >
> >> > > > > module use /global/noscrub/Julie.Prestopnik/modulefiles
> >> > > > > module load met/6.1_beta3
> >> > > > >
> >> > > > > On surge, please run the following to access this latest
> version:
> >> > > > >
> >> > > > > module use /gpfs/hps3/emc/global/noscrub/
> >> > Julie.Prestopnik/modulefiles
> >> > > > > module load met/6.1_beta3
> >> > > > > Please let me know if you have any questions about or
problems
> >> with
> >> > the
> >> > > > > installs.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Julie
> >> > > > >
> >> > > > > On Thu, Nov 16, 2017 at 1:06 PM, John Halley Gotway via
RT <
> >> > > > > met_help at ucar.edu> wrote:
> >> > > > >
> >> > > > > >
> >> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83032
> >
> >> > > > > >
> >> > > > > > Perry (and Julie),
> >> > > > > >
> >> > > > > > Julie, could you please forward Perry the instructions
you
> sent
> >> out
> >> > > for
> >> > > > > > running the met-6.1 beta versions on WCOSS?
> >> > > > > >
> >> > > > > > One of the enhancements in met-6.1_beta2 was adding
support
> for
> >> the
> >> > > > > > "--version" command line argument.
> >> > > > > >
> >> > > > > > I'd suggest using the latest beta version... beta3.
And when
> >> you
> >> > do,
> >> > > > you
> >> > > > > > can run something like:
> >> > > > > >
> >> > > > > > point_stat --version
> >> > > > > >
> >> > > > > > And you'll see this type of information:
> >> > > > > >
> >> > > > > > MET Version: V6.1
> >> > > > > > Repository: https://svn-met-dev.cgd.ucar.
> >> > > > > edu/tags/met/met-6.1_beta3
> >> > > > > > Revision: 5020
> >> > > > > > Change Date: 2017-10-24 13:44:21 -0600 (Tue, 24 Oct
2017)
> >> > > > > >
> >> > > > > > That'll confirm the version info.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > John
> >> > > > > >
> >> > > > > > On Wed, Nov 15, 2017 at 12:40 PM,
perry.shafran at noaa.gov via
> >> RT <
> >> > > > > > met_help at ucar.edu> wrote:
> >> > > > > >
> >> > > > > > >
> >> > > > > > > Wed Nov 15 12:40:22 2017: Request 83032 was acted
upon.
> >> > > > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> >> > > > > > > Queue: met_help
> >> > > > > > > Subject: verifying VIS (and other "surface"
items)
> >> > > > > > > Owner: Nobody
> >> > > > > > > Requestors: perry.shafran at noaa.gov
> >> > > > > > > Status: new
> >> > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> >> > > > Ticket/Display.html?id=83032
> >> > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > Hi, there,
> >> > > > > > >
> >> > > > > > > New question on a new topic. I am trying to verify
> visibility
> >> > and
> >> > > > > having
> >> > > > > > > some issues. I think this is something that you
might have
> >> > > discussed
> >> > > > > > > previously but I need my memory refreshed.
> >> > > > > > >
> >> > > > > > > In the observed BUFR file, the variable for
visibility is
> >> "HOVI".
> >> > > > > > > Originally in the variable obs_grib_code in PB2NC, I
had VIS
> >> and
> >> > > > > > visibility
> >> > > > > > > was never plotted out. I surmised that this is
because
> there
> >> is
> >> > no
> >> > > > > > > variable "VIS" in the observations.
> >> > > > > > >
> >> > > > > > > I went into one of Ben's parm files and noticed that
he had
> a
> >> > line
> >> > > > > > similar
> >> > > > > > > to this one, which I added into my PB2NC:
> >> > > > > > >
> >> > > > > > > obs_var_map = [
> >> > > > > > > { key = "HOVI"; val = "VIS"; },
> >> > > > > > > ];
> >> > > > > > >
> >> > > > > > > To cover my bases, I added this to the point_stat
config
> file:
> >> > > > > > >
> >> > > > > > > fcst = {
> >> > > > > > > field = [
> >> > > > > > > {
> >> > > > > > > name = "VIS";
> >> > > > > > > level = "Z0";
> >> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090
];
> >> > > > > > > };
> >> > > > > > > ];
> >> > > > > > >
> >> > > > > > > }
> >> > > > > > >
> >> > > > > > > obs = [
> >> > > > > > > {
> >> > > > > > > name = "HOVI";
> >> > > > > > > level = "Z0";
> >> > > > > > > cat_thresh = [ >=800, >=1600, >=8046, >=16090
];
> >> > > > > > > };
> >> > > > > > > ];
> >> > > > > > >
> >> > > > > > > I made the 2nd change above before I added the
obs_var_map
> >> > variable
> >> > > > > into
> >> > > > > > > the PB2NC parm file. None of these combinations got
me any
> >> > > > > verification
> >> > > > > > of
> >> > > > > > > visibility.
> >> > > > > > >
> >> > > > > > > Questions:
> >> > > > > > >
> >> > > > > > > 1) Is Z0 the correct level for this?
> >> > > > > > >
> >> > > > > > > 2) Is this something that I can only do if using the
MET
> 6.1
> >> > beta?
> >> > > > To
> >> > > > > > be
> >> > > > > > > honest I'm not entirely positive I am linking to the
MET 6.1
> >> beta
> >> > > and
> >> > > > > > might
> >> > > > > > > need some help setting that up.
> >> > > > > > >
> >> > > > > > > Thanks!
> >> > > > > > >
> >> > > > > > > Perry
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list