[Met_help] [rt.rap.ucar.edu #92975] History for Point_stat grid data use NETCDF_NCCF format
Julie Prestopnik via RT
met_help at ucar.edu
Fri Nov 8 09:20:51 MST 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MET help:
I have a question on the point_stat tool. I have grid data of LAPS
output(NETCDF format),
and point data of Prepbufr.
Grid data are following (lon: 73:135, lat:8:63):
netcdf SFC_201910280000 {
dimensions:
time = UNLIMITED ; // (1 currently)
latitude = 1801 ;
longitude = 2067 ;
variables:
float ts(time, latitude, longitude) ;
ts:_FillValue = 1.e+20f ;
ts:long_name = "Temperature" ;
ts:units = "K" ;
ts:standard_name = "air_temperature" ;
ts:grid_type = "Latitude/longitude" ;
ts:grid_mapping_name = "latitude_longitude" ;
ts:level_type = "Specified height level above ground (m)" ;
ts:level = 2LL ;
double time(time) ;
time:_FillValue = 1.e+20 ;
time:units = "hours since 2019-10-28 00:00:00" ;
time:timezone = "UTC" ;
float latitude(latitude) ;
latitude:_FillValue = 1.e+20f ;
latitude:units = "degree_north" ;
latitude:standard_name = "latitude" ;
double longitude(longitude) ;
longitude:_FillValue = 1.e+20 ;
longitude:units = "degree_east" ;
longitude:standard_name = "longitude" ;
int64 forecast_reference_time(time) ;
forecast_reference_time:units = "hours since 2019-10-28
00:00:00" ;
forecast_reference_time:timezone = "UTC" ;
// global attributes:
:Conventions = "CF-1.X" ;
}
And a part of configure file are following:
fcst = {
file_type = NETCDF_NCCF;
wind_thresh = [ NA ];
message_type = [ "ADPSFC" ];
field = [
{ name = "ts"; level = [ "(0,*,*)" ]; }
];
};
obs = {
message_type = [ "ADPSFC" ];
field = [
{ name = "TMP"; level = [ "Z2" ]; }
];
};
But, the result of point-stat is empty, a part log are following:
DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) -> Found 1 times
from between 20191028_000000 and 20191028_000000
DEBUG 4:
DEBUG 4: Data plane information:
DEBUG 4: plane min: 247.8701172
DEBUG 4: plane max: 304.5449219
DEBUG 4: valid time: 20191028_000000
DEBUG 4: lead time: 000000
DEBUG 4: init time: 20191028_000000
DEBUG 4: accum time: 000000
DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &, DataPlaneArray &) ->
time: 20191028_000000 from index 0
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for ts(0,*,*).
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny: 1801 lat_ll:
8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
DEBUG 2: Processing masking regions.
DEBUG 3: Processing grid mask: FULL
DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
DEBUG 3: Processing station ID mask: (nul)
DEBUG 2: Processing geography data.
DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0 climatology mean levels,
and 0 climatology standard deviation levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Searching 690796 observations from 415033 messages.
DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1] 41,-9999
inst_typ[0,-1] -9999,-9999
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 4: set FCST_UNITS:K
DEBUG 4: set OBS_UNITS:NA
DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type ADPSFC,
over region FULL, for interpolation method BILIN(4), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 690796
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 450597
DEBUG 3: Rejected: valid time = 240199
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: topography = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type ADPSFC,
over region NA, for interpolation method BILIN(4), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 690796
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 450597
DEBUG 3: Rejected: valid time = 240199
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: topography = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 1: Output file: ./point_stat_ADPSFC_000000L_20191028_000000V.stat
DEBUG 1: Output file: ./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
DEBUG 1: Output file: ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
DEBUG 1: Output file: ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
So, I want to know what is the reason, Can provide sample grid data of
NETCDF_NCCF format？
Best regards！
Renzhi Wang
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Point_stat grid data use NETCDF_NCCF format
From: Julie Prestopnik
Time: Tue Nov 05 23:17:46 2019
Hi Renzhi.
I see that you are having some trouble with using some LAPS data in
MET. I
found a previous met_help ticket where a colleague of mine wrote a
script
to convert some LAPS data to a format that MET can read.
He reformatted a sample LAPS file was sent to us using an R script
that
loads the RNetCDF package. It demonstrates the necessary changes to
make
thisfile look like the NetCDF output of the MET tools.
Running without arguments give the usage info:
> Rscript laps2metnc.R
Usage: laps2metnc.R file_list
where "file_list" is one or more LAPS files to be reformatted.
You should pass in one or more files to be reformatted. In the
example
below, the filename was 131401800.lmr. Unfortunately, I do not have
that
file, but I will use the filename in the example below so that you can
see
how to use it.
> Rscript laps2metnc.R 131401800.lmr
Processing 1 files...
Reading: 131401800.lmr
Writing: 131401800.lmr_met.nc
Adding timing info to variable named r
Output file names = Input "_met.nc".
And here's a command using the MET plot_data_plane tool to plot the
result:
plot_data_plane 131401800.lmr_met.nc 131401800.lmr_met.ps 'name="r";
level="(0,0,*,*)";'
I have attached the script for you. Please give it a try and let us
know
how it goes.
Thanks,
Julie
On Tue, Nov 5, 2019 at 10:55 PM wang Dawn via RT <met_help at ucar.edu>
wrote:
>
> Tue Nov 05 22:54:47 2019: Request 92975 was acted upon.
> Transaction: Ticket created by wangrzqi at gmail.com
> Queue: met_help
> Subject: Point_stat grid data use NETCDF_NCCF format
> Owner: Nobody
> Requestors: wangrzqi at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
>
>
> Dear MET help:
>
> I have a question on the point_stat tool. I have grid data of
LAPS
> output(NETCDF format),
> and point data of Prepbufr.
>
> Grid data are following (lon: 73:135, lat:8:63):
>
> netcdf SFC_201910280000 {
> dimensions:
> time = UNLIMITED ; // (1 currently)
> latitude = 1801 ;
> longitude = 2067 ;
> variables:
> float ts(time, latitude, longitude) ;
> ts:_FillValue = 1.e+20f ;
> ts:long_name = "Temperature" ;
> ts:units = "K" ;
> ts:standard_name = "air_temperature" ;
> ts:grid_type = "Latitude/longitude" ;
> ts:grid_mapping_name = "latitude_longitude" ;
> ts:level_type = "Specified height level above ground
(m)" ;
> ts:level = 2LL ;
> double time(time) ;
> time:_FillValue = 1.e+20 ;
> time:units = "hours since 2019-10-28 00:00:00" ;
> time:timezone = "UTC" ;
> float latitude(latitude) ;
> latitude:_FillValue = 1.e+20f ;
> latitude:units = "degree_north" ;
> latitude:standard_name = "latitude" ;
> double longitude(longitude) ;
> longitude:_FillValue = 1.e+20 ;
> longitude:units = "degree_east" ;
> longitude:standard_name = "longitude" ;
> int64 forecast_reference_time(time) ;
> forecast_reference_time:units = "hours since 2019-
10-28
> 00:00:00" ;
> forecast_reference_time:timezone = "UTC" ;
>
> // global attributes:
> :Conventions = "CF-1.X" ;
> }
>
> And a part of configure file are following:
> fcst = {
> file_type = NETCDF_NCCF;
> wind_thresh = [ NA ];
> message_type = [ "ADPSFC" ];
>
> field = [
> { name = "ts"; level = [ "(0,*,*)" ]; }
> ];
> };
>
>
> obs = {
> message_type = [ "ADPSFC" ];
>
> field = [
> { name = "TMP"; level = [ "Z2" ]; }
> ];
> };
>
> But, the result of point-stat is empty, a part log are following:
>
> DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) -> Found
1 times
> from between 20191028_000000 and 20191028_000000
> DEBUG 4:
> DEBUG 4: Data plane information:
> DEBUG 4: plane min: 247.8701172
> DEBUG 4: plane max: 304.5449219
> DEBUG 4: valid time: 20191028_000000
> DEBUG 4: lead time: 000000
> DEBUG 4: init time: 20191028_000000
> DEBUG 4: accum time: 000000
> DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &, DataPlaneArray
&) ->
> time: 20191028_000000 from index 0
> DEBUG 2:
> DEBUG 2:
>
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Reading data for ts(0,*,*).
> DEBUG 3: Use the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny: 1801
lat_ll:
> 8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> DEBUG 3: Processing station ID mask: (nul)
> DEBUG 2: Processing geography data.
> DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0 climatology mean
levels,
> and 0 climatology standard deviation levels.
> DEBUG 2:
> DEBUG 2:
>
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Searching 690796 observations from 415033 messages.
> DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1] 41,-9999
> inst_typ[0,-1] -9999,-9999
> DEBUG 2:
> DEBUG 2:
>
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 4: set FCST_UNITS:K
> DEBUG 4: set OBS_UNITS:NA
> DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method BILIN(4), using 0 pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 690796
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: obs type = 450597
> DEBUG 3: Rejected: valid time = 240199
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: topography = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region NA, for interpolation method BILIN(4), using 0 pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 690796
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: obs type = 450597
> DEBUG 3: Rejected: valid time = 240199
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: topography = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
> DEBUG 2:
>
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 1: Output file:
./point_stat_ADPSFC_000000L_20191028_000000V.stat
> DEBUG 1: Output file:
./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
> DEBUG 1: Output file:
> ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
> DEBUG 1: Output file:
> ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
>
> So, I want to know what is the reason, Can provide sample grid data
of
> NETCDF_NCCF format？
>
> Best regards！
> Renzhi Wang
>
>
--
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: Point_stat grid data use NETCDF_NCCF format
From: wang Dawn
Time: Wed Nov 06 08:29:46 2019
Thank you Julie. I will try again. My netcdf projection is Lat/Lon,
not
Lambert Conformal. I don't know which attributes to add.
Best regards.
Julie Prestopnik via RT <met_help at ucar.edu> 于 2019年11月6日周三 14:17写道：
> Hi Renzhi.
>
> I see that you are having some trouble with using some LAPS data in
MET. I
> found a previous met_help ticket where a colleague of mine wrote a
script
> to convert some LAPS data to a format that MET can read.
>
> He reformatted a sample LAPS file was sent to us using an R script
that
> loads the RNetCDF package. It demonstrates the necessary changes to
make
> thisfile look like the NetCDF output of the MET tools.
>
> Running without arguments give the usage info:
>
> > Rscript laps2metnc.R
>
> Usage: laps2metnc.R file_list
> where "file_list" is one or more LAPS files to be
reformatted.
>
> You should pass in one or more files to be reformatted. In the
example
> below, the filename was 131401800.lmr. Unfortunately, I do not have
that
> file, but I will use the filename in the example below so that you
can see
> how to use it.
>
> > Rscript laps2metnc.R 131401800.lmr
> Processing 1 files...
> Reading: 131401800.lmr
> Writing: 131401800.lmr_met.nc
> Adding timing info to variable named r
>
> Output file names = Input "_met.nc".
>
> And here's a command using the MET plot_data_plane tool to plot the
result:
>
> plot_data_plane 131401800.lmr_met.nc 131401800.lmr_met.ps 'name="r";
> level="(0,0,*,*)";'
>
> I have attached the script for you. Please give it a try and let us
know
> how it goes.
>
> Thanks,
> Julie
>
> On Tue, Nov 5, 2019 at 10:55 PM wang Dawn via RT <met_help at ucar.edu>
> wrote:
>
> >
> > Tue Nov 05 22:54:47 2019: Request 92975 was acted upon.
> > Transaction: Ticket created by wangrzqi at gmail.com
> > Queue: met_help
> > Subject: Point_stat grid data use NETCDF_NCCF format
> > Owner: Nobody
> > Requestors: wangrzqi at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
> >
> >
> > Dear MET help:
> >
> > I have a question on the point_stat tool. I have grid data of
LAPS
> > output(NETCDF format),
> > and point data of Prepbufr.
> >
> > Grid data are following (lon: 73:135, lat:8:63):
> >
> > netcdf SFC_201910280000 {
> > dimensions:
> > time = UNLIMITED ; // (1 currently)
> > latitude = 1801 ;
> > longitude = 2067 ;
> > variables:
> > float ts(time, latitude, longitude) ;
> > ts:_FillValue = 1.e+20f ;
> > ts:long_name = "Temperature" ;
> > ts:units = "K" ;
> > ts:standard_name = "air_temperature" ;
> > ts:grid_type = "Latitude/longitude" ;
> > ts:grid_mapping_name = "latitude_longitude" ;
> > ts:level_type = "Specified height level above
ground
> (m)" ;
> > ts:level = 2LL ;
> > double time(time) ;
> > time:_FillValue = 1.e+20 ;
> > time:units = "hours since 2019-10-28 00:00:00" ;
> > time:timezone = "UTC" ;
> > float latitude(latitude) ;
> > latitude:_FillValue = 1.e+20f ;
> > latitude:units = "degree_north" ;
> > latitude:standard_name = "latitude" ;
> > double longitude(longitude) ;
> > longitude:_FillValue = 1.e+20 ;
> > longitude:units = "degree_east" ;
> > longitude:standard_name = "longitude" ;
> > int64 forecast_reference_time(time) ;
> > forecast_reference_time:units = "hours since 2019-
10-28
> > 00:00:00" ;
> > forecast_reference_time:timezone = "UTC" ;
> >
> > // global attributes:
> > :Conventions = "CF-1.X" ;
> > }
> >
> > And a part of configure file are following:
> > fcst = {
> > file_type = NETCDF_NCCF;
> > wind_thresh = [ NA ];
> > message_type = [ "ADPSFC" ];
> >
> > field = [
> > { name = "ts"; level = [ "(0,*,*)" ]; }
> > ];
> > };
> >
> >
> > obs = {
> > message_type = [ "ADPSFC" ];
> >
> > field = [
> > { name = "TMP"; level = [ "Z2" ]; }
> > ];
> > };
> >
> > But, the result of point-stat is empty, a part log are following:
> >
> > DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) ->
Found 1
> times
> > from between 20191028_000000 and 20191028_000000
> > DEBUG 4:
> > DEBUG 4: Data plane information:
> > DEBUG 4: plane min: 247.8701172
> > DEBUG 4: plane max: 304.5449219
> > DEBUG 4: valid time: 20191028_000000
> > DEBUG 4: lead time: 000000
> > DEBUG 4: init time: 20191028_000000
> > DEBUG 4: accum time: 000000
> > DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &,
DataPlaneArray &)
> ->
> > time: 20191028_000000 from index 0
> > DEBUG 2:
> > DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Reading data for ts(0,*,*).
> > DEBUG 3: Use the matching forecast and observation grids.
> > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny: 1801
lat_ll:
> > 8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > DEBUG 3: Processing station ID mask: (nul)
> > DEBUG 2: Processing geography data.
> > DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0 climatology mean
> levels,
> > and 0 climatology standard deviation levels.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Searching 690796 observations from 415033 messages.
> > DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1] 41,-9999
> > inst_typ[0,-1] -9999,-9999
> > DEBUG 2:
> > DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 4: set FCST_UNITS:K
> > DEBUG 4: set OBS_UNITS:NA
> > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type
ADPSFC,
> > over region FULL, for interpolation method BILIN(4), using 0
pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 690796
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: obs type = 450597
> > DEBUG 3: Rejected: valid time = 240199
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: topography = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 0
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation type
ADPSFC,
> > over region NA, for interpolation method BILIN(4), using 0 pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 690796
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: obs type = 450597
> > DEBUG 3: Rejected: valid time = 240199
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: topography = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 0
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> > DEBUG 2:
> > DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 1: Output file:
./point_stat_ADPSFC_000000L_20191028_000000V.stat
> > DEBUG 1: Output file:
> ./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
> > DEBUG 1: Output file:
> > ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
> > DEBUG 1: Output file:
> > ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
> >
> > So, I want to know what is the reason, Can provide sample grid
data of
> > NETCDF_NCCF format？
> >
> > Best regards！
> > Renzhi Wang
> >
> >
>
> --
> 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: Point_stat grid data use NETCDF_NCCF format
From: John Halley Gotway
Time: Wed Nov 06 11:10:55 2019
Julie,
It looks like the file formats are fine here. They are using CF-
compliant NetCDF as input. The problem is that they're getting 0
matched pairs. Looking at the log messages they sent, it's because of
a valid time mismatch:
DEBUG 3: Observations processed = 690796
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 450597
DEBUG 3: Rejected: valid time = 240199
In these cases, I usually instruct the user to open up the matching
time window very wide to see if we can get some matches. In the
Point-Stat config file, make the obs_window very large:
obs_window = {
beg = -5400000;
end = 5400000;
}
They may still get 0 matched pairs, but the reason counts will surely
change. And they continue debugging. Once they do get matched pairs,
they should circle back around to figure out why the forecast valid
times don't match up well with the timestamps of the observations.
FYI, this is a "Comment (Not sent to requestors)". So you'd need to
reword it however you'd like in your response.
Thanks<
John
------------------------------------------------
Subject: Point_stat grid data use NETCDF_NCCF format
From: Julie Prestopnik
Time: Wed Nov 06 14:45:56 2019
Hi. Actually, it looks like the file formats are fine here and that
you
are using CF-compliant NetCDF as input. I see the problem is that you
are
getting 0 matched pairs. Looking at the log messages you sent, it is
because of a valid time mismatch:
DEBUG 3: Observations processed = 690796
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 450597
DEBUG 3: Rejected: valid time = 240199
In this case, it would be good if you could open up the matching time
window very wide to see if we can get some matches. In the Point-Stat
config file, make the obs_window very large:
obs_window = {
beg = -5400000;
end = 5400000;
}
You may still get 0 matched pairs, but the reason counts will surely
change, and you can continue debugging. Once you do get matched
pairs, you
can circle back around to figure out why the forecast valid times
don't
match up well with the timestamps of the observations.
I hope that helps. Please follow up with any further questions you
have.
Julie
On Wed, Nov 6, 2019 at 8:29 AM wang Dawn via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
>
> Thank you Julie. I will try again. My netcdf projection is Lat/Lon,
not
> Lambert Conformal. I don't know which attributes to add.
>
> Best regards.
>
> Julie Prestopnik via RT <met_help at ucar.edu> 于 2019年11月6日周三 14:17写道：
>
> > Hi Renzhi.
> >
> > I see that you are having some trouble with using some LAPS data
in
> MET. I
> > found a previous met_help ticket where a colleague of mine wrote a
script
> > to convert some LAPS data to a format that MET can read.
> >
> > He reformatted a sample LAPS file was sent to us using an R script
that
> > loads the RNetCDF package. It demonstrates the necessary changes
to make
> > thisfile look like the NetCDF output of the MET tools.
> >
> > Running without arguments give the usage info:
> >
> > > Rscript laps2metnc.R
> >
> > Usage: laps2metnc.R file_list
> > where "file_list" is one or more LAPS files to be
reformatted.
> >
> > You should pass in one or more files to be reformatted. In the
example
> > below, the filename was 131401800.lmr. Unfortunately, I do not
have that
> > file, but I will use the filename in the example below so that you
can
> see
> > how to use it.
> >
> > > Rscript laps2metnc.R 131401800.lmr
> > Processing 1 files...
> > Reading: 131401800.lmr
> > Writing: 131401800.lmr_met.nc
> > Adding timing info to variable named r
> >
> > Output file names = Input "_met.nc".
> >
> > And here's a command using the MET plot_data_plane tool to plot
the
> result:
> >
> > plot_data_plane 131401800.lmr_met.nc 131401800.lmr_met.ps
'name="r";
> > level="(0,0,*,*)";'
> >
> > I have attached the script for you. Please give it a try and let
us know
> > how it goes.
> >
> > Thanks,
> > Julie
> >
> > On Tue, Nov 5, 2019 at 10:55 PM wang Dawn via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Tue Nov 05 22:54:47 2019: Request 92975 was acted upon.
> > > Transaction: Ticket created by wangrzqi at gmail.com
> > > Queue: met_help
> > > Subject: Point_stat grid data use NETCDF_NCCF format
> > > Owner: Nobody
> > > Requestors: wangrzqi at gmail.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975
> >
> > >
> > >
> > > Dear MET help:
> > >
> > > I have a question on the point_stat tool. I have grid data
of LAPS
> > > output(NETCDF format),
> > > and point data of Prepbufr.
> > >
> > > Grid data are following (lon: 73:135, lat:8:63):
> > >
> > > netcdf SFC_201910280000 {
> > > dimensions:
> > > time = UNLIMITED ; // (1 currently)
> > > latitude = 1801 ;
> > > longitude = 2067 ;
> > > variables:
> > > float ts(time, latitude, longitude) ;
> > > ts:_FillValue = 1.e+20f ;
> > > ts:long_name = "Temperature" ;
> > > ts:units = "K" ;
> > > ts:standard_name = "air_temperature" ;
> > > ts:grid_type = "Latitude/longitude" ;
> > > ts:grid_mapping_name = "latitude_longitude" ;
> > > ts:level_type = "Specified height level above
ground
> > (m)" ;
> > > ts:level = 2LL ;
> > > double time(time) ;
> > > time:_FillValue = 1.e+20 ;
> > > time:units = "hours since 2019-10-28 00:00:00" ;
> > > time:timezone = "UTC" ;
> > > float latitude(latitude) ;
> > > latitude:_FillValue = 1.e+20f ;
> > > latitude:units = "degree_north" ;
> > > latitude:standard_name = "latitude" ;
> > > double longitude(longitude) ;
> > > longitude:_FillValue = 1.e+20 ;
> > > longitude:units = "degree_east" ;
> > > longitude:standard_name = "longitude" ;
> > > int64 forecast_reference_time(time) ;
> > > forecast_reference_time:units = "hours since
2019-10-28
> > > 00:00:00" ;
> > > forecast_reference_time:timezone = "UTC" ;
> > >
> > > // global attributes:
> > > :Conventions = "CF-1.X" ;
> > > }
> > >
> > > And a part of configure file are following:
> > > fcst = {
> > > file_type = NETCDF_NCCF;
> > > wind_thresh = [ NA ];
> > > message_type = [ "ADPSFC" ];
> > >
> > > field = [
> > > { name = "ts"; level = [ "(0,*,*)" ]; }
> > > ];
> > > };
> > >
> > >
> > > obs = {
> > > message_type = [ "ADPSFC" ];
> > >
> > > field = [
> > > { name = "TMP"; level = [ "Z2" ]; }
> > > ];
> > > };
> > >
> > > But, the result of point-stat is empty, a part log are
following:
> > >
> > > DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) ->
Found 1
> > times
> > > from between 20191028_000000 and 20191028_000000
> > > DEBUG 4:
> > > DEBUG 4: Data plane information:
> > > DEBUG 4: plane min: 247.8701172
> > > DEBUG 4: plane max: 304.5449219
> > > DEBUG 4: valid time: 20191028_000000
> > > DEBUG 4: lead time: 000000
> > > DEBUG 4: init time: 20191028_000000
> > > DEBUG 4: accum time: 000000
> > > DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &,
DataPlaneArray &)
> > ->
> > > time: 20191028_000000 from index 0
> > > DEBUG 2:
> > > DEBUG 2:
> > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Reading data for ts(0,*,*).
> > > DEBUG 3: Use the matching forecast and observation grids.
> > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny: 1801
lat_ll:
> > > 8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
> > > DEBUG 2: Processing masking regions.
> > > DEBUG 3: Processing grid mask: FULL
> > > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > > DEBUG 3: Processing station ID mask: (nul)
> > > DEBUG 2: Processing geography data.
> > > DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0 climatology
mean
> > levels,
> > > and 0 climatology standard deviation levels.
> > > DEBUG 2:
> > > DEBUG 2:
> > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Searching 690796 observations from 415033 messages.
> > > DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1] 41,-
9999
> > > inst_typ[0,-1] -9999,-9999
> > > DEBUG 2:
> > > DEBUG 2:
> > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 4: set FCST_UNITS:K
> > > DEBUG 4: set OBS_UNITS:NA
> > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > > over region FULL, for interpolation method BILIN(4), using 0
pairs.
> > > DEBUG 3: Number of matched pairs = 0
> > > DEBUG 3: Observations processed = 690796
> > > DEBUG 3: Rejected: SID exclusion = 0
> > > DEBUG 3: Rejected: obs type = 450597
> > > DEBUG 3: Rejected: valid time = 240199
> > > DEBUG 3: Rejected: bad obs value = 0
> > > DEBUG 3: Rejected: off the grid = 0
> > > DEBUG 3: Rejected: topography = 0
> > > DEBUG 3: Rejected: level mismatch = 0
> > > DEBUG 3: Rejected: quality marker = 0
> > > DEBUG 3: Rejected: message type = 0
> > > DEBUG 3: Rejected: masking region = 0
> > > DEBUG 3: Rejected: bad fcst value = 0
> > > DEBUG 3: Rejected: duplicates = 0
> > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > > over region NA, for interpolation method BILIN(4), using 0
pairs.
> > > DEBUG 3: Number of matched pairs = 0
> > > DEBUG 3: Observations processed = 690796
> > > DEBUG 3: Rejected: SID exclusion = 0
> > > DEBUG 3: Rejected: obs type = 450597
> > > DEBUG 3: Rejected: valid time = 240199
> > > DEBUG 3: Rejected: bad obs value = 0
> > > DEBUG 3: Rejected: off the grid = 0
> > > DEBUG 3: Rejected: topography = 0
> > > DEBUG 3: Rejected: level mismatch = 0
> > > DEBUG 3: Rejected: quality marker = 0
> > > DEBUG 3: Rejected: message type = 0
> > > DEBUG 3: Rejected: masking region = 0
> > > DEBUG 3: Rejected: bad fcst value = 0
> > > DEBUG 3: Rejected: duplicates = 0
> > > DEBUG 2:
> > > DEBUG 2:
> > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 1: Output file:
./point_stat_ADPSFC_000000L_20191028_000000V.stat
> > > DEBUG 1: Output file:
> > ./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
> > > DEBUG 1: Output file:
> > > ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
> > > DEBUG 1: Output file:
> > > ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
> > >
> > > So, I want to know what is the reason, Can provide sample grid
data of
> > > NETCDF_NCCF format？
> > >
> > > Best regards！
> > > Renzhi Wang
> > >
> > >
> >
> > --
> > 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.
> >
> >
>
>
--
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: Point_stat grid data use NETCDF_NCCF format
From: Julie Prestopnik
Time: Wed Nov 06 14:46:21 2019
John,
Thank you very much for your help with this. I appreciate it!
Julie
On Wed, Nov 6, 2019 at 11:10 AM John Halley Gotway via RT <
met_help-comment at rap.ucar.edu> wrote:
> Julie,
>
> It looks like the file formats are fine here. They are using CF-
compliant
> NetCDF as input. The problem is that they're getting 0 matched
pairs.
> Looking at the log messages they sent, it's because of a valid time
> mismatch:
>
> DEBUG 3: Observations processed = 690796
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: obs type = 450597
> DEBUG 3: Rejected: valid time = 240199
>
> In these cases, I usually instruct the user to open up the matching
time
> window very wide to see if we can get some matches. In the Point-
Stat
> config file, make the obs_window very large:
> obs_window = {
> beg = -5400000;
> end = 5400000;
> }
>
> They may still get 0 matched pairs, but the reason counts will
surely
> change. And they continue debugging. Once they do get matched
pairs, they
> should circle back around to figure out why the forecast valid times
don't
> match up well with the timestamps of the observations.
>
> FYI, this is a "Comment (Not sent to requestors)". So you'd need to
> reword it however you'd like in your response.
>
> Thanks<
> John
>
--
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: Point_stat grid data use NETCDF_NCCF format
From: wang Dawn
Time: Thu Nov 07 23:25:20 2019
Julie. It works. Thank you very much.
The time interval between observation data(Prepbufr) and analysis
data(LAPS
output) is relatively large.
Renzhi
Julie Prestopnik via RT <met_help at ucar.edu> 于2019年11月7日周四 上午5:54写道：
> Hi. Actually, it looks like the file formats are fine here and that
you
> are using CF-compliant NetCDF as input. I see the problem is that
you are
> getting 0 matched pairs. Looking at the log messages you sent, it
is
> because of a valid time mismatch:
>
> DEBUG 3: Observations processed = 690796
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: obs type = 450597
> DEBUG 3: Rejected: valid time = 240199
>
> In this case, it would be good if you could open up the matching
time
> window very wide to see if we can get some matches. In the Point-
Stat
> config file, make the obs_window very large:
> obs_window = {
> beg = -5400000;
> end = 5400000;
> }
>
> You may still get 0 matched pairs, but the reason counts will surely
> change, and you can continue debugging. Once you do get matched
pairs, you
> can circle back around to figure out why the forecast valid times
don't
> match up well with the timestamps of the observations.
>
> I hope that helps. Please follow up with any further questions you
have.
>
> Julie
>
> On Wed, Nov 6, 2019 at 8:29 AM wang Dawn via RT <met_help at ucar.edu>
wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
> >
> > Thank you Julie. I will try again. My netcdf projection is
Lat/Lon, not
> > Lambert Conformal. I don't know which attributes to add.
> >
> > Best regards.
> >
> > Julie Prestopnik via RT <met_help at ucar.edu> 于 2019年11月6日周三
14:17写道：
> >
> > > Hi Renzhi.
> > >
> > > I see that you are having some trouble with using some LAPS data
in
> > MET. I
> > > found a previous met_help ticket where a colleague of mine wrote
a
> script
> > > to convert some LAPS data to a format that MET can read.
> > >
> > > He reformatted a sample LAPS file was sent to us using an R
script that
> > > loads the RNetCDF package. It demonstrates the necessary
changes to
> make
> > > thisfile look like the NetCDF output of the MET tools.
> > >
> > > Running without arguments give the usage info:
> > >
> > > > Rscript laps2metnc.R
> > >
> > > Usage: laps2metnc.R file_list
> > > where "file_list" is one or more LAPS files to be
reformatted.
> > >
> > > You should pass in one or more files to be reformatted. In the
example
> > > below, the filename was 131401800.lmr. Unfortunately, I do not
have
> that
> > > file, but I will use the filename in the example below so that
you can
> > see
> > > how to use it.
> > >
> > > > Rscript laps2metnc.R 131401800.lmr
> > > Processing 1 files...
> > > Reading: 131401800.lmr
> > > Writing: 131401800.lmr_met.nc
> > > Adding timing info to variable named r
> > >
> > > Output file names = Input "_met.nc".
> > >
> > > And here's a command using the MET plot_data_plane tool to plot
the
> > result:
> > >
> > > plot_data_plane 131401800.lmr_met.nc 131401800.lmr_met.ps
'name="r";
> > > level="(0,0,*,*)";'
> > >
> > > I have attached the script for you. Please give it a try and
let us
> know
> > > how it goes.
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Tue, Nov 5, 2019 at 10:55 PM wang Dawn via RT
<met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > Tue Nov 05 22:54:47 2019: Request 92975 was acted upon.
> > > > Transaction: Ticket created by wangrzqi at gmail.com
> > > > Queue: met_help
> > > > Subject: Point_stat grid data use NETCDF_NCCF format
> > > > Owner: Nobody
> > > > Requestors: wangrzqi at gmail.com
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975
> > >
> > > >
> > > >
> > > > Dear MET help:
> > > >
> > > > I have a question on the point_stat tool. I have grid data
of
> LAPS
> > > > output(NETCDF format),
> > > > and point data of Prepbufr.
> > > >
> > > > Grid data are following (lon: 73:135, lat:8:63):
> > > >
> > > > netcdf SFC_201910280000 {
> > > > dimensions:
> > > > time = UNLIMITED ; // (1 currently)
> > > > latitude = 1801 ;
> > > > longitude = 2067 ;
> > > > variables:
> > > > float ts(time, latitude, longitude) ;
> > > > ts:_FillValue = 1.e+20f ;
> > > > ts:long_name = "Temperature" ;
> > > > ts:units = "K" ;
> > > > ts:standard_name = "air_temperature" ;
> > > > ts:grid_type = "Latitude/longitude" ;
> > > > ts:grid_mapping_name = "latitude_longitude" ;
> > > > ts:level_type = "Specified height level above
ground
> > > (m)" ;
> > > > ts:level = 2LL ;
> > > > double time(time) ;
> > > > time:_FillValue = 1.e+20 ;
> > > > time:units = "hours since 2019-10-28 00:00:00"
;
> > > > time:timezone = "UTC" ;
> > > > float latitude(latitude) ;
> > > > latitude:_FillValue = 1.e+20f ;
> > > > latitude:units = "degree_north" ;
> > > > latitude:standard_name = "latitude" ;
> > > > double longitude(longitude) ;
> > > > longitude:_FillValue = 1.e+20 ;
> > > > longitude:units = "degree_east" ;
> > > > longitude:standard_name = "longitude" ;
> > > > int64 forecast_reference_time(time) ;
> > > > forecast_reference_time:units = "hours since
> 2019-10-28
> > > > 00:00:00" ;
> > > > forecast_reference_time:timezone = "UTC" ;
> > > >
> > > > // global attributes:
> > > > :Conventions = "CF-1.X" ;
> > > > }
> > > >
> > > > And a part of configure file are following:
> > > > fcst = {
> > > > file_type = NETCDF_NCCF;
> > > > wind_thresh = [ NA ];
> > > > message_type = [ "ADPSFC" ];
> > > >
> > > > field = [
> > > > { name = "ts"; level = [ "(0,*,*)" ]; }
> > > > ];
> > > > };
> > > >
> > > >
> > > > obs = {
> > > > message_type = [ "ADPSFC" ];
> > > >
> > > > field = [
> > > > { name = "TMP"; level = [ "Z2" ]; }
> > > > ];
> > > > };
> > > >
> > > > But, the result of point-stat is empty, a part log are
following:
> > > >
> > > > DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) ->
Found 1
> > > times
> > > > from between 20191028_000000 and 20191028_000000
> > > > DEBUG 4:
> > > > DEBUG 4: Data plane information:
> > > > DEBUG 4: plane min: 247.8701172
> > > > DEBUG 4: plane max: 304.5449219
> > > > DEBUG 4: valid time: 20191028_000000
> > > > DEBUG 4: lead time: 000000
> > > > DEBUG 4: init time: 20191028_000000
> > > > DEBUG 4: accum time: 000000
> > > > DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &,
DataPlaneArray
> &)
> > > ->
> > > > time: 20191028_000000 from index 0
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > DEBUG 2:
> > > > DEBUG 2: Reading data for ts(0,*,*).
> > > > DEBUG 3: Use the matching forecast and observation grids.
> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny:
1801
> lat_ll:
> > > > 8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
> > > > DEBUG 2: Processing masking regions.
> > > > DEBUG 3: Processing grid mask: FULL
> > > > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > > > DEBUG 3: Processing station ID mask: (nul)
> > > > DEBUG 2: Processing geography data.
> > > > DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0 climatology
mean
> > > levels,
> > > > and 0 climatology standard deviation levels.
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > DEBUG 2:
> > > > DEBUG 2: Searching 690796 observations from 415033 messages.
> > > > DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1] 41,-
9999
> > > > inst_typ[0,-1] -9999,-9999
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > DEBUG 2:
> > > > DEBUG 4: set FCST_UNITS:K
> > > > DEBUG 4: set OBS_UNITS:NA
> > > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> > ADPSFC,
> > > > over region FULL, for interpolation method BILIN(4), using 0
pairs.
> > > > DEBUG 3: Number of matched pairs = 0
> > > > DEBUG 3: Observations processed = 690796
> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > DEBUG 3: Rejected: obs type = 450597
> > > > DEBUG 3: Rejected: valid time = 240199
> > > > DEBUG 3: Rejected: bad obs value = 0
> > > > DEBUG 3: Rejected: off the grid = 0
> > > > DEBUG 3: Rejected: topography = 0
> > > > DEBUG 3: Rejected: level mismatch = 0
> > > > DEBUG 3: Rejected: quality marker = 0
> > > > DEBUG 3: Rejected: message type = 0
> > > > DEBUG 3: Rejected: masking region = 0
> > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > DEBUG 3: Rejected: duplicates = 0
> > > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> > ADPSFC,
> > > > over region NA, for interpolation method BILIN(4), using 0
pairs.
> > > > DEBUG 3: Number of matched pairs = 0
> > > > DEBUG 3: Observations processed = 690796
> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > DEBUG 3: Rejected: obs type = 450597
> > > > DEBUG 3: Rejected: valid time = 240199
> > > > DEBUG 3: Rejected: bad obs value = 0
> > > > DEBUG 3: Rejected: off the grid = 0
> > > > DEBUG 3: Rejected: topography = 0
> > > > DEBUG 3: Rejected: level mismatch = 0
> > > > DEBUG 3: Rejected: quality marker = 0
> > > > DEBUG 3: Rejected: message type = 0
> > > > DEBUG 3: Rejected: masking region = 0
> > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > DEBUG 3: Rejected: duplicates = 0
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > DEBUG 2:
> > > > DEBUG 1: Output file:
> ./point_stat_ADPSFC_000000L_20191028_000000V.stat
> > > > DEBUG 1: Output file:
> > > ./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
> > > > DEBUG 1: Output file:
> > > > ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
> > > > DEBUG 1: Output file:
> > > > ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
> > > >
> > > > So, I want to know what is the reason, Can provide sample grid
data
> of
> > > > NETCDF_NCCF format？
> > > >
> > > > Best regards！
> > > > Renzhi Wang
> > > >
> > > >
> > >
> > > --
> > > 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.
> > >
> > >
> >
> >
>
> --
> 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: Point_stat grid data use NETCDF_NCCF format
From: Julie Prestopnik
Time: Fri Nov 08 09:20:47 2019
Thank you, Renzhi. I will go ahead and close this ticket. Please
feel
free to open a new ticket with any other issues you encounter.
Julie
On Thu, Nov 7, 2019 at 11:25 PM wang Dawn via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
>
> Julie. It works. Thank you very much.
> The time interval between observation data(Prepbufr) and analysis
data(LAPS
> output) is relatively large.
>
> Renzhi
>
> Julie Prestopnik via RT <met_help at ucar.edu> 于2019年11月7日周四 上午5:54写道：
>
> > Hi. Actually, it looks like the file formats are fine here and
that you
> > are using CF-compliant NetCDF as input. I see the problem is that
you
> are
> > getting 0 matched pairs. Looking at the log messages you sent, it
is
> > because of a valid time mismatch:
> >
> > DEBUG 3: Observations processed = 690796
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: obs type = 450597
> > DEBUG 3: Rejected: valid time = 240199
> >
> > In this case, it would be good if you could open up the matching
time
> > window very wide to see if we can get some matches. In the Point-
Stat
> > config file, make the obs_window very large:
> > obs_window = {
> > beg = -5400000;
> > end = 5400000;
> > }
> >
> > You may still get 0 matched pairs, but the reason counts will
surely
> > change, and you can continue debugging. Once you do get matched
pairs,
> you
> > can circle back around to figure out why the forecast valid times
don't
> > match up well with the timestamps of the observations.
> >
> > I hope that helps. Please follow up with any further questions
you have.
> >
> > Julie
> >
> > On Wed, Nov 6, 2019 at 8:29 AM wang Dawn via RT
<met_help at ucar.edu>
> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975 >
> > >
> > > Thank you Julie. I will try again. My netcdf projection is
Lat/Lon,
> not
> > > Lambert Conformal. I don't know which attributes to add.
> > >
> > > Best regards.
> > >
> > > Julie Prestopnik via RT <met_help at ucar.edu> 于 2019年11月6日周三
14:17写道：
> > >
> > > > Hi Renzhi.
> > > >
> > > > I see that you are having some trouble with using some LAPS
data in
> > > MET. I
> > > > found a previous met_help ticket where a colleague of mine
wrote a
> > script
> > > > to convert some LAPS data to a format that MET can read.
> > > >
> > > > He reformatted a sample LAPS file was sent to us using an R
script
> that
> > > > loads the RNetCDF package. It demonstrates the necessary
changes to
> > make
> > > > thisfile look like the NetCDF output of the MET tools.
> > > >
> > > > Running without arguments give the usage info:
> > > >
> > > > > Rscript laps2metnc.R
> > > >
> > > > Usage: laps2metnc.R file_list
> > > > where "file_list" is one or more LAPS files to be
reformatted.
> > > >
> > > > You should pass in one or more files to be reformatted. In
the
> example
> > > > below, the filename was 131401800.lmr. Unfortunately, I do
not have
> > that
> > > > file, but I will use the filename in the example below so that
you
> can
> > > see
> > > > how to use it.
> > > >
> > > > > Rscript laps2metnc.R 131401800.lmr
> > > > Processing 1 files...
> > > > Reading: 131401800.lmr
> > > > Writing: 131401800.lmr_met.nc
> > > > Adding timing info to variable named r
> > > >
> > > > Output file names = Input "_met.nc".
> > > >
> > > > And here's a command using the MET plot_data_plane tool to
plot the
> > > result:
> > > >
> > > > plot_data_plane 131401800.lmr_met.nc 131401800.lmr_met.ps
'name="r";
> > > > level="(0,0,*,*)";'
> > > >
> > > > I have attached the script for you. Please give it a try and
let us
> > know
> > > > how it goes.
> > > >
> > > > Thanks,
> > > > Julie
> > > >
> > > > On Tue, Nov 5, 2019 at 10:55 PM wang Dawn via RT
<met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > >
> > > > > Tue Nov 05 22:54:47 2019: Request 92975 was acted upon.
> > > > > Transaction: Ticket created by wangrzqi at gmail.com
> > > > > Queue: met_help
> > > > > Subject: Point_stat grid data use NETCDF_NCCF format
> > > > > Owner: Nobody
> > > > > Requestors: wangrzqi at gmail.com
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92975
> > > >
> > > > >
> > > > >
> > > > > Dear MET help:
> > > > >
> > > > > I have a question on the point_stat tool. I have grid
data of
> > LAPS
> > > > > output(NETCDF format),
> > > > > and point data of Prepbufr.
> > > > >
> > > > > Grid data are following (lon: 73:135, lat:8:63):
> > > > >
> > > > > netcdf SFC_201910280000 {
> > > > > dimensions:
> > > > > time = UNLIMITED ; // (1 currently)
> > > > > latitude = 1801 ;
> > > > > longitude = 2067 ;
> > > > > variables:
> > > > > float ts(time, latitude, longitude) ;
> > > > > ts:_FillValue = 1.e+20f ;
> > > > > ts:long_name = "Temperature" ;
> > > > > ts:units = "K" ;
> > > > > ts:standard_name = "air_temperature" ;
> > > > > ts:grid_type = "Latitude/longitude" ;
> > > > > ts:grid_mapping_name = "latitude_longitude"
;
> > > > > ts:level_type = "Specified height level
above
> ground
> > > > (m)" ;
> > > > > ts:level = 2LL ;
> > > > > double time(time) ;
> > > > > time:_FillValue = 1.e+20 ;
> > > > > time:units = "hours since 2019-10-28
00:00:00" ;
> > > > > time:timezone = "UTC" ;
> > > > > float latitude(latitude) ;
> > > > > latitude:_FillValue = 1.e+20f ;
> > > > > latitude:units = "degree_north" ;
> > > > > latitude:standard_name = "latitude" ;
> > > > > double longitude(longitude) ;
> > > > > longitude:_FillValue = 1.e+20 ;
> > > > > longitude:units = "degree_east" ;
> > > > > longitude:standard_name = "longitude" ;
> > > > > int64 forecast_reference_time(time) ;
> > > > > forecast_reference_time:units = "hours since
> > 2019-10-28
> > > > > 00:00:00" ;
> > > > > forecast_reference_time:timezone = "UTC" ;
> > > > >
> > > > > // global attributes:
> > > > > :Conventions = "CF-1.X" ;
> > > > > }
> > > > >
> > > > > And a part of configure file are following:
> > > > > fcst = {
> > > > > file_type = NETCDF_NCCF;
> > > > > wind_thresh = [ NA ];
> > > > > message_type = [ "ADPSFC" ];
> > > > >
> > > > > field = [
> > > > > { name = "ts"; level = [ "(0,*,*)" ]; }
> > > > > ];
> > > > > };
> > > > >
> > > > >
> > > > > obs = {
> > > > > message_type = [ "ADPSFC" ];
> > > > >
> > > > > field = [
> > > > > { name = "TMP"; level = [ "Z2" ]; }
> > > > > ];
> > > > > };
> > > > >
> > > > > But, the result of point-stat is empty, a part log are
following:
> > > > >
> > > > > DEBUG 7: MetNcCFDataFile::collect_time_offsets(VarInfo &) ->
> Found 1
> > > > times
> > > > > from between 20191028_000000 and 20191028_000000
> > > > > DEBUG 4:
> > > > > DEBUG 4: Data plane information:
> > > > > DEBUG 4: plane min: 247.8701172
> > > > > DEBUG 4: plane max: 304.5449219
> > > > > DEBUG 4: valid time: 20191028_000000
> > > > > DEBUG 4: lead time: 000000
> > > > > DEBUG 4: init time: 20191028_000000
> > > > > DEBUG 4: accum time: 000000
> > > > > DEBUG 7: MetNcCFDataFile::data_plane_array(VarInfo &,
> DataPlaneArray
> > &)
> > > > ->
> > > > > time: 20191028_000000 from index 0
> > > > > DEBUG 2:
> > > > > DEBUG 2:
> > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > > DEBUG 2:
> > > > > DEBUG 2: Reading data for ts(0,*,*).
> > > > > DEBUG 3: Use the matching forecast and observation grids.
> > > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 2067 Ny:
1801
> > lat_ll:
> > > > > 8.000 lon_ll: -73.000 delta_lat: 0.030 delta_lon: 0.030
> > > > > DEBUG 2: Processing masking regions.
> > > > > DEBUG 3: Processing grid mask: FULL
> > > > > DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> > > > > DEBUG 3: Processing station ID mask: (nul)
> > > > > DEBUG 2: Processing geography data.
> > > > > DEBUG 2: For ts(0,*,*) found 1 forecast levels, 0
climatology mean
> > > > levels,
> > > > > and 0 climatology standard deviation levels.
> > > > > DEBUG 2:
> > > > > DEBUG 2:
> > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > > DEBUG 2:
> > > > > DEBUG 2: Searching 690796 observations from 415033 messages.
> > > > > DEBUG 10: prpt_typ[0,-1] 131,-9999 irpt_typ[0,-1]
41,-9999
> > > > > inst_typ[0,-1] -9999,-9999
> > > > > DEBUG 2:
> > > > > DEBUG 2:
> > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > > DEBUG 2:
> > > > > DEBUG 4: set FCST_UNITS:K
> > > > > DEBUG 4: set OBS_UNITS:NA
> > > > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> > > ADPSFC,
> > > > > over region FULL, for interpolation method BILIN(4), using 0
pairs.
> > > > > DEBUG 3: Number of matched pairs = 0
> > > > > DEBUG 3: Observations processed = 690796
> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > > DEBUG 3: Rejected: obs type = 450597
> > > > > DEBUG 3: Rejected: valid time = 240199
> > > > > DEBUG 3: Rejected: bad obs value = 0
> > > > > DEBUG 3: Rejected: off the grid = 0
> > > > > DEBUG 3: Rejected: topography = 0
> > > > > DEBUG 3: Rejected: level mismatch = 0
> > > > > DEBUG 3: Rejected: quality marker = 0
> > > > > DEBUG 3: Rejected: message type = 0
> > > > > DEBUG 3: Rejected: masking region = 0
> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > > DEBUG 3: Rejected: duplicates = 0
> > > > > DEBUG 2: Processing ts(0,*,*) versus TMP/Z2, for observation
type
> > > ADPSFC,
> > > > > over region NA, for interpolation method BILIN(4), using 0
pairs.
> > > > > DEBUG 3: Number of matched pairs = 0
> > > > > DEBUG 3: Observations processed = 690796
> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > > DEBUG 3: Rejected: obs type = 450597
> > > > > DEBUG 3: Rejected: valid time = 240199
> > > > > DEBUG 3: Rejected: bad obs value = 0
> > > > > DEBUG 3: Rejected: off the grid = 0
> > > > > DEBUG 3: Rejected: topography = 0
> > > > > DEBUG 3: Rejected: level mismatch = 0
> > > > > DEBUG 3: Rejected: quality marker = 0
> > > > > DEBUG 3: Rejected: message type = 0
> > > > > DEBUG 3: Rejected: masking region = 0
> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > > DEBUG 3: Rejected: duplicates = 0
> > > > > DEBUG 2:
> > > > > DEBUG 2:
> > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------
> > > > > DEBUG 2:
> > > > > DEBUG 1: Output file:
> > ./point_stat_ADPSFC_000000L_20191028_000000V.stat
> > > > > DEBUG 1: Output file:
> > > > ./point_stat_ADPSFC_000000L_20191028_000000V_cnt.txt
> > > > > DEBUG 1: Output file:
> > > > > ./point_stat_ADPSFC_000000L_20191028_000000V_sl1l2.txt
> > > > > DEBUG 1: Output file:
> > > > > ./point_stat_ADPSFC_000000L_20191028_000000V_vl1l2.txt
> > > > >
> > > > > So, I want to know what is the reason, Can provide sample
grid data
> > of
> > > > > NETCDF_NCCF format？
> > > > >
> > > > > Best regards！
> > > > > Renzhi Wang
> > > > >
> > > > >
> > > >
> > > > --
> > > > 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.
> > > >
> > > >
> > >
> > >
> >
> > --
> > 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.
> >
> >
>
>
--
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.
------------------------------------------------
More information about the Met_help
mailing list