[Met_help] [rt.rap.ucar.edu #85662] History for Reading Climo File
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:03:30 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I am having trouble getting MET to find the data of interest in my
climo file. The command line is:
/h/WXQC/met-6.1/bin/point_stat
/h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-843bd8cb53f5
/h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-fbc04e9c9681
/h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated -outdir
/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v 4
In the listing below, note that 0 climatology mean levels were found. The
Config file is attached.
Reading data for APCP_06A6.
DEBUG 3: Use the forecast grid.
DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348 Ny: 636
Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha: 6852.864 Cone:
0.716 Bx: 126.9979 By: 4353.7043
DEBUG 2: Processing masking regions.
DEBUG 3: Processing grid mask: FULL
DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4:
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll: -89.761
DEBUG 4: lon_ll: -0
DEBUG 4: delta_lat: 0.312212
DEBUG 4: delta_lon: 0.3125
DEBUG 4: Nlat: 576
DEBUG 4: Nlon: 1152
DEBUG 4:
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_NcMet".
DEBUG 3: Found 0 climatology fields.
DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean levels,
and 0 climatology standard deviation levels.
DEBUG 2:
DEBUG 2:
----------------------------------------------------------------------------
----
DEBUG 2:
DEBUG 2: Searching 1715 observations from 1715 messages.
DEBUG 2:
DEBUG 2:
----------------------------------------------------------------------------
----
The files of interest are on AMERDEC. What am I doing wrong?
Thanks
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Reading Climo File
From: John Halley Gotway
Time: Mon Jun 25 15:44:53 2018
Hi Bob,
I see you're having trouble getting climo data to be used in your run
of
Point-Stat. Thanks for sending the sample data. That made it a lot
easier
to debug.
We initially setup the climo logic to handle 2 cases:
(1) make the climo month match the month currently being evaluated
(2) make the climo month *and* day match the month and day currently
being evaluated
Your case falls into neither category and that's why you're not
getting a
match. Here's the relevant timestamps:
ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
APCP_06:valid_time = "20180618_120000" ;
ncdump -h cfsr_freq_p6_world_mo_6.nc | grep valid_time
CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
Your forecast data is valid in June while the climo data is valid in
January. I suspect what you'd like to see is a 3rd option where the
climo
timestamp doesn't need to match anything in particular in the forecast
timestamp. But that logic doesn't currently exist.
So for testing, I copied/modified the CFSR dataset to give a timestamp
in
June:
> date -ud ''1970-06-01' UTC '00:00:00'' +%s
13046400
ncdump cfsr_freq_p6_world_mo_6.nc | sed
's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
"0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc cfsr_freq_p6_world_mo_6.ncdump
Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
time-step to be 24 hours:
climo_mean = {
//file_name = "/h/data/global/WXQC/data/climo/cfsr/
cfsr_freq_p6_world_mo_6.nc";
file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
field = [
{
name = "CFSR_APCP_T01_00";
level = "A6";
prob = TRUE;
cat_thresh = [ >= .01 ];
}
];
regrid = {
vld_thresh = 0.5;
method = NEAREST;
width = 1;
}
time_interp_method = DW_MEAN;
match_day = FALSE;
time_step = 24*60*60;
}
And I got a matching climo file:
DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
field(s) valid at 20180618_000000.
Seems like we should add some more useful DEBUG messages to the code
to
help determine why climo fields are not used.
Thanks,
John
On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Reading Climo File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
>
> John, I am having trouble getting MET to find the data of interest
in my
> climo file. The command line is:
>
> /h/WXQC/met-6.1/bin/point_stat
> /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f5
> /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c9681
> /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
-outdir
> /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v 4
>
> In the listing below, note that 0 climatology mean levels were
found. The
> Config file is attached.
>
>
> Reading data for APCP_06A6.
> DEBUG 3: Use the forecast grid.
> DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348 Ny:
636
> Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha: 6852.864
Cone:
> 0.716 Bx: 126.9979 By: 4353.7043
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.761
> DEBUG 4: lon_ll: -0
> DEBUG 4: delta_lat: 0.312212
> DEBUG 4: delta_lon: 0.3125
> DEBUG 4: Nlat: 576
> DEBUG 4: Nlon: 1152
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_NcMet".
> DEBUG 3: Found 0 climatology fields.
> DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
levels,
> and 0 climatology standard deviation levels.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
> DEBUG 2:
> DEBUG 2: Searching 1715 observations from 1715 messages.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> The files of interest are on AMERDEC. What am I doing wrong?
>
> Thanks
> Bob
>
>
>
------------------------------------------------
Subject: Reading Climo File
From: John Halley Gotway
Time: Mon Jun 25 16:12:04 2018
Bob,
OK, as a result of this, I added the following Debug(3) messages to
the
development version of MET when processing climo data:
Case 1: Months don't match
DEBUG 3: Skipping climatology field whose month (1) does not match the
month of the forecast valid time (6) from file:
cfsr_freq_p6_world_mo_6.nc
Case 2: Month and days don't match but match_day = TRUE
DEBUG 3: Skipping climatology field since "match_day" is TRUE but the
month
(6) and day (1) do not match the month (6) and day (18) of the
forecast
valid time from file: cfsr_freq_p6_world_mo_6_MOD.nc
Case 3: Time difference exceeds the time_step setting:
DEBUG 3: Skipping climatology field since time offset exceeds the
specified
"time_step" (43200 >= 21600) from file: cfsr_freq_p6_world_mo_6_MOD.nc
Hopefully these messages will point other users in the right direction
in
the future. Do they seem clear enough?
Thanks,
John
On Mon, Jun 25, 2018 at 3:44 PM The RT System itself via RT <
met_help at ucar.edu> wrote:
>
> Mon Jun 25 15:44:53 2018: Request 85662 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by RT_System
> Queue: met_help
> Subject: Reading Climo File
> Owner: johnhg
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
>
> This transaction appears to have no content
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo File
From: robert.craig.2 at us.af.mil
Time: Tue Jun 26 07:03:38 2018
Yes, those messages should be helpful.
thanks
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, June 25, 2018 5:12 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
File
Bob,
OK, as a result of this, I added the following Debug(3) messages to
the development version of MET when processing climo data:
Case 1: Months don't match
DEBUG 3: Skipping climatology field whose month (1) does not match the
month of the forecast valid time (6) from file:
cfsr_freq_p6_world_mo_6.nc
Case 2: Month and days don't match but match_day = TRUE DEBUG 3:
Skipping climatology field since "match_day" is TRUE but the month
(6) and day (1) do not match the month (6) and day (18) of the
forecast valid time from file: cfsr_freq_p6_world_mo_6_MOD.nc
Case 3: Time difference exceeds the time_step setting:
DEBUG 3: Skipping climatology field since time offset exceeds the
specified "time_step" (43200 >= 21600) from file:
cfsr_freq_p6_world_mo_6_MOD.nc
Hopefully these messages will point other users in the right direction
in the future. Do they seem clear enough?
Thanks,
John
On Mon, Jun 25, 2018 at 3:44 PM The RT System itself via RT <
met_help at ucar.edu> wrote:
>
> Mon Jun 25 15:44:53 2018: Request 85662 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by RT_System
> Queue: met_help
> Subject: Reading Climo File
> Owner: johnhg
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> >
>
>
> This transaction appears to have no content
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo File
From: robert.craig.2 at us.af.mil
Time: Tue Jun 26 07:04:41 2018
Okay, I will see if we can rebuild the climo files with the correct
valid time.
Thanks
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, June 25, 2018 4:45 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
File
Hi Bob,
I see you're having trouble getting climo data to be used in your run
of Point-Stat. Thanks for sending the sample data. That made it a
lot easier to debug.
We initially setup the climo logic to handle 2 cases:
(1) make the climo month match the month currently being evaluated
(2) make the climo month *and* day match the month and day currently
being evaluated
Your case falls into neither category and that's why you're not
getting a match. Here's the relevant timestamps:
ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
APCP_06:valid_time = "20180618_120000" ; ncdump -h
cfsr_freq_p6_world_mo_6.nc | grep valid_time
CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
Your forecast data is valid in June while the climo data is valid in
January. I suspect what you'd like to see is a 3rd option where the
climo timestamp doesn't need to match anything in particular in the
forecast timestamp. But that logic doesn't currently exist.
So for testing, I copied/modified the CFSR dataset to give a timestamp
in
June:
> date -ud ''1970-06-01' UTC '00:00:00'' +%s
13046400
ncdump cfsr_freq_p6_world_mo_6.nc | sed
's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
"0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc cfsr_freq_p6_world_mo_6.ncdump
Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
time-step to be 24 hours:
climo_mean = {
//file_name = "/h/data/global/WXQC/data/climo/cfsr/
cfsr_freq_p6_world_mo_6.nc";
file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
field = [
{
name = "CFSR_APCP_T01_00";
level = "A6";
prob = TRUE;
cat_thresh = [ >= .01 ];
}
];
regrid = {
vld_thresh = 0.5;
method = NEAREST;
width = 1;
}
time_interp_method = DW_MEAN;
match_day = FALSE;
time_step = 24*60*60;
}
And I got a matching climo file:
DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
field(s) valid at 20180618_000000.
Seems like we should add some more useful DEBUG messages to the code
to help determine why climo fields are not used.
Thanks,
John
On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Reading Climo File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> >
>
>
> John, I am having trouble getting MET to find the data of interest
in my
> climo file. The command line is:
>
> /h/WXQC/met-6.1/bin/point_stat
> /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f5
> /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c9681
> /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v 4
>
> In the listing below, note that 0 climatology mean levels were
found.
> The Config file is attached.
>
>
> Reading data for APCP_06A6.
> DEBUG 3: Use the forecast grid.
> DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348 Ny:
> 636
> Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha: 6852.864
Cone:
> 0.716 Bx: 126.9979 By: 4353.7043
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.761
> DEBUG 4: lon_ll: -0
> DEBUG 4: delta_lat: 0.312212
> DEBUG 4: delta_lon: 0.3125
> DEBUG 4: Nlat: 576
> DEBUG 4: Nlon: 1152
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> DEBUG 3: Found 0 climatology fields.
> DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> levels, and 0 climatology standard deviation levels.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
> DEBUG 2:
> DEBUG 2: Searching 1715 observations from 1715 messages.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> The files of interest are on AMERDEC. What am I doing wrong?
>
> Thanks
> Bob
>
>
>
------------------------------------------------
Subject: Reading Climo File
From: John Halley Gotway
Time: Tue Jun 26 09:45:23 2018
Sounds good. FYI, here are the ncdump/ncgen commands I used to do
that:
ncdump cfsr_freq_p6_world_mo_6.nc | sed
's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
"0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc cfsr_freq_p6_world_mo_6.ncdump
Alternatively, the "ncatted" NCO utility can be used to modify the
NetCDF
variable attributes. You could check to see if that's on your system.
Thanks,
John
On Tue, Jun 26, 2018 at 7:05 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
> Okay, I will see if we can rebuild the climo files with the correct
valid
> time.
>
> Thanks
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, June 25, 2018 4:45 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
File
>
> Hi Bob,
>
> I see you're having trouble getting climo data to be used in your
run of
> Point-Stat. Thanks for sending the sample data. That made it a lot
easier
> to debug.
>
> We initially setup the climo logic to handle 2 cases:
> (1) make the climo month match the month currently being evaluated
> (2) make the climo month *and* day match the month and day
currently
> being evaluated
>
> Your case falls into neither category and that's why you're not
getting a
> match. Here's the relevant timestamps:
>
> ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
> APCP_06:valid_time = "20180618_120000" ; ncdump -h
> cfsr_freq_p6_world_mo_6.nc | grep valid_time
> CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
>
> Your forecast data is valid in June while the climo data is valid in
> January. I suspect what you'd like to see is a 3rd option where the
climo
> timestamp doesn't need to match anything in particular in the
forecast
> timestamp. But that logic doesn't currently exist.
>
> So for testing, I copied/modified the CFSR dataset to give a
timestamp in
> June:
>
> > date -ud ''1970-06-01' UTC '00:00:00'' +%s
> 13046400
>
> ncdump cfsr_freq_p6_world_mo_6.nc | sed
> 's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
> "0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
>
> ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6.ncdump
>
> Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
> time-step to be 24 hours:
>
> climo_mean = {
>
> //file_name = "/h/data/global/WXQC/data/climo/cfsr/
> cfsr_freq_p6_world_mo_6.nc";
> file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
> field = [
> {
> name = "CFSR_APCP_T01_00";
> level = "A6";
> prob = TRUE;
> cat_thresh = [ >= .01 ];
> }
> ];
>
>
> regrid = {
> vld_thresh = 0.5;
> method = NEAREST;
> width = 1;
> }
>
> time_interp_method = DW_MEAN;
> match_day = FALSE;
> time_step = 24*60*60;
> }
>
> And I got a matching climo file:
> DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
> field(s) valid at 20180618_000000.
>
> Seems like we should add some more useful DEBUG messages to the code
to
> help determine why climo fields are not used.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
> On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Reading Climo File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> > >
> >
> >
> > John, I am having trouble getting MET to find the data of interest
in my
> > climo file. The command line is:
> >
> > /h/WXQC/met-6.1/bin/point_stat
> > /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f5
> > /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c9681
> > /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> > -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v
4
> >
> > In the listing below, note that 0 climatology mean levels were
found.
> > The Config file is attached.
> >
> >
> > Reading data for APCP_06A6.
> > DEBUG 3: Use the forecast grid.
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348
Ny:
> > 636
> > Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha:
6852.864
> Cone:
> > 0.716 Bx: 126.9979 By: 4353.7043
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.761
> > DEBUG 4: lon_ll: -0
> > DEBUG 4: delta_lat: 0.312212
> > DEBUG 4: delta_lon: 0.3125
> > DEBUG 4: Nlat: 576
> > DEBUG 4: Nlon: 1152
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > DEBUG 3: Found 0 climatology fields.
> > DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> > DEBUG 2:
> > DEBUG 2: Searching 1715 observations from 1715 messages.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > The files of interest are on AMERDEC. What am I doing wrong?
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo File
From: robert.craig.2 at us.af.mil
Time: Tue Jun 26 09:52:07 2018
I tried the commands you used and that worked here.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, June 26, 2018 10:45 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading
Climo File
Sounds good. FYI, here are the ncdump/ncgen commands I used to do
that:
ncdump cfsr_freq_p6_world_mo_6.nc | sed
's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
"0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc cfsr_freq_p6_world_mo_6.ncdump
Alternatively, the "ncatted" NCO utility can be used to modify the
NetCDF variable attributes. You could check to see if that's on your
system.
Thanks,
John
On Tue, Jun 26, 2018 at 7:05 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
> Okay, I will see if we can rebuild the climo files with the correct
> valid time.
>
> Thanks
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, June 25, 2018 4:45 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
> File
>
> Hi Bob,
>
> I see you're having trouble getting climo data to be used in your
run
> of Point-Stat. Thanks for sending the sample data. That made it a
> lot easier to debug.
>
> We initially setup the climo logic to handle 2 cases:
> (1) make the climo month match the month currently being evaluated
> (2) make the climo month *and* day match the month and day
currently
> being evaluated
>
> Your case falls into neither category and that's why you're not
> getting a match. Here's the relevant timestamps:
>
> ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
> APCP_06:valid_time = "20180618_120000" ; ncdump -h
> cfsr_freq_p6_world_mo_6.nc | grep valid_time
> CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
>
> Your forecast data is valid in June while the climo data is valid in
> January. I suspect what you'd like to see is a 3rd option where the
> climo timestamp doesn't need to match anything in particular in the
> forecast timestamp. But that logic doesn't currently exist.
>
> So for testing, I copied/modified the CFSR dataset to give a
timestamp
> in
> June:
>
> > date -ud ''1970-06-01' UTC '00:00:00'' +%s
> 13046400
>
> ncdump cfsr_freq_p6_world_mo_6.nc | sed
> 's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
> "0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
>
> ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6.ncdump
>
> Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
> time-step to be 24 hours:
>
> climo_mean = {
>
> //file_name = "/h/data/global/WXQC/data/climo/cfsr/
> cfsr_freq_p6_world_mo_6.nc";
> file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
> field = [
> {
> name = "CFSR_APCP_T01_00";
> level = "A6";
> prob = TRUE;
> cat_thresh = [ >= .01 ];
> }
> ];
>
>
> regrid = {
> vld_thresh = 0.5;
> method = NEAREST;
> width = 1;
> }
>
> time_interp_method = DW_MEAN;
> match_day = FALSE;
> time_step = 24*60*60;
> }
>
> And I got a matching climo file:
> DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
> field(s) valid at 20180618_000000.
>
> Seems like we should add some more useful DEBUG messages to the code
> to help determine why climo fields are not used.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
> On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Reading Climo File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> > >
> >
> >
> > John, I am having trouble getting MET to find the data of interest
in my
> > climo file. The command line is:
> >
> > /h/WXQC/met-6.1/bin/point_stat
> > /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f
> > 5
> > /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c968
> > 1 /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> > -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v
4
> >
> > In the listing below, note that 0 climatology mean levels were
found.
> > The Config file is attached.
> >
> >
> > Reading data for APCP_06A6.
> > DEBUG 3: Use the forecast grid.
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348
Ny:
> > 636
> > Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha:
6852.864
> Cone:
> > 0.716 Bx: 126.9979 By: 4353.7043
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.761
> > DEBUG 4: lon_ll: -0
> > DEBUG 4: delta_lat: 0.312212
> > DEBUG 4: delta_lon: 0.3125
> > DEBUG 4: Nlat: 576
> > DEBUG 4: Nlon: 1152
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > DEBUG 3: Found 0 climatology fields.
> > DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> > DEBUG 2:
> > DEBUG 2: Searching 1715 observations from 1715 messages.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > The files of interest are on AMERDEC. What am I doing wrong?
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo File
From: robert.craig.2 at us.af.mil
Time: Wed Jun 27 07:18:09 2018
John, I discovered a problem with the guidance below late yesterday.
I did what you said and MET found a climo field. However, when I
display the new NetCDF file, it seems to be corrupted. Did your file
display correctly in plot_data_plane? I looked at the options for
ncgen and tried setting the -k value from 1 to 4 for the different
NetCDF format types. All came up looking bad.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, June 25, 2018 4:45 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
File
Hi Bob,
I see you're having trouble getting climo data to be used in your run
of Point-Stat. Thanks for sending the sample data. That made it a
lot easier to debug.
We initially setup the climo logic to handle 2 cases:
(1) make the climo month match the month currently being evaluated
(2) make the climo month *and* day match the month and day currently
being evaluated
Your case falls into neither category and that's why you're not
getting a match. Here's the relevant timestamps:
ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
APCP_06:valid_time = "20180618_120000" ; ncdump -h
cfsr_freq_p6_world_mo_6.nc | grep valid_time
CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
Your forecast data is valid in June while the climo data is valid in
January. I suspect what you'd like to see is a 3rd option where the
climo timestamp doesn't need to match anything in particular in the
forecast timestamp. But that logic doesn't currently exist.
So for testing, I copied/modified the CFSR dataset to give a timestamp
in
June:
> date -ud ''1970-06-01' UTC '00:00:00'' +%s
13046400
ncdump cfsr_freq_p6_world_mo_6.nc | sed
's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
"0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc cfsr_freq_p6_world_mo_6.ncdump
Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
time-step to be 24 hours:
climo_mean = {
//file_name = "/h/data/global/WXQC/data/climo/cfsr/
cfsr_freq_p6_world_mo_6.nc";
file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
field = [
{
name = "CFSR_APCP_T01_00";
level = "A6";
prob = TRUE;
cat_thresh = [ >= .01 ];
}
];
regrid = {
vld_thresh = 0.5;
method = NEAREST;
width = 1;
}
time_interp_method = DW_MEAN;
match_day = FALSE;
time_step = 24*60*60;
}
And I got a matching climo file:
DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
field(s) valid at 20180618_000000.
Seems like we should add some more useful DEBUG messages to the code
to help determine why climo fields are not used.
Thanks,
John
On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Reading Climo File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> >
>
>
> John, I am having trouble getting MET to find the data of interest
in my
> climo file. The command line is:
>
> /h/WXQC/met-6.1/bin/point_stat
> /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f5
> /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c9681
> /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v 4
>
> In the listing below, note that 0 climatology mean levels were
found.
> The Config file is attached.
>
>
> Reading data for APCP_06A6.
> DEBUG 3: Use the forecast grid.
> DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348 Ny:
> 636
> Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha: 6852.864
Cone:
> 0.716 Bx: 126.9979 By: 4353.7043
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.761
> DEBUG 4: lon_ll: -0
> DEBUG 4: delta_lat: 0.312212
> DEBUG 4: delta_lon: 0.3125
> DEBUG 4: Nlat: 576
> DEBUG 4: Nlon: 1152
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> DEBUG 3: Found 0 climatology fields.
> DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> levels, and 0 climatology standard deviation levels.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
> DEBUG 2:
> DEBUG 2: Searching 1715 observations from 1715 messages.
> DEBUG 2:
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> The files of interest are on AMERDEC. What am I doing wrong?
>
> Thanks
> Bob
>
>
>
------------------------------------------------
Subject: Reading Climo File
From: John Halley Gotway
Time: Wed Jun 27 09:38:47 2018
Bob,
I'm not seeing that corruption. Here's the commands I ran:
plot_data_plane cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6_MOD.ps 'name="CFSR_APCP_T01_00";
level="(*,*)';'
convert -rotate 90 -background white -flatten
cfsr_freq_p6_world_mo_6_MOD.ps cfsr_freq_p6_world_mo_6_MOD.png
And I've attached that resulting png showing the 1-hour precip. Looks
fine
to me.
It could be that you're using inconsistent versions of ncdump and
ncgen...
but I really don't know. If you have ncatted available, that's
another way
of modifying NetCDF variable attributes.
Thanks,
John
On Wed, Jun 27, 2018 at 7:18 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
> John, I discovered a problem with the guidance below late yesterday.
I
> did what you said and MET found a climo field. However, when I
display the
> new NetCDF file, it seems to be corrupted. Did your file display
correctly
> in plot_data_plane? I looked at the options for ncgen and tried
setting
> the -k value from 1 to 4 for the different NetCDF format types. All
came
> up looking bad.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, June 25, 2018 4:45 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
File
>
> Hi Bob,
>
> I see you're having trouble getting climo data to be used in your
run of
> Point-Stat. Thanks for sending the sample data. That made it a lot
easier
> to debug.
>
> We initially setup the climo logic to handle 2 cases:
> (1) make the climo month match the month currently being evaluated
> (2) make the climo month *and* day match the month and day
currently
> being evaluated
>
> Your case falls into neither category and that's why you're not
getting a
> match. Here's the relevant timestamps:
>
> ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
> APCP_06:valid_time = "20180618_120000" ; ncdump -h
> cfsr_freq_p6_world_mo_6.nc | grep valid_time
> CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
>
> Your forecast data is valid in June while the climo data is valid in
> January. I suspect what you'd like to see is a 3rd option where the
climo
> timestamp doesn't need to match anything in particular in the
forecast
> timestamp. But that logic doesn't currently exist.
>
> So for testing, I copied/modified the CFSR dataset to give a
timestamp in
> June:
>
> > date -ud ''1970-06-01' UTC '00:00:00'' +%s
> 13046400
>
> ncdump cfsr_freq_p6_world_mo_6.nc | sed
> 's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
> "0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
>
> ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6.ncdump
>
> Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
> time-step to be 24 hours:
>
> climo_mean = {
>
> //file_name = "/h/data/global/WXQC/data/climo/cfsr/
> cfsr_freq_p6_world_mo_6.nc";
> file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
> field = [
> {
> name = "CFSR_APCP_T01_00";
> level = "A6";
> prob = TRUE;
> cat_thresh = [ >= .01 ];
> }
> ];
>
>
> regrid = {
> vld_thresh = 0.5;
> method = NEAREST;
> width = 1;
> }
>
> time_interp_method = DW_MEAN;
> match_day = FALSE;
> time_step = 24*60*60;
> }
>
> And I got a matching climo file:
> DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
> field(s) valid at 20180618_000000.
>
> Seems like we should add some more useful DEBUG messages to the code
to
> help determine why climo fields are not used.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
> On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Reading Climo File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> > >
> >
> >
> > John, I am having trouble getting MET to find the data of interest
in my
> > climo file. The command line is:
> >
> > /h/WXQC/met-6.1/bin/point_stat
> > /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f5
> > /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c9681
> > /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> > -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v
4
> >
> > In the listing below, note that 0 climatology mean levels were
found.
> > The Config file is attached.
> >
> >
> > Reading data for APCP_06A6.
> > DEBUG 3: Use the forecast grid.
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348
Ny:
> > 636
> > Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha:
6852.864
> Cone:
> > 0.716 Bx: 126.9979 By: 4353.7043
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.761
> > DEBUG 4: lon_ll: -0
> > DEBUG 4: delta_lat: 0.312212
> > DEBUG 4: delta_lon: 0.3125
> > DEBUG 4: Nlat: 576
> > DEBUG 4: Nlon: 1152
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > DEBUG 3: Found 0 climatology fields.
> > DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> > DEBUG 2:
> > DEBUG 2: Searching 1715 observations from 1715 messages.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > The files of interest are on AMERDEC. What am I doing wrong?
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo File
From: robert.craig.2 at us.af.mil
Time: Wed Jun 27 14:11:38 2018
Weird, when we do it the part of the northern hemisphere gets merged
with the southern hemisphere and the rest of the northern hemisphere
gets get to a missing value.
Chris Melick will rebuild the files using the proper header settings
so we won't have to use ncgen to fix them.
Thanks for checking into it.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, June 27, 2018 10:39 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading
Climo File
Bob,
I'm not seeing that corruption. Here's the commands I ran:
plot_data_plane cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6_MOD.ps 'name="CFSR_APCP_T01_00";
level="(*,*)';'
convert -rotate 90 -background white -flatten
cfsr_freq_p6_world_mo_6_MOD.ps cfsr_freq_p6_world_mo_6_MOD.png
And I've attached that resulting png showing the 1-hour precip. Looks
fine to me.
It could be that you're using inconsistent versions of ncdump and
ncgen...
but I really don't know. If you have ncatted available, that's
another way of modifying NetCDF variable attributes.
Thanks,
John
On Wed, Jun 27, 2018 at 7:18 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662 >
>
> John, I discovered a problem with the guidance below late yesterday.
I
> did what you said and MET found a climo field. However, when I
> display the new NetCDF file, it seems to be corrupted. Did your
file
> display correctly in plot_data_plane? I looked at the options for
> ncgen and tried setting the -k value from 1 to 4 for the different
> NetCDF format types. All came up looking bad.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, June 25, 2018 4:45 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85662] Reading Climo
> File
>
> Hi Bob,
>
> I see you're having trouble getting climo data to be used in your
run
> of Point-Stat. Thanks for sending the sample data. That made it a
> lot easier to debug.
>
> We initially setup the climo logic to handle 2 cases:
> (1) make the climo month match the month currently being evaluated
> (2) make the climo month *and* day match the month and day
currently
> being evaluated
>
> Your case falls into neither category and that's why you're not
> getting a match. Here's the relevant timestamps:
>
> ncdump -h 53a8fcf9-57db-4b93-9c55-843bd8cb53f5 | grep valid_time
> APCP_06:valid_time = "20180618_120000" ; ncdump -h
> cfsr_freq_p6_world_mo_6.nc | grep valid_time
> CFSR_APCP_T01_00:valid_time = "19700101_000000" ;
>
> Your forecast data is valid in June while the climo data is valid in
> January. I suspect what you'd like to see is a 3rd option where the
> climo timestamp doesn't need to match anything in particular in the
> forecast timestamp. But that logic doesn't currently exist.
>
> So for testing, I copied/modified the CFSR dataset to give a
timestamp
> in
> June:
>
> > date -ud ''1970-06-01' UTC '00:00:00'' +%s
> 13046400
>
> ncdump cfsr_freq_p6_world_mo_6.nc | sed
> 's/"19700101_000000"/"19700601_000000"/g' | sed 's/valid_time_ut =
> "0"/valid_time_ut = "13046400"/g' > cfsr_freq_p6_world_mo_6.ncdump
>
> ncgen -o cfsr_freq_p6_world_mo_6_MOD.nc
cfsr_freq_p6_world_mo_6.ncdump
>
> Then I reran using cfsr_freq_p6_world_mo_6_MOD.nc and increased the
> time-step to be 24 hours:
>
> climo_mean = {
>
> //file_name = "/h/data/global/WXQC/data/climo/cfsr/
> cfsr_freq_p6_world_mo_6.nc";
> file_name = "cfsr_freq_p6_world_mo_6_MOD.nc";
> field = [
> {
> name = "CFSR_APCP_T01_00";
> level = "A6";
> prob = TRUE;
> cat_thresh = [ >= .01 ];
> }
> ];
>
>
> regrid = {
> vld_thresh = 0.5;
> method = NEAREST;
> width = 1;
> }
>
> time_interp_method = DW_MEAN;
> match_day = FALSE;
> time_step = 24*60*60;
> }
>
> And I got a matching climo file:
> DEBUG 3: For forecast valid at 20180618_120000, found 1 climatology
> field(s) valid at 20180618_000000.
>
> Seems like we should add some more useful DEBUG messages to the code
> to help determine why climo fields are not used.
>
> Thanks,
> John
>
>
>
>
>
>
>
>
> On Fri, Jun 22, 2018 at 3:31 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 22 15:30:47 2018: Request 85662 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Reading Climo File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85662
> > >
> >
> >
> > John, I am having trouble getting MET to find the data of interest
in my
> > climo file. The command line is:
> >
> > /h/WXQC/met-6.1/bin/point_stat
> > /h/data/global/WXQC/data/met/tmp/53a8fcf9-57db-4b93-9c55-
843bd8cb53f
> > 5
> > /h/data/global/WXQC/data/met/tmp/874fbb67-a2cf-4b69-a4e0-
fbc04e9c968
> > 1 /h/WXQC/met-6.1/data/config/PointStatConfig_precip_hira_updated
> > -outdir /h/data/global/WXQC/data/met/ptstat/mdlob_pairs/wrf/TP -v
4
> >
> > In the listing below, note that 0 climatology mean levels were
found.
> > The Config file is attached.
> >
> >
> > Reading data for APCP_06A6.
> > DEBUG 3: Use the forecast grid.
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 348
Ny:
> > 636
> > Lat_LL: 34.081 Lon_LL: -124.665 Lon_orient: -127.000 Alpha:
6852.864
> Cone:
> > 0.716 Bx: 126.9979 By: 4353.7043
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.761
> > DEBUG 4: lon_ll: -0
> > DEBUG 4: delta_lat: 0.312212
> > DEBUG 4: delta_lon: 0.3125
> > DEBUG 4: Nlat: 576
> > DEBUG 4: Nlon: 1152
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > DEBUG 3: Found 0 climatology fields.
> > DEBUG 2: For APCP_06A6 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> > DEBUG 2:
> > DEBUG 2: Searching 1715 observations from 1715 messages.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > The files of interest are on AMERDEC. What am I doing wrong?
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list