[Met_help] [rt.rap.ucar.edu #99725] History for ask a question about TCPairsConfig file
John Halley Gotway via RT
met_help at ucar.edu
Thu Apr 29 08:52:24 MDT 2021
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
Can I ask a few questions regarding the MET-TC tools? In
TCPairsConfig_default there are settings related to "time window":
**------
//
// Model initialization time windows to include or exclude
//
init_beg = "";
init_end = "";
init_inc = [];
init_exc = [];
//
// Valid model time window
//
valid_beg = "";
valid_end = "";
**--------
In adeck file:
AL, 29, 2020103000, 03, GFSO, TAU, ...
AL, 29, 2020103012, 03, HWRF, TAU, ...
AL, 29, 2020103018, 03, HMON, TAU ...
In bdeck file:
the time is from 2020102900 to 2020111306
To me it seems that the time is not consistent.
1. According to
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
the 3rd column in adeck file is "Warning Date-Time-Group", and TAU is
"Forecast time". Does it mean that, 2020103000 (for GFSO) corresponds to
"int_beg" in TCPairsConfig file?
2. For different models, the first "Warning Date-Time-Group" is different.
e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a specific model,
different "Warning Date-Time-Group" has different TAUs. Therefore I wonder
how can I set the time related items in the tc_pairs config file? For
instance, the model initialization time window and valid model time window:
Many thanks.
Best,
Yan
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: John Halley Gotway
Time: Tue Apr 27 16:30:01 2021
Hi Yan,
I see you have a question about how the TC-Pairs config file options
are
applied to the input ADECK and BDECK track data.
First, you are correct about the ATCF timestamps. For ADECK data, the
3rd
column is the model initialization time and the TAU is the forecast
hour.
And the valid time is computed as the init time + lead time. For Best
track
data, the 3rd column is the Best track valid time and the TAU is just
0.
You are wondering how those time filtering options in the TC-Pairs
config
file are applied. These time filters are ONLY APPLIED to the ADECK
data.
They are not applied to the BDECK data.
In the config file comments that's what we mean by "*model*
initialization
time":
// Specify a model initialization time window in YYYYMMDD[_HH[MMSS]]
format
In the tc_pairs.cc source file, the track filtering function is called
on
this line:
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
TC-Pairs just parses ALL the input BDECK track data. For each ADECK
track
that survives the filtering step, we search all the BDECK tracks
looking
for a match.
Hopefully that helps clarify.
Thanks,
John Halley Gotway
On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> Transaction: Ticket created by yan.jin at noaa.gov
> Queue: met_help
> Subject: ask a question about TCPairsConfig file
> Owner: Nobody
> Requestors: yan.jin at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
>
>
> Hi,
>
> Can I ask a few questions regarding the MET-TC tools? In
> TCPairsConfig_default there are settings related to "time window":
> **------
> //
> // Model initialization time windows to include or exclude
> //
> init_beg = "";
> init_end = "";
> init_inc = [];
> init_exc = [];
>
> //
> // Valid model time window
> //
> valid_beg = "";
> valid_end = "";
> **--------
>
> In adeck file:
> AL, 29, 2020103000, 03, GFSO, TAU, ...
> AL, 29, 2020103012, 03, HWRF, TAU, ...
> AL, 29, 2020103018, 03, HMON, TAU ...
>
> In bdeck file:
> the time is from 2020102900 to 2020111306
>
> To me it seems that the time is not consistent.
>
> 1. According to
> https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> the 3rd column in adeck file is "Warning Date-Time-Group", and TAU
is
> "Forecast time". Does it mean that, 2020103000 (for GFSO)
corresponds to
> "int_beg" in TCPairsConfig file?
>
> 2. For different models, the first "Warning Date-Time-Group" is
different.
> e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a specific
model,
> different "Warning Date-Time-Group" has different TAUs. Therefore I
wonder
> how can I set the time related items in the tc_pairs config file?
For
> instance, the model initialization time window and valid model time
window:
>
> Many thanks.
> Best,
> Yan
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: Yan Jin - NOAA Affiliate
Time: Wed Apr 28 08:50:22 2021
Hi John,
Thanks for your explanation. Another question is :
In this example
https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
3 models are used, but there are no specified "Model initialization
time windows" or "Valid model time window" in the config file.
consensus = [
{
name = "CONS";
members = [ "HWRF", "AVNO", "GFDL" ];
required = [ false, false, false ];
min_req = 2;
}
];
If they do have have the same model initialization time do I need to
set
their common time period? For instance, in my last example,
***In adeck file:
AL, 29, 2020103000, 03, GFSO, TAU, ...
AL, 29, 2020103012, 03, HWRF, TAU, ...
AL, 29, 2020103018, 03, HMON, TAU ...
:
:
AL, 29, 2020111300, 03, GFSO, 192
AL, 29, 2020111300, 03, HWRF, 54,
AL, 29, 2020111300, 03, HMON, 36
***
I wonder is the following setting correct?
// Model initialization time windows to include or exclude
//
init_beg = "2020103018"; //the common initial time is 2020103018
init_end = "2020111300";
init_inc = [];
init_exc = [];
// Valid model time window
//
valid_beg = "2020103018"; //?not sure
valid_end = "2020111300"; //?not sure
Many thanks.
Best,
Yan
On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Hi Yan,
>
> I see you have a question about how the TC-Pairs config file options
are
> applied to the input ADECK and BDECK track data.
>
> First, you are correct about the ATCF timestamps. For ADECK data,
the 3rd
> column is the model initialization time and the TAU is the forecast
hour.
> And the valid time is computed as the init time + lead time. For
Best track
> data, the 3rd column is the Best track valid time and the TAU is
just 0.
>
> You are wondering how those time filtering options in the TC-Pairs
config
> file are applied. These time filters are ONLY APPLIED to the ADECK
data.
> They are not applied to the BDECK data.
>
> In the config file comments that's what we mean by "*model*
initialization
> time":
>
> // Specify a model initialization time window in YYYYMMDD[_HH[MMSS]]
format
>
>
> In the tc_pairs.cc source file, the track filtering function is
called on
> this line:
>
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
>
> TC-Pairs just parses ALL the input BDECK track data. For each ADECK
track
> that survives the filtering step, we search all the BDECK tracks
looking
> for a match.
>
> Hopefully that helps clarify.
>
> Thanks,
> John Halley Gotway
>
> On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > Transaction: Ticket created by yan.jin at noaa.gov
> > Queue: met_help
> > Subject: ask a question about TCPairsConfig file
> > Owner: Nobody
> > Requestors: yan.jin at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> >
> >
> > Hi,
> >
> > Can I ask a few questions regarding the MET-TC tools? In
> > TCPairsConfig_default there are settings related to "time window":
> > **------
> > //
> > // Model initialization time windows to include or exclude
> > //
> > init_beg = "";
> > init_end = "";
> > init_inc = [];
> > init_exc = [];
> >
> > //
> > // Valid model time window
> > //
> > valid_beg = "";
> > valid_end = "";
> > **--------
> >
> > In adeck file:
> > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > AL, 29, 2020103018, 03, HMON, TAU ...
> >
> > In bdeck file:
> > the time is from 2020102900 to 2020111306
> >
> > To me it seems that the time is not consistent.
> >
> > 1. According to
> > https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > the 3rd column in adeck file is "Warning Date-Time-Group", and TAU
is
> > "Forecast time". Does it mean that, 2020103000 (for GFSO)
corresponds to
> > "int_beg" in TCPairsConfig file?
> >
> > 2. For different models, the first "Warning Date-Time-Group" is
> different.
> > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a
specific
> model,
> > different "Warning Date-Time-Group" has different TAUs. Therefore
I
> wonder
> > how can I set the time related items in the tc_pairs config file?
For
> > instance, the model initialization time window and valid model
time
> window:
> >
> > Many thanks.
> > Best,
> > Yan
> >
> >
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: John Halley Gotway
Time: Wed Apr 28 09:43:55 2021
Yan,
You do NOT need to define any time windows when running TC-Pairs. The
default behavior is to process all tracks found in the input ADECK
files
and search for matching tracks in the BDECK files. I would recommend
just
running with the default TC-Pairs configuration file.
If for some reason, you want to limit the ADECK tracks being
processed, you
can do so by specifying a list of model names or time windows.
I do see specifically that you're asking about using the consensus
config
file option to define a consensus track.
consensus = [
{
name = "CONS";
members = [ "HWRF", "AVNO", "GFDL" ];
required = [ false, false, false ];
min_req = 2;
}
];
The setting above is used to define consensus tracks (i.e. mean
location
and intensity tracks) from these 3 component models. For each
initialization time found in the input data, TC-Pairs will attempt to
derive this consensus track. As long as at least 2 of the 3 are
present
(min_req=2), it'll compute the consensus track names CONS.
You can modify this however you'd like... change the existing
consensus
definition or add as many new ones as you'd like. Multiple entries
would be
formatted like this:
consensus [ { #define first one here# }, { #define second one here#
}, {
#define third one here# } ];
Thanks,
John
On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
>
> Hi John,
>
> Thanks for your explanation. Another question is :
>
> In this example
>
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
>
> 3 models are used, but there are no specified "Model initialization
> time windows" or "Valid model time window" in the config file.
> consensus = [
> {
> name = "CONS";
> members = [ "HWRF", "AVNO", "GFDL" ];
> required = [ false, false, false ];
> min_req = 2;
> }
> ];
>
> If they do have have the same model initialization time do I need to
set
> their common time period? For instance, in my last example,
>
> ***In adeck file:
> AL, 29, 2020103000, 03, GFSO, TAU, ...
> AL, 29, 2020103012, 03, HWRF, TAU, ...
> AL, 29, 2020103018, 03, HMON, TAU ...
> :
> :
> AL, 29, 2020111300, 03, GFSO, 192
> AL, 29, 2020111300, 03, HWRF, 54,
> AL, 29, 2020111300, 03, HMON, 36
> ***
> I wonder is the following setting correct?
>
> // Model initialization time windows to include or exclude
> //
> init_beg = "2020103018"; //the common initial time is 2020103018
> init_end = "2020111300";
> init_inc = [];
> init_exc = [];
>
> // Valid model time window
> //
> valid_beg = "2020103018"; //?not sure
> valid_end = "2020111300"; //?not sure
>
> Many thanks.
> Best,
> Yan
>
> On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Yan,
> >
> > I see you have a question about how the TC-Pairs config file
options are
> > applied to the input ADECK and BDECK track data.
> >
> > First, you are correct about the ATCF timestamps. For ADECK data,
the 3rd
> > column is the model initialization time and the TAU is the
forecast hour.
> > And the valid time is computed as the init time + lead time. For
Best
> track
> > data, the 3rd column is the Best track valid time and the TAU is
just 0.
> >
> > You are wondering how those time filtering options in the TC-Pairs
config
> > file are applied. These time filters are ONLY APPLIED to the ADECK
data.
> > They are not applied to the BDECK data.
> >
> > In the config file comments that's what we mean by "*model*
> initialization
> > time":
> >
> > // Specify a model initialization time window in
YYYYMMDD[_HH[MMSS]]
> format
> >
> >
> > In the tc_pairs.cc source file, the track filtering function is
called on
> > this line:
> >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> >
> > TC-Pairs just parses ALL the input BDECK track data. For each
ADECK track
> > that survives the filtering step, we search all the BDECK tracks
looking
> > for a match.
> >
> > Hopefully that helps clarify.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > > Transaction: Ticket created by yan.jin at noaa.gov
> > > Queue: met_help
> > > Subject: ask a question about TCPairsConfig file
> > > Owner: Nobody
> > > Requestors: yan.jin at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> >
> > >
> > >
> > > Hi,
> > >
> > > Can I ask a few questions regarding the MET-TC tools? In
> > > TCPairsConfig_default there are settings related to "time
window":
> > > **------
> > > //
> > > // Model initialization time windows to include or exclude
> > > //
> > > init_beg = "";
> > > init_end = "";
> > > init_inc = [];
> > > init_exc = [];
> > >
> > > //
> > > // Valid model time window
> > > //
> > > valid_beg = "";
> > > valid_end = "";
> > > **--------
> > >
> > > In adeck file:
> > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > AL, 29, 2020103018, 03, HMON, TAU ...
> > >
> > > In bdeck file:
> > > the time is from 2020102900 to 2020111306
> > >
> > > To me it seems that the time is not consistent.
> > >
> > > 1. According to
> > >
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > the 3rd column in adeck file is "Warning Date-Time-Group", and
TAU is
> > > "Forecast time". Does it mean that, 2020103000 (for GFSO)
corresponds
> to
> > > "int_beg" in TCPairsConfig file?
> > >
> > > 2. For different models, the first "Warning Date-Time-Group" is
> > different.
> > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a
specific
> > model,
> > > different "Warning Date-Time-Group" has different TAUs.
Therefore I
> > wonder
> > > how can I set the time related items in the tc_pairs config
file? For
> > > instance, the model initialization time window and valid model
time
> > window:
> > >
> > > Many thanks.
> > > Best,
> > > Yan
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: Yan Jin - NOAA Affiliate
Time: Wed Apr 28 12:36:42 2021
Hi John,
Thanks very much for your explanation.
I am currently using MET-TC tools on Jet ahd Hera. On Jet, when I run
the
Rscript to plot the statistic result using the following command:
Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
I got an error message:
Error in library(boot) : there is no package called ‘boot’
Execution halted
The plot_tcmpr.R uses library(boot), however, there seems no package
called
"boot". Could you give me some suggestions?
Many thanks.
Best,
Yan
On Wed, Apr 28, 2021 at 11:46 AM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Yan,
>
> You do NOT need to define any time windows when running TC-Pairs.
The
> default behavior is to process all tracks found in the input ADECK
files
> and search for matching tracks in the BDECK files. I would recommend
just
> running with the default TC-Pairs configuration file.
>
> If for some reason, you want to limit the ADECK tracks being
processed, you
> can do so by specifying a list of model names or time windows.
>
> I do see specifically that you're asking about using the consensus
config
> file option to define a consensus track.
>
> consensus = [
> {
> name = "CONS";
> members = [ "HWRF", "AVNO", "GFDL" ];
> required = [ false, false, false ];
> min_req = 2;
> }
> ];
>
> The setting above is used to define consensus tracks (i.e. mean
location
> and intensity tracks) from these 3 component models. For each
> initialization time found in the input data, TC-Pairs will attempt
to
> derive this consensus track. As long as at least 2 of the 3 are
present
> (min_req=2), it'll compute the consensus track names CONS.
>
> You can modify this however you'd like... change the existing
consensus
> definition or add as many new ones as you'd like. Multiple entries
would be
> formatted like this:
> consensus [ { #define first one here# }, { #define second one here#
}, {
> #define third one here# } ];
>
> Thanks,
> John
>
>
>
> On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> >
> > Hi John,
> >
> > Thanks for your explanation. Another question is :
> >
> > In this example
> >
> >
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
> >
> > 3 models are used, but there are no specified "Model
initialization
> > time windows" or "Valid model time window" in the config file.
> > consensus = [
> > {
> > name = "CONS";
> > members = [ "HWRF", "AVNO", "GFDL" ];
> > required = [ false, false, false ];
> > min_req = 2;
> > }
> > ];
> >
> > If they do have have the same model initialization time do I need
to set
> > their common time period? For instance, in my last example,
> >
> > ***In adeck file:
> > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > AL, 29, 2020103018, 03, HMON, TAU ...
> > :
> > :
> > AL, 29, 2020111300, 03, GFSO, 192
> > AL, 29, 2020111300, 03, HWRF, 54,
> > AL, 29, 2020111300, 03, HMON, 36
> > ***
> > I wonder is the following setting correct?
> >
> > // Model initialization time windows to include or exclude
> > //
> > init_beg = "2020103018"; //the common initial time is 2020103018
> > init_end = "2020111300";
> > init_inc = [];
> > init_exc = [];
> >
> > // Valid model time window
> > //
> > valid_beg = "2020103018"; //?not sure
> > valid_end = "2020111300"; //?not sure
> >
> > Many thanks.
> > Best,
> > Yan
> >
> > On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Yan,
> > >
> > > I see you have a question about how the TC-Pairs config file
options
> are
> > > applied to the input ADECK and BDECK track data.
> > >
> > > First, you are correct about the ATCF timestamps. For ADECK
data, the
> 3rd
> > > column is the model initialization time and the TAU is the
forecast
> hour.
> > > And the valid time is computed as the init time + lead time. For
Best
> > track
> > > data, the 3rd column is the Best track valid time and the TAU is
just
> 0.
> > >
> > > You are wondering how those time filtering options in the TC-
Pairs
> config
> > > file are applied. These time filters are ONLY APPLIED to the
ADECK
> data.
> > > They are not applied to the BDECK data.
> > >
> > > In the config file comments that's what we mean by "*model*
> > initialization
> > > time":
> > >
> > > // Specify a model initialization time window in
YYYYMMDD[_HH[MMSS]]
> > format
> > >
> > >
> > > In the tc_pairs.cc source file, the track filtering function is
called
> on
> > > this line:
> > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> > >
> > > TC-Pairs just parses ALL the input BDECK track data. For each
ADECK
> track
> > > that survives the filtering step, we search all the BDECK tracks
> looking
> > > for a match.
> > >
> > > Hopefully that helps clarify.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > > > Transaction: Ticket created by yan.jin at noaa.gov
> > > > Queue: met_help
> > > > Subject: ask a question about TCPairsConfig file
> > > > Owner: Nobody
> > > > Requestors: yan.jin at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Can I ask a few questions regarding the MET-TC tools? In
> > > > TCPairsConfig_default there are settings related to "time
window":
> > > > **------
> > > > //
> > > > // Model initialization time windows to include or exclude
> > > > //
> > > > init_beg = "";
> > > > init_end = "";
> > > > init_inc = [];
> > > > init_exc = [];
> > > >
> > > > //
> > > > // Valid model time window
> > > > //
> > > > valid_beg = "";
> > > > valid_end = "";
> > > > **--------
> > > >
> > > > In adeck file:
> > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > >
> > > > In bdeck file:
> > > > the time is from 2020102900 to 2020111306
> > > >
> > > > To me it seems that the time is not consistent.
> > > >
> > > > 1. According to
> > > >
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > > the 3rd column in adeck file is "Warning Date-Time-Group", and
TAU is
> > > > "Forecast time". Does it mean that, 2020103000 (for GFSO)
corresponds
> > to
> > > > "int_beg" in TCPairsConfig file?
> > > >
> > > > 2. For different models, the first "Warning Date-Time-Group"
is
> > > different.
> > > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a
specific
> > > model,
> > > > different "Warning Date-Time-Group" has different TAUs.
Therefore I
> > > wonder
> > > > how can I set the time related items in the tc_pairs config
file? For
> > > > instance, the model initialization time window and valid model
time
> > > window:
> > > >
> > > > Many thanks.
> > > > Best,
> > > > Yan
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: John Halley Gotway
Time: Wed Apr 28 14:14:33 2021
Hi Yan,
I logged on to jet and took a look. I see 3 versions of R available:
module spider R
Versions:
R/3.5.0
R/3.6.1
R/4.0.2
When I load R/3.5.0 and R/4.0.2, I'm able to run "library(boot)".
R version 3.5.0
> library(boot)
However, when I load R/3.6.1, attempting to load the boot library
results
in an error:
R version 3.6.1
> library(boot)
Error in library(boot) : there is no package called ‘boot’
Can you please try using version 3.5.0 or 4.0.2 instead?
Does that solve it? If not, there is a way to install packages locally
in a
user directory... but let's not do that unless needed.
Thanks,
John
On Wed, Apr 28, 2021 at 12:37 PM Yan Jin - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
>
> Hi John,
>
> Thanks very much for your explanation.
>
> I am currently using MET-TC tools on Jet ahd Hera. On Jet, when I
run the
> Rscript to plot the statistic result using the following command:
> Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
>
> I got an error message:
> Error in library(boot) : there is no package called ‘boot’
> Execution halted
>
> The plot_tcmpr.R uses library(boot), however, there seems no package
called
> "boot". Could you give me some suggestions?
>
> Many thanks.
> Best,
> Yan
>
> On Wed, Apr 28, 2021 at 11:46 AM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Yan,
> >
> > You do NOT need to define any time windows when running TC-Pairs.
The
> > default behavior is to process all tracks found in the input ADECK
files
> > and search for matching tracks in the BDECK files. I would
recommend just
> > running with the default TC-Pairs configuration file.
> >
> > If for some reason, you want to limit the ADECK tracks being
processed,
> you
> > can do so by specifying a list of model names or time windows.
> >
> > I do see specifically that you're asking about using the consensus
config
> > file option to define a consensus track.
> >
> > consensus = [
> > {
> > name = "CONS";
> > members = [ "HWRF", "AVNO", "GFDL" ];
> > required = [ false, false, false ];
> > min_req = 2;
> > }
> > ];
> >
> > The setting above is used to define consensus tracks (i.e. mean
location
> > and intensity tracks) from these 3 component models. For each
> > initialization time found in the input data, TC-Pairs will attempt
to
> > derive this consensus track. As long as at least 2 of the 3 are
present
> > (min_req=2), it'll compute the consensus track names CONS.
> >
> > You can modify this however you'd like... change the existing
consensus
> > definition or add as many new ones as you'd like. Multiple entries
would
> be
> > formatted like this:
> > consensus [ { #define first one here# }, { #define second one
here# }, {
> > #define third one here# } ];
> >
> > Thanks,
> > John
> >
> >
> >
> > On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> > >
> > > Hi John,
> > >
> > > Thanks for your explanation. Another question is :
> > >
> > > In this example
> > >
> > >
> >
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
> > >
> > > 3 models are used, but there are no specified "Model
initialization
> > > time windows" or "Valid model time window" in the config file.
> > > consensus = [
> > > {
> > > name = "CONS";
> > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > required = [ false, false, false ];
> > > min_req = 2;
> > > }
> > > ];
> > >
> > > If they do have have the same model initialization time do I
need to
> set
> > > their common time period? For instance, in my last example,
> > >
> > > ***In adeck file:
> > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > :
> > > :
> > > AL, 29, 2020111300, 03, GFSO, 192
> > > AL, 29, 2020111300, 03, HWRF, 54,
> > > AL, 29, 2020111300, 03, HMON, 36
> > > ***
> > > I wonder is the following setting correct?
> > >
> > > // Model initialization time windows to include or exclude
> > > //
> > > init_beg = "2020103018"; //the common initial time is 2020103018
> > > init_end = "2020111300";
> > > init_inc = [];
> > > init_exc = [];
> > >
> > > // Valid model time window
> > > //
> > > valid_beg = "2020103018"; //?not sure
> > > valid_end = "2020111300"; //?not sure
> > >
> > > Many thanks.
> > > Best,
> > > Yan
> > >
> > > On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Yan,
> > > >
> > > > I see you have a question about how the TC-Pairs config file
options
> > are
> > > > applied to the input ADECK and BDECK track data.
> > > >
> > > > First, you are correct about the ATCF timestamps. For ADECK
data, the
> > 3rd
> > > > column is the model initialization time and the TAU is the
forecast
> > hour.
> > > > And the valid time is computed as the init time + lead time.
For Best
> > > track
> > > > data, the 3rd column is the Best track valid time and the TAU
is just
> > 0.
> > > >
> > > > You are wondering how those time filtering options in the TC-
Pairs
> > config
> > > > file are applied. These time filters are ONLY APPLIED to the
ADECK
> > data.
> > > > They are not applied to the BDECK data.
> > > >
> > > > In the config file comments that's what we mean by "*model*
> > > initialization
> > > > time":
> > > >
> > > > // Specify a model initialization time window in
YYYYMMDD[_HH[MMSS]]
> > > format
> > > >
> > > >
> > > > In the tc_pairs.cc source file, the track filtering function
is
> called
> > on
> > > > this line:
> > > >
> > > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> > > >
> > > > TC-Pairs just parses ALL the input BDECK track data. For each
ADECK
> > track
> > > > that survives the filtering step, we search all the BDECK
tracks
> > looking
> > > > for a match.
> > > >
> > > > Hopefully that helps clarify.
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > >
> > > > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via
RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > > > > Transaction: Ticket created by yan.jin at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: ask a question about TCPairsConfig file
> > > > > Owner: Nobody
> > > > > Requestors: yan.jin at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > Can I ask a few questions regarding the MET-TC tools? In
> > > > > TCPairsConfig_default there are settings related to "time
window":
> > > > > **------
> > > > > //
> > > > > // Model initialization time windows to include or exclude
> > > > > //
> > > > > init_beg = "";
> > > > > init_end = "";
> > > > > init_inc = [];
> > > > > init_exc = [];
> > > > >
> > > > > //
> > > > > // Valid model time window
> > > > > //
> > > > > valid_beg = "";
> > > > > valid_end = "";
> > > > > **--------
> > > > >
> > > > > In adeck file:
> > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > >
> > > > > In bdeck file:
> > > > > the time is from 2020102900 to 2020111306
> > > > >
> > > > > To me it seems that the time is not consistent.
> > > > >
> > > > > 1. According to
> > > > >
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > > > the 3rd column in adeck file is "Warning Date-Time-Group",
and TAU
> is
> > > > > "Forecast time". Does it mean that, 2020103000 (for GFSO)
> corresponds
> > > to
> > > > > "int_beg" in TCPairsConfig file?
> > > > >
> > > > > 2. For different models, the first "Warning Date-Time-Group"
is
> > > > different.
> > > > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a
specific
> > > > model,
> > > > > different "Warning Date-Time-Group" has different TAUs.
Therefore I
> > > > wonder
> > > > > how can I set the time related items in the tc_pairs config
file?
> For
> > > > > instance, the model initialization time window and valid
model time
> > > > window:
> > > > >
> > > > > Many thanks.
> > > > > Best,
> > > > > Yan
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: Yan Jin - NOAA Affiliate
Time: Wed Apr 28 14:43:52 2021
Hi John,
Thanks very much for your instructions.
I set the environment on NOAA-Jet following this instruction:
http://dtcenter.org/community-code/metplus/metplus-3-1-existing-builds
Here is my script: METplusSetup.jet.sh
*-----
module load intel
module load intelpython/3.6.5
module load netcdf/4.6.1
module load hdf5/1.10.4
module load contrib
module use /contrib/met/modulefiles
module load met/9.1
module load nco/4.9.1
module load wgrib/1.8.1.0b
module load wgrib2/2.0.8
module load R/4.0.2
#module use /contrib/met/METplus/modulefiles
#module load metplus/3.1.1
export MET_BUILD_BASE=/contrib/met/9.1
export METPLUS_VRFY_DIR=/mnt/lfs4/HFIP/hwrfv3/Yan.Jin/Verification
export METPLUS_BUILD_BASE=/contrib/met/METplus/METplus-3.1.1
export
METPLUS_DATA=/lfs1/HFIP/dtc-hurr/Julie.Prestopnik/METplus/METplus-
3.1_sample_data
export MET_INSTALL_DIR=${MET_BUILD_BASE}
export MET_BASE=${MET_INSTALL_DIR}/share/met
Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
*---
I firstly use R/3.6.1 as suggested in the instruction, but there is no
boot
library.
Then I changed to R/4.0.2, and included the two highlighted lines,
then I
got the error message:
**
[Yan.Jin at fe3 Verification]$ ./METplusSetup.jet.sh
Lmod has detected the following error: Cannot load module
"metplus/3.1.1".
At
least one of these module(s) must be loaded:
R/3.6.1
***
If I deleted the highlighted lines, there is no error message.
I wonder if i need to add these lines to my .sh file?
Many thanks.
Best,
Yan
On Wed, Apr 28, 2021 at 4:14 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Hi Yan,
>
> I logged on to jet and took a look. I see 3 versions of R available:
>
> module spider R
> Versions:
> R/3.5.0
> R/3.6.1
> R/4.0.2
>
> When I load R/3.5.0 and R/4.0.2, I'm able to run "library(boot)".
>
> R version 3.5.0
> > library(boot)
>
> However, when I load R/3.6.1, attempting to load the boot library
results
> in an error:
>
> R version 3.6.1
> > library(boot)
> Error in library(boot) : there is no package called ‘boot’
>
> Can you please try using version 3.5.0 or 4.0.2 instead?
> Does that solve it? If not, there is a way to install packages
locally in a
> user directory... but let's not do that unless needed.
>
> Thanks,
> John
>
> On Wed, Apr 28, 2021 at 12:37 PM Yan Jin - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> >
> > Hi John,
> >
> > Thanks very much for your explanation.
> >
> > I am currently using MET-TC tools on Jet ahd Hera. On Jet, when I
run the
> > Rscript to plot the statistic result using the following command:
> > Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
> >
> > I got an error message:
> > Error in library(boot) : there is no package called ‘boot’
> > Execution halted
> >
> > The plot_tcmpr.R uses library(boot), however, there seems no
package
> called
> > "boot". Could you give me some suggestions?
> >
> > Many thanks.
> > Best,
> > Yan
> >
> > On Wed, Apr 28, 2021 at 11:46 AM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Yan,
> > >
> > > You do NOT need to define any time windows when running TC-
Pairs. The
> > > default behavior is to process all tracks found in the input
ADECK
> files
> > > and search for matching tracks in the BDECK files. I would
recommend
> just
> > > running with the default TC-Pairs configuration file.
> > >
> > > If for some reason, you want to limit the ADECK tracks being
processed,
> > you
> > > can do so by specifying a list of model names or time windows.
> > >
> > > I do see specifically that you're asking about using the
consensus
> config
> > > file option to define a consensus track.
> > >
> > > consensus = [
> > > {
> > > name = "CONS";
> > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > required = [ false, false, false ];
> > > min_req = 2;
> > > }
> > > ];
> > >
> > > The setting above is used to define consensus tracks (i.e. mean
> location
> > > and intensity tracks) from these 3 component models. For each
> > > initialization time found in the input data, TC-Pairs will
attempt to
> > > derive this consensus track. As long as at least 2 of the 3 are
present
> > > (min_req=2), it'll compute the consensus track names CONS.
> > >
> > > You can modify this however you'd like... change the existing
consensus
> > > definition or add as many new ones as you'd like. Multiple
entries
> would
> > be
> > > formatted like this:
> > > consensus [ { #define first one here# }, { #define second one
here#
> }, {
> > > #define third one here# } ];
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > > On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
>
> > > >
> > > > Hi John,
> > > >
> > > > Thanks for your explanation. Another question is :
> > > >
> > > > In this example
> > > >
> > > >
> > >
> >
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
> > > >
> > > > 3 models are used, but there are no specified "Model
initialization
> > > > time windows" or "Valid model time window" in the config file.
> > > > consensus = [
> > > > {
> > > > name = "CONS";
> > > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > > required = [ false, false, false ];
> > > > min_req = 2;
> > > > }
> > > > ];
> > > >
> > > > If they do have have the same model initialization time do I
need to
> > set
> > > > their common time period? For instance, in my last example,
> > > >
> > > > ***In adeck file:
> > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > :
> > > > :
> > > > AL, 29, 2020111300, 03, GFSO, 192
> > > > AL, 29, 2020111300, 03, HWRF, 54,
> > > > AL, 29, 2020111300, 03, HMON, 36
> > > > ***
> > > > I wonder is the following setting correct?
> > > >
> > > > // Model initialization time windows to include or exclude
> > > > //
> > > > init_beg = "2020103018"; //the common initial time is
2020103018
> > > > init_end = "2020111300";
> > > > init_inc = [];
> > > > init_exc = [];
> > > >
> > > > // Valid model time window
> > > > //
> > > > valid_beg = "2020103018"; //?not sure
> > > > valid_end = "2020111300"; //?not sure
> > > >
> > > > Many thanks.
> > > > Best,
> > > > Yan
> > > >
> > > > On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Yan,
> > > > >
> > > > > I see you have a question about how the TC-Pairs config file
> options
> > > are
> > > > > applied to the input ADECK and BDECK track data.
> > > > >
> > > > > First, you are correct about the ATCF timestamps. For ADECK
data,
> the
> > > 3rd
> > > > > column is the model initialization time and the TAU is the
forecast
> > > hour.
> > > > > And the valid time is computed as the init time + lead time.
For
> Best
> > > > track
> > > > > data, the 3rd column is the Best track valid time and the
TAU is
> just
> > > 0.
> > > > >
> > > > > You are wondering how those time filtering options in the
TC-Pairs
> > > config
> > > > > file are applied. These time filters are ONLY APPLIED to the
ADECK
> > > data.
> > > > > They are not applied to the BDECK data.
> > > > >
> > > > > In the config file comments that's what we mean by "*model*
> > > > initialization
> > > > > time":
> > > > >
> > > > > // Specify a model initialization time window in
> YYYYMMDD[_HH[MMSS]]
> > > > format
> > > > >
> > > > >
> > > > > In the tc_pairs.cc source file, the track filtering function
is
> > called
> > > on
> > > > > this line:
> > > > >
> > > > >
> > > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> > > > >
> > > > > TC-Pairs just parses ALL the input BDECK track data. For
each ADECK
> > > track
> > > > > that survives the filtering step, we search all the BDECK
tracks
> > > looking
> > > > > for a match.
> > > > >
> > > > > Hopefully that helps clarify.
> > > > >
> > > > > Thanks,
> > > > > John Halley Gotway
> > > > >
> > > > > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate via
RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > > > > > Transaction: Ticket created by yan.jin at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: ask a question about TCPairsConfig file
> > > > > > Owner: Nobody
> > > > > > Requestors: yan.jin at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Can I ask a few questions regarding the MET-TC tools? In
> > > > > > TCPairsConfig_default there are settings related to "time
> window":
> > > > > > **------
> > > > > > //
> > > > > > // Model initialization time windows to include or exclude
> > > > > > //
> > > > > > init_beg = "";
> > > > > > init_end = "";
> > > > > > init_inc = [];
> > > > > > init_exc = [];
> > > > > >
> > > > > > //
> > > > > > // Valid model time window
> > > > > > //
> > > > > > valid_beg = "";
> > > > > > valid_end = "";
> > > > > > **--------
> > > > > >
> > > > > > In adeck file:
> > > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > > >
> > > > > > In bdeck file:
> > > > > > the time is from 2020102900 to 2020111306
> > > > > >
> > > > > > To me it seems that the time is not consistent.
> > > > > >
> > > > > > 1. According to
> > > > > >
> https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > > > > the 3rd column in adeck file is "Warning Date-Time-Group",
and
> TAU
> > is
> > > > > > "Forecast time". Does it mean that, 2020103000 (for GFSO)
> > corresponds
> > > > to
> > > > > > "int_beg" in TCPairsConfig file?
> > > > > >
> > > > > > 2. For different models, the first "Warning Date-Time-
Group" is
> > > > > different.
> > > > > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for a
> specific
> > > > > model,
> > > > > > different "Warning Date-Time-Group" has different TAUs.
> Therefore I
> > > > > wonder
> > > > > > how can I set the time related items in the tc_pairs
config file?
> > For
> > > > > > instance, the model initialization time window and valid
model
> time
> > > > > window:
> > > > > >
> > > > > > Many thanks.
> > > > > > Best,
> > > > > > Yan
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: Julie Prestopnik
Time: Wed Apr 28 14:58:03 2021
Hi Yan.
I just changed the modulefile on jet to be “prereq R/4.0.2” instead of
3.6.1. I also changed the instructions on the Existing Builds page to
have
it load 4.0.2 instead of 3.6.1.
Please try getting a clean shell and reloading the METplus module and
let
us know how that goes.
Julie
On Wed, Apr 28, 2021 at 2:44 PM Yan Jin - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
>
> Hi John,
>
> Thanks very much for your instructions.
>
> I set the environment on NOAA-Jet following this instruction:
> http://dtcenter.org/community-code/metplus/metplus-3-1-existing-
builds
>
> Here is my script: METplusSetup.jet.sh
>
> *-----
> module load intel
> module load intelpython/3.6.5
> module load netcdf/4.6.1
> module load hdf5/1.10.4
> module load contrib
> module use /contrib/met/modulefiles
> module load met/9.1
> module load nco/4.9.1
> module load wgrib/1.8.1.0b
> module load wgrib2/2.0.8
> module load R/4.0.2
> #module use /contrib/met/METplus/modulefiles
> #module load metplus/3.1.1
>
> export MET_BUILD_BASE=/contrib/met/9.1
> export METPLUS_VRFY_DIR=/mnt/lfs4/HFIP/hwrfv3/Yan.Jin/Verification
> export METPLUS_BUILD_BASE=/contrib/met/METplus/METplus-3.1.1
> export
>
> METPLUS_DATA=/lfs1/HFIP/dtc-hurr/Julie.Prestopnik/METplus/METplus-
3.1_sample_data
> export MET_INSTALL_DIR=${MET_BUILD_BASE}
> export MET_BASE=${MET_INSTALL_DIR}/share/met
> Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
> *---
>
> I firstly use R/3.6.1 as suggested in the instruction, but there is
no boot
> library.
>
> Then I changed to R/4.0.2, and included the two highlighted lines,
then I
> got the error message:
> **
> [Yan.Jin at fe3 Verification]$ ./METplusSetup.jet.sh
> Lmod has detected the following error: Cannot load module
"metplus/3.1.1".
> At
> least one of these module(s) must be loaded:
> R/3.6.1
> ***
>
> If I deleted the highlighted lines, there is no error message.
>
> I wonder if i need to add these lines to my .sh file?
>
> Many thanks.
> Best,
> Yan
>
> On Wed, Apr 28, 2021 at 4:14 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Yan,
> >
> > I logged on to jet and took a look. I see 3 versions of R
available:
> >
> > module spider R
> > Versions:
> > R/3.5.0
> > R/3.6.1
> > R/4.0.2
> >
> > When I load R/3.5.0 and R/4.0.2, I'm able to run "library(boot)".
> >
> > R version 3.5.0
> > > library(boot)
> >
> > However, when I load R/3.6.1, attempting to load the boot library
results
> > in an error:
> >
> > R version 3.6.1
> > > library(boot)
> > Error in library(boot) : there is no package called ‘boot’
> >
> > Can you please try using version 3.5.0 or 4.0.2 instead?
> > Does that solve it? If not, there is a way to install packages
locally
> in a
> > user directory... but let's not do that unless needed.
> >
> > Thanks,
> > John
> >
> > On Wed, Apr 28, 2021 at 12:37 PM Yan Jin - NOAA Affiliate via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> > >
> > > Hi John,
> > >
> > > Thanks very much for your explanation.
> > >
> > > I am currently using MET-TC tools on Jet ahd Hera. On Jet, when
I run
> the
> > > Rscript to plot the statistic result using the following
command:
> > > Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
> > >
> > > I got an error message:
> > > Error in library(boot) : there is no package called ‘boot’
> > > Execution halted
> > >
> > > The plot_tcmpr.R uses library(boot), however, there seems no
package
> > called
> > > "boot". Could you give me some suggestions?
> > >
> > > Many thanks.
> > > Best,
> > > Yan
> > >
> > > On Wed, Apr 28, 2021 at 11:46 AM John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Yan,
> > > >
> > > > You do NOT need to define any time windows when running TC-
Pairs. The
> > > > default behavior is to process all tracks found in the input
ADECK
> > files
> > > > and search for matching tracks in the BDECK files. I would
recommend
> > just
> > > > running with the default TC-Pairs configuration file.
> > > >
> > > > If for some reason, you want to limit the ADECK tracks being
> processed,
> > > you
> > > > can do so by specifying a list of model names or time windows.
> > > >
> > > > I do see specifically that you're asking about using the
consensus
> > config
> > > > file option to define a consensus track.
> > > >
> > > > consensus = [
> > > > {
> > > > name = "CONS";
> > > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > > required = [ false, false, false ];
> > > > min_req = 2;
> > > > }
> > > > ];
> > > >
> > > > The setting above is used to define consensus tracks (i.e.
mean
> > location
> > > > and intensity tracks) from these 3 component models. For each
> > > > initialization time found in the input data, TC-Pairs will
attempt to
> > > > derive this consensus track. As long as at least 2 of the 3
are
> present
> > > > (min_req=2), it'll compute the consensus track names CONS.
> > > >
> > > > You can modify this however you'd like... change the existing
> consensus
> > > > definition or add as many new ones as you'd like. Multiple
entries
> > would
> > > be
> > > > formatted like this:
> > > > consensus [ { #define first one here# }, { #define second one
here#
> > }, {
> > > > #define third one here# } ];
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > >
> > > > On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via
RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> > > > >
> > > > > Hi John,
> > > > >
> > > > > Thanks for your explanation. Another question is :
> > > > >
> > > > > In this example
> > > > >
> > > > >
> > > >
> > >
> >
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
> > > > >
> > > > > 3 models are used, but there are no specified "Model
initialization
> > > > > time windows" or "Valid model time window" in the config
file.
> > > > > consensus = [
> > > > > {
> > > > > name = "CONS";
> > > > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > > > required = [ false, false, false ];
> > > > > min_req = 2;
> > > > > }
> > > > > ];
> > > > >
> > > > > If they do have have the same model initialization time do I
need
> to
> > > set
> > > > > their common time period? For instance, in my last example,
> > > > >
> > > > > ***In adeck file:
> > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > > :
> > > > > :
> > > > > AL, 29, 2020111300, 03, GFSO, 192
> > > > > AL, 29, 2020111300, 03, HWRF, 54,
> > > > > AL, 29, 2020111300, 03, HMON, 36
> > > > > ***
> > > > > I wonder is the following setting correct?
> > > > >
> > > > > // Model initialization time windows to include or exclude
> > > > > //
> > > > > init_beg = "2020103018"; //the common initial time is
2020103018
> > > > > init_end = "2020111300";
> > > > > init_inc = [];
> > > > > init_exc = [];
> > > > >
> > > > > // Valid model time window
> > > > > //
> > > > > valid_beg = "2020103018"; //?not sure
> > > > > valid_end = "2020111300"; //?not sure
> > > > >
> > > > > Many thanks.
> > > > > Best,
> > > > > Yan
> > > > >
> > > > > On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT <
> > > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Hi Yan,
> > > > > >
> > > > > > I see you have a question about how the TC-Pairs config
file
> > options
> > > > are
> > > > > > applied to the input ADECK and BDECK track data.
> > > > > >
> > > > > > First, you are correct about the ATCF timestamps. For
ADECK data,
> > the
> > > > 3rd
> > > > > > column is the model initialization time and the TAU is the
> forecast
> > > > hour.
> > > > > > And the valid time is computed as the init time + lead
time. For
> > Best
> > > > > track
> > > > > > data, the 3rd column is the Best track valid time and the
TAU is
> > just
> > > > 0.
> > > > > >
> > > > > > You are wondering how those time filtering options in the
> TC-Pairs
> > > > config
> > > > > > file are applied. These time filters are ONLY APPLIED to
the
> ADECK
> > > > data.
> > > > > > They are not applied to the BDECK data.
> > > > > >
> > > > > > In the config file comments that's what we mean by
"*model*
> > > > > initialization
> > > > > > time":
> > > > > >
> > > > > > // Specify a model initialization time window in
> > YYYYMMDD[_HH[MMSS]]
> > > > > format
> > > > > >
> > > > > >
> > > > > > In the tc_pairs.cc source file, the track filtering
function is
> > > called
> > > > on
> > > > > > this line:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> > > > > >
> > > > > > TC-Pairs just parses ALL the input BDECK track data. For
each
> ADECK
> > > > track
> > > > > > that survives the filtering step, we search all the BDECK
tracks
> > > > looking
> > > > > > for a match.
> > > > > >
> > > > > > Hopefully that helps clarify.
> > > > > >
> > > > > > Thanks,
> > > > > > John Halley Gotway
> > > > > >
> > > > > > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate
via RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > Tue Apr 27 15:34:18 2021: Request 99725 was acted upon.
> > > > > > > Transaction: Ticket created by yan.jin at noaa.gov
> > > > > > > Queue: met_help
> > > > > > > Subject: ask a question about TCPairsConfig file
> > > > > > > Owner: Nobody
> > > > > > > Requestors: yan.jin at noaa.gov
> > > > > > > Status: new
> > > > > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Can I ask a few questions regarding the MET-TC tools? In
> > > > > > > TCPairsConfig_default there are settings related to
"time
> > window":
> > > > > > > **------
> > > > > > > //
> > > > > > > // Model initialization time windows to include or
exclude
> > > > > > > //
> > > > > > > init_beg = "";
> > > > > > > init_end = "";
> > > > > > > init_inc = [];
> > > > > > > init_exc = [];
> > > > > > >
> > > > > > > //
> > > > > > > // Valid model time window
> > > > > > > //
> > > > > > > valid_beg = "";
> > > > > > > valid_end = "";
> > > > > > > **--------
> > > > > > >
> > > > > > > In adeck file:
> > > > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > > > >
> > > > > > > In bdeck file:
> > > > > > > the time is from 2020102900 to 2020111306
> > > > > > >
> > > > > > > To me it seems that the time is not consistent.
> > > > > > >
> > > > > > > 1. According to
> > > > > > >
> > https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > > > > > the 3rd column in adeck file is "Warning Date-Time-
Group", and
> > TAU
> > > is
> > > > > > > "Forecast time". Does it mean that, 2020103000 (for
GFSO)
> > > corresponds
> > > > > to
> > > > > > > "int_beg" in TCPairsConfig file?
> > > > > > >
> > > > > > > 2. For different models, the first "Warning Date-Time-
Group" is
> > > > > > different.
> > > > > > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also for
a
> > specific
> > > > > > model,
> > > > > > > different "Warning Date-Time-Group" has different TAUs.
> > Therefore I
> > > > > > wonder
> > > > > > > how can I set the time related items in the tc_pairs
config
> file?
> > > For
> > > > > > > instance, the model initialization time window and valid
model
> > time
> > > > > > window:
> > > > > > >
> > > > > > > Many thanks.
> > > > > > > Best,
> > > > > > > Yan
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
--
Julie Prestopnik (she/her)
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: ask a question about TCPairsConfig file
From: Yan Jin - NOAA Affiliate
Time: Wed Apr 28 16:28:42 2021
Hi Julie,
Now it works for me. There is no error message after I put
"#module use /contrib/met/METplus/modulefiles
#module load metplus/3.1.1" to my script.
Thank you.
Best,
Yan
On Wed, Apr 28, 2021 at 4:58 PM Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Yan.
>
> I just changed the modulefile on jet to be “prereq R/4.0.2” instead
of
> 3.6.1. I also changed the instructions on the Existing Builds page
to have
> it load 4.0.2 instead of 3.6.1.
>
> Please try getting a clean shell and reloading the METplus module
and let
> us know how that goes.
>
> Julie
>
> On Wed, Apr 28, 2021 at 2:44 PM Yan Jin - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> >
> > Hi John,
> >
> > Thanks very much for your instructions.
> >
> > I set the environment on NOAA-Jet following this instruction:
> > http://dtcenter.org/community-code/metplus/metplus-3-1-existing-
builds
> >
> > Here is my script: METplusSetup.jet.sh
> >
> > *-----
> > module load intel
> > module load intelpython/3.6.5
> > module load netcdf/4.6.1
> > module load hdf5/1.10.4
> > module load contrib
> > module use /contrib/met/modulefiles
> > module load met/9.1
> > module load nco/4.9.1
> > module load wgrib/1.8.1.0b
> > module load wgrib2/2.0.8
> > module load R/4.0.2
> > #module use /contrib/met/METplus/modulefiles
> > #module load metplus/3.1.1
> >
> > export MET_BUILD_BASE=/contrib/met/9.1
> > export METPLUS_VRFY_DIR=/mnt/lfs4/HFIP/hwrfv3/Yan.Jin/Verification
> > export METPLUS_BUILD_BASE=/contrib/met/METplus/METplus-3.1.1
> > export
> >
> >
> METPLUS_DATA=/lfs1/HFIP/dtc-hurr/Julie.Prestopnik/METplus/METplus-
3.1_sample_data
> > export MET_INSTALL_DIR=${MET_BUILD_BASE}
> > export MET_BASE=${MET_INSTALL_DIR}/share/met
> > Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
> > *---
> >
> > I firstly use R/3.6.1 as suggested in the instruction, but there
is no
> boot
> > library.
> >
> > Then I changed to R/4.0.2, and included the two highlighted lines,
then I
> > got the error message:
> > **
> > [Yan.Jin at fe3 Verification]$ ./METplusSetup.jet.sh
> > Lmod has detected the following error: Cannot load module
> "metplus/3.1.1".
> > At
> > least one of these module(s) must be loaded:
> > R/3.6.1
> > ***
> >
> > If I deleted the highlighted lines, there is no error message.
> >
> > I wonder if i need to add these lines to my .sh file?
> >
> > Many thanks.
> > Best,
> > Yan
> >
> > On Wed, Apr 28, 2021 at 4:14 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Yan,
> > >
> > > I logged on to jet and took a look. I see 3 versions of R
available:
> > >
> > > module spider R
> > > Versions:
> > > R/3.5.0
> > > R/3.6.1
> > > R/4.0.2
> > >
> > > When I load R/3.5.0 and R/4.0.2, I'm able to run
"library(boot)".
> > >
> > > R version 3.5.0
> > > > library(boot)
> > >
> > > However, when I load R/3.6.1, attempting to load the boot
library
> results
> > > in an error:
> > >
> > > R version 3.6.1
> > > > library(boot)
> > > Error in library(boot) : there is no package called ‘boot’
> > >
> > > Can you please try using version 3.5.0 or 4.0.2 instead?
> > > Does that solve it? If not, there is a way to install packages
locally
> > in a
> > > user directory... but let's not do that unless needed.
> > >
> > > Thanks,
> > > John
> > >
> > > On Wed, Apr 28, 2021 at 12:37 PM Yan Jin - NOAA Affiliate via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
>
> > > >
> > > > Hi John,
> > > >
> > > > Thanks very much for your explanation.
> > > >
> > > > I am currently using MET-TC tools on Jet ahd Hera. On Jet,
when I run
> > the
> > > > Rscript to plot the statistic result using the following
command:
> > > > Rscript ${MET_BASE}/Rscripts/plot_tcmpr.R
> > > >
> > > > I got an error message:
> > > > Error in library(boot) : there is no package called ‘boot’
> > > > Execution halted
> > > >
> > > > The plot_tcmpr.R uses library(boot), however, there seems no
package
> > > called
> > > > "boot". Could you give me some suggestions?
> > > >
> > > > Many thanks.
> > > > Best,
> > > > Yan
> > > >
> > > > On Wed, Apr 28, 2021 at 11:46 AM John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > > Yan,
> > > > >
> > > > > You do NOT need to define any time windows when running TC-
Pairs.
> The
> > > > > default behavior is to process all tracks found in the input
ADECK
> > > files
> > > > > and search for matching tracks in the BDECK files. I would
> recommend
> > > just
> > > > > running with the default TC-Pairs configuration file.
> > > > >
> > > > > If for some reason, you want to limit the ADECK tracks being
> > processed,
> > > > you
> > > > > can do so by specifying a list of model names or time
windows.
> > > > >
> > > > > I do see specifically that you're asking about using the
consensus
> > > config
> > > > > file option to define a consensus track.
> > > > >
> > > > > consensus = [
> > > > > {
> > > > > name = "CONS";
> > > > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > > > required = [ false, false, false ];
> > > > > min_req = 2;
> > > > > }
> > > > > ];
> > > > >
> > > > > The setting above is used to define consensus tracks (i.e.
mean
> > > location
> > > > > and intensity tracks) from these 3 component models. For
each
> > > > > initialization time found in the input data, TC-Pairs will
attempt
> to
> > > > > derive this consensus track. As long as at least 2 of the 3
are
> > present
> > > > > (min_req=2), it'll compute the consensus track names CONS.
> > > > >
> > > > > You can modify this however you'd like... change the
existing
> > consensus
> > > > > definition or add as many new ones as you'd like. Multiple
entries
> > > would
> > > > be
> > > > > formatted like this:
> > > > > consensus [ { #define first one here# }, { #define second
one
> here#
> > > }, {
> > > > > #define third one here# } ];
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Apr 28, 2021 at 8:50 AM Yan Jin - NOAA Affiliate via
RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725 >
> > > > > >
> > > > > > Hi John,
> > > > > >
> > > > > > Thanks for your explanation. Another question is :
> > > > > >
> > > > > > In this example
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dtcenter.org/metplus-practical-session-guide-july-
2019/session-5-trkintfeature-relative/met-tool-tc-pairs/tc-pairs-tool-
configure
> > > > > >
> > > > > > 3 models are used, but there are no specified "Model
> initialization
> > > > > > time windows" or "Valid model time window" in the config
file.
> > > > > > consensus = [
> > > > > > {
> > > > > > name = "CONS";
> > > > > > members = [ "HWRF", "AVNO", "GFDL" ];
> > > > > > required = [ false, false, false ];
> > > > > > min_req = 2;
> > > > > > }
> > > > > > ];
> > > > > >
> > > > > > If they do have have the same model initialization time do
I need
> > to
> > > > set
> > > > > > their common time period? For instance, in my last
example,
> > > > > >
> > > > > > ***In adeck file:
> > > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > > > :
> > > > > > :
> > > > > > AL, 29, 2020111300, 03, GFSO, 192
> > > > > > AL, 29, 2020111300, 03, HWRF, 54,
> > > > > > AL, 29, 2020111300, 03, HMON, 36
> > > > > > ***
> > > > > > I wonder is the following setting correct?
> > > > > >
> > > > > > // Model initialization time windows to include or exclude
> > > > > > //
> > > > > > init_beg = "2020103018"; //the common initial time is
2020103018
> > > > > > init_end = "2020111300";
> > > > > > init_inc = [];
> > > > > > init_exc = [];
> > > > > >
> > > > > > // Valid model time window
> > > > > > //
> > > > > > valid_beg = "2020103018"; //?not sure
> > > > > > valid_end = "2020111300"; //?not sure
> > > > > >
> > > > > > Many thanks.
> > > > > > Best,
> > > > > > Yan
> > > > > >
> > > > > > On Tue, Apr 27, 2021 at 6:30 PM John Halley Gotway via RT
<
> > > > > > met_help at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Yan,
> > > > > > >
> > > > > > > I see you have a question about how the TC-Pairs config
file
> > > options
> > > > > are
> > > > > > > applied to the input ADECK and BDECK track data.
> > > > > > >
> > > > > > > First, you are correct about the ATCF timestamps. For
ADECK
> data,
> > > the
> > > > > 3rd
> > > > > > > column is the model initialization time and the TAU is
the
> > forecast
> > > > > hour.
> > > > > > > And the valid time is computed as the init time + lead
time.
> For
> > > Best
> > > > > > track
> > > > > > > data, the 3rd column is the Best track valid time and
the TAU
> is
> > > just
> > > > > 0.
> > > > > > >
> > > > > > > You are wondering how those time filtering options in
the
> > TC-Pairs
> > > > > config
> > > > > > > file are applied. These time filters are ONLY APPLIED to
the
> > ADECK
> > > > > data.
> > > > > > > They are not applied to the BDECK data.
> > > > > > >
> > > > > > > In the config file comments that's what we mean by
"*model*
> > > > > > initialization
> > > > > > > time":
> > > > > > >
> > > > > > > // Specify a model initialization time window in
> > > YYYYMMDD[_HH[MMSS]]
> > > > > > format
> > > > > > >
> > > > > > >
> > > > > > > In the tc_pairs.cc source file, the track filtering
function is
> > > > called
> > > > > on
> > > > > > > this line:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/e93f9b0795814d802c1cddb8be996ee00786b6b9/met/src/tools/tc_utils/tc_pairs/tc_pairs.cc#L366
> > > > > > >
> > > > > > > TC-Pairs just parses ALL the input BDECK track data. For
each
> > ADECK
> > > > > track
> > > > > > > that survives the filtering step, we search all the
BDECK
> tracks
> > > > > looking
> > > > > > > for a match.
> > > > > > >
> > > > > > > Hopefully that helps clarify.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > John Halley Gotway
> > > > > > >
> > > > > > > On Tue, Apr 27, 2021 at 3:34 PM Yan Jin - NOAA Affiliate
via
> RT <
> > > > > > > met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > Tue Apr 27 15:34:18 2021: Request 99725 was acted
upon.
> > > > > > > > Transaction: Ticket created by yan.jin at noaa.gov
> > > > > > > > Queue: met_help
> > > > > > > > Subject: ask a question about TCPairsConfig file
> > > > > > > > Owner: Nobody
> > > > > > > > Requestors: yan.jin at noaa.gov
> > > > > > > > Status: new
> > > > > > > > Ticket <URL:
> > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99725
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > Can I ask a few questions regarding the MET-TC tools?
In
> > > > > > > > TCPairsConfig_default there are settings related to
"time
> > > window":
> > > > > > > > **------
> > > > > > > > //
> > > > > > > > // Model initialization time windows to include or
exclude
> > > > > > > > //
> > > > > > > > init_beg = "";
> > > > > > > > init_end = "";
> > > > > > > > init_inc = [];
> > > > > > > > init_exc = [];
> > > > > > > >
> > > > > > > > //
> > > > > > > > // Valid model time window
> > > > > > > > //
> > > > > > > > valid_beg = "";
> > > > > > > > valid_end = "";
> > > > > > > > **--------
> > > > > > > >
> > > > > > > > In adeck file:
> > > > > > > > AL, 29, 2020103000, 03, GFSO, TAU, ...
> > > > > > > > AL, 29, 2020103012, 03, HWRF, TAU, ...
> > > > > > > > AL, 29, 2020103018, 03, HMON, TAU ...
> > > > > > > >
> > > > > > > > In bdeck file:
> > > > > > > > the time is from 2020102900 to 2020111306
> > > > > > > >
> > > > > > > > To me it seems that the time is not consistent.
> > > > > > > >
> > > > > > > > 1. According to
> > > > > > > >
> > >
https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abdeck.txt,
> > > > > > > > the 3rd column in adeck file is "Warning Date-Time-
Group",
> and
> > > TAU
> > > > is
> > > > > > > > "Forecast time". Does it mean that, 2020103000 (for
GFSO)
> > > > corresponds
> > > > > > to
> > > > > > > > "int_beg" in TCPairsConfig file?
> > > > > > > >
> > > > > > > > 2. For different models, the first "Warning Date-Time-
Group"
> is
> > > > > > > different.
> > > > > > > > e.g.: 2020103000 for GFSO, 2020103012 for HWRF. Also
for a
> > > specific
> > > > > > > model,
> > > > > > > > different "Warning Date-Time-Group" has different
TAUs.
> > > Therefore I
> > > > > > > wonder
> > > > > > > > how can I set the time related items in the tc_pairs
config
> > file?
> > > > For
> > > > > > > > instance, the model initialization time window and
valid
> model
> > > time
> > > > > > > window:
> > > > > > > >
> > > > > > > > Many thanks.
> > > > > > > > Best,
> > > > > > > > Yan
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
> --
> Julie Prestopnik (she/her)
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
More information about the Met_help
mailing list