[Met_help] [rt.rap.ucar.edu #74338] History for Running MET for NMMB output
John Halley Gotway via RT
met_help at ucar.edu
Thu Dec 10 09:36:22 MST 2015
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear Met Help,
I'm trying to get the Heidke Skill Score for NMMB numerical output, and I'm using the grid_stat tool to run MET 5.0.
Obs: RTMA regridded temperature file
Forecast: NMMB output
I ran the following command:
./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb GridStatConfig_default
And got the following error:
DEBUG 1: Default Config File: /work/apps/pgi_14.10/met-5.1/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: GridStatConfig_default
ERROR :
ERROR : check_mctc_thresh() -> when verifying using multi-category contingency tables, the thresholds must be monotonically increasing and be of the same inequality type (lt, le, gt, or ge).
ERROR :
I attach the Configure File in this e-mail. Any help will be greatly appreciated.
Best Regards,
Jose M. Garcia-Rivera, PhD
I.M. Systems Group
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Running MET for NMMB output
From: John Halley Gotway
Time: Wed Dec 09 10:40:17 2015
Jose,
Here's the quick and easy answer... just edit the Grid-Stat
configuration
file to disable the computation of multi-category contingency tables
by
setting:
mctc = NONE;
mcts = NONE;
And then rerun your case.
Here's the longer answer...
MET supports the computation of multi-category contingency tables, and
the
output is written to the MCTC and MCTS line types. For example,
suppose
you're verifying precipitation and specify the following forecast and
observation thresholds: >0, >1, >2.
In your output, you'll see output for 3 traditional 2x2 contingency
tables
(i.e. CTC and CTS output lines), one each for the >0, >1, and >2
thresholds. However, these 3 thresholds can also be used to define a
4x4
contingency table. The forecast value can either be equal to 0,
between 0
and 1, between 1 and 2, or greater than 2. And the same is true for
the
observation value. And that defines the 4x4 contingency table whose
output
is written to a single MCTC and MCTS output line.
But in order to compute MCTC and MCTS output, the thresholds defined
must
follow some rules. They all have to use the same inequality type (>,
>=,
<, or <=) and must be monotonically increasing. That's what the error
message is telling you. You're requesting MCTC and MCTS output, but
your
thresholds are not of the same type:
cat_thresh = [ >0.0, >=5.0 ];
So changing that ">=5.0" to ">5.0" is another way to fix this error.
However 0 and 5 are pretty poor choices for thresholding temperature,
which
is typically defined in Kelvin. Those numbers would be pretty close
to
absolute zero, which doesn't usually occur at 2-meters?
Thanks,
John Halley Gotway
met_help at ucar.edu
On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
met_help at ucar.edu> wrote:
>
> Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> Transaction: Ticket created by GarciaJ at imsg.com
> Queue: met_help
> Subject: Running MET for NMMB output
> Owner: Nobody
> Requestors: GarciaJ at imsg.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
>
> Dear Met Help,
>
> I'm trying to get the Heidke Skill Score for NMMB numerical output,
and
> I'm using the grid_stat tool to run MET 5.0.
>
> Obs: RTMA regridded temperature file
> Forecast: NMMB output
>
> I ran the following command:
> ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> GridStatConfig_default
>
> And got the following error:
> DEBUG 1: Default Config File:
> /work/apps/pgi_14.10/met-5.1/share/met/config/GridStatConfig_default
> DEBUG 1: User Config File: GridStatConfig_default
> ERROR :
> ERROR : check_mctc_thresh() -> when verifying using multi-category
> contingency tables, the thresholds must be monotonically increasing
and be
> of the same inequality type (lt, le, gt, or ge).
> ERROR :
>
> I attach the Configure File in this e-mail. Any help will be
greatly
> appreciated.
>
> Best Regards,
> Jose M. Garcia-Rivera, PhD
> I.M. Systems Group
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #74338] Running MET for NMMB output
From: Jose Garcia-Rivera
Time: Wed Dec 09 13:02:18 2015
Dear John,
Thank you so much for the quick reply. I ran the grid_stat, and it
produces the files, albeit empty.
I got the following:
./grid_stat nmbprs_d01.12.grb LTIA98_KWBR_201510281200_regridded.grb
GridStatConfig_default
DEBUG 1: Default Config File: /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: GridStatConfig_default
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=109602902
DEBUG 1: Forecast File: nmbprs_d01.12.grb
DEBUG 1: Observation File: LTIA98_KWBR_201510281200_regridded.grb
./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
__ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
Thanks for the help,
Jose
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, December 09, 2015 12:40 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
Jose,
Here's the quick and easy answer... just edit the Grid-Stat
configuration file to disable the computation of multi-category
contingency tables by
setting:
mctc = NONE;
mcts = NONE;
And then rerun your case.
Here's the longer answer...
MET supports the computation of multi-category contingency tables, and
the output is written to the MCTC and MCTS line types. For example,
suppose you're verifying precipitation and specify the following
forecast and observation thresholds: >0, >1, >2.
In your output, you'll see output for 3 traditional 2x2 contingency
tables (i.e. CTC and CTS output lines), one each for the >0, >1, and
>2 thresholds. However, these 3 thresholds can also be used to define
a 4x4 contingency table. The forecast value can either be equal to 0,
between 0 and 1, between 1 and 2, or greater than 2. And the same is
true for the observation value. And that defines the 4x4 contingency
table whose output is written to a single MCTC and MCTS output line.
But in order to compute MCTC and MCTS output, the thresholds defined
must follow some rules. They all have to use the same inequality type
(>, >=, <, or <=) and must be monotonically increasing. That's what
the error message is telling you. You're requesting MCTC and MCTS
output, but your thresholds are not of the same type:
cat_thresh = [ >0.0, >=5.0 ];
So changing that ">=5.0" to ">5.0" is another way to fix this error.
However 0 and 5 are pretty poor choices for thresholding temperature,
which is typically defined in Kelvin. Those numbers would be pretty
close to absolute zero, which doesn't usually occur at 2-meters?
Thanks,
John Halley Gotway
met_help at ucar.edu
On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
met_help at ucar.edu> wrote:
>
> Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> Transaction: Ticket created by GarciaJ at imsg.com
> Queue: met_help
> Subject: Running MET for NMMB output
> Owner: Nobody
> Requestors: GarciaJ at imsg.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> >
>
>
> Dear Met Help,
>
> I'm trying to get the Heidke Skill Score for NMMB numerical output,
> and I'm using the grid_stat tool to run MET 5.0.
>
> Obs: RTMA regridded temperature file
> Forecast: NMMB output
>
> I ran the following command:
> ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> GridStatConfig_default
>
> And got the following error:
> DEBUG 1: Default Config File:
> /work/apps/pgi_14.10/met-5.1/share/met/config/GridStatConfig_default
> DEBUG 1: User Config File: GridStatConfig_default ERROR :
> ERROR : check_mctc_thresh() -> when verifying using multi-category
> contingency tables, the thresholds must be monotonically increasing
> and be of the same inequality type (lt, le, gt, or ge).
> ERROR :
>
> I attach the Configure File in this e-mail. Any help will be
greatly
> appreciated.
>
> Best Regards,
> Jose M. Garcia-Rivera, PhD
> I.M. Systems Group
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
Subject: Running MET for NMMB output
From: John Halley Gotway
Time: Wed Dec 09 13:23:10 2015
Jose,
This is the first time I've seen this error. Based on the error
message,
my guess is that the runtime linker isn't able to locate the NetCDF
library. If that is indeed the problem, you could try setting the
LD_LIBRARY_PATH environment variable to the NetCDF directory which
contains
files named "libnetcdf.so*". That might enable the linker to find
that
symbol.
Also, be sure that MET is compiled with the same compilers used for
that
NetCDF library. Although, I would have guessed that those problems
would
have shown up at compilation time.
If you'd like, I could run your data here to make sure there aren't
other
issue. You can send me the sample data files you're using by posting
them
to our anonymous ftp site, following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
I'd need nmbprs_d01.12.grb, LTIA98_KWBR_201510281200_regridded.grb,
and
GridStatConfig_default. Please write once you've posted the data.
I'll go
grab it and try to replicate the behavior you're seeing.
Thanks,
John
On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> Thank you so much for the quick reply. I ran the grid_stat, and it
> produces the files, albeit empty.
>
> I got the following:
>
> ./grid_stat nmbprs_d01.12.grb LTIA98_KWBR_201510281200_regridded.grb
> GridStatConfig_default
> DEBUG 1: Default Config File:
> /work/apps/pgi_14.10/met-5.1/share/met/config/GridStatConfig_default
> DEBUG 1: User Config File: GridStatConfig_default
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=109602902
> DEBUG 1: Forecast File: nmbprs_d01.12.grb
> DEBUG 1: Observation File: LTIA98_KWBR_201510281200_regridded.grb
> ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
>
>
> Thanks for the help,
> Jose
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 12:40 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> Here's the quick and easy answer... just edit the Grid-Stat
configuration
> file to disable the computation of multi-category contingency tables
by
> setting:
> mctc = NONE;
> mcts = NONE;
>
> And then rerun your case.
>
> Here's the longer answer...
>
> MET supports the computation of multi-category contingency tables,
and the
> output is written to the MCTC and MCTS line types. For example,
suppose
> you're verifying precipitation and specify the following forecast
and
> observation thresholds: >0, >1, >2.
> In your output, you'll see output for 3 traditional 2x2 contingency
tables
> (i.e. CTC and CTS output lines), one each for the >0, >1, and >2
> thresholds. However, these 3 thresholds can also be used to define
a 4x4
> contingency table. The forecast value can either be equal to 0,
between 0
> and 1, between 1 and 2, or greater than 2. And the same is true for
the
> observation value. And that defines the 4x4 contingency table whose
output
> is written to a single MCTC and MCTS output line.
>
> But in order to compute MCTC and MCTS output, the thresholds defined
must
> follow some rules. They all have to use the same inequality type
(>, >=,
> <, or <=) and must be monotonically increasing. That's what the
error
> message is telling you. You're requesting MCTC and MCTS output, but
your
> thresholds are not of the same type:
> cat_thresh = [ >0.0, >=5.0 ];
>
> So changing that ">=5.0" to ">5.0" is another way to fix this error.
> However 0 and 5 are pretty poor choices for thresholding
temperature,
> which is typically defined in Kelvin. Those numbers would be pretty
close
> to absolute zero, which doesn't usually occur at 2-meters?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
>
> On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > Transaction: Ticket created by GarciaJ at imsg.com
> > Queue: met_help
> > Subject: Running MET for NMMB output
> > Owner: Nobody
> > Requestors: GarciaJ at imsg.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > >
> >
> >
> > Dear Met Help,
> >
> > I'm trying to get the Heidke Skill Score for NMMB numerical
output,
> > and I'm using the grid_stat tool to run MET 5.0.
> >
> > Obs: RTMA regridded temperature file
> > Forecast: NMMB output
> >
> > I ran the following command:
> > ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> > GridStatConfig_default
> >
> > And got the following error:
> > DEBUG 1: Default Config File:
> > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > DEBUG 1: User Config File: GridStatConfig_default ERROR :
> > ERROR : check_mctc_thresh() -> when verifying using multi-
category
> > contingency tables, the thresholds must be monotonically
increasing
> > and be of the same inequality type (lt, le, gt, or ge).
> > ERROR :
> >
> > I attach the Configure File in this e-mail. Any help will be
greatly
> > appreciated.
> >
> > Best Regards,
> > Jose M. Garcia-Rivera, PhD
> > I.M. Systems Group
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended recipient or his or her authorized agent, the reader is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
error,
> > please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #74338] Running MET for NMMB output
From: Jose Garcia-Rivera
Time: Wed Dec 09 13:47:19 2015
Dear John,
I just uploaded the three files to: garcia_data.
I'll be on stand-by waiting for your findings. I appreciate all the
help.
Best Regards,
Jose
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, December 09, 2015 3:23 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
Jose,
This is the first time I've seen this error. Based on the error
message, my guess is that the runtime linker isn't able to locate the
NetCDF library. If that is indeed the problem, you could try setting
the LD_LIBRARY_PATH environment variable to the NetCDF directory which
contains files named "libnetcdf.so*". That might enable the linker to
find that symbol.
Also, be sure that MET is compiled with the same compilers used for
that NetCDF library. Although, I would have guessed that those
problems would have shown up at compilation time.
If you'd like, I could run your data here to make sure there aren't
other issue. You can send me the sample data files you're using by
posting them to our anonymous ftp site, following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
I'd need nmbprs_d01.12.grb, LTIA98_KWBR_201510281200_regridded.grb,
and GridStatConfig_default. Please write once you've posted the data.
I'll go grab it and try to replicate the behavior you're seeing.
Thanks,
John
On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> Thank you so much for the quick reply. I ran the grid_stat, and it
> produces the files, albeit empty.
>
> I got the following:
>
> ./grid_stat nmbprs_d01.12.grb LTIA98_KWBR_201510281200_regridded.grb
> GridStatConfig_default
> DEBUG 1: Default Config File:
> /work/apps/pgi_14.10/met-5.1/share/met/config/GridStatConfig_default
> DEBUG 1: User Config File: GridStatConfig_default
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=109602902
> DEBUG 1: Forecast File: nmbprs_d01.12.grb DEBUG 1: Observation File:
> LTIA98_KWBR_201510281200_regridded.grb
> ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
>
>
> Thanks for the help,
> Jose
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 12:40 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> Here's the quick and easy answer... just edit the Grid-Stat
> configuration file to disable the computation of multi-category
> contingency tables by
> setting:
> mctc = NONE;
> mcts = NONE;
>
> And then rerun your case.
>
> Here's the longer answer...
>
> MET supports the computation of multi-category contingency tables,
and
> the output is written to the MCTC and MCTS line types. For example,
> suppose you're verifying precipitation and specify the following
> forecast and observation thresholds: >0, >1, >2.
> In your output, you'll see output for 3 traditional 2x2 contingency
> tables (i.e. CTC and CTS output lines), one each for the >0, >1, and
> >2 thresholds. However, these 3 thresholds can also be used to
define
> a 4x4 contingency table. The forecast value can either be equal to
0,
> between 0 and 1, between 1 and 2, or greater than 2. And the same
is
> true for the observation value. And that defines the 4x4
contingency
> table whose output is written to a single MCTC and MCTS output line.
>
> But in order to compute MCTC and MCTS output, the thresholds defined
> must follow some rules. They all have to use the same inequality
type
> (>, >=, <, or <=) and must be monotonically increasing. That's what
> the error message is telling you. You're requesting MCTC and MCTS
> output, but your thresholds are not of the same type:
> cat_thresh = [ >0.0, >=5.0 ];
>
> So changing that ">=5.0" to ">5.0" is another way to fix this error.
> However 0 and 5 are pretty poor choices for thresholding
temperature,
> which is typically defined in Kelvin. Those numbers would be pretty
> close to absolute zero, which doesn't usually occur at 2-meters?
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
>
> On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > Transaction: Ticket created by GarciaJ at imsg.com
> > Queue: met_help
> > Subject: Running MET for NMMB output
> > Owner: Nobody
> > Requestors: GarciaJ at imsg.com
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > >
> >
> >
> > Dear Met Help,
> >
> > I'm trying to get the Heidke Skill Score for NMMB numerical
output,
> > and I'm using the grid_stat tool to run MET 5.0.
> >
> > Obs: RTMA regridded temperature file
> > Forecast: NMMB output
> >
> > I ran the following command:
> > ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> > GridStatConfig_default
> >
> > And got the following error:
> > DEBUG 1: Default Config File:
> > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > DEBUG 1: User Config File: GridStatConfig_default ERROR :
> > ERROR : check_mctc_thresh() -> when verifying using multi-
category
> > contingency tables, the thresholds must be monotonically
increasing
> > and be of the same inequality type (lt, le, gt, or ge).
> > ERROR :
> >
> > I attach the Configure File in this e-mail. Any help will be
> > greatly appreciated.
> >
> > Best Regards,
> > Jose M. Garcia-Rivera, PhD
> > I.M. Systems Group
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
> > entity to which it is addressed. If the reader of this e-mail is
not
> > the intended recipient or his or her authorized agent, the reader
is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
> > error, please notify the sender by replying to this message and
> > delete this
> e-mail immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
Subject: Running MET for NMMB output
From: John Halley Gotway
Time: Wed Dec 09 14:12:23 2015
Jose,
I pulled your data and was able to run it through Grid-Stat without
any
problems. Although here's a WARNING message about the grid:
WARNING:
WARNING: gds_to_lambert() -> MET does not currently support Lambert
Conformal grids where dx (3.317) != dy (2.97) and may produce
unexpected
results!
WARNING:
But I remember that we previously had a conversation about this.
So this is a configuration issue on your system. Did you try setting
the
LD_LIBRARY_PATH environment variable by adding the NetCDF library
directory? And are you sure that that NetCDF library was compiled
using
the same compilers as MET?
Perhaps we could try using static linking instead of dynamic linking.
That
would force the linker to resolve these types of undefined references
at
compilation time rather than at runtime. Run "./configure --help" for
details, but the "--enable-static_linking" option for the configure
command
should force static linking. You'd need to rerun configure with this
option and then try recompiling MET.
John
On Wed, Dec 9, 2015 at 1:47 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> I just uploaded the three files to: garcia_data.
>
> I'll be on stand-by waiting for your findings. I appreciate all the
help.
>
> Best Regards,
> Jose
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 3:23 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> This is the first time I've seen this error. Based on the error
message,
> my guess is that the runtime linker isn't able to locate the NetCDF
> library. If that is indeed the problem, you could try setting the
> LD_LIBRARY_PATH environment variable to the NetCDF directory which
contains
> files named "libnetcdf.so*". That might enable the linker to find
that
> symbol.
>
> Also, be sure that MET is compiled with the same compilers used for
that
> NetCDF library. Although, I would have guessed that those problems
would
> have shown up at compilation time.
>
> If you'd like, I could run your data here to make sure there aren't
other
> issue. You can send me the sample data files you're using by
posting them
> to our anonymous ftp site, following these instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I'd need nmbprs_d01.12.grb, LTIA98_KWBR_201510281200_regridded.grb,
and
> GridStatConfig_default. Please write once you've posted the data.
I'll go
> grab it and try to replicate the behavior you're seeing.
>
> Thanks,
> John
>
> On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> >
> > Dear John,
> >
> > Thank you so much for the quick reply. I ran the grid_stat, and it
> > produces the files, albeit empty.
> >
> > I got the following:
> >
> > ./grid_stat nmbprs_d01.12.grb
LTIA98_KWBR_201510281200_regridded.grb
> > GridStatConfig_default
> > DEBUG 1: Default Config File:
> > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > DEBUG 1: User Config File: GridStatConfig_default
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=109602902
> > DEBUG 1: Forecast File: nmbprs_d01.12.grb DEBUG 1: Observation
File:
> > LTIA98_KWBR_201510281200_regridded.grb
> > ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> > __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
> >
> >
> > Thanks for the help,
> > Jose
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, December 09, 2015 12:40 PM
> > To: Jose Garcia-Rivera
> > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
> >
> > Jose,
> >
> > Here's the quick and easy answer... just edit the Grid-Stat
> > configuration file to disable the computation of multi-category
> > contingency tables by
> > setting:
> > mctc = NONE;
> > mcts = NONE;
> >
> > And then rerun your case.
> >
> > Here's the longer answer...
> >
> > MET supports the computation of multi-category contingency tables,
and
> > the output is written to the MCTC and MCTS line types. For
example,
> > suppose you're verifying precipitation and specify the following
> > forecast and observation thresholds: >0, >1, >2.
> > In your output, you'll see output for 3 traditional 2x2
contingency
> > tables (i.e. CTC and CTS output lines), one each for the >0, >1,
and
> > >2 thresholds. However, these 3 thresholds can also be used to
define
> > a 4x4 contingency table. The forecast value can either be equal
to 0,
> > between 0 and 1, between 1 and 2, or greater than 2. And the same
is
> > true for the observation value. And that defines the 4x4
contingency
> > table whose output is written to a single MCTC and MCTS output
line.
> >
> > But in order to compute MCTC and MCTS output, the thresholds
defined
> > must follow some rules. They all have to use the same inequality
type
> > (>, >=, <, or <=) and must be monotonically increasing. That's
what
> > the error message is telling you. You're requesting MCTC and MCTS
> > output, but your thresholds are not of the same type:
> > cat_thresh = [ >0.0, >=5.0 ];
> >
> > So changing that ">=5.0" to ">5.0" is another way to fix this
error.
> > However 0 and 5 are pretty poor choices for thresholding
temperature,
> > which is typically defined in Kelvin. Those numbers would be
pretty
> > close to absolute zero, which doesn't usually occur at 2-meters?
> >
> > Thanks,
> > John Halley Gotway
> > met_help at ucar.edu
> >
> >
> > On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > > Transaction: Ticket created by GarciaJ at imsg.com
> > > Queue: met_help
> > > Subject: Running MET for NMMB output
> > > Owner: Nobody
> > > Requestors: GarciaJ at imsg.com
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > > >
> > >
> > >
> > > Dear Met Help,
> > >
> > > I'm trying to get the Heidke Skill Score for NMMB numerical
output,
> > > and I'm using the grid_stat tool to run MET 5.0.
> > >
> > > Obs: RTMA regridded temperature file
> > > Forecast: NMMB output
> > >
> > > I ran the following command:
> > > ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> > > GridStatConfig_default
> > >
> > > And got the following error:
> > > DEBUG 1: Default Config File:
> > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > > DEBUG 1: User Config File: GridStatConfig_default ERROR :
> > > ERROR : check_mctc_thresh() -> when verifying using multi-
category
> > > contingency tables, the thresholds must be monotonically
increasing
> > > and be of the same inequality type (lt, le, gt, or ge).
> > > ERROR :
> > >
> > > I attach the Configure File in this e-mail. Any help will be
> > > greatly appreciated.
> > >
> > > Best Regards,
> > > Jose M. Garcia-Rivera, PhD
> > > I.M. Systems Group
> > >
> > > This e-mail, including attachments, may include confidential
and/or
> > > proprietary information, and may be used only by the person or
> > > entity to which it is addressed. If the reader of this e-mail is
not
> > > the intended recipient or his or her authorized agent, the
reader is
> > > hereby notified that any dissemination, distribution or copying
of
> > > this e-mail is prohibited. If you have received this e-mail in
> > > error, please notify the sender by replying to this message and
> > > delete this
> > e-mail immediately.
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended recipient or his or her authorized agent, the reader is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
error,
> > please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #74338] Running MET for NMMB output
From: Jose Garcia-Rivera
Time: Wed Dec 09 14:24:22 2015
Dear John,
I'm not sure about how MET was compiled here exactly. I'll have to
refer this problem to the cluster administrator.
One question: Do I set LD_LIBRARY_PATH environment variable by adding
the NetCDF library directory in my bashrc file, or in the MET
compilation process?
Best Regards,
Jose
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, December 09, 2015 4:12 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
Jose,
I pulled your data and was able to run it through Grid-Stat without
any problems. Although here's a WARNING message about the grid:
WARNING:
WARNING: gds_to_lambert() -> MET does not currently support Lambert
Conformal grids where dx (3.317) != dy (2.97) and may produce
unexpected results!
WARNING:
But I remember that we previously had a conversation about this.
So this is a configuration issue on your system. Did you try setting
the LD_LIBRARY_PATH environment variable by adding the NetCDF library
directory? And are you sure that that NetCDF library was compiled
using the same compilers as MET?
Perhaps we could try using static linking instead of dynamic linking.
That would force the linker to resolve these types of undefined
references at compilation time rather than at runtime. Run
"./configure --help" for details, but the "--enable-static_linking"
option for the configure command should force static linking. You'd
need to rerun configure with this option and then try recompiling MET.
John
On Wed, Dec 9, 2015 at 1:47 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> I just uploaded the three files to: garcia_data.
>
> I'll be on stand-by waiting for your findings. I appreciate all the
help.
>
> Best Regards,
> Jose
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 3:23 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> This is the first time I've seen this error. Based on the error
> message, my guess is that the runtime linker isn't able to locate
the
> NetCDF library. If that is indeed the problem, you could try
setting
> the LD_LIBRARY_PATH environment variable to the NetCDF directory
which
> contains files named "libnetcdf.so*". That might enable the linker
to
> find that symbol.
>
> Also, be sure that MET is compiled with the same compilers used for
> that NetCDF library. Although, I would have guessed that those
> problems would have shown up at compilation time.
>
> If you'd like, I could run your data here to make sure there aren't
> other issue. You can send me the sample data files you're using by
> posting them to our anonymous ftp site, following these
instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I'd need nmbprs_d01.12.grb, LTIA98_KWBR_201510281200_regridded.grb,
> and GridStatConfig_default. Please write once you've posted the
data.
> I'll go grab it and try to replicate the behavior you're seeing.
>
> Thanks,
> John
>
> On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> >
> > Dear John,
> >
> > Thank you so much for the quick reply. I ran the grid_stat, and it
> > produces the files, albeit empty.
> >
> > I got the following:
> >
> > ./grid_stat nmbprs_d01.12.grb
LTIA98_KWBR_201510281200_regridded.grb
> > GridStatConfig_default
> > DEBUG 1: Default Config File:
> > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > DEBUG 1: User Config File: GridStatConfig_default
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=109602902
> > DEBUG 1: Forecast File: nmbprs_d01.12.grb DEBUG 1: Observation
File:
> > LTIA98_KWBR_201510281200_regridded.grb
> > ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> > __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
> >
> >
> > Thanks for the help,
> > Jose
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, December 09, 2015 12:40 PM
> > To: Jose Garcia-Rivera
> > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
> >
> > Jose,
> >
> > Here's the quick and easy answer... just edit the Grid-Stat
> > configuration file to disable the computation of multi-category
> > contingency tables by
> > setting:
> > mctc = NONE;
> > mcts = NONE;
> >
> > And then rerun your case.
> >
> > Here's the longer answer...
> >
> > MET supports the computation of multi-category contingency tables,
> > and the output is written to the MCTC and MCTS line types. For
> > example, suppose you're verifying precipitation and specify the
> > following forecast and observation thresholds: >0, >1, >2.
> > In your output, you'll see output for 3 traditional 2x2
contingency
> > tables (i.e. CTC and CTS output lines), one each for the >0, >1,
and
> > >2 thresholds. However, these 3 thresholds can also be used to
> > >define
> > a 4x4 contingency table. The forecast value can either be equal
to
> > 0, between 0 and 1, between 1 and 2, or greater than 2. And the
> > same is true for the observation value. And that defines the 4x4
> > contingency table whose output is written to a single MCTC and
MCTS output line.
> >
> > But in order to compute MCTC and MCTS output, the thresholds
defined
> > must follow some rules. They all have to use the same inequality
> > type (>, >=, <, or <=) and must be monotonically increasing.
That's
> > what the error message is telling you. You're requesting MCTC and
> > MCTS output, but your thresholds are not of the same type:
> > cat_thresh = [ >0.0, >=5.0 ];
> >
> > So changing that ">=5.0" to ">5.0" is another way to fix this
error.
> > However 0 and 5 are pretty poor choices for thresholding
> > temperature, which is typically defined in Kelvin. Those numbers
> > would be pretty close to absolute zero, which doesn't usually
occur at 2-meters?
> >
> > Thanks,
> > John Halley Gotway
> > met_help at ucar.edu
> >
> >
> > On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > > Transaction: Ticket created by GarciaJ at imsg.com
> > > Queue: met_help
> > > Subject: Running MET for NMMB output
> > > Owner: Nobody
> > > Requestors: GarciaJ at imsg.com
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > > >
> > >
> > >
> > > Dear Met Help,
> > >
> > > I'm trying to get the Heidke Skill Score for NMMB numerical
> > > output, and I'm using the grid_stat tool to run MET 5.0.
> > >
> > > Obs: RTMA regridded temperature file
> > > Forecast: NMMB output
> > >
> > > I ran the following command:
> > > ./grid_stat nmbprs_d01.12 LTIA98_KWBR_201510281200_regridded.grb
> > > GridStatConfig_default
> > >
> > > And got the following error:
> > > DEBUG 1: Default Config File:
> > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_defau
> > > lt DEBUG 1: User Config File: GridStatConfig_default ERROR :
> > > ERROR : check_mctc_thresh() -> when verifying using
> > > multi-category contingency tables, the thresholds must be
> > > monotonically increasing and be of the same inequality type (lt,
le, gt, or ge).
> > > ERROR :
> > >
> > > I attach the Configure File in this e-mail. Any help will be
> > > greatly appreciated.
> > >
> > > Best Regards,
> > > Jose M. Garcia-Rivera, PhD
> > > I.M. Systems Group
> > >
> > > This e-mail, including attachments, may include confidential
> > > and/or proprietary information, and may be used only by the
person
> > > or entity to which it is addressed. If the reader of this e-mail
> > > is not the intended recipient or his or her authorized agent,
the
> > > reader is hereby notified that any dissemination, distribution
or
> > > copying of this e-mail is prohibited. If you have received this
> > > e-mail in error, please notify the sender by replying to this
> > > message and delete this
> > e-mail immediately.
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
> > entity to which it is addressed. If the reader of this e-mail is
not
> > the intended recipient or his or her authorized agent, the reader
is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
> > error, please notify the sender by replying to this message and
> > delete this
> e-mail immediately.
> >
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
Subject: Running MET for NMMB output
From: John Halley Gotway
Time: Wed Dec 09 15:02:23 2015
Jose,
You'd set the LD_LIBRARY_PATH in your bashrc file, and then source
that
file:
source ~/.bashrc
echo $LD_LIBRARY_PATH
For example, here's how mine is set:
echo $LD_LIBRARY_PATH
/var/autofs/mnt/dakota_d3/projects/MET/MET_releases/external_libs/netcdf/netcdf-
4.1.3/lib:/tools/pgi/bin:/tools/pgi/mpich/bin:/usr/lib
When software is built using "dynamic linking" then the linking to
external
libraries is done at run time. If those external libraries are
installed
in some non-standard location where the linker wouldn't know to look,
you
set LD_LIBRARY_PATH to explicitly tell it where is should look.
However,
this may or may not resolve the problem you're seeing.
I think talking to your sys admin about this is a great idea.
John
On Wed, Dec 9, 2015 at 2:24 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> I'm not sure about how MET was compiled here exactly. I'll have to
refer
> this problem to the cluster administrator.
>
> One question: Do I set LD_LIBRARY_PATH environment variable by
adding the
> NetCDF library directory in my bashrc file, or in the MET
compilation
> process?
>
> Best Regards,
> Jose
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 4:12 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> I pulled your data and was able to run it through Grid-Stat without
any
> problems. Although here's a WARNING message about the grid:
>
> WARNING:
> WARNING: gds_to_lambert() -> MET does not currently support Lambert
> Conformal grids where dx (3.317) != dy (2.97) and may produce
unexpected
> results!
> WARNING:
>
> But I remember that we previously had a conversation about this.
>
> So this is a configuration issue on your system. Did you try
setting the
> LD_LIBRARY_PATH environment variable by adding the NetCDF library
> directory? And are you sure that that NetCDF library was compiled
using
> the same compilers as MET?
>
> Perhaps we could try using static linking instead of dynamic
linking.
> That would force the linker to resolve these types of undefined
references
> at compilation time rather than at runtime. Run "./configure
--help" for
> details, but the "--enable-static_linking" option for the configure
command
> should force static linking. You'd need to rerun configure with
this
> option and then try recompiling MET.
>
> John
>
>
>
>
> On Wed, Dec 9, 2015 at 1:47 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> >
> > Dear John,
> >
> > I just uploaded the three files to: garcia_data.
> >
> > I'll be on stand-by waiting for your findings. I appreciate all
the help.
> >
> > Best Regards,
> > Jose
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, December 09, 2015 3:23 PM
> > To: Jose Garcia-Rivera
> > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
> >
> > Jose,
> >
> > This is the first time I've seen this error. Based on the error
> > message, my guess is that the runtime linker isn't able to locate
the
> > NetCDF library. If that is indeed the problem, you could try
setting
> > the LD_LIBRARY_PATH environment variable to the NetCDF directory
which
> > contains files named "libnetcdf.so*". That might enable the
linker to
> > find that symbol.
> >
> > Also, be sure that MET is compiled with the same compilers used
for
> > that NetCDF library. Although, I would have guessed that those
> > problems would have shown up at compilation time.
> >
> > If you'd like, I could run your data here to make sure there
aren't
> > other issue. You can send me the sample data files you're using
by
> > posting them to our anonymous ftp site, following these
instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > I'd need nmbprs_d01.12.grb,
LTIA98_KWBR_201510281200_regridded.grb,
> > and GridStatConfig_default. Please write once you've posted the
data.
> > I'll go grab it and try to replicate the behavior you're seeing.
> >
> > Thanks,
> > John
> >
> > On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> > >
> > > Dear John,
> > >
> > > Thank you so much for the quick reply. I ran the grid_stat, and
it
> > > produces the files, albeit empty.
> > >
> > > I got the following:
> > >
> > > ./grid_stat nmbprs_d01.12.grb
LTIA98_KWBR_201510281200_regridded.grb
> > > GridStatConfig_default
> > > DEBUG 1: Default Config File:
> > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_default
> > > DEBUG 1: User Config File: GridStatConfig_default
> > > GSL_RNG_TYPE=mt19937
> > > GSL_RNG_SEED=109602902
> > > DEBUG 1: Forecast File: nmbprs_d01.12.grb DEBUG 1: Observation
File:
> > > LTIA98_KWBR_201510281200_regridded.grb
> > > ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> > > __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
> > >
> > >
> > > Thanks for the help,
> > > Jose
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, December 09, 2015 12:40 PM
> > > To: Jose Garcia-Rivera
> > > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB
output
> > >
> > > Jose,
> > >
> > > Here's the quick and easy answer... just edit the Grid-Stat
> > > configuration file to disable the computation of multi-category
> > > contingency tables by
> > > setting:
> > > mctc = NONE;
> > > mcts = NONE;
> > >
> > > And then rerun your case.
> > >
> > > Here's the longer answer...
> > >
> > > MET supports the computation of multi-category contingency
tables,
> > > and the output is written to the MCTC and MCTS line types. For
> > > example, suppose you're verifying precipitation and specify the
> > > following forecast and observation thresholds: >0, >1, >2.
> > > In your output, you'll see output for 3 traditional 2x2
contingency
> > > tables (i.e. CTC and CTS output lines), one each for the >0, >1,
and
> > > >2 thresholds. However, these 3 thresholds can also be used to
> > > >define
> > > a 4x4 contingency table. The forecast value can either be equal
to
> > > 0, between 0 and 1, between 1 and 2, or greater than 2. And the
> > > same is true for the observation value. And that defines the
4x4
> > > contingency table whose output is written to a single MCTC and
MCTS
> output line.
> > >
> > > But in order to compute MCTC and MCTS output, the thresholds
defined
> > > must follow some rules. They all have to use the same
inequality
> > > type (>, >=, <, or <=) and must be monotonically increasing.
That's
> > > what the error message is telling you. You're requesting MCTC
and
> > > MCTS output, but your thresholds are not of the same type:
> > > cat_thresh = [ >0.0, >=5.0 ];
> > >
> > > So changing that ">=5.0" to ">5.0" is another way to fix this
error.
> > > However 0 and 5 are pretty poor choices for thresholding
> > > temperature, which is typically defined in Kelvin. Those
numbers
> > > would be pretty close to absolute zero, which doesn't usually
occur at
> 2-meters?
> > >
> > > Thanks,
> > > John Halley Gotway
> > > met_help at ucar.edu
> > >
> > >
> > > On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > > > Transaction: Ticket created by GarciaJ at imsg.com
> > > > Queue: met_help
> > > > Subject: Running MET for NMMB output
> > > > Owner: Nobody
> > > > Requestors: GarciaJ at imsg.com
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > > > >
> > > >
> > > >
> > > > Dear Met Help,
> > > >
> > > > I'm trying to get the Heidke Skill Score for NMMB numerical
> > > > output, and I'm using the grid_stat tool to run MET 5.0.
> > > >
> > > > Obs: RTMA regridded temperature file
> > > > Forecast: NMMB output
> > > >
> > > > I ran the following command:
> > > > ./grid_stat nmbprs_d01.12
LTIA98_KWBR_201510281200_regridded.grb
> > > > GridStatConfig_default
> > > >
> > > > And got the following error:
> > > > DEBUG 1: Default Config File:
> > > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_defau
> > > > lt DEBUG 1: User Config File: GridStatConfig_default ERROR :
> > > > ERROR : check_mctc_thresh() -> when verifying using
> > > > multi-category contingency tables, the thresholds must be
> > > > monotonically increasing and be of the same inequality type
(lt, le,
> gt, or ge).
> > > > ERROR :
> > > >
> > > > I attach the Configure File in this e-mail. Any help will be
> > > > greatly appreciated.
> > > >
> > > > Best Regards,
> > > > Jose M. Garcia-Rivera, PhD
> > > > I.M. Systems Group
> > > >
> > > > This e-mail, including attachments, may include confidential
> > > > and/or proprietary information, and may be used only by the
person
> > > > or entity to which it is addressed. If the reader of this e-
mail
> > > > is not the intended recipient or his or her authorized agent,
the
> > > > reader is hereby notified that any dissemination, distribution
or
> > > > copying of this e-mail is prohibited. If you have received
this
> > > > e-mail in error, please notify the sender by replying to this
> > > > message and delete this
> > > e-mail immediately.
> > > >
> > > >
> > >
> > > This e-mail, including attachments, may include confidential
and/or
> > > proprietary information, and may be used only by the person or
> > > entity to which it is addressed. If the reader of this e-mail is
not
> > > the intended recipient or his or her authorized agent, the
reader is
> > > hereby notified that any dissemination, distribution or copying
of
> > > this e-mail is prohibited. If you have received this e-mail in
> > > error, please notify the sender by replying to this message and
> > > delete this
> > e-mail immediately.
> > >
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended recipient or his or her authorized agent, the reader is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
error,
> > please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #74338] Running MET for NMMB output
From: Jose Garcia-Rivera
Time: Wed Dec 09 15:28:17 2015
Hi John,
It seems we'll have to recompile MET. Thanks for all the help.
Best Regards,
Jose
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, December 09, 2015 5:02 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
Jose,
You'd set the LD_LIBRARY_PATH in your bashrc file, and then source
that
file:
source ~/.bashrc
echo $LD_LIBRARY_PATH
For example, here's how mine is set:
echo $LD_LIBRARY_PATH
/var/autofs/mnt/dakota_d3/projects/MET/MET_releases/external_libs/netcdf/netcdf-
4.1.3/lib:/tools/pgi/bin:/tools/pgi/mpich/bin:/usr/lib
When software is built using "dynamic linking" then the linking to
external libraries is done at run time. If those external libraries
are installed in some non-standard location where the linker wouldn't
know to look, you set LD_LIBRARY_PATH to explicitly tell it where is
should look. However, this may or may not resolve the problem you're
seeing.
I think talking to your sys admin about this is a great idea.
John
On Wed, Dec 9, 2015 at 2:24 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
>
> Dear John,
>
> I'm not sure about how MET was compiled here exactly. I'll have to
> refer this problem to the cluster administrator.
>
> One question: Do I set LD_LIBRARY_PATH environment variable by
adding
> the NetCDF library directory in my bashrc file, or in the MET
> compilation process?
>
> Best Regards,
> Jose
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, December 09, 2015 4:12 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
>
> Jose,
>
> I pulled your data and was able to run it through Grid-Stat without
> any problems. Although here's a WARNING message about the grid:
>
> WARNING:
> WARNING: gds_to_lambert() -> MET does not currently support Lambert
> Conformal grids where dx (3.317) != dy (2.97) and may produce
> unexpected results!
> WARNING:
>
> But I remember that we previously had a conversation about this.
>
> So this is a configuration issue on your system. Did you try
setting
> the LD_LIBRARY_PATH environment variable by adding the NetCDF
library
> directory? And are you sure that that NetCDF library was compiled
> using the same compilers as MET?
>
> Perhaps we could try using static linking instead of dynamic
linking.
> That would force the linker to resolve these types of undefined
> references at compilation time rather than at runtime. Run
> "./configure --help" for details, but the "--enable-static_linking"
> option for the configure command should force static linking. You'd
> need to rerun configure with this option and then try recompiling
MET.
>
> John
>
>
>
>
> On Wed, Dec 9, 2015 at 1:47 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> >
> > Dear John,
> >
> > I just uploaded the three files to: garcia_data.
> >
> > I'll be on stand-by waiting for your findings. I appreciate all
the help.
> >
> > Best Regards,
> > Jose
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, December 09, 2015 3:23 PM
> > To: Jose Garcia-Rivera
> > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB output
> >
> > Jose,
> >
> > This is the first time I've seen this error. Based on the error
> > message, my guess is that the runtime linker isn't able to locate
> > the NetCDF library. If that is indeed the problem, you could try
> > setting the LD_LIBRARY_PATH environment variable to the NetCDF
> > directory which contains files named "libnetcdf.so*". That might
> > enable the linker to find that symbol.
> >
> > Also, be sure that MET is compiled with the same compilers used
for
> > that NetCDF library. Although, I would have guessed that those
> > problems would have shown up at compilation time.
> >
> > If you'd like, I could run your data here to make sure there
aren't
> > other issue. You can send me the sample data files you're using
by
> > posting them to our anonymous ftp site, following these
instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > I'd need nmbprs_d01.12.grb,
LTIA98_KWBR_201510281200_regridded.grb,
> > and GridStatConfig_default. Please write once you've posted the
data.
> > I'll go grab it and try to replicate the behavior you're seeing.
> >
> > Thanks,
> > John
> >
> > On Wed, Dec 9, 2015 at 1:02 PM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338 >
> > >
> > > Dear John,
> > >
> > > Thank you so much for the quick reply. I ran the grid_stat, and
it
> > > produces the files, albeit empty.
> > >
> > > I got the following:
> > >
> > > ./grid_stat nmbprs_d01.12.grb
> > > LTIA98_KWBR_201510281200_regridded.grb
> > > GridStatConfig_default
> > > DEBUG 1: Default Config File:
> > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_defau
> > > lt DEBUG 1: User Config File: GridStatConfig_default
> > > GSL_RNG_TYPE=mt19937
> > > GSL_RNG_SEED=109602902
> > > DEBUG 1: Forecast File: nmbprs_d01.12.grb DEBUG 1: Observation
File:
> > > LTIA98_KWBR_201510281200_regridded.grb
> > > ./grid_stat: symbol lookup error: ./grid_stat: undefined symbol:
> > > __ct__6NcFileFPCcQ2_6NcFile8FileModePUlUlQ2_6NcFile10FileFormat
> > >
> > >
> > > Thanks for the help,
> > > Jose
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, December 09, 2015 12:40 PM
> > > To: Jose Garcia-Rivera
> > > Subject: Re: [rt.rap.ucar.edu #74338] Running MET for NMMB
output
> > >
> > > Jose,
> > >
> > > Here's the quick and easy answer... just edit the Grid-Stat
> > > configuration file to disable the computation of multi-category
> > > contingency tables by
> > > setting:
> > > mctc = NONE;
> > > mcts = NONE;
> > >
> > > And then rerun your case.
> > >
> > > Here's the longer answer...
> > >
> > > MET supports the computation of multi-category contingency
tables,
> > > and the output is written to the MCTC and MCTS line types. For
> > > example, suppose you're verifying precipitation and specify the
> > > following forecast and observation thresholds: >0, >1, >2.
> > > In your output, you'll see output for 3 traditional 2x2
> > > contingency tables (i.e. CTC and CTS output lines), one each for
> > > the >0, >1, and
> > > >2 thresholds. However, these 3 thresholds can also be used to
> > > >define
> > > a 4x4 contingency table. The forecast value can either be equal
> > > to 0, between 0 and 1, between 1 and 2, or greater than 2. And
> > > the same is true for the observation value. And that defines
the
> > > 4x4 contingency table whose output is written to a single MCTC
and
> > > MCTS
> output line.
> > >
> > > But in order to compute MCTC and MCTS output, the thresholds
> > > defined must follow some rules. They all have to use the same
> > > inequality type (>, >=, <, or <=) and must be monotonically
> > > increasing. That's what the error message is telling you.
You're
> > > requesting MCTC and MCTS output, but your thresholds are not of
the same type:
> > > cat_thresh = [ >0.0, >=5.0 ];
> > >
> > > So changing that ">=5.0" to ">5.0" is another way to fix this
error.
> > > However 0 and 5 are pretty poor choices for thresholding
> > > temperature, which is typically defined in Kelvin. Those
numbers
> > > would be pretty close to absolute zero, which doesn't usually
> > > occur at
> 2-meters?
> > >
> > > Thanks,
> > > John Halley Gotway
> > > met_help at ucar.edu
> > >
> > >
> > > On Wed, Dec 9, 2015 at 10:20 AM, Jose Garcia-Rivera via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Dec 09 10:20:35 2015: Request 74338 was acted upon.
> > > > Transaction: Ticket created by GarciaJ at imsg.com
> > > > Queue: met_help
> > > > Subject: Running MET for NMMB output
> > > > Owner: Nobody
> > > > Requestors: GarciaJ at imsg.com
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74338
> > > > >
> > > >
> > > >
> > > > Dear Met Help,
> > > >
> > > > I'm trying to get the Heidke Skill Score for NMMB numerical
> > > > output, and I'm using the grid_stat tool to run MET 5.0.
> > > >
> > > > Obs: RTMA regridded temperature file
> > > > Forecast: NMMB output
> > > >
> > > > I ran the following command:
> > > > ./grid_stat nmbprs_d01.12
LTIA98_KWBR_201510281200_regridded.grb
> > > > GridStatConfig_default
> > > >
> > > > And got the following error:
> > > > DEBUG 1: Default Config File:
> > > > /work/apps/pgi_14.10/met-
5.1/share/met/config/GridStatConfig_def
> > > > au lt DEBUG 1: User Config File: GridStatConfig_default ERROR
:
> > > > ERROR : check_mctc_thresh() -> when verifying using
> > > > multi-category contingency tables, the thresholds must be
> > > > monotonically increasing and be of the same inequality type
(lt,
> > > > le,
> gt, or ge).
> > > > ERROR :
> > > >
> > > > I attach the Configure File in this e-mail. Any help will be
> > > > greatly appreciated.
> > > >
> > > > Best Regards,
> > > > Jose M. Garcia-Rivera, PhD
> > > > I.M. Systems Group
> > > >
> > > > This e-mail, including attachments, may include confidential
> > > > and/or proprietary information, and may be used only by the
> > > > person or entity to which it is addressed. If the reader of
this
> > > > e-mail is not the intended recipient or his or her authorized
> > > > agent, the reader is hereby notified that any dissemination,
> > > > distribution or copying of this e-mail is prohibited. If you
> > > > have received this e-mail in error, please notify the sender
by
> > > > replying to this message and delete this
> > > e-mail immediately.
> > > >
> > > >
> > >
> > > This e-mail, including attachments, may include confidential
> > > and/or proprietary information, and may be used only by the
person
> > > or entity to which it is addressed. If the reader of this e-mail
> > > is not the intended recipient or his or her authorized agent,
the
> > > reader is hereby notified that any dissemination, distribution
or
> > > copying of this e-mail is prohibited. If you have received this
> > > e-mail in error, please notify the sender by replying to this
> > > message and delete this
> > e-mail immediately.
> > >
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
> > entity to which it is addressed. If the reader of this e-mail is
not
> > the intended recipient or his or her authorized agent, the reader
is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
> > error, please notify the sender by replying to this message and
> > delete this
> e-mail immediately.
> >
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
More information about the Met_help
mailing list