[Met_help] [rt.rap.ucar.edu #79384] History for Point Stat help
John Halley Gotway via RT
met_help at ucar.edu
Wed Feb 15 14:07:42 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello MET help,
I’m going to go ahead and apologize for all the information in this email, but hopefully it will help you better diagnose what the best way for me to move forward is. As part of my research I generated 12 different WRF runs over the same week using the same I.C.s and B.C.s, and am currently in the process of comparing them against real world observations to see which config worked the best. I am primary concerned with comparing precip, surface temp/dewpoint, and surface winds.
The first tool I have tried to use has been the point stat tool. I am using your met-5.2_bugfix package and did not find any errors while/after compiling and made sure the test files, like test_point_stat.sh, all work. The data I am using is as follows:
Instead of downloading prepbufer files and converting them with the PB2NC tool, I just used the UCAR site to do it for me ( http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_subset.php?_da=y <http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_subset.php?_da=y>)
Request Detail:
Date Limits : 2016-08-12 00:00 2016-08-20 06:00
NCEP Verification Regions : SEC
Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR PRMSL
PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT QKSWND SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
Quality Mark Threshold : 9
File Compression : gz
Data Output Format : NETCDF
To convert my WRF data into a readable format I used P_Interp. I am now realizing this might not be the best way forward, but seemed the easiest to set up as I had to offload all my model output to a different cluster that I did not configure WRF on. I have been a bit confused as P_Interp says it can unstager data to pressure levels, but on your website it says that P_Interp cannot onstager data (at least for use with MODE and other tools). Either way do you think I should try use a different pre-processing software to unpack my WRF data or will P_Interp be sufficient to compare precip, surface temp/dewpoint and winds?
When I run my file PointStat.sh using the attached PointStatConfig1 file, I get the following data error message:
*** Running Point-Stat on prepbuffer files ***
DEBUG 1: Default Config File: /marge/r0/mdawson/met/met-5.2_bugfix/share/met/config/PointStatConfig_default
DEBUG 1: User Config File: config/PointStatConfig
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1
DEBUG 1: Forecast File: ../../../P_INTERP/preproc/ndown/linout/lin/day1/wrfout_d01_2016-08-12_12:00:00_PLEV
DEBUG 1: Observation File: ../data/prepbuffer/12/prepbufr.gdas.225564.2016081200.nc
DEBUG 2:
DEBUG 2: --------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for T2(*,*,0).
WARNING:
WARNING: PinterpFile::data(NcVar *, const LongArray &, DataPlane &, double &) const -> star found in bad slot
WARNING:
ERROR :
ERROR : PinterpFile::valid_time(int) const -> range check error
ERROR :
Looking at the ncdump P_Interp File, T2 (2 meter temperature shows):
float T2(Time, south_north, west_east) ;
T2:FieldType = 104 ;
T2:MemoryOrder = "XY " ;
T2:description = "TEMP at 2 M" ;
T2:units = "K" ;
T2:stagger = "" ;
T2:coordinates = "XLONG XLAT XTIME" ;
T2:missing_value = 1.e+36f ;
I am not sure if the issue is that P_Interp is not properly extracting this information, or If I just need to change my PointStatConfig1 file.
Thanks!
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: Dawsonmattg at gmail.com <mailto:Dawsonmattg at gmail.com>
Cell: (904)-333-5427
> On Feb 7, 2017, at 11:49 AM, Thomas Cram <tcram at ucar.edu <mailto:tcram at ucar.edu>> wrote:
>
> Hi Matthew,
>
> I recommend contacting MET support (cc'd here). It's possible you should be using the PrepBUFR data instead of the NetCDF data in MET, but having no experience using MET, I am merely speculating on this. MET support should be able to help you out.
>
> Good luck,
> - Tom
>
> On Tue, Feb 7, 2017 at 9:27 AM, Dawson, Matthew <dawsonmattg at gmail.com <mailto:dawsonmattg at gmail.com>> wrote:
> Hey Thomas
>
> I was able to get the data download with no issues, however I have been having issues with actually using that data in MET. I am trying to compare it to some WRF output (used P-Interp to convert into a MET readable format), but the PointStatConfig file keeps having issues (I’m not sure I filled it out correctly). Anyways I was wondering if you, or anyone happened to know of an online resource, or even someone who had a configuration set up for comparing data against WRF data so I can compare what I have against there config files and hopefully figure out where I am going wrong. I’ve been looking through the MET user guide but haven’t found a solution yet. Thanks!
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: mgd08 at my.fsu.edu <mailto:mgd08 at my.fsu.edu>
> Cell: (904)-333-5427 <tel:%28904%29-333-5427>
>
> > On Jan 24, 2017, at 1:26 PM, tcram at ucar.edu <mailto:tcram at ucar.edu> wrote:
> >
> > Your subset request for NCEP ADP Global Upper Air and Surface Weather Observations has completed.
> > Please login to the NCAR RDA server at http://rda.ucar.edu <http://rda.ucar.edu/>, then download your files from the
> > following URL:
> >
> > http://rda.ucar.edu/#dsrqst/DAWSON225564/ <http://rda.ucar.edu/#dsrqst/DAWSON225564/>
> >
> > Request ID: DAWSON225564
> >
> > Request Detail:
> > Date Limits : 2016-08-12 00:00 2016-08-20 06:00
> > NCEP Verification Regions : SEC
> > Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR PRMSL
> > PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT QKSWND SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
> > Quality Mark Threshold : 9
> > File Compression : gz
> > Data Output Format : NETCDF
> >
> >
> > The "rda-request-manager" command line tool provides an additional option for users to download
> > request output files on unix based systems. The "rda-request-manager" tool can be accessed at:
> >
> > http://rda.ucar.edu/#apps <http://rda.ucar.edu/#apps>
> >
> > The data provided in your data request are a subset of the NCAR RDA dataset ds337.0 --
> > 'NCEP ADP Global Upper Air and Surface Weather Observations (PREPBUFR format), May 1997 - Continuing'. Please see http://rda.ucar.edu/datasets/ds337.0/ <http://rda.ucar.edu/datasets/ds337.0/> for more information.
> >
> > Your data will remain on our system for 5 days. If this is not sufficient time for you to retrieve
> > your data, please let me know as soon as possible, so that I can prevent the data files from being
> > purged too soon.
> >
> > If you have any questions related to this data request, please let me know by replying to this
> > email.
> >
> > Sincerely,
> >
> > Thomas Cram
> > NCAR/CISL/Data Support Section
> > Phone: (303)-497-1217 <tel:%28303%29-497-1217>
> > Email: tcram at ucar.edu <mailto:tcram at ucar.edu>
> > Web: http://rda.ucar.edu <http://rda.ucar.edu/>
>
>
>
>
> --
> Thomas Cram
> NCAR / CISL / DSS
> tel: +1-303-497-1217
> e-mail: tcram at ucar.edu <mailto:tcram at ucar.edu>
> web: rda.ucar.edu <http://rda.ucar.edu/>
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: mgd08 at my.fsu.edu
Cell: (904)-333-5427
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Point Stat help
From: John Halley Gotway
Time: Wed Feb 08 15:58:50 2017
Matthew,
I see that you have some questions about running the Point-Stat tool.
Regarding post-processing, I'd suggest switching from the pinterp
utility
to using the Unified Post-Processor (UPP). It writes output in GRIB
which
MET can easily handle. Why pinterp output could work fine for precip,
temperature, and dewpoint, MET won't be able to process the winds
since
they're defined on the staggered dimension. I realize that running
UPP,
yet another tool to compile and script up, can be a hassle. But I
think
it'll be less work in the long run.
But as for your specific error from Point-Stat, I suspect that'll be
easy
to fix. In your Point-Stat config file, try using:
name = "T2";
level = [ "(0,*,*)" ];
I often like plotting the data first:
met-5.2/bin/plot_data_plane \
../../../P_INTERP/preproc/ndown/linout/lin/day1/wrfout_d01_2016-08-
12_12:00:00_PLEV
\
T2.ps \
'name="T2"; level="(0,*,*)";'
Hopefully that'll create a PostScript plot of your data.
Thanks,
John Halley Gotway
met_help at ucar.edu
On Tue, Feb 7, 2017 at 7:27 PM, dawsonmattg at gmail.com via RT <
met_help at ucar.edu> wrote:
>
> Tue Feb 07 19:27:38 2017: Request 79384 was acted upon.
> Transaction: Ticket created by dawsonmattg at gmail.com
> Queue: met_help
> Subject: Point Stat help
> Owner: Nobody
> Requestors: dawsonmattg at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79384 >
>
>
> Hello MET help,
>
> I’m going to go ahead and apologize for all the information
in
> this email, but hopefully it will help you better diagnose what the
best
> way for me to move forward is. As part of my research I generated 12
> different WRF runs over the same week using the same I.C.s and
B.C.s, and
> am currently in the process of comparing them against real world
> observations to see which config worked the best. I am primary
concerned
> with comparing precip, surface temp/dewpoint, and surface winds.
>
> The first tool I have tried to use has been the point stat
tool. I
> am using your met-5.2_bugfix package and did not find any errors
> while/after compiling and made sure the test files, like
> test_point_stat.sh, all work. The data I am using is as follows:
>
>
> Instead of downloading prepbufer files and
converting them
> with the PB2NC tool, I just used the UCAR site to do it for me (
>
http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_subset.php?_da=y
> <http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_
> subset.php?_da=y>)
> Request Detail:
> Date Limits : 2016-08-12 00:00 2016-08-20 06:00
> NCEP Verification Regions : SEC
> Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR
PRMSL
> PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT
QKSWND
> SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
> Quality Mark Threshold : 9
> File Compression : gz
> Data Output Format : NETCDF
>
>
>
> To convert my WRF data into a readable format I used
P_Interp. I
> am now realizing this might not be the best way forward, but seemed
the
> easiest to set up as I had to offload all my model output to a
different
> cluster that I did not configure WRF on. I have been a bit confused
as
> P_Interp says it can unstager data to pressure levels, but on your
website
> it says that P_Interp cannot onstager data (at least for use with
MODE and
> other tools). Either way do you think I should try use a different
> pre-processing software to unpack my WRF data or will P_Interp be
> sufficient to compare precip, surface temp/dewpoint and winds?
>
>
>
>
> When I run my file PointStat.sh using the attached
> PointStatConfig1 file, I get the following data error message:
>
> *** Running Point-Stat on prepbuffer files ***
> DEBUG 1: Default Config File: /marge/r0/mdawson/met/met-5.2_
> bugfix/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: config/PointStatConfig
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1
> DEBUG 1: Forecast File: ../../../P_INTERP/preproc/
> ndown/linout/lin/day1/wrfout_d01_2016-08-12_12:00:00_PLEV
> DEBUG 1: Observation File: ../data/prepbuffer/12/prepbufr
> .gdas.225564.2016081200.nc
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Reading data for T2(*,*,0).
> WARNING:
> WARNING: PinterpFile::data(NcVar *, const LongArray &, DataPlane &,
double
> &) const -> star found in bad slot
> WARNING:
> ERROR :
> ERROR : PinterpFile::valid_time(int) const -> range check error
> ERROR :
>
>
> Looking at the ncdump P_Interp File, T2 (2 meter temperature shows):
> float T2(Time, south_north, west_east) ;
> T2:FieldType = 104 ;
> T2:MemoryOrder = "XY " ;
> T2:description = "TEMP at 2 M" ;
> T2:units = "K" ;
> T2:stagger = "" ;
> T2:coordinates = "XLONG XLAT XTIME" ;
> T2:missing_value = 1.e+36f ;
>
> I am not sure if the issue is that P_Interp is not properly
extracting
> this information, or If I just need to change my PointStatConfig1
file.
>
>
> Thanks!
>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: Dawsonmattg at gmail.com <mailto:Dawsonmattg at gmail.com>
> Cell: (904)-333-5427
>
> > On Feb 7, 2017, at 11:49 AM, Thomas Cram <tcram at ucar.edu <mailto:
> tcram at ucar.edu>> wrote:
> >
> > Hi Matthew,
> >
> > I recommend contacting MET support (cc'd here). It's possible you
> should be using the PrepBUFR data instead of the NetCDF data in MET,
but
> having no experience using MET, I am merely speculating on this.
MET
> support should be able to help you out.
> >
> > Good luck,
> > - Tom
> >
> > On Tue, Feb 7, 2017 at 9:27 AM, Dawson, Matthew
<dawsonmattg at gmail.com
> <mailto:dawsonmattg at gmail.com>> wrote:
> > Hey Thomas
> >
> > I was able to get the data download with no issues, however I have
been
> having issues with actually using that data in MET. I am trying to
compare
> it to some WRF output (used P-Interp to convert into a MET readable
> format), but the PointStatConfig file keeps having issues (I’m not
sure I
> filled it out correctly). Anyways I was wondering if you, or anyone
> happened to know of an online resource, or even someone who had a
> configuration set up for comparing data against WRF data so I can
compare
> what I have against there config files and hopefully figure out
where I am
> going wrong. I’ve been looking through the MET user guide but
haven’t found
> a solution yet. Thanks!
> >
> > Matthew G. Dawson, Capt, USAF
> > AFIT Student, Civilian Institution Program
> > Email: mgd08 at my.fsu.edu <mailto:mgd08 at my.fsu.edu>
> > Cell: (904)-333-5427 <tel:%28904%29-333-5427>
> >
> > > On Jan 24, 2017, at 1:26 PM, tcram at ucar.edu
<mailto:tcram at ucar.edu>
> wrote:
> > >
> > > Your subset request for NCEP ADP Global Upper Air and Surface
Weather
> Observations has completed.
> > > Please login to the NCAR RDA server at http://rda.ucar.edu <
> http://rda.ucar.edu/>, then download your files from the
> > > following URL:
> > >
> > > http://rda.ucar.edu/#dsrqst/DAWSON225564/ <
> http://rda.ucar.edu/#dsrqst/DAWSON225564/>
> > >
> > > Request ID: DAWSON225564
> > >
> > > Request Detail:
> > > Date Limits : 2016-08-12 00:00 2016-08-20 06:00
> > > NCEP Verification Regions : SEC
> > > Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH
MIXR
> PRMSL
> > > PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT
QKSWND
> SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
> > > Quality Mark Threshold : 9
> > > File Compression : gz
> > > Data Output Format : NETCDF
> > >
> > >
> > > The "rda-request-manager" command line tool provides an
additional
> option for users to download
> > > request output files on unix based systems. The "rda-request-
manager"
> tool can be accessed at:
> > >
> > > http://rda.ucar.edu/#apps <http://rda.ucar.edu/#apps>
> > >
> > > The data provided in your data request are a subset of the NCAR
RDA
> dataset ds337.0 --
> > > 'NCEP ADP Global Upper Air and Surface Weather Observations
(PREPBUFR
> format), May 1997 - Continuing'. Please see
http://rda.ucar.edu/datasets/
> ds337.0/ <http://rda.ucar.edu/datasets/ds337.0/> for more
information.
> > >
> > > Your data will remain on our system for 5 days. If this is not
> sufficient time for you to retrieve
> > > your data, please let me know as soon as possible, so that I can
> prevent the data files from being
> > > purged too soon.
> > >
> > > If you have any questions related to this data request, please
let me
> know by replying to this
> > > email.
> > >
> > > Sincerely,
> > >
> > > Thomas Cram
> > > NCAR/CISL/Data Support Section
> > > Phone: (303)-497-1217 <tel:%28303%29-497-1217>
> > > Email: tcram at ucar.edu <mailto:tcram at ucar.edu>
> > > Web: http://rda.ucar.edu <http://rda.ucar.edu/>
> >
> >
> >
> >
> > --
> > Thomas Cram
> > NCAR / CISL / DSS
> > tel: +1-303-497-1217
> > e-mail: tcram at ucar.edu <mailto:tcram at ucar.edu>
> > web: rda.ucar.edu <http://rda.ucar.edu/>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: mgd08 at my.fsu.edu
> Cell: (904)-333-5427
>
>
>
------------------------------------------------
Subject: Point Stat help
From: dawsonmattg at gmail.com
Time: Wed Feb 08 16:50:01 2017
John,
Thanks for the reply! I originally wanted to use UPP, but the cluster
I ran
my WRF models on didn’t have much space (very fast though) so I had to
offload all my data to another cluster my professor uses which isn’t
very
fast but has plenty of space. Since UPP has to have a path to my WRF
build
(excerpt below), I decided it was not feasible.
"Overview of the scripts to run the UPP Note: It is recommended that
the
user refer to the run_unipost* scripts in the script/ while reading
this
overview.
1. Set up variables:
TOP_DIR: top level directory for source codes (UPPV2.1 and WRFV3)
DOMAINPATH: directory where UPP will be run from
WRFPATH: path to your WRFV3 build; defaults to the environment
variable
used during the installation with the configure script
UNI_POST_HOME: path to your UPPV2.1 build
POSTEXEC: path to your UPPV2.1 executables”
As for the winds, my WRF output does supply 10 meter winds, which I
would
assume P_Interp would just put at the level (0,*,*), so in the case
shouldn't I be able to verify winds as well?
Anyways I tried your fix and while it does run I'm not actually
getting any
values. I'm fairly certain its because I specified the Level for the
obs
at, "P1000". I'm not sure how to specify the level as the "surface" or
10
meters though.
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for T2(0,*,*).
DEBUG 2: For T2(0,*,*) found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Searching 41979 observations from 6956 messages.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPUPA, over region FULL, for interpolation method NEAREST(1), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPUPA, over region FULL, for interpolation method MEDIAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPUPA, over region FULL, for interpolation method DW_MEAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPSFC, over region FULL, for interpolation method MEDIAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
ADPSFC, over region FULL, for interpolation method DW_MEAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
MSONET, over region FULL, for interpolation method NEAREST(1), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
MSONET, over region FULL, for interpolation method MEDIAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
MSONET, over region FULL, for interpolation method DW_MEAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
SRFSHP, over region FULL, for interpolation method NEAREST(1), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
SRFSHP, over region FULL, for interpolation method MEDIAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
SRFSHP, over region FULL, for interpolation method DW_MEAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
VADWND, over region FULL, for interpolation method NEAREST(1), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
VADWND, over region FULL, for interpolation method MEDIAN(9), using 0
pairs.
DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
VADWND, over region FULL, for interpolation method DW_MEAN(9), using 0
pairs.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V.stat
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_fho.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_ctc.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_cts.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_cnt.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_sl1l2.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_sal1l2.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_vl1l2.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_val1l2.txt
DEBUG 1: Output file:
../work/point_stat/point_stat_060000L_20160812_120000V_mpr.txt
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: Dawsonmattg at gmail.com
Cell: (904)-333-5427 <(904)%20333-5427>
On Feb 8, 2017, at 5:58 PM, John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
Matthew,
I see that you have some questions about running the Point-Stat tool.
Regarding post-processing, I'd suggest switching from the pinterp
utility
to using the Unified Post-Processor (UPP). It writes output in GRIB
which
MET can easily handle. Why pinterp output could work fine for precip,
temperature, and dewpoint, MET won't be able to process the winds
since
they're defined on the staggered dimension. I realize that running
UPP,
yet another tool to compile and script up, can be a hassle. But I
think
it'll be less work in the long run.
But as for your specific error from Point-Stat, I suspect that'll be
easy
to fix. In your Point-Stat config file, try using:
name = "T2";
level = [ "(0,*,*)" ];
I often like plotting the data first:
met-5.2/bin/plot_data_plane \
../../../P_INTERP/preproc/ndown/linout/lin/day1/wrfout_
d01_2016-08-12_12:00:00_PLEV
\
T2.ps \
'name="T2"; level="(0,*,*)";'
Hopefully that'll create a PostScript plot of your data.
Thanks,
John Halley Gotway
met_help at ucar.edu
On Tue, Feb 7, 2017 at 7:27 PM, dawsonmattg at gmail.com via RT <
met_help at ucar.edu> wrote:
Tue Feb 07 19:27:38 2017: Request 79384 was acted upon.
Transaction: Ticket created by dawsonmattg at gmail.com
Queue: met_help
Subject: Point Stat help
Owner: Nobody
Requestors: dawsonmattg at gmail.com
Status: new
Ticket <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79384 >
Hello MET help,
I’m going to go ahead and apologize for all the information in
this email, but hopefully it will help you better diagnose what the
best
way for me to move forward is. As part of my research I generated 12
different WRF runs over the same week using the same I.C.s and B.C.s,
and
am currently in the process of comparing them against real world
observations to see which config worked the best. I am primary
concerned
with comparing precip, surface temp/dewpoint, and surface winds.
The first tool I have tried to use has been the point stat
tool. I
am using your met-5.2_bugfix package and did not find any errors
while/after compiling and made sure the test files, like
test_point_stat.sh, all work. The data I am using is as follows:
Instead of downloading prepbufer files and converting
them
with the PB2NC tool, I just used the UCAR site to do it for me (
http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_subset.php?_da=y
<http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_
subset.php?_da=y>)
Request Detail:
Date Limits : 2016-08-12 00:00 2016-08-20 06:00
NCEP Verification Regions : SEC
Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR
PRMSL
PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT QKSWND
SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
Quality Mark Threshold : 9
File Compression : gz
Data Output Format : NETCDF
To convert my WRF data into a readable format I used P_Interp.
I
am now realizing this might not be the best way forward, but seemed
the
easiest to set up as I had to offload all my model output to a
different
cluster that I did not configure WRF on. I have been a bit confused as
P_Interp says it can unstager data to pressure levels, but on your
website
it says that P_Interp cannot onstager data (at least for use with MODE
and
other tools). Either way do you think I should try use a different
pre-processing software to unpack my WRF data or will P_Interp be
sufficient to compare precip, surface temp/dewpoint and winds?
When I run my file PointStat.sh using the attached
PointStatConfig1 file, I get the following data error message:
*** Running Point-Stat on prepbuffer files ***
DEBUG 1: Default Config File: /marge/r0/mdawson/met/met-5.2_
bugfix/share/met/config/PointStatConfig_default
DEBUG 1: User Config File: config/PointStatConfig
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1
DEBUG 1: Forecast File: ../../../P_INTERP/preproc/
ndown/linout/lin/day1/wrfout_d01_2016-08-12_12:00:00_PLEV
DEBUG 1: Observation File: ../data/prepbuffer/12/prepbufr
.gdas.225564.2016081200.nc
DEBUG 2:
DEBUG 2: ------------------------------------------------------------
--------------------
DEBUG 2:
DEBUG 2: Reading data for T2(*,*,0).
WARNING:
WARNING: PinterpFile::data(NcVar *, const LongArray &, DataPlane &,
double
&) const -> star found in bad slot
WARNING:
ERROR :
ERROR : PinterpFile::valid_time(int) const -> range check error
ERROR :
Looking at the ncdump P_Interp File, T2 (2 meter temperature shows):
float T2(Time, south_north, west_east) ;
T2:FieldType = 104 ;
T2:MemoryOrder = "XY " ;
T2:description = "TEMP at 2 M" ;
T2:units = "K" ;
T2:stagger = "" ;
T2:coordinates = "XLONG XLAT XTIME" ;
T2:missing_value = 1.e+36f ;
I am not sure if the issue is that P_Interp is not properly extracting
this information, or If I just need to change my PointStatConfig1
file.
Thanks!
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: Dawsonmattg at gmail.com <mailto:Dawsonmattg at gmail.com
<Dawsonmattg at gmail.com>>
Cell: (904)-333-5427 <(904)%20333-5427>
On Feb 7, 2017, at 11:49 AM, Thomas Cram <tcram at ucar.edu <mailto:
tcram at ucar.edu>> wrote:
Hi Matthew,
I recommend contacting MET support (cc'd here). It's possible you
should be using the PrepBUFR data instead of the NetCDF data in MET,
but
having no experience using MET, I am merely speculating on this. MET
support should be able to help you out.
Good luck,
- Tom
On Tue, Feb 7, 2017 at 9:27 AM, Dawson, Matthew <dawsonmattg at gmail.com
<mailto:dawsonmattg at gmail.com <dawsonmattg at gmail.com>>> wrote:
Hey Thomas
I was able to get the data download with no issues, however I have
been
having issues with actually using that data in MET. I am trying to
compare
it to some WRF output (used P-Interp to convert into a MET readable
format), but the PointStatConfig file keeps having issues (I’m not
sure I
filled it out correctly). Anyways I was wondering if you, or anyone
happened to know of an online resource, or even someone who had a
configuration set up for comparing data against WRF data so I can
compare
what I have against there config files and hopefully figure out where
I am
going wrong. I’ve been looking through the MET user guide but haven’t
found
a solution yet. Thanks!
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: mgd08 at my.fsu.edu <mailto:mgd08 at my.fsu.edu <mgd08 at my.fsu.edu>>
Cell: (904)-333-5427 <(904)%20333-5427> <tel:%28904%29-333-5427
<%28904%29-333-5427>>
On Jan 24, 2017, at 1:26 PM, tcram at ucar.edu <mailto:tcram at ucar.edu
<tcram at ucar.edu>>
wrote:
Your subset request for NCEP ADP Global Upper Air and Surface Weather
Observations has completed.
Please login to the NCAR RDA server at http://rda.ucar.edu <
http://rda.ucar.edu/>, then download your files from the
following URL:
http://rda.ucar.edu/#dsrqst/DAWSON225564/ <
http://rda.ucar.edu/#dsrqst/DAWSON225564/>
Request ID: DAWSON225564
Request Detail:
Date Limits : 2016-08-12 00:00 2016-08-20 06:00
NCEP Verification Regions : SEC
Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR
PRMSL
PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT QKSWND
SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
Quality Mark Threshold : 9
File Compression : gz
Data Output Format : NETCDF
The "rda-request-manager" command line tool provides an additional
option for users to download
request output files on unix based systems. The "rda-request-manager"
tool can be accessed at:
http://rda.ucar.edu/#apps <http://rda.ucar.edu/#apps>
The data provided in your data request are a subset of the NCAR RDA
dataset ds337.0 --
'NCEP ADP Global Upper Air and Surface Weather Observations (PREPBUFR
format), May 1997 - Continuing'. Please see
http://rda.ucar.edu/datasets/
ds337.0/ <http://rda.ucar.edu/datasets/ds337.0/> for more information.
Your data will remain on our system for 5 days. If this is not
sufficient time for you to retrieve
your data, please let me know as soon as possible, so that I can
prevent the data files from being
purged too soon.
If you have any questions related to this data request, please let me
know by replying to this
email.
Sincerely,
Thomas Cram
NCAR/CISL/Data Support Section
Phone: (303)-497-1217 <(303)%20497-1217> <tel:%28303%29-497-1217
<%28303%29-497-1217>>
Email: tcram at ucar.edu <mailto:tcram at ucar.edu <tcram at ucar.edu>>
Web: http://rda.ucar.edu <http://rda.ucar.edu/>
--
Thomas Cram
NCAR / CISL / DSS
tel: +1-303-497-1217 <(303)%20497-1217>
e-mail: tcram at ucar.edu <mailto:tcram at ucar.edu <tcram at ucar.edu>>
web: rda.ucar.edu <http://rda.ucar.edu/>
Matthew G. Dawson, Capt, USAF
AFIT Student, Civilian Institution Program
Email: mgd08 at my.fsu.edu
Cell: (904)-333-5427 <(904)%20333-5427>
------------------------------------------------
Subject: Point Stat help
From: John Halley Gotway
Time: Wed Feb 08 17:03:05 2017
Matthew,
The verification of surface variables is done in a pretty simplistic
way by
specifying the message type.
The ADPSFC and SFCSHP message types are assumed to exist at the
surface and
are used to verifying "surface" variables such as 2m temperature and
10-m
winds. And ONLYSF is a short-cut for combining land-based ADPSFC and
water-based SFCSHP observations together. Your Point-Stat config file
should look something like this:
fcst = {
field = [
{
name = "T2";
level = [ "(*,*,0)" ];
cat_thresh = [ <=273, >273 ];
}
];
}
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ <=273, >273 ];
}
];
}
Does that produce any matched pairs? I don't see the source of the
PREPBUFR observation data you're using, but if you're using GDAS,
please
read the NOTE at the bottom of this page about the quality marker
that's
assigned to surface observations:
http://www.dtcenter.org/met/users/downloads/observation_data.php
Thanks,
John
John
On Wed, Feb 8, 2017 at 4:50 PM, dawsonmattg at gmail.com via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79384 >
>
> John,
>
> Thanks for the reply! I originally wanted to use UPP, but the
cluster I ran
> my WRF models on didn’t have much space (very fast though) so I had
to
> offload all my data to another cluster my professor uses which isn’t
very
> fast but has plenty of space. Since UPP has to have a path to my WRF
build
> (excerpt below), I decided it was not feasible.
>
> "Overview of the scripts to run the UPP Note: It is recommended that
the
> user refer to the run_unipost* scripts in the script/ while reading
this
> overview.
> 1. Set up variables:
> TOP_DIR: top level directory for source codes (UPPV2.1 and WRFV3)
> DOMAINPATH: directory where UPP will be run from
> WRFPATH: path to your WRFV3 build; defaults to the environment
variable
> used during the installation with the configure script
> UNI_POST_HOME: path to your UPPV2.1 build
> POSTEXEC: path to your UPPV2.1 executables”
>
> As for the winds, my WRF output does supply 10 meter winds, which I
would
> assume P_Interp would just put at the level (0,*,*), so in the case
> shouldn't I be able to verify winds as well?
>
> Anyways I tried your fix and while it does run I'm not actually
getting any
> values. I'm fairly certain its because I specified the Level for the
obs
> at, "P1000". I'm not sure how to specify the level as the "surface"
or 10
> meters though.
>
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Reading data for T2(0,*,*).
> DEBUG 2: For T2(0,*,*) found 1 forecast levels and 0 climatology
levels.
> DEBUG 2:
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Searching 41979 observations from 6956 messages.
> DEBUG 2:
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPUPA, over region FULL, for interpolation method NEAREST(1), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPUPA, over region FULL, for interpolation method MEDIAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPUPA, over region FULL, for interpolation method DW_MEAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPSFC, over region FULL, for interpolation method MEDIAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> ADPSFC, over region FULL, for interpolation method DW_MEAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> MSONET, over region FULL, for interpolation method NEAREST(1), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> MSONET, over region FULL, for interpolation method MEDIAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> MSONET, over region FULL, for interpolation method DW_MEAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> SRFSHP, over region FULL, for interpolation method NEAREST(1), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> SRFSHP, over region FULL, for interpolation method MEDIAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> SRFSHP, over region FULL, for interpolation method DW_MEAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> VADWND, over region FULL, for interpolation method NEAREST(1), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> VADWND, over region FULL, for interpolation method MEDIAN(9), using
0
> pairs.
> DEBUG 2: Processing T2(0,*,*) versus TMP/P1000, for observation type
> VADWND, over region FULL, for interpolation method DW_MEAN(9), using
0
> pairs.
> DEBUG 2:
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V.stat
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_fho.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_ctc.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_cts.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_cnt.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_sl1l2.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_sal1l2.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_vl1l2.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_val1l2.txt
> DEBUG 1: Output file:
> ../work/point_stat/point_stat_060000L_20160812_120000V_mpr.txt
>
>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: Dawsonmattg at gmail.com
> Cell: (904)-333-5427 <(904)%20333-5427>
>
> On Feb 8, 2017, at 5:58 PM, John Halley Gotway via RT
<met_help at ucar.edu>
> wrote:
>
> Matthew,
>
> I see that you have some questions about running the Point-Stat
tool.
>
> Regarding post-processing, I'd suggest switching from the pinterp
utility
> to using the Unified Post-Processor (UPP). It writes output in GRIB
which
> MET can easily handle. Why pinterp output could work fine for
precip,
> temperature, and dewpoint, MET won't be able to process the winds
since
> they're defined on the staggered dimension. I realize that running
UPP,
> yet another tool to compile and script up, can be a hassle. But I
think
> it'll be less work in the long run.
>
> But as for your specific error from Point-Stat, I suspect that'll be
easy
> to fix. In your Point-Stat config file, try using:
> name = "T2";
> level = [ "(0,*,*)" ];
>
> I often like plotting the data first:
> met-5.2/bin/plot_data_plane \
> ../../../P_INTERP/preproc/ndown/linout/lin/day1/wrfout_
> d01_2016-08-12_12:00:00_PLEV
> \
> T2.ps \
> 'name="T2"; level="(0,*,*)";'
>
> Hopefully that'll create a PostScript plot of your data.
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
>
> On Tue, Feb 7, 2017 at 7:27 PM, dawsonmattg at gmail.com via RT <
> met_help at ucar.edu> wrote:
>
>
> Tue Feb 07 19:27:38 2017: Request 79384 was acted upon.
> Transaction: Ticket created by dawsonmattg at gmail.com
> Queue: met_help
> Subject: Point Stat help
> Owner: Nobody
> Requestors: dawsonmattg at gmail.com
> Status: new
> Ticket <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79384
>
>
>
> Hello MET help,
>
> I’m going to go ahead and apologize for all the information
in
> this email, but hopefully it will help you better diagnose what the
best
> way for me to move forward is. As part of my research I generated 12
> different WRF runs over the same week using the same I.C.s and
B.C.s, and
> am currently in the process of comparing them against real world
> observations to see which config worked the best. I am primary
concerned
> with comparing precip, surface temp/dewpoint, and surface winds.
>
> The first tool I have tried to use has been the point stat
tool. I
> am using your met-5.2_bugfix package and did not find any errors
> while/after compiling and made sure the test files, like
> test_point_stat.sh, all work. The data I am using is as follows:
>
>
> Instead of downloading prepbufer files and converting
them
> with the PB2NC tool, I just used the UCAR site to do it for me (
>
http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_subset.php?_da=y
> <http://rda.ucar.edu/datasets/ds337.0/index.html#forms/337_
> subset.php?_da=y>)
> Request Detail:
> Date Limits : 2016-08-12 00:00 2016-08-20 06:00
> NCEP Verification Regions : SEC
> Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR
PRMSL
> PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT
QKSWND
> SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
> Quality Mark Threshold : 9
> File Compression : gz
> Data Output Format : NETCDF
>
>
>
> To convert my WRF data into a readable format I used
P_Interp. I
> am now realizing this might not be the best way forward, but seemed
the
> easiest to set up as I had to offload all my model output to a
different
> cluster that I did not configure WRF on. I have been a bit confused
as
> P_Interp says it can unstager data to pressure levels, but on your
website
> it says that P_Interp cannot onstager data (at least for use with
MODE and
> other tools). Either way do you think I should try use a different
> pre-processing software to unpack my WRF data or will P_Interp be
> sufficient to compare precip, surface temp/dewpoint and winds?
>
>
>
>
> When I run my file PointStat.sh using the attached
> PointStatConfig1 file, I get the following data error message:
>
> *** Running Point-Stat on prepbuffer files ***
> DEBUG 1: Default Config File: /marge/r0/mdawson/met/met-5.2_
> bugfix/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: config/PointStatConfig
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1
> DEBUG 1: Forecast File: ../../../P_INTERP/preproc/
> ndown/linout/lin/day1/wrfout_d01_2016-08-12_12:00:00_PLEV
> DEBUG 1: Observation File: ../data/prepbuffer/12/prepbufr
> .gdas.225564.2016081200.nc
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Reading data for T2(*,*,0).
> WARNING:
> WARNING: PinterpFile::data(NcVar *, const LongArray &, DataPlane &,
double
> &) const -> star found in bad slot
> WARNING:
> ERROR :
> ERROR : PinterpFile::valid_time(int) const -> range check error
> ERROR :
>
>
> Looking at the ncdump P_Interp File, T2 (2 meter temperature shows):
> float T2(Time, south_north, west_east) ;
> T2:FieldType = 104 ;
> T2:MemoryOrder = "XY " ;
> T2:description = "TEMP at 2 M" ;
> T2:units = "K" ;
> T2:stagger = "" ;
> T2:coordinates = "XLONG XLAT XTIME" ;
> T2:missing_value = 1.e+36f ;
>
> I am not sure if the issue is that P_Interp is not properly
extracting
> this information, or If I just need to change my PointStatConfig1
file.
>
>
> Thanks!
>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: Dawsonmattg at gmail.com <mailto:Dawsonmattg at gmail.com
> <Dawsonmattg at gmail.com>>
> Cell: (904)-333-5427 <(904)%20333-5427>
>
> On Feb 7, 2017, at 11:49 AM, Thomas Cram <tcram at ucar.edu <mailto:
>
> tcram at ucar.edu>> wrote:
>
>
> Hi Matthew,
>
> I recommend contacting MET support (cc'd here). It's possible you
>
> should be using the PrepBUFR data instead of the NetCDF data in MET,
but
> having no experience using MET, I am merely speculating on this.
MET
> support should be able to help you out.
>
>
> Good luck,
> - Tom
>
> On Tue, Feb 7, 2017 at 9:27 AM, Dawson, Matthew
<dawsonmattg at gmail.com
>
> <mailto:dawsonmattg at gmail.com <dawsonmattg at gmail.com>>> wrote:
>
> Hey Thomas
>
> I was able to get the data download with no issues, however I have
been
>
> having issues with actually using that data in MET. I am trying to
compare
> it to some WRF output (used P-Interp to convert into a MET readable
> format), but the PointStatConfig file keeps having issues (I’m not
sure I
> filled it out correctly). Anyways I was wondering if you, or anyone
> happened to know of an online resource, or even someone who had a
> configuration set up for comparing data against WRF data so I can
compare
> what I have against there config files and hopefully figure out
where I am
> going wrong. I’ve been looking through the MET user guide but
haven’t found
> a solution yet. Thanks!
>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: mgd08 at my.fsu.edu <mailto:mgd08 at my.fsu.edu <mgd08 at my.fsu.edu>>
> Cell: (904)-333-5427 <(904)%20333-5427> <tel:%28904%29-333-5427
> <%28904%29-333-5427>>
>
> On Jan 24, 2017, at 1:26 PM, tcram at ucar.edu <mailto:tcram at ucar.edu
> <tcram at ucar.edu>>
>
> wrote:
>
>
> Your subset request for NCEP ADP Global Upper Air and Surface
Weather
>
> Observations has completed.
>
> Please login to the NCAR RDA server at http://rda.ucar.edu <
>
> http://rda.ucar.edu/>, then download your files from the
>
> following URL:
>
> http://rda.ucar.edu/#dsrqst/DAWSON225564/ <
>
> http://rda.ucar.edu/#dsrqst/DAWSON225564/>
>
>
> Request ID: DAWSON225564
>
> Request Detail:
> Date Limits : 2016-08-12 00:00 2016-08-20 06:00
> NCEP Verification Regions : SEC
> Parameters : SPFH TMP HGT UGRD VGRD DPT WIND RH MIXR
>
> PRMSL
>
> PREPBUFR Message Types : ADPUPA SFCSHP AIRCAR SPSSMI AIRCFT
QKSWND
>
> SATWND RASSDA PROFLR WDSATR VADWND ASCATW ADPSFC
>
> Quality Mark Threshold : 9
> File Compression : gz
> Data Output Format : NETCDF
>
>
> The "rda-request-manager" command line tool provides an additional
>
> option for users to download
>
> request output files on unix based systems. The "rda-request-
manager"
>
> tool can be accessed at:
>
>
> http://rda.ucar.edu/#apps <http://rda.ucar.edu/#apps>
>
> The data provided in your data request are a subset of the NCAR RDA
>
> dataset ds337.0 --
>
> 'NCEP ADP Global Upper Air and Surface Weather Observations
(PREPBUFR
>
> format), May 1997 - Continuing'. Please see
http://rda.ucar.edu/datasets/
> ds337.0/ <http://rda.ucar.edu/datasets/ds337.0/> for more
information.
>
>
> Your data will remain on our system for 5 days. If this is not
>
> sufficient time for you to retrieve
>
> your data, please let me know as soon as possible, so that I can
>
> prevent the data files from being
>
> purged too soon.
>
> If you have any questions related to this data request, please let
me
>
> know by replying to this
>
> email.
>
> Sincerely,
>
> Thomas Cram
> NCAR/CISL/Data Support Section
> Phone: (303)-497-1217 <(303)%20497-1217> <tel:%28303%29-497-1217
> <%28303%29-497-1217>>
> Email: tcram at ucar.edu <mailto:tcram at ucar.edu <tcram at ucar.edu>>
> Web: http://rda.ucar.edu <http://rda.ucar.edu/>
>
>
>
>
>
> --
> Thomas Cram
> NCAR / CISL / DSS
> tel: +1-303-497-1217 <(303)%20497-1217>
> e-mail: tcram at ucar.edu <mailto:tcram at ucar.edu <tcram at ucar.edu>>
> web: rda.ucar.edu <http://rda.ucar.edu/>
>
>
> Matthew G. Dawson, Capt, USAF
> AFIT Student, Civilian Institution Program
> Email: mgd08 at my.fsu.edu
> Cell: (904)-333-5427 <(904)%20333-5427>
>
>
------------------------------------------------
More information about the Met_help
mailing list