[Met_help] [rt.rap.ucar.edu #65244] History for model suffix

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

In tc_pairs, when listing the ADECK and BDECK sources, debug 1 mentions 
"Model Suffix: (nul)"
What is the Model Suffix?

e.g.
DEBUG 1: [Source 28 of 33] ADECK Source: 
/glade/scratch/ahijevyc/awp192013.dat, Model Suffix: (nul)



----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Re: [rt.rap.ucar.edu #65244] model suffix
From: John Halley Gotway
Time: Wed Feb 05 11:05:29 2014

Dave,

We added this option in support of the testing we do in the DTC.  I
can't remember all the details, but basically we had multiple sources
of ADECK model data that used the same 4-letter ATCF ID.
However they were actually created from different NWP model
configurations.  If we blindly ran them through the tc_pairs tool,
we'd end up with a bunch of track data we wouldn't be able to
distinguish
from one another.  The MODEL column would contain the same value in
the output.  The model suffix is an optional string that can be
appended to the end of all the model names from that source of track
data.

For example, suppose model1.dat and model2.dat use the ATCF ID "CTCX"
but are actually different physics configurations.  You could run
tc_pairs like this...
   tc_pairs \
   -adeck model1.dat suffix=_mod1 \
   -adeck model2.dat suffix=_mod2 \
   -bdeck best_track.dat \
   -config TCPairsConfig

In the output, in the MODEL column, you'd see CTCX_mod1 and CTCX_mod2.
I believe in our case, we appended an "X" to indicate that some of the
models were "experimental".

Make sense?

Thanks,
John

On 02/04/2014 04:14 PM, David Ahijevych via RT wrote:
>
> Tue Feb 04 16:14:23 2014: Request 65244 was acted upon.
> Transaction: Ticket created by ahijevyc
>         Queue: met_help
>       Subject: model suffix
>         Owner: Nobody
>    Requestors: ahijevyc at ucar.edu
>        Status: new
>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65244 >
>
>
> In tc_pairs, when listing the ADECK and BDECK sources, debug 1
mentions
> "Model Suffix: (nul)"
> What is the Model Suffix?
>
> e.g.
> DEBUG 1: [Source 28 of 33] ADECK Source:
> /glade/scratch/ahijevyc/awp192013.dat, Model Suffix: (nul)
>

------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65244] model suffix
From: David Ahijevych
Time: Wed Feb 05 11:20:23 2014

Yes, that makes sense.
d


On 2/5/14 11:05 AM, John Halley Gotway via RT wrote:
> Dave,
>
> We added this option in support of the testing we do in the DTC.  I
can't remember all the details, but basically we had multiple sources
of ADECK model data that used the same 4-letter ATCF ID.
> However they were actually created from different NWP model
configurations.  If we blindly ran them through the tc_pairs tool,
we'd end up with a bunch of track data we wouldn't be able to
distinguish
> from one another.  The MODEL column would contain the same value in
the output.  The model suffix is an optional string that can be
appended to the end of all the model names from that source of track
> data.
>
> For example, suppose model1.dat and model2.dat use the ATCF ID
"CTCX" but are actually different physics configurations.  You could
run tc_pairs like this...
>     tc_pairs \
>     -adeck model1.dat suffix=_mod1 \
>     -adeck model2.dat suffix=_mod2 \
>     -bdeck best_track.dat \
>     -config TCPairsConfig
>
> In the output, in the MODEL column, you'd see CTCX_mod1 and
CTCX_mod2.  I believe in our case, we appended an "X" to indicate that
some of the models were "experimental".
>
> Make sense?
>
> Thanks,
> John
>
> On 02/04/2014 04:14 PM, David Ahijevych via RT wrote:
>> Tue Feb 04 16:14:23 2014: Request 65244 was acted upon.
>> Transaction: Ticket created by ahijevyc
>>          Queue: met_help
>>        Subject: model suffix
>>          Owner: Nobody
>>     Requestors: ahijevyc at ucar.edu
>>         Status: new
>>    Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65244 >
>>
>>
>> In tc_pairs, when listing the ADECK and BDECK sources, debug 1
mentions
>> "Model Suffix: (nul)"
>> What is the Model Suffix?
>>
>> e.g.
>> DEBUG 1: [Source 28 of 33] ADECK Source:
>> /glade/scratch/ahijevyc/awp192013.dat, Model Suffix: (nul)
>>


------------------------------------------------