[Met_help] [rt.rap.ucar.edu #93516] History for wrong matching of the prepbufr file and the valid time.
George McCabe via RT
met_help at ucar.edu
Thu Dec 19 08:15:08 MST 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear Mr. or Mrs.,
When I am running metplus to invoke pb2nc, from the log file, I found the
code found the wrong prepbfur file for the verification time.
Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the observation to
get prepbufr.rap.2019121400.nc. . While, the correct one should be
../rap.20191214/rap.t00z.prepbufr.tm00
Would you please tell me where I have the problem in the setup?
Your help is appreciated.
My related configure set up is in the following:
^^
LOOP_BY = INIT
LEAD_SEQ = begin_end_incr(0,48,1)/2/
INIT_TIME_FMT = %Y%m%d%
INIT_BEG = 2019121400
INIT_END = 2019121400
INIT_INCREMENT = 86400
PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
VVV
Regards,
Ting
______________________________
Ting Lei
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Cubicle 2765
College Park, MD 20740
Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
301-683-3624
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: wrong matching of the prepbufr file and the valid time.
From: Julie Prestopnik
Time: Wed Dec 18 09:22:49 2019
Hi Ting.
I have assigned this ticket to George, who I believe is best suited to
help
you with this issue. Please allow a few business days for a response.
Thanks,
Julie
On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> Transaction: Ticket created by ting.lei at noaa.gov
> Queue: met_help
> Subject: wrong matching of the prepbufr file and the valid
time.
> Owner: Nobody
> Requestors: ting.lei at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
>
>
> Dear Mr. or Mrs.,
> When I am running metplus to invoke pb2nc, from the log file, I
found the
> code found the wrong prepbfur file for the verification time.
> Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
observation to
> get prepbufr.rap.2019121400.nc. . While, the correct one should be
> ../rap.20191214/rap.t00z.prepbufr.tm00
> Would you please tell me where I have the problem in the setup?
> Your help is appreciated.
> My related configure set up is in the following:
> ^^
> LOOP_BY = INIT
> LEAD_SEQ = begin_end_incr(0,48,1)/2/
> INIT_TIME_FMT = %Y%m%d%
> INIT_BEG = 2019121400
> INIT_END = 2019121400
> INIT_INCREMENT = 86400
> PB2NC_INPUT_TEMPLATE =
> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
>
> VVV
>
> Regards,
>
> Ting
>
>
>
> ______________________________
>
> Ting Lei
>
> IMSG at NOAA/NWS/NCEP/EMC
>
> 5830 University Research Ct., Cubicle 2765
>
> College Park, MD 20740
>
> Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
>
> 301-683-3624
>
>
--
Julie Prestopnik
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
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: wrong matching of the prepbufr file and the valid time.
From: George McCabe
Time: Wed Dec 18 10:37:51 2019
Hi Ting,
Your configuration is looping over initialization times, defined here:
LOOP_BY = INIT
LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove the /2/
from
this line)*
INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
INIT_BEG = 2019121400
INIT_END = 2019121400
INIT_INCREMENT = 86400
This says loop from 20191214 0Z to 20191214 0Z by an increment of
86400
seconds, which is just one initialization time at 20191214 0Z.
The LEAD_SEQ item defines the list of forecast leads to process for
each
initialization time.
LEAD_SEQ = begin_end_incr(0,48,1)
will create a list of forecast leads from 0 to 48 by 1, so it will be
0, 1,
2, 3, 4, 5, ..., 48
For this setup, the initialization time will always be 20191214 0Z and
the
valid times to process will be 20191214 0Z, 20191214 1Z, 20191214 2Z,
...
20191216 0Z
You can also loop by valid time and have the initialization time
adjust
based on the forecast lead list.
LOOP_BY = *VALID*
LEAD_SEQ = begin_end_incr(0,48,1)
*VALID*_TIME_FMT = %Y%m%d%H
*VALID*_BEG = 2019121400
*VALID*_END = 2019121400
*VALID*_INCREMENT = 86400
This will process valid time 20191214 0Z, and initialization times
20191214
0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
Your input template is using valid time and cycle. cycle is the same
as the *data
assimilation *initialization time, or da_init (not the same as init).
PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
The valid time is computed by adding each forecast lead to the
initialization time, so for each forecast lead, the valid time will
adjust.
If you have PB2NC_OFFSETS set in your config file, this will be used
to
calculate the da_init (or cycle) value. This can be a list of offsets
that
you want to allow. For example, if you set
PB2NC_OFFSET = 6, 3
then for valid time 20191214 0Z, it will look for a file with a
da_init
(cycle) time of 20191214 6Z, then if that is not found it will look
for a
file with cycle time 20191214 3Z.
Unset the variable or set the list = 0 to avoid this adjustment.
One way to get the desired result you mentioned is to loop over valid
times
with no offsets:
LOOP_BY = VALID
VALID_TIME_FMT = %Y%m%d%H
VALID_BEG = 2019121400
VALID_END = 2019121400
VALID_INCREMENT = 86400
PB2NC_OFFSETS = 0
PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
This should look for the file: rap.20191214/rap.t00z.prepbufr.tm00
If you know you only want to use files named rap.t00z.prepbufr.tm00,
you
can just replace the cycle tag with 00:
PB2NC_INPUT_TEMPLATE = rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
Please let me know if that helps or if you have any questions.
Thanks,
George
On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
>
> Hi Ting.
>
> I have assigned this ticket to George, who I believe is best suited
to help
> you with this issue. Please allow a few business days for a
response.
>
> Thanks,
> Julie
>
> On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> > Transaction: Ticket created by ting.lei at noaa.gov
> > Queue: met_help
> > Subject: wrong matching of the prepbufr file and the valid
time.
> > Owner: Nobody
> > Requestors: ting.lei at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> >
> >
> > Dear Mr. or Mrs.,
> > When I am running metplus to invoke pb2nc, from the log file, I
found the
> > code found the wrong prepbfur file for the verification time.
> > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
observation to
> > get prepbufr.rap.2019121400.nc. . While, the correct one should
be
> > ../rap.20191214/rap.t00z.prepbufr.tm00
> > Would you please tell me where I have the problem in the setup?
> > Your help is appreciated.
> > My related configure set up is in the following:
> > ^^
> > LOOP_BY = INIT
> > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> > INIT_TIME_FMT = %Y%m%d%
> > INIT_BEG = 2019121400
> > INIT_END = 2019121400
> > INIT_INCREMENT = 86400
> > PB2NC_INPUT_TEMPLATE =
> > rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> >
> > VVV
> >
> > Regards,
> >
> > Ting
> >
> >
> >
> > ______________________________
> >
> > Ting Lei
> >
> > IMSG at NOAA/NWS/NCEP/EMC
> >
> > 5830 University Research Ct., Cubicle 2765
> >
> > College Park, MD 20740
> >
> > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> >
> > 301-683-3624
> >
> >
>
> --
> Julie Prestopnik
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> 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.
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
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: wrong matching of the prepbufr file and the valid time.
From: Ting Lei - NOAA Affiliate
Time: Wed Dec 18 12:50:50 2019
Gorge,
Thank you so much for your detailed explanation, though i will need
more
trials and errors to understand all of them.
Now I just use one of your suggestion ( use *t00z" ,directly) and that
works for me.
Really appreciate your help, promptly.
Regards,
Ting
______________________________
Ting Lei
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Cubicle 2765
College Park, MD 20740
Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
301-683-3624
On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Ting,
>
> Your configuration is looping over initialization times, defined
here:
>
> LOOP_BY = INIT
> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove the
/2/ from
> this line)*
> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
> INIT_BEG = 2019121400
> INIT_END = 2019121400
> INIT_INCREMENT = 86400
>
> This says loop from 20191214 0Z to 20191214 0Z by an increment of
86400
> seconds, which is just one initialization time at 20191214 0Z.
>
> The LEAD_SEQ item defines the list of forecast leads to process for
each
> initialization time.
>
> LEAD_SEQ = begin_end_incr(0,48,1)
>
> will create a list of forecast leads from 0 to 48 by 1, so it will
be 0, 1,
> 2, 3, 4, 5, ..., 48
>
> For this setup, the initialization time will always be 20191214 0Z
and the
> valid times to process will be 20191214 0Z, 20191214 1Z, 20191214
2Z, ...
> 20191216 0Z
>
> You can also loop by valid time and have the initialization time
adjust
> based on the forecast lead list.
>
> LOOP_BY = *VALID*
> LEAD_SEQ = begin_end_incr(0,48,1)
> *VALID*_TIME_FMT = %Y%m%d%H
> *VALID*_BEG = 2019121400
> *VALID*_END = 2019121400
> *VALID*_INCREMENT = 86400
>
> This will process valid time 20191214 0Z, and initialization times
20191214
> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
>
> Your input template is using valid time and cycle. cycle is the same
> as the *data
> assimilation *initialization time, or da_init (not the same as
init).
> PB2NC_INPUT_TEMPLATE =
> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
>
> The valid time is computed by adding each forecast lead to the
> initialization time, so for each forecast lead, the valid time will
adjust.
>
> If you have PB2NC_OFFSETS set in your config file, this will be
used to
> calculate the da_init (or cycle) value. This can be a list of
offsets that
> you want to allow. For example, if you set
>
> PB2NC_OFFSET = 6, 3
>
> then for valid time 20191214 0Z, it will look for a file with a
da_init
> (cycle) time of 20191214 6Z, then if that is not found it will look
for a
> file with cycle time 20191214 3Z.
>
> Unset the variable or set the list = 0 to avoid this adjustment.
>
> One way to get the desired result you mentioned is to loop over
valid times
> with no offsets:
>
> LOOP_BY = VALID
> VALID_TIME_FMT = %Y%m%d%H
> VALID_BEG = 2019121400
> VALID_END = 2019121400
> VALID_INCREMENT = 86400
> PB2NC_OFFSETS = 0
>
> PB2NC_INPUT_TEMPLATE =
> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
>
> This should look for the file: rap.20191214/rap.t00z.prepbufr.tm00
>
> If you know you only want to use files named rap.t00z.prepbufr.tm00,
you
> can just replace the cycle tag with 00:
>
> PB2NC_INPUT_TEMPLATE = rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
>
> Please let me know if that helps or if you have any questions.
>
> Thanks,
> George
>
> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> >
> > Hi Ting.
> >
> > I have assigned this ticket to George, who I believe is best
suited to
> help
> > you with this issue. Please allow a few business days for a
response.
> >
> > Thanks,
> > Julie
> >
> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> > > Transaction: Ticket created by ting.lei at noaa.gov
> > > Queue: met_help
> > > Subject: wrong matching of the prepbufr file and the valid
time.
> > > Owner: Nobody
> > > Requestors: ting.lei at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
> >
> > >
> > >
> > > Dear Mr. or Mrs.,
> > > When I am running metplus to invoke pb2nc, from the log file, I
found
> the
> > > code found the wrong prepbfur file for the verification time.
> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
observation
> to
> > > get prepbufr.rap.2019121400.nc. . While, the correct one
should be
> > > ../rap.20191214/rap.t00z.prepbufr.tm00
> > > Would you please tell me where I have the problem in the setup?
> > > Your help is appreciated.
> > > My related configure set up is in the following:
> > > ^^
> > > LOOP_BY = INIT
> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> > > INIT_TIME_FMT = %Y%m%d%
> > > INIT_BEG = 2019121400
> > > INIT_END = 2019121400
> > > INIT_INCREMENT = 86400
> > > PB2NC_INPUT_TEMPLATE =
> > > rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> > >
> > > VVV
> > >
> > > Regards,
> > >
> > > Ting
> > >
> > >
> > >
> > > ______________________________
> > >
> > > Ting Lei
> > >
> > > IMSG at NOAA/NWS/NCEP/EMC
> > >
> > > 5830 University Research Ct., Cubicle 2765
> > >
> > > College Park, MD 20740
> > >
> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > >
> > > 301-683-3624
> > >
> > >
> >
> > --
> > Julie Prestopnik
> > Software Engineer
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > 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.
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> 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: wrong matching of the prepbufr file and the valid time.
From: Ting Lei - NOAA Affiliate
Time: Wed Dec 18 13:19:46 2019
Hi, George,
I have a following up question. Thanks a lot in advance for your
help.
Now, I 'd like the pb2nc is able to find obs files like:
rap.t00z.prepbufr.tm00, rap.t01z.prepbufr.tm00 ..and *t12z"*" and so
on.
I am still trying to tune those parameters you mentioned and not
succeeded
yet.
Would you please let me know what set up I should make?
Your help is appreciated.
Regards,
Ting.
______________________________
Ting Lei
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Cubicle 2765
College Park, MD 20740
Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
301-683-3624
On Wed, Dec 18, 2019 at 2:49 PM Ting Lei - NOAA Affiliate
<ting.lei at noaa.gov>
wrote:
> Gorge,
> Thank you so much for your detailed explanation, though i will need
more
> trials and errors to understand all of them.
> Now I just use one of your suggestion ( use *t00z" ,directly) and
that
> works for me.
> Really appreciate your help, promptly.
> Regards,
> Ting
>
> ______________________________
>
> Ting Lei
>
> IMSG at NOAA/NWS/NCEP/EMC
>
> 5830 University Research Ct., Cubicle 2765
>
> College Park, MD 20740
>
> Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
>
> 301-683-3624
>
>
> On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
>> Hi Ting,
>>
>> Your configuration is looping over initialization times, defined
here:
>>
>> LOOP_BY = INIT
>> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove the
/2/ from
>> this line)*
>> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
>> INIT_BEG = 2019121400
>> INIT_END = 2019121400
>> INIT_INCREMENT = 86400
>>
>> This says loop from 20191214 0Z to 20191214 0Z by an increment of
86400
>> seconds, which is just one initialization time at 20191214 0Z.
>>
>> The LEAD_SEQ item defines the list of forecast leads to process for
each
>> initialization time.
>>
>> LEAD_SEQ = begin_end_incr(0,48,1)
>>
>> will create a list of forecast leads from 0 to 48 by 1, so it will
be 0,
>> 1,
>> 2, 3, 4, 5, ..., 48
>>
>> For this setup, the initialization time will always be 20191214 0Z
and the
>> valid times to process will be 20191214 0Z, 20191214 1Z, 20191214
2Z, ...
>> 20191216 0Z
>>
>> You can also loop by valid time and have the initialization time
adjust
>> based on the forecast lead list.
>>
>> LOOP_BY = *VALID*
>> LEAD_SEQ = begin_end_incr(0,48,1)
>> *VALID*_TIME_FMT = %Y%m%d%H
>> *VALID*_BEG = 2019121400
>> *VALID*_END = 2019121400
>> *VALID*_INCREMENT = 86400
>>
>> This will process valid time 20191214 0Z, and initialization times
>> 20191214
>> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
>>
>> Your input template is using valid time and cycle. cycle is the
same
>> as the *data
>> assimilation *initialization time, or da_init (not the same as
init).
>> PB2NC_INPUT_TEMPLATE =
>> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
>>
>> The valid time is computed by adding each forecast lead to the
>> initialization time, so for each forecast lead, the valid time will
>> adjust.
>>
>> If you have PB2NC_OFFSETS set in your config file, this will be
used to
>> calculate the da_init (or cycle) value. This can be a list of
offsets that
>> you want to allow. For example, if you set
>>
>> PB2NC_OFFSET = 6, 3
>>
>> then for valid time 20191214 0Z, it will look for a file with a
da_init
>> (cycle) time of 20191214 6Z, then if that is not found it will look
for a
>> file with cycle time 20191214 3Z.
>>
>> Unset the variable or set the list = 0 to avoid this adjustment.
>>
>> One way to get the desired result you mentioned is to loop over
valid
>> times
>> with no offsets:
>>
>> LOOP_BY = VALID
>> VALID_TIME_FMT = %Y%m%d%H
>> VALID_BEG = 2019121400
>> VALID_END = 2019121400
>> VALID_INCREMENT = 86400
>> PB2NC_OFFSETS = 0
>>
>> PB2NC_INPUT_TEMPLATE =
>> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
>>
>> This should look for the file: rap.20191214/rap.t00z.prepbufr.tm00
>>
>> If you know you only want to use files named
rap.t00z.prepbufr.tm00, you
>> can just replace the cycle tag with 00:
>>
>> PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
>>
>> Please let me know if that helps or if you have any questions.
>>
>> Thanks,
>> George
>>
>> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT <
>> met_help at ucar.edu>
>> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
>> >
>> > Hi Ting.
>> >
>> > I have assigned this ticket to George, who I believe is best
suited to
>> help
>> > you with this issue. Please allow a few business days for a
response.
>> >
>> > Thanks,
>> > Julie
>> >
>> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via RT
<
>> > met_help at ucar.edu> wrote:
>> >
>> > >
>> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
>> > > Transaction: Ticket created by ting.lei at noaa.gov
>> > > Queue: met_help
>> > > Subject: wrong matching of the prepbufr file and the valid
time.
>> > > Owner: Nobody
>> > > Requestors: ting.lei at noaa.gov
>> > > Status: new
>> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
>> >
>> > >
>> > >
>> > > Dear Mr. or Mrs.,
>> > > When I am running metplus to invoke pb2nc, from the log file, I
found
>> the
>> > > code found the wrong prepbfur file for the verification time.
>> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
>> observation to
>> > > get prepbufr.rap.2019121400.nc. . While, the correct one
should be
>> > > ../rap.20191214/rap.t00z.prepbufr.tm00
>> > > Would you please tell me where I have the problem in the setup?
>> > > Your help is appreciated.
>> > > My related configure set up is in the following:
>> > > ^^
>> > > LOOP_BY = INIT
>> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
>> > > INIT_TIME_FMT = %Y%m%d%
>> > > INIT_BEG = 2019121400
>> > > INIT_END = 2019121400
>> > > INIT_INCREMENT = 86400
>> > > PB2NC_INPUT_TEMPLATE =
>> > > rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
>> > > PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
>> > >
>> > > VVV
>> > >
>> > > Regards,
>> > >
>> > > Ting
>> > >
>> > >
>> > >
>> > > ______________________________
>> > >
>> > > Ting Lei
>> > >
>> > > IMSG at NOAA/NWS/NCEP/EMC
>> > >
>> > > 5830 University Research Ct., Cubicle 2765
>> > >
>> > > College Park, MD 20740
>> > >
>> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
>> > >
>> > > 301-683-3624
>> > >
>> > >
>> >
>> > --
>> > Julie Prestopnik
>> > Software Engineer
>> > National Center for Atmospheric Research
>> > Research Applications Laboratory
>> > Phone: 303.497.8399
>> > 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.
>> >
>> >
>>
>> --
>> George McCabe - Software Engineer III
>> National Center for Atmospheric Research
>> Research Applications Laboratory
>> 303-497-2768
>> ---
>> 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: wrong matching of the prepbufr file and the valid time.
From: George McCabe
Time: Wed Dec 18 14:03:38 2019
Hi,
If all of the files are going to be tm00 (no offset), then you can
likely
use the valid time for that spot, like this:
PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t{valid?fmt=%2H}z.prepbufr.tm00
at valid time 20191214 0Z, it will find
rap.20191214/rap.t00z.prepbufr.tm00
at valid time 20191214 1Z, it will find
rap.20191214/rap.t01z.prepbufr.tm00
at valid time 20191214 12Z, it will find
rap.20191214/rap.t12z.prepbufr.tm00
If you need to use offsets, you could use a template that looks like
this:
PB2NC_INPUT_TEMPLATE = rap.{da_init?fmt=%Y%m%d}/rap.t{da_init?fmt=%2H}
z.prepbufr.tm{offset=%2H}
PB2NC_OFFSETS = 3, 6
at valid time 20191214 0Z, it will first look for
rap.20191214/rap.t03z.prepbufr.tm03, then
rap.20191214/rap.t06z.prepbufr.tm06 if the first file is not found
(da_init
= valid time + offset)
at valid time 20191214 1Z, it will first look for
rap.20191214/rap.t04z.prepbufr.tm03, then
rap.20191214/rap.t07z.prepbufr.tm06 if the first file is not found
Does that make sense?
On Wed, Dec 18, 2019 at 1:20 PM Ting Lei - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
>
> Hi, George,
> I have a following up question. Thanks a lot in advance for your
help.
> Now, I 'd like the pb2nc is able to find obs files like:
> rap.t00z.prepbufr.tm00, rap.t01z.prepbufr.tm00 ..and *t12z"*" and so
on.
> I am still trying to tune those parameters you mentioned and not
succeeded
> yet.
> Would you please let me know what set up I should make?
> Your help is appreciated.
> Regards,
> Ting.
>
> ______________________________
>
> Ting Lei
>
> IMSG at NOAA/NWS/NCEP/EMC
>
> 5830 University Research Ct., Cubicle 2765
>
> College Park, MD 20740
>
> Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
>
> 301-683-3624
>
>
> On Wed, Dec 18, 2019 at 2:49 PM Ting Lei - NOAA Affiliate <
> ting.lei at noaa.gov>
> wrote:
>
> > Gorge,
> > Thank you so much for your detailed explanation, though i will
need more
> > trials and errors to understand all of them.
> > Now I just use one of your suggestion ( use *t00z" ,directly) and
that
> > works for me.
> > Really appreciate your help, promptly.
> > Regards,
> > Ting
> >
> > ______________________________
> >
> > Ting Lei
> >
> > IMSG at NOAA/NWS/NCEP/EMC
> >
> > 5830 University Research Ct., Cubicle 2765
> >
> > College Park, MD 20740
> >
> > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> >
> > 301-683-3624
> >
> >
> > On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> Hi Ting,
> >>
> >> Your configuration is looping over initialization times, defined
here:
> >>
> >> LOOP_BY = INIT
> >> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove the
/2/
> from
> >> this line)*
> >> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
> >> INIT_BEG = 2019121400
> >> INIT_END = 2019121400
> >> INIT_INCREMENT = 86400
> >>
> >> This says loop from 20191214 0Z to 20191214 0Z by an increment of
86400
> >> seconds, which is just one initialization time at 20191214 0Z.
> >>
> >> The LEAD_SEQ item defines the list of forecast leads to process
for each
> >> initialization time.
> >>
> >> LEAD_SEQ = begin_end_incr(0,48,1)
> >>
> >> will create a list of forecast leads from 0 to 48 by 1, so it
will be 0,
> >> 1,
> >> 2, 3, 4, 5, ..., 48
> >>
> >> For this setup, the initialization time will always be 20191214
0Z and
> the
> >> valid times to process will be 20191214 0Z, 20191214 1Z, 20191214
2Z,
> ...
> >> 20191216 0Z
> >>
> >> You can also loop by valid time and have the initialization time
adjust
> >> based on the forecast lead list.
> >>
> >> LOOP_BY = *VALID*
> >> LEAD_SEQ = begin_end_incr(0,48,1)
> >> *VALID*_TIME_FMT = %Y%m%d%H
> >> *VALID*_BEG = 2019121400
> >> *VALID*_END = 2019121400
> >> *VALID*_INCREMENT = 86400
> >>
> >> This will process valid time 20191214 0Z, and initialization
times
> >> 20191214
> >> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
> >>
> >> Your input template is using valid time and cycle. cycle is the
same
> >> as the *data
> >> assimilation *initialization time, or da_init (not the same as
init).
> >> PB2NC_INPUT_TEMPLATE =
> >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> >>
> >> The valid time is computed by adding each forecast lead to the
> >> initialization time, so for each forecast lead, the valid time
will
> >> adjust.
> >>
> >> If you have PB2NC_OFFSETS set in your config file, this will be
used to
> >> calculate the da_init (or cycle) value. This can be a list of
offsets
> that
> >> you want to allow. For example, if you set
> >>
> >> PB2NC_OFFSET = 6, 3
> >>
> >> then for valid time 20191214 0Z, it will look for a file with a
da_init
> >> (cycle) time of 20191214 6Z, then if that is not found it will
look for
> a
> >> file with cycle time 20191214 3Z.
> >>
> >> Unset the variable or set the list = 0 to avoid this adjustment.
> >>
> >> One way to get the desired result you mentioned is to loop over
valid
> >> times
> >> with no offsets:
> >>
> >> LOOP_BY = VALID
> >> VALID_TIME_FMT = %Y%m%d%H
> >> VALID_BEG = 2019121400
> >> VALID_END = 2019121400
> >> VALID_INCREMENT = 86400
> >> PB2NC_OFFSETS = 0
> >>
> >> PB2NC_INPUT_TEMPLATE =
> >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> >>
> >> This should look for the file:
rap.20191214/rap.t00z.prepbufr.tm00
> >>
> >> If you know you only want to use files named
rap.t00z.prepbufr.tm00, you
> >> can just replace the cycle tag with 00:
> >>
> >> PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
> >>
> >> Please let me know if that helps or if you have any questions.
> >>
> >> Thanks,
> >> George
> >>
> >> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT <
> >> met_help at ucar.edu>
> >> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> >> >
> >> > Hi Ting.
> >> >
> >> > I have assigned this ticket to George, who I believe is best
suited to
> >> help
> >> > you with this issue. Please allow a few business days for a
response.
> >> >
> >> > Thanks,
> >> > Julie
> >> >
> >> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via
RT <
> >> > met_help at ucar.edu> wrote:
> >> >
> >> > >
> >> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> >> > > Transaction: Ticket created by ting.lei at noaa.gov
> >> > > Queue: met_help
> >> > > Subject: wrong matching of the prepbufr file and the
valid
> time.
> >> > > Owner: Nobody
> >> > > Requestors: ting.lei at noaa.gov
> >> > > Status: new
> >> > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
> >> >
> >> > >
> >> > >
> >> > > Dear Mr. or Mrs.,
> >> > > When I am running metplus to invoke pb2nc, from the log file,
I
> found
> >> the
> >> > > code found the wrong prepbfur file for the verification time.
> >> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
> >> observation to
> >> > > get prepbufr.rap.2019121400.nc. . While, the correct one
should
> be
> >> > > ../rap.20191214/rap.t00z.prepbufr.tm00
> >> > > Would you please tell me where I have the problem in the
setup?
> >> > > Your help is appreciated.
> >> > > My related configure set up is in the following:
> >> > > ^^
> >> > > LOOP_BY = INIT
> >> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> >> > > INIT_TIME_FMT = %Y%m%d%
> >> > > INIT_BEG = 2019121400
> >> > > INIT_END = 2019121400
> >> > > INIT_INCREMENT = 86400
> >> > > PB2NC_INPUT_TEMPLATE =
> >> > > rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> >> > > PB2NC_OUTPUT_TEMPLATE = prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> >> > >
> >> > > VVV
> >> > >
> >> > > Regards,
> >> > >
> >> > > Ting
> >> > >
> >> > >
> >> > >
> >> > > ______________________________
> >> > >
> >> > > Ting Lei
> >> > >
> >> > > IMSG at NOAA/NWS/NCEP/EMC
> >> > >
> >> > > 5830 University Research Ct., Cubicle 2765
> >> > >
> >> > > College Park, MD 20740
> >> > >
> >> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> >> > >
> >> > > 301-683-3624
> >> > >
> >> > >
> >> >
> >> > --
> >> > Julie Prestopnik
> >> > Software Engineer
> >> > National Center for Atmospheric Research
> >> > Research Applications Laboratory
> >> > Phone: 303.497.8399
> >> > 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.
> >> >
> >> >
> >>
> >> --
> >> George McCabe - Software Engineer III
> >> National Center for Atmospheric Research
> >> Research Applications Laboratory
> >> 303-497-2768
> >> ---
> >> 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.
> >>
> >>
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
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: wrong matching of the prepbufr file and the valid time.
From: Ting Lei - NOAA Affiliate
Time: Wed Dec 18 14:10:19 2019
George,
Thank you for your detailed answers.
I will try them carefully.
At least, you let me know metplus can handle those situations and I am
very
happy to know that.
Really appreciate your prompt helps.
Ting
______________________________
Ting Lei
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Cubicle 2765
College Park, MD 20740
Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
301-683-3624
On Wed, Dec 18, 2019 at 4:03 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi,
>
> If all of the files are going to be tm00 (no offset), then you can
likely
> use the valid time for that spot, like this:
>
> PB2NC_INPUT_TEMPLATE =
> rap.{valid?fmt=%Y%m%d}/rap.t{valid?fmt=%2H}z.prepbufr.tm00
>
> at valid time 20191214 0Z, it will find
rap.20191214/rap.t00z.prepbufr.tm00
>
> at valid time 20191214 1Z, it will find
rap.20191214/rap.t01z.prepbufr.tm00
>
> at valid time 20191214 12Z, it will find
> rap.20191214/rap.t12z.prepbufr.tm00
>
> If you need to use offsets, you could use a template that looks like
this:
>
> PB2NC_INPUT_TEMPLATE =
rap.{da_init?fmt=%Y%m%d}/rap.t{da_init?fmt=%2H}
> z.prepbufr.tm{offset=%2H}
> PB2NC_OFFSETS = 3, 6
>
> at valid time 20191214 0Z, it will first look for
> rap.20191214/rap.t03z.prepbufr.tm03, then
> rap.20191214/rap.t06z.prepbufr.tm06 if the first file is not found
(da_init
> = valid time + offset)
>
> at valid time 20191214 1Z, it will first look for
> rap.20191214/rap.t04z.prepbufr.tm03, then
> rap.20191214/rap.t07z.prepbufr.tm06 if the first file is not found
>
> Does that make sense?
>
> On Wed, Dec 18, 2019 at 1:20 PM Ting Lei - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> >
> > Hi, George,
> > I have a following up question. Thanks a lot in advance for your
help.
> > Now, I 'd like the pb2nc is able to find obs files like:
> > rap.t00z.prepbufr.tm00, rap.t01z.prepbufr.tm00 ..and *t12z"*" and
so on.
> > I am still trying to tune those parameters you mentioned and not
> succeeded
> > yet.
> > Would you please let me know what set up I should make?
> > Your help is appreciated.
> > Regards,
> > Ting.
> >
> > ______________________________
> >
> > Ting Lei
> >
> > IMSG at NOAA/NWS/NCEP/EMC
> >
> > 5830 University Research Ct., Cubicle 2765
> >
> > College Park, MD 20740
> >
> > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> >
> > 301-683-3624
> >
> >
> > On Wed, Dec 18, 2019 at 2:49 PM Ting Lei - NOAA Affiliate <
> > ting.lei at noaa.gov>
> > wrote:
> >
> > > Gorge,
> > > Thank you so much for your detailed explanation, though i will
need
> more
> > > trials and errors to understand all of them.
> > > Now I just use one of your suggestion ( use *t00z" ,directly)
and that
> > > works for me.
> > > Really appreciate your help, promptly.
> > > Regards,
> > > Ting
> > >
> > > ______________________________
> > >
> > > Ting Lei
> > >
> > > IMSG at NOAA/NWS/NCEP/EMC
> > >
> > > 5830 University Research Ct., Cubicle 2765
> > >
> > > College Park, MD 20740
> > >
> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > >
> > > 301-683-3624
> > >
> > >
> > > On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > >> Hi Ting,
> > >>
> > >> Your configuration is looping over initialization times,
defined here:
> > >>
> > >> LOOP_BY = INIT
> > >> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove
the /2/
> > from
> > >> this line)*
> > >> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
> > >> INIT_BEG = 2019121400
> > >> INIT_END = 2019121400
> > >> INIT_INCREMENT = 86400
> > >>
> > >> This says loop from 20191214 0Z to 20191214 0Z by an increment
of
> 86400
> > >> seconds, which is just one initialization time at 20191214 0Z.
> > >>
> > >> The LEAD_SEQ item defines the list of forecast leads to process
for
> each
> > >> initialization time.
> > >>
> > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > >>
> > >> will create a list of forecast leads from 0 to 48 by 1, so it
will be
> 0,
> > >> 1,
> > >> 2, 3, 4, 5, ..., 48
> > >>
> > >> For this setup, the initialization time will always be 20191214
0Z and
> > the
> > >> valid times to process will be 20191214 0Z, 20191214 1Z,
20191214 2Z,
> > ...
> > >> 20191216 0Z
> > >>
> > >> You can also loop by valid time and have the initialization
time
> adjust
> > >> based on the forecast lead list.
> > >>
> > >> LOOP_BY = *VALID*
> > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > >> *VALID*_TIME_FMT = %Y%m%d%H
> > >> *VALID*_BEG = 2019121400
> > >> *VALID*_END = 2019121400
> > >> *VALID*_INCREMENT = 86400
> > >>
> > >> This will process valid time 20191214 0Z, and initialization
times
> > >> 20191214
> > >> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
> > >>
> > >> Your input template is using valid time and cycle. cycle is the
same
> > >> as the *data
> > >> assimilation *initialization time, or da_init (not the same as
init).
> > >> PB2NC_INPUT_TEMPLATE =
> > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > >>
> > >> The valid time is computed by adding each forecast lead to the
> > >> initialization time, so for each forecast lead, the valid time
will
> > >> adjust.
> > >>
> > >> If you have PB2NC_OFFSETS set in your config file, this will
be used
> to
> > >> calculate the da_init (or cycle) value. This can be a list of
offsets
> > that
> > >> you want to allow. For example, if you set
> > >>
> > >> PB2NC_OFFSET = 6, 3
> > >>
> > >> then for valid time 20191214 0Z, it will look for a file with a
> da_init
> > >> (cycle) time of 20191214 6Z, then if that is not found it will
look
> for
> > a
> > >> file with cycle time 20191214 3Z.
> > >>
> > >> Unset the variable or set the list = 0 to avoid this
adjustment.
> > >>
> > >> One way to get the desired result you mentioned is to loop over
valid
> > >> times
> > >> with no offsets:
> > >>
> > >> LOOP_BY = VALID
> > >> VALID_TIME_FMT = %Y%m%d%H
> > >> VALID_BEG = 2019121400
> > >> VALID_END = 2019121400
> > >> VALID_INCREMENT = 86400
> > >> PB2NC_OFFSETS = 0
> > >>
> > >> PB2NC_INPUT_TEMPLATE =
> > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > >>
> > >> This should look for the file:
rap.20191214/rap.t00z.prepbufr.tm00
> > >>
> > >> If you know you only want to use files named
rap.t00z.prepbufr.tm00,
> you
> > >> can just replace the cycle tag with 00:
> > >>
> > >> PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
> > >>
> > >> Please let me know if that helps or if you have any questions.
> > >>
> > >> Thanks,
> > >> George
> > >>
> > >> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT <
> > >> met_help at ucar.edu>
> > >> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
>
> > >> >
> > >> > Hi Ting.
> > >> >
> > >> > I have assigned this ticket to George, who I believe is best
suited
> to
> > >> help
> > >> > you with this issue. Please allow a few business days for a
> response.
> > >> >
> > >> > Thanks,
> > >> > Julie
> > >> >
> > >> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate via
RT <
> > >> > met_help at ucar.edu> wrote:
> > >> >
> > >> > >
> > >> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> > >> > > Transaction: Ticket created by ting.lei at noaa.gov
> > >> > > Queue: met_help
> > >> > > Subject: wrong matching of the prepbufr file and the
valid
> > time.
> > >> > > Owner: Nobody
> > >> > > Requestors: ting.lei at noaa.gov
> > >> > > Status: new
> > >> > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
> > >> >
> > >> > >
> > >> > >
> > >> > > Dear Mr. or Mrs.,
> > >> > > When I am running metplus to invoke pb2nc, from the log
file, I
> > found
> > >> the
> > >> > > code found the wrong prepbfur file for the verification
time.
> > >> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as the
> > >> observation to
> > >> > > get prepbufr.rap.2019121400.nc. . While, the correct one
should
> > be
> > >> > > ../rap.20191214/rap.t00z.prepbufr.tm00
> > >> > > Would you please tell me where I have the problem in the
setup?
> > >> > > Your help is appreciated.
> > >> > > My related configure set up is in the following:
> > >> > > ^^
> > >> > > LOOP_BY = INIT
> > >> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> > >> > > INIT_TIME_FMT = %Y%m%d%
> > >> > > INIT_BEG = 2019121400
> > >> > > INIT_END = 2019121400
> > >> > > INIT_INCREMENT = 86400
> > >> > > PB2NC_INPUT_TEMPLATE =
> > >> > > rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > >> > > PB2NC_OUTPUT_TEMPLATE =
prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> > >> > >
> > >> > > VVV
> > >> > >
> > >> > > Regards,
> > >> > >
> > >> > > Ting
> > >> > >
> > >> > >
> > >> > >
> > >> > > ______________________________
> > >> > >
> > >> > > Ting Lei
> > >> > >
> > >> > > IMSG at NOAA/NWS/NCEP/EMC
> > >> > >
> > >> > > 5830 University Research Ct., Cubicle 2765
> > >> > >
> > >> > > College Park, MD 20740
> > >> > >
> > >> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > >> > >
> > >> > > 301-683-3624
> > >> > >
> > >> > >
> > >> >
> > >> > --
> > >> > Julie Prestopnik
> > >> > Software Engineer
> > >> > National Center for Atmospheric Research
> > >> > Research Applications Laboratory
> > >> > Phone: 303.497.8399
> > >> > 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.
> > >> >
> > >> >
> > >>
> > >> --
> > >> George McCabe - Software Engineer III
> > >> National Center for Atmospheric Research
> > >> Research Applications Laboratory
> > >> 303-497-2768
> > >> ---
> > >> 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.
> > >>
> > >>
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> 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: wrong matching of the prepbufr file and the valid time.
From: George McCabe
Time: Wed Dec 18 14:22:07 2019
Glad to help! Feel free to let me know if you have any other questions
or
problems. I will leave this ticket open for a little while longer so
you
can respond directly to me.
On Wed, Dec 18, 2019 at 2:10 PM Ting Lei - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
>
> George,
> Thank you for your detailed answers.
> I will try them carefully.
> At least, you let me know metplus can handle those situations and I
am very
> happy to know that.
> Really appreciate your prompt helps.
> Ting
>
> ______________________________
>
> Ting Lei
>
> IMSG at NOAA/NWS/NCEP/EMC
>
> 5830 University Research Ct., Cubicle 2765
>
> College Park, MD 20740
>
> Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
>
> 301-683-3624
>
>
> On Wed, Dec 18, 2019 at 4:03 PM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi,
> >
> > If all of the files are going to be tm00 (no offset), then you can
likely
> > use the valid time for that spot, like this:
> >
> > PB2NC_INPUT_TEMPLATE =
> > rap.{valid?fmt=%Y%m%d}/rap.t{valid?fmt=%2H}z.prepbufr.tm00
> >
> > at valid time 20191214 0Z, it will find
> rap.20191214/rap.t00z.prepbufr.tm00
> >
> > at valid time 20191214 1Z, it will find
> rap.20191214/rap.t01z.prepbufr.tm00
> >
> > at valid time 20191214 12Z, it will find
> > rap.20191214/rap.t12z.prepbufr.tm00
> >
> > If you need to use offsets, you could use a template that looks
like
> this:
> >
> > PB2NC_INPUT_TEMPLATE =
rap.{da_init?fmt=%Y%m%d}/rap.t{da_init?fmt=%2H}
> > z.prepbufr.tm{offset=%2H}
> > PB2NC_OFFSETS = 3, 6
> >
> > at valid time 20191214 0Z, it will first look for
> > rap.20191214/rap.t03z.prepbufr.tm03, then
> > rap.20191214/rap.t06z.prepbufr.tm06 if the first file is not found
> (da_init
> > = valid time + offset)
> >
> > at valid time 20191214 1Z, it will first look for
> > rap.20191214/rap.t04z.prepbufr.tm03, then
> > rap.20191214/rap.t07z.prepbufr.tm06 if the first file is not found
> >
> > Does that make sense?
> >
> > On Wed, Dec 18, 2019 at 1:20 PM Ting Lei - NOAA Affiliate via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> > >
> > > Hi, George,
> > > I have a following up question. Thanks a lot in advance for
your help.
> > > Now, I 'd like the pb2nc is able to find obs files like:
> > > rap.t00z.prepbufr.tm00, rap.t01z.prepbufr.tm00 ..and *t12z"*"
and so
> on.
> > > I am still trying to tune those parameters you mentioned and not
> > succeeded
> > > yet.
> > > Would you please let me know what set up I should make?
> > > Your help is appreciated.
> > > Regards,
> > > Ting.
> > >
> > > ______________________________
> > >
> > > Ting Lei
> > >
> > > IMSG at NOAA/NWS/NCEP/EMC
> > >
> > > 5830 University Research Ct., Cubicle 2765
> > >
> > > College Park, MD 20740
> > >
> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > >
> > > 301-683-3624
> > >
> > >
> > > On Wed, Dec 18, 2019 at 2:49 PM Ting Lei - NOAA Affiliate <
> > > ting.lei at noaa.gov>
> > > wrote:
> > >
> > > > Gorge,
> > > > Thank you so much for your detailed explanation, though i will
need
> > more
> > > > trials and errors to understand all of them.
> > > > Now I just use one of your suggestion ( use *t00z" ,directly)
and
> that
> > > > works for me.
> > > > Really appreciate your help, promptly.
> > > > Regards,
> > > > Ting
> > > >
> > > > ______________________________
> > > >
> > > > Ting Lei
> > > >
> > > > IMSG at NOAA/NWS/NCEP/EMC
> > > >
> > > > 5830 University Research Ct., Cubicle 2765
> > > >
> > > > College Park, MD 20740
> > > >
> > > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > > >
> > > > 301-683-3624
> > > >
> > > >
> > > > On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT <
> > met_help at ucar.edu
> > > >
> > > > wrote:
> > > >
> > > >> Hi Ting,
> > > >>
> > > >> Your configuration is looping over initialization times,
defined
> here:
> > > >>
> > > >> LOOP_BY = INIT
> > > >> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to remove
the
> /2/
> > > from
> > > >> this line)*
> > > >> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
> > > >> INIT_BEG = 2019121400
> > > >> INIT_END = 2019121400
> > > >> INIT_INCREMENT = 86400
> > > >>
> > > >> This says loop from 20191214 0Z to 20191214 0Z by an
increment of
> > 86400
> > > >> seconds, which is just one initialization time at 20191214
0Z.
> > > >>
> > > >> The LEAD_SEQ item defines the list of forecast leads to
process for
> > each
> > > >> initialization time.
> > > >>
> > > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > > >>
> > > >> will create a list of forecast leads from 0 to 48 by 1, so it
will
> be
> > 0,
> > > >> 1,
> > > >> 2, 3, 4, 5, ..., 48
> > > >>
> > > >> For this setup, the initialization time will always be
20191214 0Z
> and
> > > the
> > > >> valid times to process will be 20191214 0Z, 20191214 1Z,
20191214
> 2Z,
> > > ...
> > > >> 20191216 0Z
> > > >>
> > > >> You can also loop by valid time and have the initialization
time
> > adjust
> > > >> based on the forecast lead list.
> > > >>
> > > >> LOOP_BY = *VALID*
> > > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > > >> *VALID*_TIME_FMT = %Y%m%d%H
> > > >> *VALID*_BEG = 2019121400
> > > >> *VALID*_END = 2019121400
> > > >> *VALID*_INCREMENT = 86400
> > > >>
> > > >> This will process valid time 20191214 0Z, and initialization
times
> > > >> 20191214
> > > >> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
> > > >>
> > > >> Your input template is using valid time and cycle. cycle is
the same
> > > >> as the *data
> > > >> assimilation *initialization time, or da_init (not the same
as
> init).
> > > >> PB2NC_INPUT_TEMPLATE =
> > > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > >>
> > > >> The valid time is computed by adding each forecast lead to
the
> > > >> initialization time, so for each forecast lead, the valid
time will
> > > >> adjust.
> > > >>
> > > >> If you have PB2NC_OFFSETS set in your config file, this will
be
> used
> > to
> > > >> calculate the da_init (or cycle) value. This can be a list of
> offsets
> > > that
> > > >> you want to allow. For example, if you set
> > > >>
> > > >> PB2NC_OFFSET = 6, 3
> > > >>
> > > >> then for valid time 20191214 0Z, it will look for a file with
a
> > da_init
> > > >> (cycle) time of 20191214 6Z, then if that is not found it
will look
> > for
> > > a
> > > >> file with cycle time 20191214 3Z.
> > > >>
> > > >> Unset the variable or set the list = 0 to avoid this
adjustment.
> > > >>
> > > >> One way to get the desired result you mentioned is to loop
over
> valid
> > > >> times
> > > >> with no offsets:
> > > >>
> > > >> LOOP_BY = VALID
> > > >> VALID_TIME_FMT = %Y%m%d%H
> > > >> VALID_BEG = 2019121400
> > > >> VALID_END = 2019121400
> > > >> VALID_INCREMENT = 86400
> > > >> PB2NC_OFFSETS = 0
> > > >>
> > > >> PB2NC_INPUT_TEMPLATE =
> > > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > >>
> > > >> This should look for the file:
rap.20191214/rap.t00z.prepbufr.tm00
> > > >>
> > > >> If you know you only want to use files named
rap.t00z.prepbufr.tm00,
> > you
> > > >> can just replace the cycle tag with 00:
> > > >>
> > > >> PB2NC_INPUT_TEMPLATE =
rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
> > > >>
> > > >> Please let me know if that helps or if you have any
questions.
> > > >>
> > > >> Thanks,
> > > >> George
> > > >>
> > > >> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT <
> > > >> met_help at ucar.edu>
> > > >> wrote:
> > > >>
> > > >> >
> > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> > > >> >
> > > >> > Hi Ting.
> > > >> >
> > > >> > I have assigned this ticket to George, who I believe is
best
> suited
> > to
> > > >> help
> > > >> > you with this issue. Please allow a few business days for
a
> > response.
> > > >> >
> > > >> > Thanks,
> > > >> > Julie
> > > >> >
> > > >> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate
via RT <
> > > >> > met_help at ucar.edu> wrote:
> > > >> >
> > > >> > >
> > > >> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> > > >> > > Transaction: Ticket created by ting.lei at noaa.gov
> > > >> > > Queue: met_help
> > > >> > > Subject: wrong matching of the prepbufr file and the
valid
> > > time.
> > > >> > > Owner: Nobody
> > > >> > > Requestors: ting.lei at noaa.gov
> > > >> > > Status: new
> > > >> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
> > > >> >
> > > >> > >
> > > >> > >
> > > >> > > Dear Mr. or Mrs.,
> > > >> > > When I am running metplus to invoke pb2nc, from the log
file, I
> > > found
> > > >> the
> > > >> > > code found the wrong prepbfur file for the verification
time.
> > > >> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as
the
> > > >> observation to
> > > >> > > get prepbufr.rap.2019121400.nc. . While, the correct
one
> should
> > > be
> > > >> > > ../rap.20191214/rap.t00z.prepbufr.tm00
> > > >> > > Would you please tell me where I have the problem in the
setup?
> > > >> > > Your help is appreciated.
> > > >> > > My related configure set up is in the following:
> > > >> > > ^^
> > > >> > > LOOP_BY = INIT
> > > >> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> > > >> > > INIT_TIME_FMT = %Y%m%d%
> > > >> > > INIT_BEG = 2019121400
> > > >> > > INIT_END = 2019121400
> > > >> > > INIT_INCREMENT = 86400
> > > >> > > PB2NC_INPUT_TEMPLATE =
> > > >> > >
rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > >> > > PB2NC_OUTPUT_TEMPLATE =
prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> > > >> > >
> > > >> > > VVV
> > > >> > >
> > > >> > > Regards,
> > > >> > >
> > > >> > > Ting
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > ______________________________
> > > >> > >
> > > >> > > Ting Lei
> > > >> > >
> > > >> > > IMSG at NOAA/NWS/NCEP/EMC
> > > >> > >
> > > >> > > 5830 University Research Ct., Cubicle 2765
> > > >> > >
> > > >> > > College Park, MD 20740
> > > >> > >
> > > >> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > > >> > >
> > > >> > > 301-683-3624
> > > >> > >
> > > >> > >
> > > >> >
> > > >> > --
> > > >> > Julie Prestopnik
> > > >> > Software Engineer
> > > >> > National Center for Atmospheric Research
> > > >> > Research Applications Laboratory
> > > >> > Phone: 303.497.8399
> > > >> > 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.
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> George McCabe - Software Engineer III
> > > >> National Center for Atmospheric Research
> > > >> Research Applications Laboratory
> > > >> 303-497-2768
> > > >> ---
> > > >> 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.
> > > >>
> > > >>
> > >
> > >
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > 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.
> >
> >
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
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: wrong matching of the prepbufr file and the valid time.
From: Ting Lei - NOAA Affiliate
Time: Thu Dec 19 06:15:32 2019
George,
Yes, your solution does work.
Thank you so much!. This ticket can be closed now.
Happy Holiday.
Ting
______________________________
Ting Lei
IMSG at NOAA/NWS/NCEP/EMC
5830 University Research Ct., Cubicle 2765
College Park, MD 20740
Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
301-683-3624
On Wed, Dec 18, 2019 at 4:22 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Glad to help! Feel free to let me know if you have any other
questions or
> problems. I will leave this ticket open for a little while longer so
you
> can respond directly to me.
>
> On Wed, Dec 18, 2019 at 2:10 PM Ting Lei - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> >
> > George,
> > Thank you for your detailed answers.
> > I will try them carefully.
> > At least, you let me know metplus can handle those situations and
I am
> very
> > happy to know that.
> > Really appreciate your prompt helps.
> > Ting
> >
> > ______________________________
> >
> > Ting Lei
> >
> > IMSG at NOAA/NWS/NCEP/EMC
> >
> > 5830 University Research Ct., Cubicle 2765
> >
> > College Park, MD 20740
> >
> > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> >
> > 301-683-3624
> >
> >
> > On Wed, Dec 18, 2019 at 4:03 PM George McCabe via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hi,
> > >
> > > If all of the files are going to be tm00 (no offset), then you
can
> likely
> > > use the valid time for that spot, like this:
> > >
> > > PB2NC_INPUT_TEMPLATE =
> > > rap.{valid?fmt=%Y%m%d}/rap.t{valid?fmt=%2H}z.prepbufr.tm00
> > >
> > > at valid time 20191214 0Z, it will find
> > rap.20191214/rap.t00z.prepbufr.tm00
> > >
> > > at valid time 20191214 1Z, it will find
> > rap.20191214/rap.t01z.prepbufr.tm00
> > >
> > > at valid time 20191214 12Z, it will find
> > > rap.20191214/rap.t12z.prepbufr.tm00
> > >
> > > If you need to use offsets, you could use a template that looks
like
> > this:
> > >
> > > PB2NC_INPUT_TEMPLATE =
rap.{da_init?fmt=%Y%m%d}/rap.t{da_init?fmt=%2H}
> > > z.prepbufr.tm{offset=%2H}
> > > PB2NC_OFFSETS = 3, 6
> > >
> > > at valid time 20191214 0Z, it will first look for
> > > rap.20191214/rap.t03z.prepbufr.tm03, then
> > > rap.20191214/rap.t06z.prepbufr.tm06 if the first file is not
found
> > (da_init
> > > = valid time + offset)
> > >
> > > at valid time 20191214 1Z, it will first look for
> > > rap.20191214/rap.t04z.prepbufr.tm03, then
> > > rap.20191214/rap.t07z.prepbufr.tm06 if the first file is not
found
> > >
> > > Does that make sense?
> > >
> > > On Wed, Dec 18, 2019 at 1:20 PM Ting Lei - NOAA Affiliate via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
>
> > > >
> > > > Hi, George,
> > > > I have a following up question. Thanks a lot in advance for
your
> help.
> > > > Now, I 'd like the pb2nc is able to find obs files like:
> > > > rap.t00z.prepbufr.tm00, rap.t01z.prepbufr.tm00 ..and *t12z"*"
and so
> > on.
> > > > I am still trying to tune those parameters you mentioned and
not
> > > succeeded
> > > > yet.
> > > > Would you please let me know what set up I should make?
> > > > Your help is appreciated.
> > > > Regards,
> > > > Ting.
> > > >
> > > > ______________________________
> > > >
> > > > Ting Lei
> > > >
> > > > IMSG at NOAA/NWS/NCEP/EMC
> > > >
> > > > 5830 University Research Ct., Cubicle 2765
> > > >
> > > > College Park, MD 20740
> > > >
> > > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > > >
> > > > 301-683-3624
> > > >
> > > >
> > > > On Wed, Dec 18, 2019 at 2:49 PM Ting Lei - NOAA Affiliate <
> > > > ting.lei at noaa.gov>
> > > > wrote:
> > > >
> > > > > Gorge,
> > > > > Thank you so much for your detailed explanation, though i
will need
> > > more
> > > > > trials and errors to understand all of them.
> > > > > Now I just use one of your suggestion ( use *t00z"
,directly) and
> > that
> > > > > works for me.
> > > > > Really appreciate your help, promptly.
> > > > > Regards,
> > > > > Ting
> > > > >
> > > > > ______________________________
> > > > >
> > > > > Ting Lei
> > > > >
> > > > > IMSG at NOAA/NWS/NCEP/EMC
> > > > >
> > > > > 5830 University Research Ct., Cubicle 2765
> > > > >
> > > > > College Park, MD 20740
> > > > >
> > > > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > > > >
> > > > > 301-683-3624
> > > > >
> > > > >
> > > > > On Wed, Dec 18, 2019 at 12:37 PM George McCabe via RT <
> > > met_help at ucar.edu
> > > > >
> > > > > wrote:
> > > > >
> > > > >> Hi Ting,
> > > > >>
> > > > >> Your configuration is looping over initialization times,
defined
> > here:
> > > > >>
> > > > >> LOOP_BY = INIT
> > > > >> LEAD_SEQ = begin_end_incr(0,48,1)/2/ *(you may need to
remove the
> > /2/
> > > > from
> > > > >> this line)*
> > > > >> INIT_TIME_FMT = %Y%m%d%*H* (*there is a missing H here)*
> > > > >> INIT_BEG = 2019121400
> > > > >> INIT_END = 2019121400
> > > > >> INIT_INCREMENT = 86400
> > > > >>
> > > > >> This says loop from 20191214 0Z to 20191214 0Z by an
increment of
> > > 86400
> > > > >> seconds, which is just one initialization time at 20191214
0Z.
> > > > >>
> > > > >> The LEAD_SEQ item defines the list of forecast leads to
process
> for
> > > each
> > > > >> initialization time.
> > > > >>
> > > > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > > > >>
> > > > >> will create a list of forecast leads from 0 to 48 by 1, so
it will
> > be
> > > 0,
> > > > >> 1,
> > > > >> 2, 3, 4, 5, ..., 48
> > > > >>
> > > > >> For this setup, the initialization time will always be
20191214 0Z
> > and
> > > > the
> > > > >> valid times to process will be 20191214 0Z, 20191214 1Z,
20191214
> > 2Z,
> > > > ...
> > > > >> 20191216 0Z
> > > > >>
> > > > >> You can also loop by valid time and have the initialization
time
> > > adjust
> > > > >> based on the forecast lead list.
> > > > >>
> > > > >> LOOP_BY = *VALID*
> > > > >> LEAD_SEQ = begin_end_incr(0,48,1)
> > > > >> *VALID*_TIME_FMT = %Y%m%d%H
> > > > >> *VALID*_BEG = 2019121400
> > > > >> *VALID*_END = 2019121400
> > > > >> *VALID*_INCREMENT = 86400
> > > > >>
> > > > >> This will process valid time 20191214 0Z, and
initialization times
> > > > >> 20191214
> > > > >> 0Z, 20191213 23Z, 20191213 22Z, ... 20191212 0Z.
> > > > >>
> > > > >> Your input template is using valid time and cycle. cycle is
the
> same
> > > > >> as the *data
> > > > >> assimilation *initialization time, or da_init (not the same
as
> > init).
> > > > >> PB2NC_INPUT_TEMPLATE =
> > > > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > > >>
> > > > >> The valid time is computed by adding each forecast lead to
the
> > > > >> initialization time, so for each forecast lead, the valid
time
> will
> > > > >> adjust.
> > > > >>
> > > > >> If you have PB2NC_OFFSETS set in your config file, this
will be
> > used
> > > to
> > > > >> calculate the da_init (or cycle) value. This can be a list
of
> > offsets
> > > > that
> > > > >> you want to allow. For example, if you set
> > > > >>
> > > > >> PB2NC_OFFSET = 6, 3
> > > > >>
> > > > >> then for valid time 20191214 0Z, it will look for a file
with a
> > > da_init
> > > > >> (cycle) time of 20191214 6Z, then if that is not found it
will
> look
> > > for
> > > > a
> > > > >> file with cycle time 20191214 3Z.
> > > > >>
> > > > >> Unset the variable or set the list = 0 to avoid this
adjustment.
> > > > >>
> > > > >> One way to get the desired result you mentioned is to loop
over
> > valid
> > > > >> times
> > > > >> with no offsets:
> > > > >>
> > > > >> LOOP_BY = VALID
> > > > >> VALID_TIME_FMT = %Y%m%d%H
> > > > >> VALID_BEG = 2019121400
> > > > >> VALID_END = 2019121400
> > > > >> VALID_INCREMENT = 86400
> > > > >> PB2NC_OFFSETS = 0
> > > > >>
> > > > >> PB2NC_INPUT_TEMPLATE =
> > > > >> rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > > >>
> > > > >> This should look for the file:
rap.20191214/rap.t00z.prepbufr.tm00
> > > > >>
> > > > >> If you know you only want to use files named
> rap.t00z.prepbufr.tm00,
> > > you
> > > > >> can just replace the cycle tag with 00:
> > > > >>
> > > > >> PB2NC_INPUT_TEMPLATE =
> rap.{valid?fmt=%Y%m%d}/rap.t00z.prepbufr.tm00
> > > > >>
> > > > >> Please let me know if that helps or if you have any
questions.
> > > > >>
> > > > >> Thanks,
> > > > >> George
> > > > >>
> > > > >> On Wed, Dec 18, 2019 at 9:23 AM Julie Prestopnik via RT <
> > > > >> met_help at ucar.edu>
> > > > >> wrote:
> > > > >>
> > > > >> >
> > > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516 >
> > > > >> >
> > > > >> > Hi Ting.
> > > > >> >
> > > > >> > I have assigned this ticket to George, who I believe is
best
> > suited
> > > to
> > > > >> help
> > > > >> > you with this issue. Please allow a few business days
for a
> > > response.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > Julie
> > > > >> >
> > > > >> > On Tue, Dec 17, 2019 at 4:06 PM Ting Lei - NOAA Affiliate
via
> RT <
> > > > >> > met_help at ucar.edu> wrote:
> > > > >> >
> > > > >> > >
> > > > >> > > Tue Dec 17 16:05:50 2019: Request 93516 was acted upon.
> > > > >> > > Transaction: Ticket created by ting.lei at noaa.gov
> > > > >> > > Queue: met_help
> > > > >> > > Subject: wrong matching of the prepbufr file and
the
> valid
> > > > time.
> > > > >> > > Owner: Nobody
> > > > >> > > Requestors: ting.lei at noaa.gov
> > > > >> > > Status: new
> > > > >> > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=93516
> > > > >> >
> > > > >> > >
> > > > >> > >
> > > > >> > > Dear Mr. or Mrs.,
> > > > >> > > When I am running metplus to invoke pb2nc, from the log
file,
> I
> > > > found
> > > > >> the
> > > > >> > > code found the wrong prepbfur file for the verification
time.
> > > > >> > > Like : using ../rap.20191214/rap.t06z.prepbufr.tm00 as
the
> > > > >> observation to
> > > > >> > > get prepbufr.rap.2019121400.nc. . While, the correct
one
> > should
> > > > be
> > > > >> > > ../rap.20191214/rap.t00z.prepbufr.tm00
> > > > >> > > Would you please tell me where I have the problem in
the
> setup?
> > > > >> > > Your help is appreciated.
> > > > >> > > My related configure set up is in the following:
> > > > >> > > ^^
> > > > >> > > LOOP_BY = INIT
> > > > >> > > LEAD_SEQ = begin_end_incr(0,48,1)/2/
> > > > >> > > INIT_TIME_FMT = %Y%m%d%
> > > > >> > > INIT_BEG = 2019121400
> > > > >> > > INIT_END = 2019121400
> > > > >> > > INIT_INCREMENT = 86400
> > > > >> > > PB2NC_INPUT_TEMPLATE =
> > > > >> > >
rap.{valid?fmt=%Y%m%d}/rap.t{cycle?fmt=%2H}z.prepbufr.tm00
> > > > >> > > PB2NC_OUTPUT_TEMPLATE =
prepbufr.rap.{valid?fmt=%Y%m%d%H}.nc
> > > > >> > >
> > > > >> > > VVV
> > > > >> > >
> > > > >> > > Regards,
> > > > >> > >
> > > > >> > > Ting
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > ______________________________
> > > > >> > >
> > > > >> > > Ting Lei
> > > > >> > >
> > > > >> > > IMSG at NOAA/NWS/NCEP/EMC
> > > > >> > >
> > > > >> > > 5830 University Research Ct., Cubicle 2765
> > > > >> > >
> > > > >> > > College Park, MD 20740
> > > > >> > >
> > > > >> > > Ting.Lei at noaa.gov <Joe.Smith at noaa.gov>
> > > > >> > >
> > > > >> > > 301-683-3624
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> > --
> > > > >> > Julie Prestopnik
> > > > >> > Software Engineer
> > > > >> > National Center for Atmospheric Research
> > > > >> > Research Applications Laboratory
> > > > >> > Phone: 303.497.8399
> > > > >> > 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.
> > > > >> >
> > > > >> >
> > > > >>
> > > > >> --
> > > > >> George McCabe - Software Engineer III
> > > > >> National Center for Atmospheric Research
> > > > >> Research Applications Laboratory
> > > > >> 303-497-2768
> > > > >> ---
> > > > >> 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.
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> > > --
> > > George McCabe - Software Engineer III
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > 303-497-2768
> > > ---
> > > 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.
> > >
> > >
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> 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