[Met_help] [rt.rap.ucar.edu #97312] History for Why I can not create CTC line-type
John Halley Gotway via RT
met_help at ucar.edu
Mon Nov 16 13:04:39 MST 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I was trying to make performance diagram using ensemble mean, here is the
script I used:
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
verf_g2g_Raikoke_ens.CSI.sh
I can create other line types like "pct, nbrctc" etc, but "ctc" is not
created although I did set " ctc = STAT" in the config file. All the log
file "run_gs.log" and configure files can be read from the script. What is
the problem?
Thank you for your help.
Binyu
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Why I can not create CTC line-type
From: John Halley Gotway
Time: Mon Nov 02 17:20:14 2020
Binyu,
I see you have a question about configuring Grid-Stat to run on the
output
from Ensemble-Stat. I took a look in your Grid-Stat config file on
WCOSS
here:
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
You have requested CTC in the output from Grid-Stat but are not seeing
any
CTC output lines being produced. Looking in your config file, I see
the
following:
fcst = {
cat_thresh = [ ==0.1 ];
level = "(*,*)";
prob = TRUE;
field = [
{ name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
{ name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
];
}
Note the setting "prob = TRUE". That tells Grid-Stat that all of this
data
should be processed a probability forecasts. MET verifies probability
forecasts by using the cat_thresh settings to define and Nx2
contingency
table and write the results to a PCT line type. The CTC line type does
not
apply to the verification of probability fields.
You can of course change the configuration to do whatever you'd like.
For
example, perhaps you'd like to verify the ensemble mean field using a
2x2
contingency table and write the output the .stat output file.
To do so, you'd just add another field... something like this:
add a fcst field...
{ name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh = [
ge0.1,
ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
add a matching obs field...
{ name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5, ge1, ge3,
ge5,
ge7, gt10];}
That should result in 7 CTC output lines, one for each threshold
defined,
and comparing the ensemble mean field to the verifying observations of
"ash".
Does that make sense? Or were you trying to do something different?
Thanks,
John Halley Gotway
On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT
<met_help at ucar.edu>
wrote:
>
> Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> Transaction: Ticket created by binyu.wang at noaa.gov
> Queue: met_help
> Subject: Why I can not create CTC line-type
> Owner: Nobody
> Requestors: binyu.wang at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
>
>
> Hello,
>
> I was trying to make performance diagram using ensemble mean, here
is the
> script I used:
>
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> verf_g2g_Raikoke_ens.CSI.sh
>
> I can create other line types like "pct, nbrctc" etc, but "ctc" is
not
> created although I did set " ctc = STAT" in the config file. All
the log
> file "run_gs.log" and configure files can be read from the script.
What is
> the problem?
>
> Thank you for your help.
>
> Binyu
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: binyu.wang at noaa.gov
Time: Tue Nov 03 09:22:13 2020
Hello John,
Thank you, and it does work.
However, I noticed under "FCST_THRESH", there are so many thresholds
which
are more than that had been defined in the config files, eg: 0.2, 0.4,
0.6
etc (see the attachment pls.). But they are not defined in the config
file, so where do they come from?
Binyu
On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Binyu,
>
> I see you have a question about configuring Grid-Stat to run on the
output
> from Ensemble-Stat. I took a look in your Grid-Stat config file on
WCOSS
> here:
>
>
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
>
> You have requested CTC in the output from Grid-Stat but are not
seeing any
> CTC output lines being produced. Looking in your config file, I see
the
> following:
>
> fcst = {
> cat_thresh = [ ==0.1 ];
> level = "(*,*)";
> prob = TRUE;
> field = [
> { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> ];
> }
>
> Note the setting "prob = TRUE". That tells Grid-Stat that all of
this data
> should be processed a probability forecasts. MET verifies
probability
> forecasts by using the cat_thresh settings to define and Nx2
contingency
> table and write the results to a PCT line type. The CTC line type
does not
> apply to the verification of probability fields.
>
> You can of course change the configuration to do whatever you'd
like. For
> example, perhaps you'd like to verify the ensemble mean field using
a 2x2
> contingency table and write the output the .stat output file.
>
> To do so, you'd just add another field... something like this:
>
> add a fcst field...
> { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh = [
ge0.1,
> ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
>
> add a matching obs field...
> { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5, ge1, ge3,
ge5,
> ge7, gt10];}
>
> That should result in 7 CTC output lines, one for each threshold
defined,
> and comparing the ensemble mean field to the verifying observations
of
> "ash".
>
> Does that make sense? Or were you trying to do something different?
>
> Thanks,
> John Halley Gotway
>
> On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > Transaction: Ticket created by binyu.wang at noaa.gov
> > Queue: met_help
> > Subject: Why I can not create CTC line-type
> > Owner: Nobody
> > Requestors: binyu.wang at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> >
> >
> > Hello,
> >
> > I was trying to make performance diagram using ensemble mean, here
is the
> > script I used:
> >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > verf_g2g_Raikoke_ens.CSI.sh
> >
> > I can create other line types like "pct, nbrctc" etc, but "ctc" is
not
> > created although I did set " ctc = STAT" in the config file.
All the
> log
> > file "run_gs.log" and configure files can be read from the script.
What
> is
> > the problem?
> >
> > Thank you for your help.
> >
> > Binyu
> >
> >
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: John Halley Gotway
Time: Tue Nov 03 09:32:29 2020
Binyu,
METviewer populates the FCST_THRESH column using the union of all the
thresholds that appear in the FCST_THRESH column of the files that
have
been loaded to that database.
When verifying probabilities, we use the threshold "==0.1" as a
shortcut to
define 10 probability bins:
>=0.0, >=0.1, >=0.2, ..., >=0.9, >=1.0
I suspect if you looked closely at the FCST_THRESH column of the
output
that you've loaded into this database, you'd find that a threshold
like
>=0.6 appears in one of those lines. I don't know which off the top of
my
head, but perhaps NBRCTC?
You could try running a command like this:
*cat `find ./ -name "*.stat"` | awk '{print $20, $24}' | sort -u*
That will find any files ending with .stat, extract the 20-th and 24-
th
columns from them (i.e. FCST_THRESH), and report the unique values.
Then
you can look to see where ">=0.6" shows up, for example.
Thanks,
John
On Tue, Nov 3, 2020 at 9:22 AM binyu.wang at noaa.gov via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
>
> Hello John,
>
> Thank you, and it does work.
>
> However, I noticed under "FCST_THRESH", there are so many thresholds
which
> are more than that had been defined in the config files, eg: 0.2,
0.4, 0.6
> etc (see the attachment pls.). But they are not defined in the
config
> file, so where do they come from?
>
> Binyu
>
> On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Binyu,
> >
> > I see you have a question about configuring Grid-Stat to run on
the
> output
> > from Ensemble-Stat. I took a look in your Grid-Stat config file on
WCOSS
> > here:
> >
> >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
> >
> > You have requested CTC in the output from Grid-Stat but are not
seeing
> any
> > CTC output lines being produced. Looking in your config file, I
see the
> > following:
> >
> > fcst = {
> > cat_thresh = [ ==0.1 ];
> > level = "(*,*)";
> > prob = TRUE;
> > field = [
> > { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> > { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> > ];
> > }
> >
> > Note the setting "prob = TRUE". That tells Grid-Stat that all of
this
> data
> > should be processed a probability forecasts. MET verifies
probability
> > forecasts by using the cat_thresh settings to define and Nx2
contingency
> > table and write the results to a PCT line type. The CTC line type
does
> not
> > apply to the verification of probability fields.
> >
> > You can of course change the configuration to do whatever you'd
like. For
> > example, perhaps you'd like to verify the ensemble mean field
using a 2x2
> > contingency table and write the output the .stat output file.
> >
> > To do so, you'd just add another field... something like this:
> >
> > add a fcst field...
> > { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh = [
ge0.1,
> > ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
> >
> > add a matching obs field...
> > { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5, ge1,
ge3, ge5,
> > ge7, gt10];}
> >
> > That should result in 7 CTC output lines, one for each threshold
defined,
> > and comparing the ensemble mean field to the verifying
observations of
> > "ash".
> >
> > Does that make sense? Or were you trying to do something
different?
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > Queue: met_help
> > > Subject: Why I can not create CTC line-type
> > > Owner: Nobody
> > > Requestors: binyu.wang at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
> >
> > >
> > >
> > > Hello,
> > >
> > > I was trying to make performance diagram using ensemble mean,
here is
> the
> > > script I used:
> > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > > verf_g2g_Raikoke_ens.CSI.sh
> > >
> > > I can create other line types like "pct, nbrctc" etc, but "ctc"
is not
> > > created although I did set " ctc = STAT" in the config file.
All the
> > log
> > > file "run_gs.log" and configure files can be read from the
script.
> What
> > is
> > > the problem?
> > >
> > > Thank you for your help.
> > >
> > > Binyu
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: binyu.wang at noaa.gov
Time: Thu Nov 05 18:37:25 2020
Thank you, John. ">=0.6" shows up at line "ECLV".
I attached part of the *stat output to the email:
Based on your email, "threshold "==0.1" as a shortcut to define 10
probability bins", so the "FCST_THRESH" in the attachment is NOT a
real
threshold, (i.e. >=0.6 refers to 60%), but "OBS_THRESH" (>=0.1) means
"obs
" larger than 0.1, am I right?
Binyu
On Tue, Nov 3, 2020 at 11:32 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Binyu,
>
> METviewer populates the FCST_THRESH column using the union of all
the
> thresholds that appear in the FCST_THRESH column of the files that
have
> been loaded to that database.
>
> When verifying probabilities, we use the threshold "==0.1" as a
shortcut to
> define 10 probability bins:
> >=0.0, >=0.1, >=0.2, ..., >=0.9, >=1.0
>
> I suspect if you looked closely at the FCST_THRESH column of the
output
> that you've loaded into this database, you'd find that a threshold
like
> >=0.6 appears in one of those lines. I don't know which off the top
of my
> head, but perhaps NBRCTC?
>
> You could try running a command like this:
>
>
> *cat `find ./ -name "*.stat"` | awk '{print $20, $24}' | sort -u*
>
> That will find any files ending with .stat, extract the 20-th and
24-th
> columns from them (i.e. FCST_THRESH), and report the unique values.
Then
> you can look to see where ">=0.6" shows up, for example.
>
> Thanks,
> John
>
>
> On Tue, Nov 3, 2020 at 9:22 AM binyu.wang at noaa.gov via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> >
> > Hello John,
> >
> > Thank you, and it does work.
> >
> > However, I noticed under "FCST_THRESH", there are so many
thresholds
> which
> > are more than that had been defined in the config files, eg: 0.2,
0.4,
> 0.6
> > etc (see the attachment pls.). But they are not defined in the
config
> > file, so where do they come from?
> >
> > Binyu
> >
> > On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Binyu,
> > >
> > > I see you have a question about configuring Grid-Stat to run on
the
> > output
> > > from Ensemble-Stat. I took a look in your Grid-Stat config file
on
> WCOSS
> > > here:
> > >
> > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
> > >
> > > You have requested CTC in the output from Grid-Stat but are not
seeing
> > any
> > > CTC output lines being produced. Looking in your config file, I
see the
> > > following:
> > >
> > > fcst = {
> > > cat_thresh = [ ==0.1 ];
> > > level = "(*,*)";
> > > prob = TRUE;
> > > field = [
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> > > { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> > > ];
> > > }
> > >
> > > Note the setting "prob = TRUE". That tells Grid-Stat that all of
this
> > data
> > > should be processed a probability forecasts. MET verifies
probability
> > > forecasts by using the cat_thresh settings to define and Nx2
> contingency
> > > table and write the results to a PCT line type. The CTC line
type does
> > not
> > > apply to the verification of probability fields.
> > >
> > > You can of course change the configuration to do whatever you'd
like.
> For
> > > example, perhaps you'd like to verify the ensemble mean field
using a
> 2x2
> > > contingency table and write the output the .stat output file.
> > >
> > > To do so, you'd just add another field... something like this:
> > >
> > > add a fcst field...
> > > { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh = [
ge0.1,
> > > ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
> > >
> > > add a matching obs field...
> > > { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5, ge1,
ge3,
> ge5,
> > > ge7, gt10];}
> > >
> > > That should result in 7 CTC output lines, one for each threshold
> defined,
> > > and comparing the ensemble mean field to the verifying
observations of
> > > "ash".
> > >
> > > Does that make sense? Or were you trying to do something
different?
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > > Queue: met_help
> > > > Subject: Why I can not create CTC line-type
> > > > Owner: Nobody
> > > > Requestors: binyu.wang at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
> > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I was trying to make performance diagram using ensemble mean,
here is
> > the
> > > > script I used:
> > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > > > verf_g2g_Raikoke_ens.CSI.sh
> > > >
> > > > I can create other line types like "pct, nbrctc" etc, but
"ctc" is
> not
> > > > created although I did set " ctc = STAT" in the config
file. All
> the
> > > log
> > > > file "run_gs.log" and configure files can be read from the
script.
> > What
> > > is
> > > > the problem?
> > > >
> > > > Thank you for your help.
> > > >
> > > > Binyu
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: John Halley Gotway
Time: Fri Nov 06 09:00:40 2020
Binyu,
The appearance of FCST_THRESH = >=0.6 in the ECLV line is just a
function
of how the ECLV logic is implemented. I suspect including the ECLV
line
type in your analysis will cause more confusion than benefit. If
you're not
familiar with the economic cost-loss value line type and the
statistics
derived from it, I'd recommend just turning that output off:
eclv = NONE;
This table lists the output columns for the ECLV line type:
https://dtcenter.github.io/MET/latest/Users_Guide/point-
stat.html#id18
And there is a brief description of it here:
https://dtcenter.github.io/MET/latest/Users_Guide/appendixC.html?highlight=eclv#economic-
cost-loss-relative-value-eclv
John
On Thu, Nov 5, 2020 at 6:37 PM binyu.wang at noaa.gov via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
>
> Thank you, John. ">=0.6" shows up at line "ECLV".
>
> I attached part of the *stat output to the email:
> Based on your email, "threshold "==0.1" as a shortcut to define 10
> probability bins", so the "FCST_THRESH" in the attachment is NOT a
real
> threshold, (i.e. >=0.6 refers to 60%), but "OBS_THRESH" (>=0.1)
means "obs
> " larger than 0.1, am I right?
>
> Binyu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Tue, Nov 3, 2020 at 11:32 AM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Binyu,
> >
> > METviewer populates the FCST_THRESH column using the union of all
the
> > thresholds that appear in the FCST_THRESH column of the files that
have
> > been loaded to that database.
> >
> > When verifying probabilities, we use the threshold "==0.1" as a
shortcut
> to
> > define 10 probability bins:
> > >=0.0, >=0.1, >=0.2, ..., >=0.9, >=1.0
> >
> > I suspect if you looked closely at the FCST_THRESH column of the
output
> > that you've loaded into this database, you'd find that a threshold
like
> > >=0.6 appears in one of those lines. I don't know which off the
top of my
> > head, but perhaps NBRCTC?
> >
> > You could try running a command like this:
> >
> >
> > *cat `find ./ -name "*.stat"` | awk '{print $20, $24}' | sort -u*
> >
> > That will find any files ending with .stat, extract the 20-th and
24-th
> > columns from them (i.e. FCST_THRESH), and report the unique
values. Then
> > you can look to see where ">=0.6" shows up, for example.
> >
> > Thanks,
> > John
> >
> >
> > On Tue, Nov 3, 2020 at 9:22 AM binyu.wang at noaa.gov via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> > >
> > > Hello John,
> > >
> > > Thank you, and it does work.
> > >
> > > However, I noticed under "FCST_THRESH", there are so many
thresholds
> > which
> > > are more than that had been defined in the config files, eg:
0.2, 0.4,
> > 0.6
> > > etc (see the attachment pls.). But they are not defined in the
config
> > > file, so where do they come from?
> > >
> > > Binyu
> > >
> > > On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Binyu,
> > > >
> > > > I see you have a question about configuring Grid-Stat to run
on the
> > > output
> > > > from Ensemble-Stat. I took a look in your Grid-Stat config
file on
> > WCOSS
> > > > here:
> > > >
> > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
> > > >
> > > > You have requested CTC in the output from Grid-Stat but are
not
> seeing
> > > any
> > > > CTC output lines being produced. Looking in your config file,
I see
> the
> > > > following:
> > > >
> > > > fcst = {
> > > > cat_thresh = [ ==0.1 ];
> > > > level = "(*,*)";
> > > > prob = TRUE;
> > > > field = [
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> > > > { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> > > > ];
> > > > }
> > > >
> > > > Note the setting "prob = TRUE". That tells Grid-Stat that all
of this
> > > data
> > > > should be processed a probability forecasts. MET verifies
probability
> > > > forecasts by using the cat_thresh settings to define and Nx2
> > contingency
> > > > table and write the results to a PCT line type. The CTC line
type
> does
> > > not
> > > > apply to the verification of probability fields.
> > > >
> > > > You can of course change the configuration to do whatever
you'd like.
> > For
> > > > example, perhaps you'd like to verify the ensemble mean field
using a
> > 2x2
> > > > contingency table and write the output the .stat output file.
> > > >
> > > > To do so, you'd just add another field... something like this:
> > > >
> > > > add a fcst field...
> > > > { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh =
[
> ge0.1,
> > > > ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
> > > >
> > > > add a matching obs field...
> > > > { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5,
ge1, ge3,
> > ge5,
> > > > ge7, gt10];}
> > > >
> > > > That should result in 7 CTC output lines, one for each
threshold
> > defined,
> > > > and comparing the ensemble mean field to the verifying
observations
> of
> > > > "ash".
> > > >
> > > > Does that make sense? Or were you trying to do something
different?
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > >
> > > > On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > >
> > > > > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > > > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: Why I can not create CTC line-type
> > > > > Owner: Nobody
> > > > > Requestors: binyu.wang at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
> > > >
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I was trying to make performance diagram using ensemble
mean, here
> is
> > > the
> > > > > script I used:
> > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > > > > verf_g2g_Raikoke_ens.CSI.sh
> > > > >
> > > > > I can create other line types like "pct, nbrctc" etc, but
"ctc" is
> > not
> > > > > created although I did set " ctc = STAT" in the config
file. All
> > the
> > > > log
> > > > > file "run_gs.log" and configure files can be read from the
script.
> > > What
> > > > is
> > > > > the problem?
> > > > >
> > > > > Thank you for your help.
> > > > >
> > > > > Binyu
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: binyu.wang at noaa.gov
Time: Mon Nov 16 12:12:33 2020
Hello John,
Thank you.
I have another question for you. I know I was supposed to start a new
ticket, but you had worked on the similar question before, so I
started the
question here:
I used to have problems reading in some satellite data before and I
ended
to have to convert them to "txt' file and then start from there. Now
the
data creator tried to provide new data in netcdf format so we can read
them
using MET directly. I tried an example using "plot_data_plane", here
is
what I got:
cd /gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/Download/Raikoke/New
$ plot_data_plane
VOLCAT_HIMAWARI-
8_FLDK_s2020296_173000_v300250_VCB_w167_FLDK_b2020295_204000_g001.nc
test.ps 'name="ash_mass_loading";level="(*,*)";'
DEBUG 1: Opening data file:
VOLCAT_HIMAWARI-
8_FLDK_s2020296_173000_v300250_VCB_w167_FLDK_b2020295_204000_g001.nc
terminate called after throwing an instance of
'netCDF::exceptions::NcInvalidCoords'
what(): NetCDF: Index exceeds dimension bound
file: ncVar.cpp line:1598
Aborted (core dumped)
Frankly I still don't know what information is needed to fill in to
the
header file. Would you help to take a look and let us know what is
missing?
So I can get back to the data producer. Thank you.
Binyu
On Fri, Nov 6, 2020 at 11:00 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Binyu,
>
> The appearance of FCST_THRESH = >=0.6 in the ECLV line is just a
function
> of how the ECLV logic is implemented. I suspect including the ECLV
line
> type in your analysis will cause more confusion than benefit. If
you're not
> familiar with the economic cost-loss value line type and the
statistics
> derived from it, I'd recommend just turning that output off:
> eclv = NONE;
>
> This table lists the output columns for the ECLV line type:
> https://dtcenter.github.io/MET/latest/Users_Guide/point-
stat.html#id18
> And there is a brief description of it here:
>
>
>
https://dtcenter.github.io/MET/latest/Users_Guide/appendixC.html?highlight=eclv#economic-
cost-loss-relative-value-eclv
>
> John
>
> On Thu, Nov 5, 2020 at 6:37 PM binyu.wang at noaa.gov via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> >
> > Thank you, John. ">=0.6" shows up at line "ECLV".
> >
> > I attached part of the *stat output to the email:
> > Based on your email, "threshold "==0.1" as a shortcut to define
10
> > probability bins", so the "FCST_THRESH" in the attachment is NOT
a real
> > threshold, (i.e. >=0.6 refers to 60%), but "OBS_THRESH" (>=0.1)
means
> "obs
> > " larger than 0.1, am I right?
> >
> > Binyu
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Nov 3, 2020 at 11:32 AM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Binyu,
> > >
> > > METviewer populates the FCST_THRESH column using the union of
all the
> > > thresholds that appear in the FCST_THRESH column of the files
that have
> > > been loaded to that database.
> > >
> > > When verifying probabilities, we use the threshold "==0.1" as a
> shortcut
> > to
> > > define 10 probability bins:
> > > >=0.0, >=0.1, >=0.2, ..., >=0.9, >=1.0
> > >
> > > I suspect if you looked closely at the FCST_THRESH column of the
output
> > > that you've loaded into this database, you'd find that a
threshold like
> > > >=0.6 appears in one of those lines. I don't know which off the
top of
> my
> > > head, but perhaps NBRCTC?
> > >
> > > You could try running a command like this:
> > >
> > >
> > > *cat `find ./ -name "*.stat"` | awk '{print $20, $24}' | sort
-u*
> > >
> > > That will find any files ending with .stat, extract the 20-th
and 24-th
> > > columns from them (i.e. FCST_THRESH), and report the unique
values.
> Then
> > > you can look to see where ">=0.6" shows up, for example.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > > On Tue, Nov 3, 2020 at 9:22 AM binyu.wang at noaa.gov via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
>
> > > >
> > > > Hello John,
> > > >
> > > > Thank you, and it does work.
> > > >
> > > > However, I noticed under "FCST_THRESH", there are so many
thresholds
> > > which
> > > > are more than that had been defined in the config files, eg:
0.2,
> 0.4,
> > > 0.6
> > > > etc (see the attachment pls.). But they are not defined in the
config
> > > > file, so where do they come from?
> > > >
> > > > Binyu
> > > >
> > > > On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Binyu,
> > > > >
> > > > > I see you have a question about configuring Grid-Stat to run
on the
> > > > output
> > > > > from Ensemble-Stat. I took a look in your Grid-Stat config
file on
> > > WCOSS
> > > > > here:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
> > > > >
> > > > > You have requested CTC in the output from Grid-Stat but are
not
> > seeing
> > > > any
> > > > > CTC output lines being produced. Looking in your config
file, I see
> > the
> > > > > following:
> > > > >
> > > > > fcst = {
> > > > > cat_thresh = [ ==0.1 ];
> > > > > level = "(*,*)";
> > > > > prob = TRUE;
> > > > > field = [
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> > > > > ];
> > > > > }
> > > > >
> > > > > Note the setting "prob = TRUE". That tells Grid-Stat that
all of
> this
> > > > data
> > > > > should be processed a probability forecasts. MET verifies
> probability
> > > > > forecasts by using the cat_thresh settings to define and Nx2
> > > contingency
> > > > > table and write the results to a PCT line type. The CTC line
type
> > does
> > > > not
> > > > > apply to the verification of probability fields.
> > > > >
> > > > > You can of course change the configuration to do whatever
you'd
> like.
> > > For
> > > > > example, perhaps you'd like to verify the ensemble mean
field
> using a
> > > 2x2
> > > > > contingency table and write the output the .stat output
file.
> > > > >
> > > > > To do so, you'd just add another field... something like
this:
> > > > >
> > > > > add a fcst field...
> > > > > { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE; cat_thresh
= [
> > ge0.1,
> > > > > ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
> > > > >
> > > > > add a matching obs field...
> > > > > { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5,
ge1,
> ge3,
> > > ge5,
> > > > > ge7, gt10];}
> > > > >
> > > > > That should result in 7 CTC output lines, one for each
threshold
> > > defined,
> > > > > and comparing the ensemble mean field to the verifying
observations
> > of
> > > > > "ash".
> > > > >
> > > > > Does that make sense? Or were you trying to do something
different?
> > > > >
> > > > > Thanks,
> > > > > John Halley Gotway
> > > > >
> > > > > On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT <
> > > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > > > > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: Why I can not create CTC line-type
> > > > > > Owner: Nobody
> > > > > > Requestors: binyu.wang at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
> > > > >
> > > > > >
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I was trying to make performance diagram using ensemble
mean,
> here
> > is
> > > > the
> > > > > > script I used:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > > > > > verf_g2g_Raikoke_ens.CSI.sh
> > > > > >
> > > > > > I can create other line types like "pct, nbrctc" etc, but
"ctc"
> is
> > > not
> > > > > > created although I did set " ctc = STAT" in the config
file.
> All
> > > the
> > > > > log
> > > > > > file "run_gs.log" and configure files can be read from the
> script.
> > > > What
> > > > > is
> > > > > > the problem?
> > > > > >
> > > > > > Thank you for your help.
> > > > > >
> > > > > > Binyu
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Why I can not create CTC line-type
From: John Halley Gotway
Time: Mon Nov 16 12:25:33 2020
Binyu,
I'm going to resolve this ticket and answer your other question in a
new
one.
Thanks,
John
On Mon, Nov 16, 2020 at 12:13 PM binyu.wang at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
>
> Hello John,
>
> Thank you.
>
> I have another question for you. I know I was supposed to start a
new
> ticket, but you had worked on the similar question before, so I
started the
> question here:
> I used to have problems reading in some satellite data before and I
ended
> to have to convert them to "txt' file and then start from there. Now
the
> data creator tried to provide new data in netcdf format so we can
read them
> using MET directly. I tried an example using "plot_data_plane", here
is
> what I got:
>
> cd /gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/Download/Raikoke/New
> $ plot_data_plane
>
> VOLCAT_HIMAWARI-
8_FLDK_s2020296_173000_v300250_VCB_w167_FLDK_b2020295_204000_
> g001.nc
> test.ps 'name="ash_mass_loading";level="(*,*)";'
>
> DEBUG 1: Opening data file:
>
> VOLCAT_HIMAWARI-
8_FLDK_s2020296_173000_v300250_VCB_w167_FLDK_b2020295_204000_
> g001.nc
> terminate called after throwing an instance of
> 'netCDF::exceptions::NcInvalidCoords'
> what(): NetCDF: Index exceeds dimension bound
> file: ncVar.cpp line:1598
> Aborted (core dumped)
>
> Frankly I still don't know what information is needed to fill in to
the
> header file. Would you help to take a look and let us know what is
missing?
> So I can get back to the data producer. Thank you.
>
> Binyu
>
> On Fri, Nov 6, 2020 at 11:00 AM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Binyu,
> >
> > The appearance of FCST_THRESH = >=0.6 in the ECLV line is just a
function
> > of how the ECLV logic is implemented. I suspect including the ECLV
line
> > type in your analysis will cause more confusion than benefit. If
you're
> not
> > familiar with the economic cost-loss value line type and the
statistics
> > derived from it, I'd recommend just turning that output off:
> > eclv = NONE;
> >
> > This table lists the output columns for the ECLV line type:
> >
> https://dtcenter.github.io/MET/latest/Users_Guide/point-
stat.html#id18
> > And there is a brief description of it here:
> >
> >
> >
>
https://dtcenter.github.io/MET/latest/Users_Guide/appendixC.html?highlight=eclv#economic-
cost-loss-relative-value-eclv
> >
> > John
> >
> > On Thu, Nov 5, 2020 at 6:37 PM binyu.wang at noaa.gov via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> > >
> > > Thank you, John. ">=0.6" shows up at line "ECLV".
> > >
> > > I attached part of the *stat output to the email:
> > > Based on your email, "threshold "==0.1" as a shortcut to define
10
> > > probability bins", so the "FCST_THRESH" in the attachment is
NOT a
> real
> > > threshold, (i.e. >=0.6 refers to 60%), but "OBS_THRESH" (>=0.1)
means
> > "obs
> > > " larger than 0.1, am I right?
> > >
> > > Binyu
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Nov 3, 2020 at 11:32 AM John Halley Gotway via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Binyu,
> > > >
> > > > METviewer populates the FCST_THRESH column using the union of
all the
> > > > thresholds that appear in the FCST_THRESH column of the files
that
> have
> > > > been loaded to that database.
> > > >
> > > > When verifying probabilities, we use the threshold "==0.1" as
a
> > shortcut
> > > to
> > > > define 10 probability bins:
> > > > >=0.0, >=0.1, >=0.2, ..., >=0.9, >=1.0
> > > >
> > > > I suspect if you looked closely at the FCST_THRESH column of
the
> output
> > > > that you've loaded into this database, you'd find that a
threshold
> like
> > > > >=0.6 appears in one of those lines. I don't know which off
the top
> of
> > my
> > > > head, but perhaps NBRCTC?
> > > >
> > > > You could try running a command like this:
> > > >
> > > >
> > > > *cat `find ./ -name "*.stat"` | awk '{print $20, $24}' | sort
-u*
> > > >
> > > > That will find any files ending with .stat, extract the 20-th
and
> 24-th
> > > > columns from them (i.e. FCST_THRESH), and report the unique
values.
> > Then
> > > > you can look to see where ">=0.6" shows up, for example.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > > On Tue, Nov 3, 2020 at 9:22 AM binyu.wang at noaa.gov via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312 >
> > > > >
> > > > > Hello John,
> > > > >
> > > > > Thank you, and it does work.
> > > > >
> > > > > However, I noticed under "FCST_THRESH", there are so many
> thresholds
> > > > which
> > > > > are more than that had been defined in the config files, eg:
0.2,
> > 0.4,
> > > > 0.6
> > > > > etc (see the attachment pls.). But they are not defined in
the
> config
> > > > > file, so where do they come from?
> > > > >
> > > > > Binyu
> > > > >
> > > > > On Mon, Nov 2, 2020 at 7:20 PM John Halley Gotway via RT <
> > > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Binyu,
> > > > > >
> > > > > > I see you have a question about configuring Grid-Stat to
run on
> the
> > > > > output
> > > > > > from Ensemble-Stat. I took a look in your Grid-Stat config
file
> on
> > > > WCOSS
> > > > > > here:
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/parm/verf_g2g_grid_stat_regn_config_Raikoke.ens.csi
> > > > > >
> > > > > > You have requested CTC in the output from Grid-Stat but
are not
> > > seeing
> > > > > any
> > > > > > CTC output lines being produced. Looking in your config
file, I
> see
> > > the
> > > > > > following:
> > > > > >
> > > > > > fcst = {
> > > > > > cat_thresh = [ ==0.1 ];
> > > > > > level = "(*,*)";
> > > > > > prob = TRUE;
> > > > > > field = [
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.1"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge0.5"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge1"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge3"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge5"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge7"; },
> > > > > > { name="VAFTD_L18000-0_ENS_FREQ_ge10"; }
> > > > > > ];
> > > > > > }
> > > > > >
> > > > > > Note the setting "prob = TRUE". That tells Grid-Stat that
all of
> > this
> > > > > data
> > > > > > should be processed a probability forecasts. MET verifies
> > probability
> > > > > > forecasts by using the cat_thresh settings to define and
Nx2
> > > > contingency
> > > > > > table and write the results to a PCT line type. The CTC
line type
> > > does
> > > > > not
> > > > > > apply to the verification of probability fields.
> > > > > >
> > > > > > You can of course change the configuration to do whatever
you'd
> > like.
> > > > For
> > > > > > example, perhaps you'd like to verify the ensemble mean
field
> > using a
> > > > 2x2
> > > > > > contingency table and write the output the .stat output
file.
> > > > > >
> > > > > > To do so, you'd just add another field... something like
this:
> > > > > >
> > > > > > add a fcst field...
> > > > > > { name = "VAFTD_L18000-0_ENS_MEAN"; prob = FALSE;
cat_thresh = [
> > > ge0.1,
> > > > > > ge0.5, ge1, ge3, ge5, ge7, ge10 ]; }
> > > > > >
> > > > > > add a matching obs field...
> > > > > > { name = "ash"; level = "L0"; cat_thresh = [ ge0.1, ge0.5,
ge1,
> > ge3,
> > > > ge5,
> > > > > > ge7, gt10];}
> > > > > >
> > > > > > That should result in 7 CTC output lines, one for each
threshold
> > > > defined,
> > > > > > and comparing the ensemble mean field to the verifying
> observations
> > > of
> > > > > > "ash".
> > > > > >
> > > > > > Does that make sense? Or were you trying to do something
> different?
> > > > > >
> > > > > > Thanks,
> > > > > > John Halley Gotway
> > > > > >
> > > > > > On Mon, Nov 2, 2020 at 1:30 PM binyu.wang at noaa.gov via RT
<
> > > > > > met_help at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > > Mon Nov 02 13:30:13 2020: Request 97312 was acted upon.
> > > > > > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > > > > > Queue: met_help
> > > > > > > Subject: Why I can not create CTC line-type
> > > > > > > Owner: Nobody
> > > > > > > Requestors: binyu.wang at noaa.gov
> > > > > > > Status: new
> > > > > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97312
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I was trying to make performance diagram using ensemble
mean,
> > here
> > > is
> > > > > the
> > > > > > > script I used:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/dell2/emc/modeling/noscrub/Binyu.Wang/MET/grid2grid/verf_met_ens/ush/
> > > > > > > verf_g2g_Raikoke_ens.CSI.sh
> > > > > > >
> > > > > > > I can create other line types like "pct, nbrctc" etc,
but "ctc"
> > is
> > > > not
> > > > > > > created although I did set " ctc = STAT" in the
config file.
> > All
> > > > the
> > > > > > log
> > > > > > > file "run_gs.log" and configure files can be read from
the
> > script.
> > > > > What
> > > > > > is
> > > > > > > the problem?
> > > > > > >
> > > > > > > Thank you for your help.
> > > > > > >
> > > > > > > Binyu
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list