[Met_help] [rt.rap.ucar.edu #84890] History for ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
John Halley Gotway via RT
met_help at ucar.edu
Wed Jul 10 16:39:17 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Good afternoon,
My name is Steve Lilly. I am working on the "extratropical cyclone" track
and intensity
project (w/Guang Ping Lou). I am testing Guang Ping Lou data files
using MET+.
I am currently looking at the following configuration files:
track_and_intensity.conf; and,
TCPairsETCConfig.
Inside "track_and_intensity.conf" file: You have the following
parameter:
TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
then a couple lines down you are ask to fill in the following parameters:
# The init time begin and end times, increment, and the last init hour.
INIT_BEG = 20141214
INIT_END = 20141216
INIT_INC = 21600
INIT_HOUR_END = 12
BUT:
Inside "TCPairsETCConfig" file just provides TCPairs default values. Right?
So, if you define INIT_BEG; INIT_END...you override the default values.
Question 2: If you are considering extratropical cyclone over a given
month
(say April); but only have reports for 3days out of 30 days(say 10th, 11th
and
12th) would MET accept the following values (without introducing errors):
INIT_BEG = 20180401
INIT_END = 20180430
INIT_INC = ?????
INIT_HOUR_END = ??????????
I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END means.
Question 3: Do have documentation describing these various config/ush files
which I can access online?
Thank you for your patience, time and attention to this matter.
Steve
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Minna Win
Time: Wed Apr 25 12:43:13 2018
Hi Steve,
I'll try to answer your questions, the other MET/MET+ team may also
contribute based on their expertise/experience.
When you define something in your MET+ config file, such as the
initialization times, they get passed to MET, so yes you are
overriding
what is in the TCPairsETCConfig file. This can be useful for values
in
the MET config file that get modified frequently, or for customizing
your
configuration.
For question #2 regarding "missing data", if the tc_pairs wrapper
doesn't
find data within a time range, no error messages are generated. The
wrapper
continues to collect whatever data it finds and creates the command to
call
MET tc_pairs.
We sometimes have comments for the config files and it looks like we
lost
the description to the INIT_HOUR_END and INIT_INC, as these values
were
added to accommodate another use case. The INIT_INC is the time step
in
seconds, so the default/example is set to 21600, which corresponds to
6
hours. The INIT_HOUR_END corresponds to the last hour you want
included in
your time window. So if you had 20141201 - 20141205 data and your
data
spanned 00Z-72Z but you were only interested in data from 00Z to 36Z,
you
would indicate the INIT_HOUR_END to 36.
There is no online documentation for the MET+ config files. These
config
files are used to override *some* of the values in the MET config
files.
Our goal is to eventually support overriding all the values in the MET
config files via the MET+ config files, but we haven't had the
opportunity. Currently, the MET+ config files provide the MET user
with
the flexibility to modify the values that get changed most frequently.
I hope that clarifies things a bit more. Please feel free to submit
any
other MET+ related questions.
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Wed, Apr 25, 2018 at 12:12 PM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:
>
> Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> Transaction: Ticket created by steven.lilly at noaa.gov
> Queue: met_help
> Subject: ref: Questions: TCPairsETCConfig vs
track_and_intensity.conf
> Owner: Nobody
> Requestors: steven.lilly at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
>
>
> Good afternoon,
>
> My name is Steve Lilly. I am working on the "extratropical cyclone"
track
> and intensity
> project (w/Guang Ping Lou). I am testing Guang Ping Lou data files
> using MET+.
>
> I am currently looking at the following configuration files:
> track_and_intensity.conf; and,
> TCPairsETCConfig.
>
> Inside "track_and_intensity.conf" file: You have the following
> parameter:
> TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
>
> then a couple lines down you are ask to fill in the following
parameters:
> # The init time begin and end times, increment, and the last init
hour.
>
> INIT_BEG = 20141214
> INIT_END = 20141216
> INIT_INC = 21600
> INIT_HOUR_END = 12
>
> BUT:
>
> Inside "TCPairsETCConfig" file just provides TCPairs default values.
Right?
> So, if you define INIT_BEG; INIT_END...you override the default
values.
>
>
>
> Question 2: If you are considering extratropical cyclone over a
given
> month
> (say April); but only have reports for 3days out of 30 days(say
10th, 11th
> and
> 12th) would MET accept the following values (without introducing
errors):
> INIT_BEG = 20180401
> INIT_END = 20180430
> INIT_INC = ?????
> INIT_HOUR_END = ??????????
> I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END
means.
>
>
> Question 3: Do have documentation describing these various
config/ush files
> which I can access online?
>
> Thank you for your patience, time and attention to this matter.
>
> Steve
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Minna Win
Time: Fri Apr 27 13:11:13 2018
Hi Steve,
I have been refactoring the tc-pairs wrapper and noticed that we were
incorrectly setting the INIT_INC to indicate the initialization step
time
in seconds. This should correspond to a list of initialization times
you
wish to include. We are fixing this in the latest version of the code
to
avoid any further confusion. For now, you can continue to use the
MET+
configuration file in its current form, but instead of setting the
INIT_INC
to an increment time in seconds, you would provide a list of
initialization
times you wish to include:
e.g. INIT_INC = 20120112_06, 20120113_06
(in the MET+ track_and_intensity.conf file)
If there aren't any initialization times you need to explicitly
include,
you can leave this empty: INIT_INC =
I hope this hasn't caused further confusion. We are still in the
process
of getting all of our use cases to be consistent with one another and
unfortunately we incorrectly labelled this key-value pair. Please do
not
hesitate to contact us with any questions you have regarding MET+.
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:
>
> Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> Transaction: Ticket created by steven.lilly at noaa.gov
> Queue: met_help
> Subject: ref: Questions: TCPairsETCConfig vs
track_and_intensity.conf
> Owner: Nobody
> Requestors: steven.lilly at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
>
>
> Good afternoon,
>
> My name is Steve Lilly. I am working on the "extratropical cyclone"
track
> and intensity
> project (w/Guang Ping Lou). I am testing Guang Ping Lou data files
> using MET+.
>
> I am currently looking at the following configuration files:
> track_and_intensity.conf; and,
> TCPairsETCConfig.
>
> Inside "track_and_intensity.conf" file: You have the following
> parameter:
> TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
>
> then a couple lines down you are ask to fill in the following
parameters:
> # The init time begin and end times, increment, and the last init
hour.
>
> INIT_BEG = 20141214
> INIT_END = 20141216
> INIT_INC = 21600
> INIT_HOUR_END = 12
>
> BUT:
>
> Inside "TCPairsETCConfig" file just provides TCPairs default values.
Right?
> So, if you define INIT_BEG; INIT_END...you override the default
values.
>
>
>
> Question 2: If you are considering extratropical cyclone over a
given
> month
> (say April); but only have reports for 3days out of 30 days(say
10th, 11th
> and
> 12th) would MET accept the following values (without introducing
errors):
> INIT_BEG = 20180401
> INIT_END = 20180430
> INIT_INC = ?????
> INIT_HOUR_END = ??????????
> I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END
means.
>
>
> Question 3: Do have documentation describing these various
config/ush files
> which I can access online?
>
> Thank you for your patience, time and attention to this matter.
>
> Steve
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Minna Win
Time: Fri Apr 27 14:22:18 2018
Hi Steve,
Please disregard the instructions from the previous email regarding
the
INIT_INC option. Upon closer inspection of the code the INIT_INC is
indeed
being used to define an initialization interval. If this option has a
value assigned to it (in seconds), it will calculate a range of
initialization times that are then used to search for track files. If
you
set this to 21600 seconds, this corresponds to a 6 hour time step and
the
tc-pairs wrapper searches for track files from the INIT_BEG time to
the
INIT_END time by 6 hour intervals. You will need to set this
according to
how much data you wish to evaluate. We will need to rename INIT_INC
to
INIT_INCREMENT in the MET+ use case config files to avoid confusion
with
the INIT_INC used in the MET TC-pairs config file. Unfortunately, we
didn't realize that the INIT_INC was already in use by another MET
tool and
decided to use this in our other MET+ config files.
Thank you for your patience while we work out the issues with
refactoring
the myriad of use cases.
Thanks,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:
>
> Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> Transaction: Ticket created by steven.lilly at noaa.gov
> Queue: met_help
> Subject: ref: Questions: TCPairsETCConfig vs
track_and_intensity.conf
> Owner: Nobody
> Requestors: steven.lilly at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
>
>
> Good afternoon,
>
> My name is Steve Lilly. I am working on the "extratropical cyclone"
track
> and intensity
> project (w/Guang Ping Lou). I am testing Guang Ping Lou data files
> using MET+.
>
> I am currently looking at the following configuration files:
> track_and_intensity.conf; and,
> TCPairsETCConfig.
>
> Inside "track_and_intensity.conf" file: You have the following
> parameter:
> TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
>
> then a couple lines down you are ask to fill in the following
parameters:
> # The init time begin and end times, increment, and the last init
hour.
>
> INIT_BEG = 20141214
> INIT_END = 20141216
> INIT_INC = 21600
> INIT_HOUR_END = 12
>
> BUT:
>
> Inside "TCPairsETCConfig" file just provides TCPairs default values.
Right?
> So, if you define INIT_BEG; INIT_END...you override the default
values.
>
>
>
> Question 2: If you are considering extratropical cyclone over a
given
> month
> (say April); but only have reports for 3days out of 30 days(say
10th, 11th
> and
> 12th) would MET accept the following values (without introducing
errors):
> INIT_BEG = 20180401
> INIT_END = 20180430
> INIT_INC = ?????
> INIT_HOUR_END = ??????????
> I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END
means.
>
>
> Question 3: Do have documentation describing these various
config/ush files
> which I can access online?
>
> Thank you for your patience, time and attention to this matter.
>
> Steve
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Steven Lilly - NOAA Federal
Time: Mon Apr 30 09:02:34 2018
Good morning Minna,
I am sorry; but, I am totally confused.
1. What happens if the INIT_INC option is left blank?
vs
2, what would be the initialization time ( INIT_INC = ????) given the
following parameters:
a. each day will have 4 cycles ( 00z 06z 12z and 18z);
b. each cycle forecast hr will extent out to 120hrs; every 6hr
interval?
ie; 00z--> 00hr 06hr 12hr 18hr 24hr 30hr ...120hr
06z--> 00hr 06h 12hr 18hr 24hr ... 120hr
3, There are a total of 30 days for that month
Solution: ?????
INIT_INC = "blank"
INIT_INC = ?????? sec
It would be greatly appreciative if you would provide some examples
along with the explanation to my questions ( more of a visual person).
Again, thank you for your time and attention to this matter.
Best Regards,
Steve
On Fri, Apr 27, 2018 at 8:22 PM, Minna Win via RT <met_help at ucar.edu>
wrote:
> Hi Steve,
>
> Please disregard the instructions from the previous email regarding
the
> INIT_INC option. Upon closer inspection of the code the INIT_INC is
indeed
> being used to define an initialization interval. If this option has
a
> value assigned to it (in seconds), it will calculate a range of
> initialization times that are then used to search for track files.
If you
> set this to 21600 seconds, this corresponds to a 6 hour time step
and the
> tc-pairs wrapper searches for track files from the INIT_BEG time to
the
> INIT_END time by 6 hour intervals. You will need to set this
according to
> how much data you wish to evaluate. We will need to rename INIT_INC
to
> INIT_INCREMENT in the MET+ use case config files to avoid confusion
with
> the INIT_INC used in the MET TC-pairs config file. Unfortunately,
we
> didn't realize that the INIT_INC was already in use by another MET
tool and
> decided to use this in our other MET+ config files.
>
> Thank you for your patience while we work out the issues with
refactoring
> the myriad of use cases.
>
> Thanks,
> Minna
>
> ---------------
> Minna Win
> NCAR
> Research Applications Lab
> Phone: 303-497-8423
> Fax: 302-497-8401
>
>
> On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal via RT
<
> met_help at ucar.edu> wrote:
>
> >
> > Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> > Transaction: Ticket created by steven.lilly at noaa.gov
> > Queue: met_help
> > Subject: ref: Questions: TCPairsETCConfig vs
> track_and_intensity.conf
> > Owner: Nobody
> > Requestors: steven.lilly at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
> >
> >
> > Good afternoon,
> >
> > My name is Steve Lilly. I am working on the "extratropical
cyclone"
> track
> > and intensity
> > project (w/Guang Ping Lou). I am testing Guang Ping Lou data
files
> > using MET+.
> >
> > I am currently looking at the following configuration files:
> > track_and_intensity.conf; and,
> > TCPairsETCConfig.
> >
> > Inside "track_and_intensity.conf" file: You have the following
> > parameter:
> > TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
> >
> > then a couple lines down you are ask to fill in the following
parameters:
> > # The init time begin and end times, increment, and the last init
hour.
> >
> > INIT_BEG = 20141214
> > INIT_END = 20141216
> > INIT_INC = 21600
> > INIT_HOUR_END = 12
> >
> > BUT:
> >
> > Inside "TCPairsETCConfig" file just provides TCPairs default
values.
> Right?
> > So, if you define INIT_BEG; INIT_END...you override the default
values.
> >
> >
> >
> > Question 2: If you are considering extratropical cyclone over a
given
> > month
> > (say April); but only have reports for 3days out of 30 days(say
10th,
> 11th
> > and
> > 12th) would MET accept the following values (without introducing
errors):
> > INIT_BEG = 20180401
> > INIT_END = 20180430
> > INIT_INC = ?????
> > INIT_HOUR_END = ??????????
> > I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END
means.
> >
> >
> > Question 3: Do have documentation describing these various
config/ush
> files
> > which I can access online?
> >
> > Thank you for your patience, time and attention to this matter.
> >
> > Steve
> >
> >
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Minna Win
Time: Mon Apr 30 09:48:10 2018
Hello Steve,
My apologies for the confusion. The way the current TC-pairs wrapper
is
implemented, the INIT_INC is used in finding track files that are
within a
time window, and cannot be left blank. If I have track data for
201201 to
201506 with data for every month (ie 201201, 201202,201203, ...201501,
201502, 201503, 201504, 201505,201506) but I was only interested in
the
2012-2013 season, I'd set up my time window like this in the MET+
config
file:
INIT_BEG = 201201
INIT_END = 201305
If my forecast model has 00, 06, 12, and 18 hour forecast lead times
(6-hourly) and I want to capture all of these forecast hours, I would
set
my INIT_INC to this:
INIT_INC = 21600 (21600 sec = 6 hours)
INIT_INC is a confusing name for the initialization increment,
especially
since MET tc_pairs has an init_inc in it's config file to indicate
which
initialization times are to be included. This will be changed to
INIT_INCREMENT in future versions of the MET+ TC-pairs wrapper to
avoid
confusion.
As I mentioned earlier, you cannot leave this empty, as the wrapper
code
currently uses this to calculate which times to look for, so it would
look
for 20120100, 20120106, 20120112,...etc in creating a list of files to
feed
to the MET TC-pairs tool :
tc_pairs -adeck <a-deck file for 20120100> -bdeck <your best track
file>
-config <your tc-paris config file>
To capture all the initialization times for this data set, set the
INIT_HOUR_END = 18. Sometimes the forecast model goes beyond what is
of
interest: ie 24, 30, 36, 42, ..., 96 and you would use INIT_HOUR_END
to
truncate your initialization hour of interest window.
So my MET+ config file would look like this:
INIT_BEG = 201201
INIT_END = 201305
INIT_INC = 21600
INIT_HOUR_END = 18
for 6-hourly data and to focus on the 201201-201305 storm season.
I hope that helps. If not, feel free to let us know how your data is
set
up and what you are trying to achieve and we can assist you in setting
up
your MET and MET+ config files.
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Mon, Apr 30, 2018 at 3:02 PM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
>
> Good morning Minna,
>
> I am sorry; but, I am totally confused.
>
> 1. What happens if the INIT_INC option is left blank?
>
> vs
>
> 2, what would be the initialization time ( INIT_INC = ????) given
the
> following parameters:
>
> a. each day will have 4 cycles ( 00z 06z 12z and 18z);
>
> b. each cycle forecast hr will extent out to 120hrs; every 6hr
interval?
>
> ie; 00z--> 00hr 06hr 12hr 18hr 24hr 30hr ...120hr
> 06z--> 00hr 06h 12hr 18hr 24hr ... 120hr
>
> 3, There are a total of 30 days for that month
>
> Solution: ?????
>
> INIT_INC = "blank"
> INIT_INC = ?????? sec
>
> It would be greatly appreciative if you would provide some examples
> along with the explanation to my questions ( more of a visual
person).
>
> Again, thank you for your time and attention to this matter.
>
>
> Best Regards,
> Steve
>
>
> On Fri, Apr 27, 2018 at 8:22 PM, Minna Win via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Steve,
> >
> > Please disregard the instructions from the previous email
regarding the
> > INIT_INC option. Upon closer inspection of the code the INIT_INC
is
> indeed
> > being used to define an initialization interval. If this option
has a
> > value assigned to it (in seconds), it will calculate a range of
> > initialization times that are then used to search for track files.
If
> you
> > set this to 21600 seconds, this corresponds to a 6 hour time step
and the
> > tc-pairs wrapper searches for track files from the INIT_BEG time
to the
> > INIT_END time by 6 hour intervals. You will need to set this
according
> to
> > how much data you wish to evaluate. We will need to rename
INIT_INC to
> > INIT_INCREMENT in the MET+ use case config files to avoid
confusion with
> > the INIT_INC used in the MET TC-pairs config file. Unfortunately,
we
> > didn't realize that the INIT_INC was already in use by another MET
tool
> and
> > decided to use this in our other MET+ config files.
> >
> > Thank you for your patience while we work out the issues with
refactoring
> > the myriad of use cases.
> >
> > Thanks,
> > Minna
> >
> > ---------------
> > Minna Win
> > NCAR
> > Research Applications Lab
> > Phone: 303-497-8423
> > Fax: 302-497-8401
> >
> >
> > On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal via
RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> > > Transaction: Ticket created by steven.lilly at noaa.gov
> > > Queue: met_help
> > > Subject: ref: Questions: TCPairsETCConfig vs
> > track_and_intensity.conf
> > > Owner: Nobody
> > > Requestors: steven.lilly at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890
> >
> > >
> > >
> > > Good afternoon,
> > >
> > > My name is Steve Lilly. I am working on the "extratropical
cyclone"
> > track
> > > and intensity
> > > project (w/Guang Ping Lou). I am testing Guang Ping Lou data
files
> > > using MET+.
> > >
> > > I am currently looking at the following configuration files:
> > > track_and_intensity.conf; and,
> > > TCPairsETCConfig.
> > >
> > > Inside "track_and_intensity.conf" file: You have the following
> > > parameter:
> > > TC_PAIRS_CONFIG_FILE = {PARM_BASE}/met_config/TCPairsETCConfig
> > >
> > > then a couple lines down you are ask to fill in the following
> parameters:
> > > # The init time begin and end times, increment, and the last
init
> hour.
> > >
> > > INIT_BEG = 20141214
> > > INIT_END = 20141216
> > > INIT_INC = 21600
> > > INIT_HOUR_END = 12
> > >
> > > BUT:
> > >
> > > Inside "TCPairsETCConfig" file just provides TCPairs default
values.
> > Right?
> > > So, if you define INIT_BEG; INIT_END...you override the default
values.
> > >
> > >
> > >
> > > Question 2: If you are considering extratropical cyclone over
a given
> > > month
> > > (say April); but only have reports for 3days out of 30 days(say
10th,
> > 11th
> > > and
> > > 12th) would MET accept the following values (without introducing
> errors):
> > > INIT_BEG = 20180401
> > > INIT_END = 20180430
> > > INIT_INC = ?????
> > > INIT_HOUR_END = ??????????
> > > I not sure what the 21600 for INIT_INC or 12 foor INIT_HOUR_END
means.
> > >
> > >
> > > Question 3: Do have documentation describing these various
config/ush
> > files
> > > which I can access online?
> > >
> > > Thank you for your patience, time and attention to this matter.
> > >
> > > Steve
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Steven Lilly - NOAA Federal
Time: Mon Apr 30 10:14:30 2018
Good afternoon Minna,
Your explanation along with the examples were very useful to me.
I am beginning to understand the functionally of these parameters.
Thanks again for help.
Have a Great Day!
Steve
On Mon, Apr 30, 2018 at 3:48 PM, Minna Win via RT <met_help at ucar.edu>
wrote:
> Hello Steve,
>
> My apologies for the confusion. The way the current TC-pairs
wrapper is
> implemented, the INIT_INC is used in finding track files that are
within a
> time window, and cannot be left blank. If I have track data for
201201 to
> 201506 with data for every month (ie 201201, 201202,201203,
...201501,
> 201502, 201503, 201504, 201505,201506) but I was only interested in
the
> 2012-2013 season, I'd set up my time window like this in the MET+
config
> file:
>
> INIT_BEG = 201201
> INIT_END = 201305
>
> If my forecast model has 00, 06, 12, and 18 hour forecast lead times
> (6-hourly) and I want to capture all of these forecast hours, I
would set
> my INIT_INC to this:
>
> INIT_INC = 21600 (21600 sec = 6 hours)
>
> INIT_INC is a confusing name for the initialization increment,
especially
> since MET tc_pairs has an init_inc in it's config file to indicate
which
> initialization times are to be included. This will be changed to
> INIT_INCREMENT in future versions of the MET+ TC-pairs wrapper to
avoid
> confusion.
>
> As I mentioned earlier, you cannot leave this empty, as the wrapper
code
> currently uses this to calculate which times to look for, so it
would look
> for 20120100, 20120106, 20120112,...etc in creating a list of files
to feed
> to the MET TC-pairs tool :
> tc_pairs -adeck <a-deck file for 20120100> -bdeck <your best
track file>
> -config <your tc-paris config file>
>
> To capture all the initialization times for this data set, set the
> INIT_HOUR_END = 18. Sometimes the forecast model goes beyond what
is of
> interest: ie 24, 30, 36, 42, ..., 96 and you would use INIT_HOUR_END
to
> truncate your initialization hour of interest window.
>
> So my MET+ config file would look like this:
> INIT_BEG = 201201
> INIT_END = 201305
> INIT_INC = 21600
> INIT_HOUR_END = 18
>
> for 6-hourly data and to focus on the 201201-201305 storm season.
>
>
> I hope that helps. If not, feel free to let us know how your data
is set
> up and what you are trying to achieve and we can assist you in
setting up
> your MET and MET+ config files.
>
> Regards,
> Minna
>
>
>
>
> ---------------
> Minna Win
> NCAR
> Research Applications Lab
> Phone: 303-497-8423
> Fax: 302-497-8401
>
>
> On Mon, Apr 30, 2018 at 3:02 PM, Steven Lilly - NOAA Federal via RT
<
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
> >
> > Good morning Minna,
> >
> > I am sorry; but, I am totally confused.
> >
> > 1. What happens if the INIT_INC option is left blank?
> >
> > vs
> >
> > 2, what would be the initialization time ( INIT_INC = ????) given
the
> > following parameters:
> >
> > a. each day will have 4 cycles ( 00z 06z 12z and 18z);
> >
> > b. each cycle forecast hr will extent out to 120hrs; every 6hr
> interval?
> >
> > ie; 00z--> 00hr 06hr 12hr 18hr 24hr 30hr ...120hr
> > 06z--> 00hr 06h 12hr 18hr 24hr ... 120hr
> >
> > 3, There are a total of 30 days for that month
> >
> > Solution: ?????
> >
> > INIT_INC = "blank"
> > INIT_INC = ?????? sec
> >
> > It would be greatly appreciative if you would provide some
examples
> > along with the explanation to my questions ( more of a visual
person).
> >
> > Again, thank you for your time and attention to this matter.
> >
> >
> > Best Regards,
> > Steve
> >
> >
> > On Fri, Apr 27, 2018 at 8:22 PM, Minna Win via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hi Steve,
> > >
> > > Please disregard the instructions from the previous email
regarding the
> > > INIT_INC option. Upon closer inspection of the code the INIT_INC
is
> > indeed
> > > being used to define an initialization interval. If this option
has a
> > > value assigned to it (in seconds), it will calculate a range of
> > > initialization times that are then used to search for track
files. If
> > you
> > > set this to 21600 seconds, this corresponds to a 6 hour time
step and
> the
> > > tc-pairs wrapper searches for track files from the INIT_BEG time
to the
> > > INIT_END time by 6 hour intervals. You will need to set this
according
> > to
> > > how much data you wish to evaluate. We will need to rename
INIT_INC to
> > > INIT_INCREMENT in the MET+ use case config files to avoid
confusion
> with
> > > the INIT_INC used in the MET TC-pairs config file.
Unfortunately, we
> > > didn't realize that the INIT_INC was already in use by another
MET tool
> > and
> > > decided to use this in our other MET+ config files.
> > >
> > > Thank you for your patience while we work out the issues with
> refactoring
> > > the myriad of use cases.
> > >
> > > Thanks,
> > > Minna
> > >
> > > ---------------
> > > Minna Win
> > > NCAR
> > > Research Applications Lab
> > > Phone: 303-497-8423
> > > Fax: 302-497-8401
> > >
> > >
> > > On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal via
RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> > > > Transaction: Ticket created by steven.lilly at noaa.gov
> > > > Queue: met_help
> > > > Subject: ref: Questions: TCPairsETCConfig vs
> > > track_and_intensity.conf
> > > > Owner: Nobody
> > > > Requestors: steven.lilly at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=84890
> > >
> > > >
> > > >
> > > > Good afternoon,
> > > >
> > > > My name is Steve Lilly. I am working on the "extratropical
cyclone"
> > > track
> > > > and intensity
> > > > project (w/Guang Ping Lou). I am testing Guang Ping Lou data
files
> > > > using MET+.
> > > >
> > > > I am currently looking at the following configuration files:
> > > > track_and_intensity.conf; and,
> > > > TCPairsETCConfig.
> > > >
> > > > Inside "track_and_intensity.conf" file: You have the following
> > > > parameter:
> > > > TC_PAIRS_CONFIG_FILE =
{PARM_BASE}/met_config/TCPairsETCConfig
> > > >
> > > > then a couple lines down you are ask to fill in the following
> > parameters:
> > > > # The init time begin and end times, increment, and the last
init
> > hour.
> > > >
> > > > INIT_BEG = 20141214
> > > > INIT_END = 20141216
> > > > INIT_INC = 21600
> > > > INIT_HOUR_END = 12
> > > >
> > > > BUT:
> > > >
> > > > Inside "TCPairsETCConfig" file just provides TCPairs default
values.
> > > Right?
> > > > So, if you define INIT_BEG; INIT_END...you override the
default
> values.
> > > >
> > > >
> > > >
> > > > Question 2: If you are considering extratropical cyclone
over a
> given
> > > > month
> > > > (say April); but only have reports for 3days out of 30
days(say 10th,
> > > 11th
> > > > and
> > > > 12th) would MET accept the following values (without
introducing
> > errors):
> > > > INIT_BEG = 20180401
> > > > INIT_END = 20180430
> > > > INIT_INC = ?????
> > > > INIT_HOUR_END = ??????????
> > > > I not sure what the 21600 for INIT_INC or 12 foor
INIT_HOUR_END
> means.
> > > >
> > > >
> > > > Question 3: Do have documentation describing these various
config/ush
> > > files
> > > > which I can access online?
> > > >
> > > > Thank you for your patience, time and attention to this
matter.
> > > >
> > > > Steve
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: ref: Questions: TCPairsETCConfig vs track_and_intensity.conf
From: Minna Win
Time: Mon Apr 30 10:37:27 2018
Hi Steve,
Please don't hesitate to contact us if you have any questions or if
you
need any clarification. You are also helping us refine our code and
documentation!
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Mon, Apr 30, 2018 at 4:14 PM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
>
> Good afternoon Minna,
>
> Your explanation along with the examples were very useful to me.
> I am beginning to understand the functionally of these parameters.
>
> Thanks again for help.
>
> Have a Great Day!
>
> Steve
>
> On Mon, Apr 30, 2018 at 3:48 PM, Minna Win via RT
<met_help at ucar.edu>
> wrote:
>
> > Hello Steve,
> >
> > My apologies for the confusion. The way the current TC-pairs
wrapper is
> > implemented, the INIT_INC is used in finding track files that are
within
> a
> > time window, and cannot be left blank. If I have track data for
201201
> to
> > 201506 with data for every month (ie 201201, 201202,201203,
...201501,
> > 201502, 201503, 201504, 201505,201506) but I was only interested
in the
> > 2012-2013 season, I'd set up my time window like this in the MET+
config
> > file:
> >
> > INIT_BEG = 201201
> > INIT_END = 201305
> >
> > If my forecast model has 00, 06, 12, and 18 hour forecast lead
times
> > (6-hourly) and I want to capture all of these forecast hours, I
would set
> > my INIT_INC to this:
> >
> > INIT_INC = 21600 (21600 sec = 6 hours)
> >
> > INIT_INC is a confusing name for the initialization increment,
especially
> > since MET tc_pairs has an init_inc in it's config file to indicate
which
> > initialization times are to be included. This will be changed to
> > INIT_INCREMENT in future versions of the MET+ TC-pairs wrapper to
avoid
> > confusion.
> >
> > As I mentioned earlier, you cannot leave this empty, as the
wrapper code
> > currently uses this to calculate which times to look for, so it
would
> look
> > for 20120100, 20120106, 20120112,...etc in creating a list of
files to
> feed
> > to the MET TC-pairs tool :
> > tc_pairs -adeck <a-deck file for 20120100> -bdeck <your best
track
> file>
> > -config <your tc-paris config file>
> >
> > To capture all the initialization times for this data set, set the
> > INIT_HOUR_END = 18. Sometimes the forecast model goes beyond what
is of
> > interest: ie 24, 30, 36, 42, ..., 96 and you would use
INIT_HOUR_END to
> > truncate your initialization hour of interest window.
> >
> > So my MET+ config file would look like this:
> > INIT_BEG = 201201
> > INIT_END = 201305
> > INIT_INC = 21600
> > INIT_HOUR_END = 18
> >
> > for 6-hourly data and to focus on the 201201-201305 storm season.
> >
> >
> > I hope that helps. If not, feel free to let us know how your data
is set
> > up and what you are trying to achieve and we can assist you in
setting up
> > your MET and MET+ config files.
> >
> > Regards,
> > Minna
> >
> >
> >
> >
> > ---------------
> > Minna Win
> > NCAR
> > Research Applications Lab
> > Phone: 303-497-8423
> > Fax: 302-497-8401
> >
> >
> > On Mon, Apr 30, 2018 at 3:02 PM, Steven Lilly - NOAA Federal via
RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84890 >
> > >
> > > Good morning Minna,
> > >
> > > I am sorry; but, I am totally confused.
> > >
> > > 1. What happens if the INIT_INC option is left blank?
> > >
> > > vs
> > >
> > > 2, what would be the initialization time ( INIT_INC = ????)
given the
> > > following parameters:
> > >
> > > a. each day will have 4 cycles ( 00z 06z 12z and 18z);
> > >
> > > b. each cycle forecast hr will extent out to 120hrs; every 6hr
> > interval?
> > >
> > > ie; 00z--> 00hr 06hr 12hr 18hr 24hr 30hr ...120hr
> > > 06z--> 00hr 06h 12hr 18hr 24hr ... 120hr
> > >
> > > 3, There are a total of 30 days for that month
> > >
> > > Solution: ?????
> > >
> > > INIT_INC = "blank"
> > > INIT_INC = ?????? sec
> > >
> > > It would be greatly appreciative if you would provide some
examples
> > > along with the explanation to my questions ( more of a visual
person).
> > >
> > > Again, thank you for your time and attention to this matter.
> > >
> > >
> > > Best Regards,
> > > Steve
> > >
> > >
> > > On Fri, Apr 27, 2018 at 8:22 PM, Minna Win via RT
<met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Steve,
> > > >
> > > > Please disregard the instructions from the previous email
regarding
> the
> > > > INIT_INC option. Upon closer inspection of the code the
INIT_INC is
> > > indeed
> > > > being used to define an initialization interval. If this
option has
> a
> > > > value assigned to it (in seconds), it will calculate a range
of
> > > > initialization times that are then used to search for track
files.
> If
> > > you
> > > > set this to 21600 seconds, this corresponds to a 6 hour time
step and
> > the
> > > > tc-pairs wrapper searches for track files from the INIT_BEG
time to
> the
> > > > INIT_END time by 6 hour intervals. You will need to set this
> according
> > > to
> > > > how much data you wish to evaluate. We will need to rename
INIT_INC
> to
> > > > INIT_INCREMENT in the MET+ use case config files to avoid
confusion
> > with
> > > > the INIT_INC used in the MET TC-pairs config file.
Unfortunately, we
> > > > didn't realize that the INIT_INC was already in use by another
MET
> tool
> > > and
> > > > decided to use this in our other MET+ config files.
> > > >
> > > > Thank you for your patience while we work out the issues with
> > refactoring
> > > > the myriad of use cases.
> > > >
> > > > Thanks,
> > > > Minna
> > > >
> > > > ---------------
> > > > Minna Win
> > > > NCAR
> > > > Research Applications Lab
> > > > Phone: 303-497-8423
> > > > Fax: 302-497-8401
> > > >
> > > >
> > > > On Wed, Apr 25, 2018 at 6:12 PM, Steven Lilly - NOAA Federal
via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Wed Apr 25 12:12:08 2018: Request 84890 was acted upon.
> > > > > Transaction: Ticket created by steven.lilly at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: ref: Questions: TCPairsETCConfig vs
> > > > track_and_intensity.conf
> > > > > Owner: Nobody
> > > > > Requestors: steven.lilly at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=84890
> > > >
> > > > >
> > > > >
> > > > > Good afternoon,
> > > > >
> > > > > My name is Steve Lilly. I am working on the "extratropical
> cyclone"
> > > > track
> > > > > and intensity
> > > > > project (w/Guang Ping Lou). I am testing Guang Ping Lou
data files
> > > > > using MET+.
> > > > >
> > > > > I am currently looking at the following configuration files:
> > > > > track_and_intensity.conf; and,
> > > > > TCPairsETCConfig.
> > > > >
> > > > > Inside "track_and_intensity.conf" file: You have the
following
> > > > > parameter:
> > > > > TC_PAIRS_CONFIG_FILE =
{PARM_BASE}/met_config/TCPairsETCConfig
> > > > >
> > > > > then a couple lines down you are ask to fill in the
following
> > > parameters:
> > > > > # The init time begin and end times, increment, and the
last init
> > > hour.
> > > > >
> > > > > INIT_BEG = 20141214
> > > > > INIT_END = 20141216
> > > > > INIT_INC = 21600
> > > > > INIT_HOUR_END = 12
> > > > >
> > > > > BUT:
> > > > >
> > > > > Inside "TCPairsETCConfig" file just provides TCPairs default
> values.
> > > > Right?
> > > > > So, if you define INIT_BEG; INIT_END...you override the
default
> > values.
> > > > >
> > > > >
> > > > >
> > > > > Question 2: If you are considering extratropical cyclone
over a
> > given
> > > > > month
> > > > > (say April); but only have reports for 3days out of 30
days(say
> 10th,
> > > > 11th
> > > > > and
> > > > > 12th) would MET accept the following values (without
introducing
> > > errors):
> > > > > INIT_BEG = 20180401
> > > > > INIT_END = 20180430
> > > > > INIT_INC = ?????
> > > > > INIT_HOUR_END = ??????????
> > > > > I not sure what the 21600 for INIT_INC or 12 foor
INIT_HOUR_END
> > means.
> > > > >
> > > > >
> > > > > Question 3: Do have documentation describing these various
> config/ush
> > > > files
> > > > > which I can access online?
> > > > >
> > > > > Thank you for your patience, time and attention to this
matter.
> > > > >
> > > > > Steve
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list