[Met_help] [rt.rap.ucar.edu #90347] History for GO_Index
John Halley Gotway via RT
met_help at ucar.edu
Mon Jun 3 09:36:02 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, running under MET 8.1 I am getting the following error below when
running GO_INDEX. I have 3 SL1L2 stat files for MET to read and they are
attached. My command line is:
/h/WXQC/met-8.1/bin/stat_analysis -lookin
/h/data/global/WXQC/data/met/ptstat/go_index -out
/h/data/global/WXQC/data/met/summary/go_index -tmp_dir
/h/data/global/WXQC/data/met/tmp -job go_index -line_type SL1L2
-out_line_type CNT -dump_row /h/data/global/WXQC/data/met/filter_job_4
-config
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index_k
orea_study -v 4.0
My config file is attached. What is causing this error?
[1612670 qcteam DEV9 /home/qcteam/STAT_ANAL -]>
/h/WXQC/met-8.1/bin/stat_analysis -lookin
/h/data/global/WXQC/data/met/ptstat/go_index >
DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
DEBUG 1: Creating STAT-Analysis output file
"/h/data/global/WXQC/data/met/summary/go_index"
DEBUG 1: Default Config File:
/h/WXQC/met-8.1/share/met/config/STATAnalysisConfig_default
DEBUG 1: User Config File:
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index_k
orea_study
DEBUG 4: Default Job from the config file: "-fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var TMP
-fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP
-fcst_var TMP -fcst_var TMP -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL
-fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850
-fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10
-fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
-line_type SL1L2 -line_type SL1L2 -column RMSE -column RMSE -column RMSE
-column RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight 4.00000
-weight 3.00000 -weight 2.00000 -weight 1.00000 -weight 8.00000 -weight
6.00000 -weight 4.00000 -weight 2.00000 -weight 8.00000 -weight 6.00000
-weight 4.00000 -weight 2.00000 -weight 4.00000 -weight 3.00000 -weight
2.00000 -weight 1.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000
-weight 2.00000 "
DEBUG 4: Amending default job with command line options: "-job go_index
-line_type SL1L2 -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job_4"
DEBUG 4: New default jobstring: "-job go_index -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var TMP
-fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP
-fcst_var TMP -fcst_var TMP -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL
-fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850
-fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10
-fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2 -column RMSE
-column RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE -column RMSE -column RMSE -weight 4.00000 -weight 3.00000 -weight
2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight 2.00000
-weight 1.00000 -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight
1.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000
-weight 8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight 8.00000
-weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
/h/data/global/WXQC/data/met/filter_job_4 -out_line_type CNT -out_alpha
0.05000 -rank_corr_flag 0 "
DEBUG 2: Processing 3 STAT files.
DEBUG 3: Processing STAT file
"/h/data/global/WXQC/data/met/ptstat/go_index/TT_SL1L2.stat" ... 1 of 3
DEBUG 4: Reading MET header columns:
DEBUG 4:
/h/WXQC/met-8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
ERROR :
ERROR : AsciiHeader::read() -> trouble reading file:
ERROR :
/h/WXQC/met-8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
ERROR :
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: GO_Index
From: John Halley Gotway
Time: Fri May 24 12:02:16 2019
Hi Bob,
I see you're having trouble with the GO Index job from stat-analysis.
The
first clue as to what's going on is this error message:
*AsciiHeader::read() -> trouble reading file:*
*/h/WXQC/met-
8.1/share/met/tabl**e_files/met_header_columns_**JOB_LIST:.txt*
When stat-analysis runs it grabs the version number from the first
column
of the data it's reading (X.Y.Z) and then it reads the corresponding
header
file:
met_header_columns_X.Y.Z.txt
Where there should be a version number listed in that file name, I
instead
see "*JOB_LIST:*" which looks like the output that stat-analysis
prints to
the screen or writes to the "-out" file.
Sure enough, when I checked the SL_SL1L2.stat, TT_SL1L2.stat, and
WS_SL1L2.stat files, they all start with this line:
"JOB_LIST: ..."
Even though you named those files with a ".stat" suffix, these are not
really .stat files. Here's what I suspect happened... You run
STAT-Analysis to aggregate together some SL1L2 lines and wrote the
output
to a file using the "-out" job command option. That produced these
files.
Please replace the "-out" option with the "-out_stat" option instead.
That
will write true .stat files which you can then read as input to
stat-analysis.
I realize that this is a pesky little difference. From the beginning,
stat-analysis either printed its output to the screen or to a file
using
the "-out" option. The "-out_stat" option is much newer and writes
true
.stat files that stat-analysis can read back in or can be loaded into
METviewer. But we didn't want to remove the "-out" option in case
folks
were using it... so we added "-out_stat" as a new option instead.
Thanks,
John
On Fri, May 24, 2019 at 10:12 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri May 24 10:12:07 2019: Request 90347 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: GO_Index
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90347 >
>
>
> John, running under MET 8.1 I am getting the following error below
when
> running GO_INDEX. I have 3 SL1L2 stat files for MET to read and
they are
> attached. My command line is:
>
>
>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index -out
> /h/data/global/WXQC/data/met/summary/go_index -tmp_dir
> /h/data/global/WXQC/data/met/tmp -job go_index -line_type SL1L2
> -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job_4
> -config
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index_k
> orea_study -v 4.0
>
>
>
> My config file is attached. What is causing this error?
>
>
>
> [1612670 qcteam DEV9 /home/qcteam/STAT_ANAL -]>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index >
>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>
> DEBUG 1: Creating STAT-Analysis output file
> "/h/data/global/WXQC/data/met/summary/go_index"
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1/share/met/config/STATAnalysisConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index_k
> orea_study
>
> DEBUG 4: Default Job from the config file: "-fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var PRMSL -fcst_var PRMSL
-fcst_var PRMSL
> -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev P250
> -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev
Z10
> -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2
-line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2
> -line_type SL1L2 -line_type SL1L2 -column RMSE -column RMSE -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
> RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
> RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000
> -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000
> -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight 8.00000
-weight
> 6.00000 -weight 4.00000 -weight 2.00000 -weight 8.00000 -weight
6.00000
> -weight 4.00000 -weight 2.00000 -weight 4.00000 -weight 3.00000
-weight
> 2.00000 -weight 1.00000 -weight 8.00000 -weight 6.00000 -weight
4.00000
> -weight 2.00000 "
>
> DEBUG 4: Amending default job with command line options: "-job
go_index
> -line_type SL1L2 -out_line_type CNT -dump_row
> /h/data/global/WXQC/data/met/filter_job_4"
>
> DEBUG 4: New default jobstring: "-job go_index -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
-fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var PRMSL -fcst_var PRMSL
-fcst_var PRMSL
> -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev P250
> -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev
Z10
> -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2 -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
> RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
> RMSE -column RMSE -column RMSE -weight 4.00000 -weight 3.00000
-weight
> 2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight
2.00000
> -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight 2.00000
-weight
> 1.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight
2.00000
> -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000
-weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000
> -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
> /h/data/global/WXQC/data/met/filter_job_4 -out_line_type CNT
-out_alpha
> 0.05000 -rank_corr_flag 0 "
>
> DEBUG 2: Processing 3 STAT files.
>
> DEBUG 3: Processing STAT file
> "/h/data/global/WXQC/data/met/ptstat/go_index/TT_SL1L2.stat" ... 1
of 3
>
> DEBUG 4: Reading MET header columns:
>
> DEBUG 4:
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
> ERROR : AsciiHeader::read() -> trouble reading file:
>
> ERROR :
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
From: robert.craig.2 at us.af.mil
Time: Fri May 24 12:28:13 2019
Thanks John for the quick reply, I will give that a try.
General question - Does MET viewer plot Roebber diagrams? I saw a
chart in your last tutorial but not sure if MET generated it.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, May 24, 2019 1:02 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
Hi Bob,
I see you're having trouble with the GO Index job from stat-analysis.
The first clue as to what's going on is this error message:
*AsciiHeader::read() -> trouble reading file:*
*/h/WXQC/met-
8.1/share/met/tabl**e_files/met_header_columns_**JOB_LIST:.txt*
When stat-analysis runs it grabs the version number from the first
column of the data it's reading (X.Y.Z) and then it reads the
corresponding header
file:
met_header_columns_X.Y.Z.txt
Where there should be a version number listed in that file name, I
instead see "*JOB_LIST:*" which looks like the output that stat-
analysis prints to the screen or writes to the "-out" file.
Sure enough, when I checked the SL_SL1L2.stat, TT_SL1L2.stat, and
WS_SL1L2.stat files, they all start with this line:
"JOB_LIST: ..."
Even though you named those files with a ".stat" suffix, these are not
really .stat files. Here's what I suspect happened... You run STAT-
Analysis to aggregate together some SL1L2 lines and wrote the output
to a file using the "-out" job command option. That produced these
files.
Please replace the "-out" option with the "-out_stat" option instead.
That will write true .stat files which you can then read as input to
stat-analysis.
I realize that this is a pesky little difference. From the beginning,
stat-analysis either printed its output to the screen or to a file
using the "-out" option. The "-out_stat" option is much newer and
writes true .stat files that stat-analysis can read back in or can be
loaded into METviewer. But we didn't want to remove the "-out" option
in case folks were using it... so we added "-out_stat" as a new option
instead.
Thanks,
John
On Fri, May 24, 2019 at 10:12 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri May 24 10:12:07 2019: Request 90347 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: GO_Index
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7C5fbc682c4415412017f908d6e0720112%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636943177625973440&sdata=
> PR5GjN00Adg3sSLI7eVqkbJFH7mb6Y%2BF2fa7ccRAdUM%3D&reserved=0 >
>
>
> John, running under MET 8.1 I am getting the following error below
> when running GO_INDEX. I have 3 SL1L2 stat files for MET to read
and
> they are attached. My command line is:
>
>
>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index -out
> /h/data/global/WXQC/data/met/summary/go_index -tmp_dir
> /h/data/global/WXQC/data/met/tmp -job go_index -line_type SL1L2
> -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job_4
> -config
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_I
> ndex_k
> orea_study -v 4.0
>
>
>
> My config file is attached. What is causing this error?
>
>
>
> [1612670 qcteam DEV9 /home/qcteam/STAT_ANAL -]>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index >
>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>
> DEBUG 1: Creating STAT-Analysis output file
> "/h/data/global/WXQC/data/met/summary/go_index"
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1/share/met/config/STATAnalysisConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_I
> ndex_k
> orea_study
>
> DEBUG 4: Default Job from the config file: "-fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
> PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_lev P250
> -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P400
-fcst_lev
> P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850 -fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev
> Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2
-line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -weight 4.00000 -weight
3.00000
> -weight 2.00000 -weight 1.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 8.00000 -weight
> 6.00000 -weight 4.00000 -weight 2.00000 -weight 8.00000 -weight
> 6.00000 -weight 4.00000 -weight 2.00000 -weight 4.00000 -weight
> 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 8.00000 -weight 6.00000 -weight
> 4.00000 -weight 2.00000 "
>
> DEBUG 4: Amending default job with command line options: "-job
> go_index -line_type SL1L2 -out_line_type CNT -dump_row
> /h/data/global/WXQC/data/met/filter_job_4"
>
> DEBUG 4: New default jobstring: "-job go_index -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
> PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_lev P250
> -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P400
-fcst_lev
> P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850 -fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev
> Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2 -column
> RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -weight 4.00000
> -weight 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight
> 2.00000 -weight
> 1.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight
> 2.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight
> 2.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
> /h/data/global/WXQC/data/met/filter_job_4 -out_line_type CNT
> -out_alpha
> 0.05000 -rank_corr_flag 0 "
>
> DEBUG 2: Processing 3 STAT files.
>
> DEBUG 3: Processing STAT file
> "/h/data/global/WXQC/data/met/ptstat/go_index/TT_SL1L2.stat" ... 1
of
> 3
>
> DEBUG 4: Reading MET header columns:
>
> DEBUG 4:
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
> ERROR : AsciiHeader::read() -> trouble reading file:
>
> ERROR :
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
>
>
------------------------------------------------
Subject: GO_Index
From: robert.craig.2 at us.af.mil
Time: Fri May 24 13:03:39 2019
John, well that got me further but I still am encountering an error.
The
updated stat files are attached. My command is:
/h/WXQC/met-8.1/bin/stat_analysis -lookin
/h/data/global/WXQC/data/met/ptstat/go_index -out
/h/data/global/WXQC/data/met/summary/go_index -tmp_dir
/h/data/global/WXQC/data/met/tmp -job go_index -line_type SL1L2
-out_line_type
CNT -dump_row /h/data/global/WXQC/data/met/filter_job -config
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index
-v
4.0
The error is:
[1612838 qcteam DEV9 /h/data/global/WXQC/data/met/summary -]>
ig/STATAnalysisConfig_GO_Index -v 4.0
<
DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
DEBUG 1: Creating STAT-Analysis output file
"/h/data/global/WXQC/data/met/summary/go_index"
DEBUG 1: Default Config File:
/h/WXQC/met-8.1/share/met/config/STATAnalysisConfig_default
DEBUG 1: User Config File:
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_Index
DEBUG 4: Default Job from the config file: "-fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_var WIND -fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var HGT -fcst_var
HGT -fcst_var HGT -fcst_var HGT -fcst_var PRMSL -fcst_var PRMSL
-fcst_var
PRMSL -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev
P250 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10
-fcst_lev
Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P400 -fcst_lev P400 -fcst_lev P700 -fcst_lev P700 -fcst_lev P700
-fcst_lev
P700 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 "
DEBUG 4: Amending default job with command line options: "-job
go_index -line_type SL1L2 -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job"
DEBUG 4: New default jobstring: "-job go_index -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_var WIND -fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var HGT -fcst_var
HGT -fcst_var HGT -fcst_var HGT -fcst_var PRMSL -fcst_var PRMSL
-fcst_var
PRMSL -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev
P250 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10
-fcst_lev
Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P400 -fcst_lev P400 -fcst_lev P700 -fcst_lev P700 -fcst_lev P700
-fcst_lev
P700 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type
SL1L2 -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000
-weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
/h/data/global/WXQC/data/met/filter_job -out_line_type CNT -out_alpha
0.05000 -rank_corr_flag 0 "
DEBUG 2: Processing 3 STAT files.
DEBUG 3: Processing STAT file
"/h/data/global/WXQC/data/met/ptstat/go_index/TT_SL1L2.stat" ... 1 of
3
DEBUG 3: Processing STAT file
"/h/data/global/WXQC/data/met/ptstat/go_index/WS_SL1L2.stat" ... 2 of
3
DEBUG 3: Processing STAT file
"/h/data/global/WXQC/data/met/ptstat/go_index/SL_SL1L2.stat" ... 3 of
3
DEBUG 2: STAT Lines read = 129
DEBUG 2: STAT Lines retained = 25
DEBUG 4: process_job(jobstring):-job filter -dump_row
./filter_job.stat"
DEBUG 4:
DEBUG 4: Initializing Job 1 to default job: "-job go_index -fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000
-fcst_lead
120000 -fcst_lead 240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
HGT -fcst_var HGT -fcst_var HGT -fcst_var HGT -fcst_var PRMSL
-fcst_var
PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250
-fcst_lev
P250 -fcst_lev P250 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P400 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P700 -fcst_lev P700
-fcst_lev
P700 -fcst_lev P700 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
P850 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev Z2
-fcst_lev
Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev
Z0 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
SL1L2 -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000
-weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
/h/data/global/WXQC/data/met/filter_job -out_line_type CNT -out_alpha
0.05000 -rank_corr_flag 0 "
DEBUG 4:
DEBUG 4: Amending Job 1 with options: "-job filter -dump_row
./filter_job.stat"
DEBUG 4:
DEBUG 4: Amending Job 1 with command line options: "-job go_index
-line_type
SL1L2 -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job"
DEBUG 2:
DEBUG 2: Processing Job 1: -job go_index -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_var WIND -fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var HGT -fcst_var
HGT -fcst_var HGT -fcst_var HGT -fcst_var PRMSL -fcst_var PRMSL
-fcst_var
PRMSL -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev
P250 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10
-fcst_lev
Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P400 -fcst_lev P400 -fcst_lev P700 -fcst_lev P700 -fcst_lev P700
-fcst_lev
P700 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type
SL1L2 -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000
-weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
/h/data/global/WXQC/data/met/filter_job -out_line_type CNT -out_alpha
0.05000 -rank_corr_flag 0
DEBUG 1: Creating dump row output file
"/h/data/global/WXQC/data/met/filter_job"
ERROR :
ERROR : compute_ss_index() -> this job may only be called when the "-
model"
option has been used exactly twice to specify the forecast model
followed by
the reference model: -job go_index -fcst_lead 120000 -fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_lead 120000
-fcst_lead
240000 -fcst_lead 360000 -fcst_lead 480000 -fcst_var WIND -fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var DPT -fcst_var
DPT -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var HGT -fcst_var
HGT -fcst_var HGT -fcst_var HGT -fcst_var PRMSL -fcst_var PRMSL
-fcst_var
PRMSL -fcst_var PRMSL -fcst_lev P250 -fcst_lev P250 -fcst_lev P250
-fcst_lev
P250 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10
-fcst_lev
Z10 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400
-fcst_lev
P400 -fcst_lev P400 -fcst_lev P700 -fcst_lev P700 -fcst_lev P700
-fcst_lev
P700 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850 -fcst_lev P850
-fcst_lev
Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev
P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev
Z2 -fcst_lev Z2 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev
P400 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type
SL1L2 -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
-column
RMSE -weight 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000
-weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -weight
4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
/h/data/global/WXQC/data/met/filter_job -out_line_type CNT -out_alpha
0.05000 -rank_corr_flag 0
ERROR :
ERROR :
ERROR : main() -> encountered an error value of 1. Calling
clean_up() and
usage() before exiting.
ERROR :
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, May 24, 2019 1:02 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
Hi Bob,
I see you're having trouble with the GO Index job from stat-analysis.
The
first clue as to what's going on is this error message:
*AsciiHeader::read() -> trouble reading file:*
*/h/WXQC/met-
8.1/share/met/tabl**e_files/met_header_columns_**JOB_LIST:.txt*
When stat-analysis runs it grabs the version number from the first
column of
the data it's reading (X.Y.Z) and then it reads the corresponding
header
file:
met_header_columns_X.Y.Z.txt
Where there should be a version number listed in that file name, I
instead see
"*JOB_LIST:*" which looks like the output that stat-analysis prints to
the
screen or writes to the "-out" file.
Sure enough, when I checked the SL_SL1L2.stat, TT_SL1L2.stat, and
WS_SL1L2.stat files, they all start with this line:
"JOB_LIST: ..."
Even though you named those files with a ".stat" suffix, these are not
really
.stat files. Here's what I suspect happened... You run STAT-Analysis
to
aggregate together some SL1L2 lines and wrote the output to a file
using the
"-out" job command option. That produced these files.
Please replace the "-out" option with the "-out_stat" option instead.
That
will write true .stat files which you can then read as input to stat-
analysis.
I realize that this is a pesky little difference. From the beginning,
stat-analysis either printed its output to the screen or to a file
using the
"-out" option. The "-out_stat" option is much newer and writes true
.stat
files that stat-analysis can read back in or can be loaded into
METviewer.
But we didn't want to remove the "-out" option in case folks were
using it...
so we added "-out_stat" as a new option instead.
Thanks,
John
On Fri, May 24, 2019 at 10:12 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri May 24 10:12:07 2019: Request 90347 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: GO_Index
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7C5fbc682c4415412017f908d6e0720112%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636943177625973440&sdata=
> PR5GjN00Adg3sSLI7eVqkbJFH7mb6Y%2BF2fa7ccRAdUM%3D&reserved=0 >
>
>
> John, running under MET 8.1 I am getting the following error below
> when running GO_INDEX. I have 3 SL1L2 stat files for MET to read
and
> they are attached. My command line is:
>
>
>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index -out
> /h/data/global/WXQC/data/met/summary/go_index -tmp_dir
> /h/data/global/WXQC/data/met/tmp -job go_index -line_type SL1L2
> -out_line_type CNT -dump_row
/h/data/global/WXQC/data/met/filter_job_4
> -config
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_I
> ndex_k
> orea_study -v 4.0
>
>
>
> My config file is attached. What is causing this error?
>
>
>
> [1612670 qcteam DEV9 /home/qcteam/STAT_ANAL -]>
> /h/WXQC/met-8.1/bin/stat_analysis -lookin
> /h/data/global/WXQC/data/met/ptstat/go_index >
>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>
> DEBUG 1: Creating STAT-Analysis output file
> "/h/data/global/WXQC/data/met/summary/go_index"
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1/share/met/config/STATAnalysisConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/STATAnalysisConfig_GO_I
> ndex_k
> orea_study
>
> DEBUG 4: Default Job from the config file: "-fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
> PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_lev P250
> -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P400
-fcst_lev
> P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850 -fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev
> Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2
-line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type SL1L2 -line_type
> SL1L2 -line_type SL1L2 -line_type SL1L2 -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -weight 4.00000 -weight
3.00000
> -weight 2.00000 -weight 1.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 8.00000 -weight
> 6.00000 -weight 4.00000 -weight 2.00000 -weight 8.00000 -weight
> 6.00000 -weight 4.00000 -weight 2.00000 -weight 4.00000 -weight
> 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 8.00000 -weight 6.00000 -weight
> 4.00000 -weight 2.00000 "
>
> DEBUG 4: Amending default job with command line options: "-job
> go_index -line_type SL1L2 -out_line_type CNT -dump_row
> /h/data/global/WXQC/data/met/filter_job_4"
>
> DEBUG 4: New default jobstring: "-job go_index -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_lead 120000
> -fcst_lead
> 240000 -fcst_lead 360000 -fcst_lead 180000 -fcst_var WIND -fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
-fcst_var
> WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND -fcst_var WIND
> -fcst_var WIND -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
TMP
> -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var TMP -fcst_var
> PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_var PRMSL -fcst_lev P250
> -fcst_lev P250 -fcst_lev P250 -fcst_lev P250 -fcst_lev P400
-fcst_lev
> P400 -fcst_lev P400 -fcst_lev P400 -fcst_lev P850 -fcst_lev P850
> -fcst_lev P850 -fcst_lev P850 -fcst_lev Z10 -fcst_lev Z10 -fcst_lev
> Z10 -fcst_lev Z10 -fcst_lev P400 -fcst_lev P400 -fcst_lev P400
> -fcst_lev P400 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2 -fcst_lev Z2
> -fcst_lev
> Z0 -fcst_lev Z0 -fcst_lev Z0 -fcst_lev Z0 -line_type SL1L2 -column
> RMSE -column RMSE -column RMSE -column RMSE -column RMSE -column
RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -column RMSE
> -column RMSE -column RMSE -column RMSE -column RMSE -weight 4.00000
> -weight 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight
> 2.00000 -weight 1.00000 -weight 4.00000 -weight 3.00000 -weight
> 2.00000 -weight
> 1.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight
> 2.00000 -weight 8.00000 -weight 6.00000 -weight 4.00000 -weight
> 2.00000 -weight
> 4.00000 -weight 3.00000 -weight 2.00000 -weight 1.00000 -weight
> 8.00000 -weight 6.00000 -weight 4.00000 -weight 2.00000 -dump_row
> /h/data/global/WXQC/data/met/filter_job_4 -out_line_type CNT
> -out_alpha
> 0.05000 -rank_corr_flag 0 "
>
> DEBUG 2: Processing 3 STAT files.
>
> DEBUG 3: Processing STAT file
> "/h/data/global/WXQC/data/met/ptstat/go_index/TT_SL1L2.stat" ... 1
of
> 3
>
> DEBUG 4: Reading MET header columns:
>
> DEBUG 4:
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
> ERROR : AsciiHeader::read() -> trouble reading file:
>
> ERROR :
> /h/WXQC/met-
8.1/share/met/table_files/met_header_columns_JOB_LIST:.txt
>
> ERROR :
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
From: robert.craig.2 at us.af.mil
Time: Fri May 24 13:10:05 2019
John, I just noticed in the error output mention of a second model the
reference. I obviously don’t have a second model - is that the issue?
The user's manual doesn't explain this aspect of the go_index. To
compare two models, do I need to sets of SL1L2 files?
Thanks
Bob
------------------------------------------------
Subject: GO_Index
From: John Halley Gotway
Time: Wed May 29 10:25:46 2019
Bob,
That's correct. The GO Index is defined as the performance of one
model
relative to another model. A GO Index > 1 means that the first model
is
better and less than < 1 means that the second model is better. So
you
must list exactly 2 models. I believe the first model listed is the
"forecast" model and the second is the "reference" model.
For example, here's a GO Index command we run as part of our
regression
tests:
stat_analysis \
-lookin ref_config/point_stat/AFWAv3.4_Noahv3.3/ \
-lookin ref_config/point_stat/AFWAv3.4_Noahv2.7.1/ \
-job go_index -fcst_init_beg 2011090200 -fcst_init_end 2011090200 \
-model AFWAv3.4_Noahv3.3 -model AFWAv3.4_Noahv2.7.1 \
-vx_mask FULL -interp_mthd BILIN \
-out ref_config/stat_analysis/go_index.out \
-v 1
This searches recursively through the 2 "-lookin" directories for
files
ending in .stat. Since it's the GO Index job, it knows to look for
and
process SL1L2 and VL1L2 lines. It only processes data whose
initialization
time falls inside the defined window. And I'm only processing data
for
VX_MASK=FULL and INTERP_MTHD=BILIN.
So you really shouldn't *need* to run these pre-processing aggregation
jobs. The GO Index job can be configured to filter and aggregate the
.stat
data in whatever way you'd like. But yes, you definitely need exactly
2
models. For the sake of testing, you could try listing the same model
name
twice... which should result in a GO Index of 1... but I haven't done
that
myself so I'm not positive it'll work as expected.
As for the "reference" model, I believe the AF typically defines that
as a
persistence forecast. Frankly, that's the hardest part... generating
the
persistence forecast in the desired way. So I'd give it some thought
as to
what you're trying to compare the model's performance against.
Hope that helps clarify.
Thanks,
John
On Fri, May 24, 2019 at 1:11 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90347 >
>
> John, I just noticed in the error output mention of a second model
the
> reference. I obviously don’t have a second model - is that the
issue? The
> user's manual doesn't explain this aspect of the go_index. To
compare two
> models, do I need to sets of SL1L2 files?
>
> Thanks
> Bob
>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
From: robert.craig.2 at us.af.mil
Time: Thu May 30 08:20:10 2019
Thanks John, that got it working. In this case I am comparing two
versions of a model so didn't need to worry about persistence. Did
you guys have a method to do significance testing on the GO index
results?
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Wednesday, May 29, 2019 11:26 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
Bob,
That's correct. The GO Index is defined as the performance of one
model relative to another model. A GO Index > 1 means that the first
model is better and less than < 1 means that the second model is
better. So you must list exactly 2 models. I believe the first model
listed is the "forecast" model and the second is the "reference"
model.
For example, here's a GO Index command we run as part of our
regression
tests:
stat_analysis \
-lookin ref_config/point_stat/AFWAv3.4_Noahv3.3/ \
-lookin ref_config/point_stat/AFWAv3.4_Noahv2.7.1/ \
-job go_index -fcst_init_beg 2011090200 -fcst_init_end 2011090200 \
-model AFWAv3.4_Noahv3.3 -model AFWAv3.4_Noahv2.7.1 \
-vx_mask FULL -interp_mthd BILIN \
-out ref_config/stat_analysis/go_index.out \
-v 1
This searches recursively through the 2 "-lookin" directories for
files ending in .stat. Since it's the GO Index job, it knows to look
for and process SL1L2 and VL1L2 lines. It only processes data whose
initialization time falls inside the defined window. And I'm only
processing data for VX_MASK=FULL and INTERP_MTHD=BILIN.
So you really shouldn't *need* to run these pre-processing aggregation
jobs. The GO Index job can be configured to filter and aggregate the
.stat data in whatever way you'd like. But yes, you definitely need
exactly 2 models. For the sake of testing, you could try listing the
same model name twice... which should result in a GO Index of 1... but
I haven't done that myself so I'm not positive it'll work as expected.
As for the "reference" model, I believe the AF typically defines that
as a persistence forecast. Frankly, that's the hardest part...
generating the persistence forecast in the desired way. So I'd give
it some thought as to what you're trying to compare the model's
performance against.
Hope that helps clarify.
Thanks,
John
On Fri, May 24, 2019 at 1:11 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7Cf43ca8d25047460adbe308d6e45278d2%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947440228883345&sdata=
> 1jbjbedbn99hAP2F5fvEql5xYmSaWAqtDQXdJKpJ2sQ%3D&reserved=0 >
>
> John, I just noticed in the error output mention of a second model
the
> reference. I obviously don’t have a second model - is that the
issue?
> The user's manual doesn't explain this aspect of the go_index. To
> compare two models, do I need to sets of SL1L2 files?
>
> Thanks
> Bob
>
>
>
>
>
------------------------------------------------
Subject: GO_Index
From: John Halley Gotway
Time: Thu May 30 12:11:24 2019
Bob,
Great, glad you were able to make progress. The GO Index is typically
computed once for each model initialization. And it is computed as a
weighted average of skill scores of RMSE statistics for a variety of
model
variables, levels, and lead times. But we do not have a recommended
method
for determining significance.
However, if you have computed it for many model initializations, you
could
look at the mean of those values and estimate a confidence interval
for
that mean value.
I suspect that you'd ultimately like to determine which version of the
model performs better for which variables, levels, and lead times.
The GO
Index does a nice job summarizing that performance down into one
number.
However, it lacks all the detail that you're probably like to see.
I think you'll find scorecards in METviewer to be very useful.
Essentially, for each component of the GO Index, you can see one cell
of a
table specify which model performs better. So once you get up and
running
with METviewer, I'd recommend looking into that.
Thanks,
John
On Thu, May 30, 2019 at 8:20 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90347 >
>
> Thanks John, that got it working. In this case I am comparing two
> versions of a model so didn't need to worry about persistence. Did
you
> guys have a method to do significance testing on the GO index
results?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Wednesday, May 29, 2019 11:26 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
>
> Bob,
>
> That's correct. The GO Index is defined as the performance of one
model
> relative to another model. A GO Index > 1 means that the first
model is
> better and less than < 1 means that the second model is better. So
you
> must list exactly 2 models. I believe the first model listed is the
> "forecast" model and the second is the "reference" model.
>
> For example, here's a GO Index command we run as part of our
regression
> tests:
>
> stat_analysis \
>
> -lookin ref_config/point_stat/AFWAv3.4_Noahv3.3/ \
>
> -lookin ref_config/point_stat/AFWAv3.4_Noahv2.7.1/ \
>
> -job go_index -fcst_init_beg 2011090200 -fcst_init_end 2011090200 \
>
> -model AFWAv3.4_Noahv3.3 -model AFWAv3.4_Noahv2.7.1 \
>
> -vx_mask FULL -interp_mthd BILIN \
>
> -out ref_config/stat_analysis/go_index.out \
>
> -v 1
>
> This searches recursively through the 2 "-lookin" directories for
files
> ending in .stat. Since it's the GO Index job, it knows to look for
and
> process SL1L2 and VL1L2 lines. It only processes data whose
initialization
> time falls inside the defined window. And I'm only processing data
for
> VX_MASK=FULL and INTERP_MTHD=BILIN.
>
> So you really shouldn't *need* to run these pre-processing
aggregation
> jobs. The GO Index job can be configured to filter and aggregate
the .stat
> data in whatever way you'd like. But yes, you definitely need
exactly 2
> models. For the sake of testing, you could try listing the same
model name
> twice... which should result in a GO Index of 1... but I haven't
done that
> myself so I'm not positive it'll work as expected.
>
> As for the "reference" model, I believe the AF typically defines
that as a
> persistence forecast. Frankly, that's the hardest part...
generating the
> persistence forecast in the desired way. So I'd give it some
thought as to
> what you're trying to compare the model's performance against.
>
> Hope that helps clarify.
>
> Thanks,
> John
>
>
> On Fri, May 24, 2019 at 1:11 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL:
> >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7C0
> >
1%7Crobert.craig.2%40us.af.mil%7Cf43ca8d25047460adbe308d6e45278d2%7C83
> >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947440228883345&sdata=
> > 1jbjbedbn99hAP2F5fvEql5xYmSaWAqtDQXdJKpJ2sQ%3D&reserved=0 >
> >
> > John, I just noticed in the error output mention of a second model
the
> > reference. I obviously don’t have a second model - is that the
issue?
> > The user's manual doesn't explain this aspect of the go_index. To
> > compare two models, do I need to sets of SL1L2 files?
> >
> > Thanks
> > Bob
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
From: robert.craig.2 at us.af.mil
Time: Thu May 30 12:45:02 2019
Okay, thanks.
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Thursday, May 30, 2019 1:11 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
Bob,
Great, glad you were able to make progress. The GO Index is typically
computed once for each model initialization. And it is computed as a
weighted average of skill scores of RMSE statistics for a variety of
model variables, levels, and lead times. But we do not have a
recommended method for determining significance.
However, if you have computed it for many model initializations, you
could look at the mean of those values and estimate a confidence
interval for that mean value.
I suspect that you'd ultimately like to determine which version of the
model performs better for which variables, levels, and lead times.
The GO Index does a nice job summarizing that performance down into
one number.
However, it lacks all the detail that you're probably like to see.
I think you'll find scorecards in METviewer to be very useful.
Essentially, for each component of the GO Index, you can see one cell
of a table specify which model performs better. So once you get up
and running with METviewer, I'd recommend looking into that.
Thanks,
John
On Thu, May 30, 2019 at 8:20 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7C1e92955fab4b4568e97008d6e52a7ffe%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C0%7C636948368063398378&sdata=
> BFLXQe6CF12v6D7xVA3iWt21wenD3ELBOsZue2K8w6g%3D&reserved=0 >
>
> Thanks John, that got it working. In this case I am comparing two
> versions of a model so didn't need to worry about persistence. Did
you
> guys have a method to do significance testing on the GO index
results?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Wednesday, May 29, 2019 11:26 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90347] GO_Index
>
> Bob,
>
> That's correct. The GO Index is defined as the performance of one
> model relative to another model. A GO Index > 1 means that the
first
> model is better and less than < 1 means that the second model is
> better. So you must list exactly 2 models. I believe the first
model
> listed is the "forecast" model and the second is the "reference"
model.
>
> For example, here's a GO Index command we run as part of our
> regression
> tests:
>
> stat_analysis \
>
> -lookin ref_config/point_stat/AFWAv3.4_Noahv3.3/ \
>
> -lookin ref_config/point_stat/AFWAv3.4_Noahv2.7.1/ \
>
> -job go_index -fcst_init_beg 2011090200 -fcst_init_end 2011090200 \
>
> -model AFWAv3.4_Noahv3.3 -model AFWAv3.4_Noahv2.7.1 \
>
> -vx_mask FULL -interp_mthd BILIN \
>
> -out ref_config/stat_analysis/go_index.out \
>
> -v 1
>
> This searches recursively through the 2 "-lookin" directories for
> files ending in .stat. Since it's the GO Index job, it knows to
look
> for and process SL1L2 and VL1L2 lines. It only processes data whose
> initialization time falls inside the defined window. And I'm only
> processing data for VX_MASK=FULL and INTERP_MTHD=BILIN.
>
> So you really shouldn't *need* to run these pre-processing
aggregation
> jobs. The GO Index job can be configured to filter and aggregate
the
> .stat data in whatever way you'd like. But yes, you definitely need
> exactly 2 models. For the sake of testing, you could try listing
the
> same model name twice... which should result in a GO Index of 1...
but
> I haven't done that myself so I'm not positive it'll work as
expected.
>
> As for the "reference" model, I believe the AF typically defines
that
> as a persistence forecast. Frankly, that's the hardest part...
> generating the persistence forecast in the desired way. So I'd give
> it some thought as to what you're trying to compare the model's
performance against.
>
> Hope that helps clarify.
>
> Thanks,
> John
>
>
> On Fri, May 24, 2019 at 1:11 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL:
> >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90347&data=02%7
> > C0
> >
1%7Crobert.craig.2%40us.af.mil%7Cf43ca8d25047460adbe308d6e45278d2%7C
> > 83
> >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947440228883345&sdat
> > a=
> > 1jbjbedbn99hAP2F5fvEql5xYmSaWAqtDQXdJKpJ2sQ%3D&reserved=0 >
> >
> > John, I just noticed in the error output mention of a second model
> > the reference. I obviously don’t have a second model - is that
the issue?
> > The user's manual doesn't explain this aspect of the go_index. To
> > compare two models, do I need to sets of SL1L2 files?
> >
> > Thanks
> > Bob
> >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list