[Met_help] new version of MET

John Halley Gotway johnhg at rap.ucar.edu
Wed Jul 9 08:48:56 MDT 2008


Xiaqiong,

Could you please send me the a sample input GRIB file and the corresponding output of PCP-Combine where you're seeing the problem?

I'd like to run them through MET and plot up the grids to see the difference.  Also, can you tell me what version of MET you're running?

Thanks,
John


Xiaqiong Zhou wrote:
> Dear John:
> After I run pcp_combine, the output netcdf file has different lat/lon grids 
> with  the input grib file.
> 
> I attached the grid information:
> Input grib file information (wrfprs_d01_00.ctl)
> output netcdf information (1) by using ncdump.
> 
>  Any problems when pcp_combine deal with user own defined grids?
> Thanks a lot.
> xiaqiong
> 
> ----- Original Message -----
> From: John Halley Gotway <johnhg at rap.ucar.edu>
> Date: Monday, July 7, 2008 9:03 am
> Subject: Re: [Met_help] new version of MET
> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
> Cc: met_help <met_help at ucar.edu>
> 
>  > Xiaqiong,
>  >
>  > METv1.1 is *almost* ready.  The code changes are finished,
>  > but we're still updating the User's Guide, which is distributed
>  > with the code.  We're planning to have it finished by the
>  > end of the week.
>  >
>  > In the meantime, you're welcome to use the latest beta version
>  > for METv1.1.  You can access it via:
>  > 
> ftp://ftp.rap.ucar.edu/incoming/irap/johnhg/METv1.1beta9.20080702.tar.gzYou'll 
> just need to copy over one of the sample Makefiles (for PGI, GNU, or IBM), 
> configure it to your local environment, and build it.
>  >
>  > We'll send out an email when METv1.1 is officially released with
>  > the updated documentation.
>  >
>  > Thanks,
>  > John
>  >
>  > Xiaqiong Zhou wrote:
>  > > Dear John:
>  > > Can I get the new version of MET now?
>  > > Best regards
>  > > xiaqiong
>  > >
>  > > ----- Original Message -----
>  > > From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > > Date: Thursday, June 12, 2008 10:40 am
>  > > Subject: Re: MASK_GRID and MASK_POLY
>  > > To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
>  > > Cc: met_help <met_help at ucar.edu>
>  > >
>  > >> Good question...
>  > >>
>  > >> In the Point-Stat and Grid-Stat tools, the "mask_grids" and
>  > >> "mask_polys" regions are used to define the areas over which
>  > >> you'd like to accumulate statistics.  The grids in
>  > >> "mask_grids" are simply used
>  > >> to define an area - there's no interpolation done or anything.
>  > >>
>  > >> If you'd like to compute statistics over the entire domain,
>  > >> rather than looking at subregions of the domain, it would
>  > >> probably be easiest to just create a lat/lon polyline that
>  > fully
>  > >> encompasses your
>  > >> grid.
>  > >>
>  > >> In MODE, the "mask_grid" and "mask_poly" regions are used to
>  > >> just zero out data that's outside those regions.  So
>  > >> objects will only be created inside those grid or polyline areas.
>  > >>
>  > >> You are correct that in order to define and use a NEW grid,
>  > >> you'd have to make code changes and then recompile - which
>  > >> you're welcome to do.  In the future, it would probably
>  > be
>  > >> a good idea to enable
>  > >> users to specify grids at runtime, rather than requiring them
>  > to
>  > >> recompile.  But in the mean time, in order to define a
>  > new
>  > >> grid, you'd need to edit one file:
>  > >> In METv1.0/lib/vx_data_grids/grid_defs.h:
>  > >> (1) add a new PlateCarreeData structure defining your grid
>  > >> (2) Increment the n_pc_grids_data value by one.
>  > >> (3) Add the name of the PlateCarreeData structure you defined
>  > in
>  > >> (1) to the end of the array for "pc_grids_data"
>  > >> And then do a "make clean" and rebuild MET.  If you do
>  > try
>  > >> this, please let me know how it goes.
>  > >>
>  > >> However, like I said, it'd probably be easier just to use a
>  > >> lat/lon polyline.  Look in the METv1.0/data/poly
>  > directory
>  > >> for examples.
>  > >>
>  > >> Hope that helps.
>  > >>
>  > >> John
>  > >>
>  > >>
>  > >> Xiaqiong Zhou wrote:
>  > >>> Hello John:
>  > >>> Sorry to bother you again.
>  > >>> I am confused about the MASK_GRID and MASK_POLY.
>  > >>> I interpolated my WRF-ARW output with Mercator grids to
>  > >> lat/lon projection. It almost cover the original domain,
>  > which
>  > >> is not one of those NCEP's pre-defined grids.
>  > >>> When  I run MET,  should  I  defining a
>  > >> new masking grid in MET and recompiling? How to add a new
>  > grid set?
>  > >>> Cannot I just define "MASK_POLY"?
>  > >>> xiaqiong zhou
>  > >>>
>  > >>> ----- Original Message -----
>  > >>> From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > >>> Date: Friday, June 6, 2008 1:12 pm
>  > >>> Subject: Re: [Met_help] Problem when compiling MET
>  > >>> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
>  > >>> Cc: met_help at ucar.edu
>  > >>>
>  > >>>> Xiaqiong,
>  > >>>>
>  > >>>> I'm sorry to say that currently MET does not read data on a
>  > >>>> Mercator projection.  It currently reads lat/lon,
>  > >>>> stereographic, and lambert conformal grids.  Reading
>  > >>>> Mercator grids is something that's
>  > >>>> been on our list of things to implement for a while, but we
>  > >>>> haven't gotten to it yet.  I'll bump it up on the
>  > >> priority list.
>  > >>>> As for problems with "copygb", could you send me a sample
>  > >> file
>  > >>>> and the copygb command that you're trying to execute? 
>  > >> I'd
>  > >>>> be really surprised if it were not able to read Mercator grids.
>  > >>>>
>  > >>>> I could get you a beta release of the new version but it
>  > >> still
>  > >>>> wouldn't read Mercator grids and the documentation has not
>  > >> yet
>  > >>>> been updated.
>  > >>>>
>  > >>>> John
>  > >>>>
>  > >>>>
>  > >>>> Xiaqiong Zhou wrote:
>  > >>>>> Hello John:
>  > >>>>> Thank you for your information.I  found the prep-BUFR
>  > >>>> dataset. It works for MET.
>  > >>>>> I am working in Hans Wang's group in NCAR now. They hope
>  > to
>  > >>>> get verification results before
>  > >>>>> the 9th WRF workshop.
>  > >>>>> There is another problem when MET read WRF-ARW output with
>  > >>>> Mercator projection.
>  > >>>>> COPYGB in the WRF post processing developed by NCEP likely
>  > >>>> cannot interpolate WRF-ARW output to user-defined grid.
>  > >>>>> How about your developing version of MET? Does it support
>  > >>>> Mercator projection? Is it possible for me to get the new
>  > >>>> version now?
>  > >>>>> Best regards
>  > >>>>> xiaqiong
>  > >>>>>
>  > >>>>> ----- Original Message -----
>  > >>>>> From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > >>>>> Date: Friday, June 6, 2008 12:41 pm
>  > >>>>> Subject: Re: [Met_help] Problem when compiling MET
>  > >>>>> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
>  > >>>>> Cc: met_help <met_help at ucar.edu>
>  > >>>>>
>  > >>>>>> Xiaqiong,
>  > >>>>>>
>  > >>>>>> The only sources of PREPBUFR data that I've used of are
>  > >> those
>  > >>>>>> posted on the MET Website:
>  > >>>>>>
>  > http://www.dtcenter.org/met/users/downloads/observation_data.php>>>>>> 
> However, there does appear to be PREPBUFR observation data
>  > >>>>>> available for the NCEP/NCAR reanalysis project:
>  > >>>>>> http://dss.ucar.edu/pub/reanalysis/
>  > >>>>>>
>  > >>>>>> The files named "prepqm..." (the first line of the table
>  > on
>  > >>>>>> http://dss.ucar.edu/pub/reanalysis/aval_ftyp.html) would
>  > be
>  > >>>> ones
>  > >>>>>> to try.  That data should be freely available once
>  > you
>  > >>>>>> register as a user.
>  > >>>>>>
>  > >>>>>> BUT - I've never tried this and it may or may not
>  > >> work. 
>  > >>>> If
>  > >>>>>> you do decide to try it, please let me know whether MET
>  > is
>  > >>>> able
>  > >>>>>> to read the data.
>  > >>>>>>
>  > >>>>>> Also, METv1.1 should be released within the next
>  > >> month. 
>  > >>>> It
>  > >>>>>> includes a tool called ASCII2NC which will allow you to
>  > >> used
>  > >>>>>> ASCII point observations in MET.  I don't know if
>  > that
>  > >>>> will
>  > >>>>>> help or not.
>  > >>>>>>
>  > >>>>>> Thanks,
>  > >>>>>> John
>  > >>>>>>
>  > >>>>>> Xiaqiong Zhou wrote:
>  > >>>>>>> Hello, John:
>  > >>>>>>> I have one more question. It is  about prepBUFR.
>  > >>>>>>> I only find the prepBUFR data  in 2008. Where can I
>  > >> get
>  > >>>>>> the data before 2008?
>  > >>>>>>> Best regards
>  > >>>>>>> xiaqiong  
>  > >>>>>>>
>  > >>>>>>> ----- Original Message -----
>  > >>>>>>> From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > >>>>>>> Date: Thursday, May 29, 2008 2:08 pm
>  > >>>>>>> Subject: Re: [Met_help] Problem when compiling MET
>  > >>>>>>> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>, met_help
>  > >>>>>> <met_help at ucar.edu>>
>  > >>>>>>>> Xiaqiong,
>  > >>>>>>>>
>  > >>>>>>>> Sorry that didn't work for you.  I'm really
>  > puzzled
>  > >> by
>  > >>>>>> that
>  > >>>>>>>> compiler error message and surprised that it didn't
>  > show
>  > >> up
>  > >>>>>> when
>  > >>>>>>>> compiling the other MET tools.
>  > >>>>>>>>
>  > >>>>>>>> To answer your questions...
>  > >>>>>>>>
>  > >>>>>>>> - We're currently working on METv1.1 and had hoped to
>  > >> have
>  > >>>> it
>  > >>>>>>>> released about a month ago.  However, we've had
>  > some
>  > >>>>>>>> setbacks and have decided that we will not include
>  > >> support
>  > >>>>>> for
>  > >>>>>>>> Grib2 in this release.
>  > >>>>>>>>       METv1.1 should be
>  > available
>  > >> no
>  > >>>> later than
>  > >>>>>> mid-July,
>  > >>>>>>>> but we're aiming for the end of June.
>  > >>>>>>>>
>  > >>>>>>>> - The list of things to finish up before releasing
>  > >> METv1.1
>  > >>>>>>>> includes figuring out 64-bit compatibility for BUFRLIB
>  > >> and
>  > >>>>>>>> making sure that it compiles on an IBM.  We'll be
>  > >>>>>> sending
>  > >>>>>>>> out an announcement when
>  > >>>>>>>> the new version is available for download.
>  > >>>>>>>>
>  > >>>>>>>> - The Point-Stat tool (and Grid-Stat and MODE tools)
>  > read
>  > >>>>>>>> gridded data in Grib1 format.  They also read the
>  > >>>> NetCDF
>  > >>>>>>>> output of the PCP-Combine tool, but not NetCDF
>  > >>>>>> generally. 
>  > >>>>>>>> We're working with the ARW
>  > >>>>>>>> WRF developers to enable MET to read the NetCDF output
>  > of
>  > >>>> the
>  > >>>>>>>> ARW post-processor tool in the next 12 months. 
>  > The
>  > >>>>>> current
>  > >>>>>>>> WRF Post-Processor (WPP) which works with both ARW and
>  > >> NMM
>  > >>>>>>>> generates output in
>  > >>>>>>>> Grib1.  We suggest running your WRF model output
>  > >>>> through
>  > >>>>>>>> WPP prior to running MET.
>  > >>>>>>>>
>  > >>>>>>>> Thanks,
>  > >>>>>>>> John
>  > >>>>>>>>
>  > >>>>>>>> Xiaqiong Zhou wrote:
>  > >>>>>>>>> John:
>  > >>>>>>>>> Thank for your quick reply.
>  > >>>>>>>>> I tried what you suggested, but I  get same error
>  > >>>>>>>> message. Since you mentioned this tool can not work on
>  > 64-
>  > >>>> bit
>  > >>>>>>>> machine, I will give up.
>  > >>>>>>>>> I have two more questions:
>  > >>>>>>>>> 1) When will the new version be released?  
>  > It
>  > >>>>>> will
>  > >>>>>>>> run on IBM, right?
>  > >>>>>>>>> 2)Does the point-stat tool only read GRIB format? how
>  > >>>> about
>  > >>>>>>>> NETCDF format?
>  > >>>>>>>>> Best regards
>  > >>>>>>>>> xiaqiong
>  > >>>>>>>>>
>  > >>>>>>>>> ----- Original Message -----
>  > >>>>>>>>> From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > >>>>>>>>> Date: Thursday, May 29, 2008 11:38 am
>  > >>>>>>>>> Subject: Re: [Met_help] Problem when compiling MET
>  > >>>>>>>>> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
>  > >>>>>>>>> Cc: met_help <met_help at ucar.edu>
>  > >>>>>>>>>
>  > >>>>>>>>>> Xiaqiong,
>  > >>>>>>>>>>
>  > >>>>>>>>>> No, I do not believe this error is due to compiling
>  > on
>  > >> a
>  > >>>> 64-
>  > >>>>>>>> bit
>  > >>>>>>>>>> machine.  You should be able to compile the
>  > >> "pb2nc"
>  > >>>>>> tool
>  > >>>>>>>> on
>  > >>>>>>>>>> a 64-bit machine, but when you actually run it,
>  > you'll
>  > >>>>>>>> encounter
>  > >>>>>>>>>> a runtime
>  > >>>>>>>>>> error similar to the following:
>  > >>>>>>>>>>      
>  > **************BUFR
>  > >> ARCHIVE
>  > >>>> LIBRARY
>  > >>>>>>>> ABORT*****************>>   BUFRLIB: OPENBF -
>  > >>>> FIRST
>  > >>>>>> 4
>  > >>>>>>>> BYTES READ FROM RECORD IN INPUT
>  > >>>>>>>>>> FILE CONNECTED TO UNIT  11 NOT 'BUFR', DOES NOT
>  > >>>>>> CONTAIN
>  > >>>>>>>>>> BUFR DATA
>  > >>>>>>>>>>      
>  > **************BUFR
>  > >> ARCHIVE
>  > >>>> LIBRARY
>  > >>>>>>>> ABORT*****************>>
>  > >>>>>>>>>> The error I'm seeing in your attached logfile seems
>  > odd
>  > >>>> to
>  > >>>>>>>>>> me.  I don't know while this error would show up
>  > >> for
>  > >>>>>>>>>> "pb2nc" and not the other MET tools.
>  > >>>>>>>>>> intermediate
>  > >>>>>>>>>> The compiler appears unable to find some common
>  > things
>  > >>>> that
>  > >>>>>>>> are
>  > >>>>>>>>>> defined in the "ctype.h" include file.  I
>  > searched
>  > >>>> on
>  > >>>>>>>> the
>  > >>>>>>>>>> internet for similar problems on RedHat linux, and I
>  > >> did
>  > >>>>>> find
>  > >>>>>>>>>> one thing we
>  > >>>>>>>>>> could try.  So please do the following:
>  > >>>>>>>>>> (1) Open up the file METv1.0/src/pb2nc/pb2nc.cc
>  > >>>>>>>>>> (2) Cut out line number 34: #include <ctype.h>
>  > >>>>>>>>>> (3) And insert that line after line number 42:
>  > #include
>  > >>>>>>>> <unistd.h>>> (4) Save and close the file.
>  > >>>>>>>>>> (5) Try to rebuild MET.
>  > >>>>>>>>>>
>  > >>>>>>>>>> The order of the include files really SHOULD NOT
>  > >> matter,
>  > >>>>>> but
>  > >>>>>>>>>> let's see if this has any impact.  Please let me
>  > >>>> know
>  > >>>>>>>> what
>  > >>>>>>>>>> happens.
>  > >>>>>>>>>> Ultimately, this is a minor point since you will be
>  > >>>> unable
>  > >>>>>> to
>  > >>>>>>>>>> run the PB2NC tool on a 64-bit machine anyway.
>  > >>>>>>>>>>
>  > >>>>>>>>>> John
>  > >>>>>>>>>>
>  > >>>>>>>>>> Xiaqiong Zhou wrote:
>  > >>>>>>>>>>> Hello, John:
>  > >>>>>>>>>>> Thank you for your information.
>  > >>>>>>>>>>> I can get 6 tools (grid_stat mode mode_analysis
>  > >>>>>> pcp_combine
>  > >>>>>>>>>> point_stat
>  > >>>>>>>>>>> vsdb_analysis) except PB2NC tool.
>  > >>>>>>>>>>> The compiling output is attached. Is it due to my 64-
>  > >> bit
>  > >>>>>> machine?>>>>> Thanks again
>  > >>>>>>>>>>> Xiaqiong
>  > >>>>>>>>>>>
>  > >>>>>>>>>>> ----- Original Message -----
>  > >>>>>>>>>>> From: John Halley Gotway <johnhg at rap.ucar.edu>
>  > >>>>>>>>>>> Date: Wednesday, May 28, 2008 12:20 pm
>  > >>>>>>>>>>> Subject: Re: [Met_help] Problem when compiling MET
>  > >>>>>>>>>>> To: Xiaqiong Zhou <xiaqiong at hawaii.edu>
>  > >>>>>>>>>>> Cc: met_help at ucar.edu
>  > >>>>>>>>>>>
>  > >>>>>>>>>>>       > Xiaqiong,
>  > >>>>>>>>>>>       >
>  > >>>>>>>>>>>       > I believe that
>  > you're
>  > >>>> encountering one
>  > >>>>>> of the
>  > >>>>>>>> issues already
>  > >>>>>>>>>>>       > included on
>  > the "known
>  > >> issue" page.
>  > >>>>>>>>>>>       >
>  > >>>>>>>>>>>       > Please take a
>  > look here:
>  > >>>>>>>>>>>       >
>  > >>
>  > http://www.dtcenter.org/met/users/support/known_issues/METv1.0/index.phpFor
>  > >>>>>>>>>>> the line: "Compilation Error in the vx_met_util Library"
>  > >>>>>>>>>>>       >
>  > >>>>>>>>>>>       > And update the
>  > version
>  > >> of the file
>  > >>>>>>>>>>>       >
>  > >>>> METv1.0/lib/vx_met_util/Makefile with
>  > >>>>>> the one
>  > >>>>>>>> posted
>  > >>>>>>>>>> on the
>  > >>>>>>>>>>>       > known issues page.
>  > >>>>>>>>>>>       >
>  > >>>>>>>>>>>       > Please let me
>  > know if
>  > >> you run
>  > >>>> into any
>  > >>>>>> more
>  > >>>>>>>> problems.>>>   >
>  > >>>>>>>>>>>       > Thanks,
>  > >>>>>>>>>>>       > John Halley-Gotway
>  > >>>>>>>>>>>       > johnhg at ucar.edu
>  > >>>>>>>>>>>       >
>  > >>>>>>>>>>>       > Xiaqiong Zhou wrote:
>  > >>>>>>>>>>>       > > Hello, MET:
>  > >>>>>>>>>>>       > >  I have
>  > a
>  > >> problem when
>  > >>>>>> compiling MET.
>  > >>>>>>>>>>>       > >  I am
>  > using x86-
>  > >> 64
>  > >>>> GNU/linux
>  > >>>>>> with
>  > >>>>>>>> f77/gcc.
>  > >>>>>>>>>>>       > > The error is
>  > from
>  > >>>> read_grib.c.
>  > >>>>>> Please see
>  > >>>>>>>> the following
>  > >>>>>>>>>>>       > information.
>  > Is it a
>  > >> problem
>  > >>>> due
>  > >>>>>> to 
>  > >>>>>>>> netcdf 
>  > >>>>>>>>>> library?>  > I use f77 to install netcdf.
>  > >>>>>>>>>>>       > >  Thanks
>  > >>>>>>>>>>>       > >  Kate
>  > >>>>>>>>>>>       > >  gcc
>  > >> read_grib.cc -g -
>  > >>>> Wall -
>  > >>>>>> Wshadow -
>  > >>>>>>>>>> static  -c -I..
>  > >>>>>>>>>>>       > -
>  > >>>> I/usbdisk4jylee/xiaqiong/lib/gsl-1.11
>  > >>>>>>>>>>>       > >  In
>  > file
>  > >> included from
>  > >>>>>>>>>> ../vx_met_util/vx_met_util.h:21,>  >
>  > >>>>>>>>>>>                        from read_grib.cc:20:
>  > >>>>>>>>>>>       > > 
>  > >>
>  > ../vx_met_util/read_pcp_combine_netcdf.h:16:21:>>>   >
>  > >>>>>>>> netcdf.hh: No such file or directory
>  > >>>>>>>>>>>       > >  In
>  > file
>  > >> included from
>  > >>>>>>>>>> ../vx_met_util/vx_met_util.h:21,>  >
>  > >>>>>>>>>>>                        from read_grib.cc:20:
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25:
>  > >>>>>>>>>> warning:>  > `read_pcp_combine_netcdf'
>  > initialized
>  > >>>> and
>  > >>>>>>>>>> declared `extern'
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > variable or
>  > field
>  > >>>>>> `read_pcp_combine_netcdf'
>  > >>>>>>>> declared void
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > `NcFile' was
>  > not
>  > >> declared in
>  > >>>> this scope
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ',' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before '&' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ',' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before '&' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ',' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:25: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before "int"
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:26: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before '&' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:26: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ',' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:26: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before '&' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:26: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ',' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:27: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before '&' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:27: error:
>  > >>>>>>>>>>>       > expected
>  > primary-
>  > >> expression
>  > >>>> before ')' token
>  > >>>>>>>>>>>       > > 
>  > >>>>>>>> ../vx_met_util/read_pcp_combine_netcdf.h:27: error:
>  > >>>>>>>>>>>       > initializer
>  > expression
>  > >> list
>  > >>>> treated as
>  > >>>>>>>> compound expression
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_wrfdata/vx_wrfdata.h:41:
>  > >>>>>>>> warning:
>  > >>>>>>>>>> 'wrfdata_magic'>  > defined but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_wrfdata/vx_wrfdata.h:64:
>  > >>>>>> warning:>>>>>    > 'thresh_type_str'
>  > defined
>  > >>>> but
>  > >>>>>> not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_wrfdata/vx_wrfdata.h:85:
>  > >>>>>> warning:>>>>>    > 'step_direction_str'
>  > >>>> defined
>  > >>>>>> but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:23:
>  > >>>>>>>> warning:
>  > >>>>>>>>>> 'na_str' defined
>  > >>>>>>>>>>>       > but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:26:
>  > >>>>>> warning:>>>>>    > 'all_msg_typ_str'
>  > defined
>  > >>>> but
>  > >>>>>> not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:30:
>  > >>>>>>>> warning: 'anyair_str'
>  > >>>>>>>>>>>       > defined but
>  > not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:31:
>  > >>>>>> warning:>>>>>    > 'anyair_msg_typ_str'
>  > >>>> defined
>  > >>>>>> but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:32:
>  > >>>>>>>> warning: 'anysfc_str'
>  > >>>>>>>>>>>       > defined but
>  > not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:33:
>  > >>>>>> warning:>>>>>    > 'anysfc_msg_typ_str'
>  > >>>> defined
>  > >>>>>> but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:34:
>  > >>>>>>>> warning: 'onlysf_str'
>  > >>>>>>>>>>>       > defined but
>  > not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:35:
>  > >>>>>> warning:>>>>>    > 'onlysf_msg_typ_str'
>  > >>>> defined
>  > >>>>>> but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:38:
>  > >>>>>> warning:>>>>>    > 'all_interp_mthd_str'
>  > >>>> defined
>  > >>>>>> but not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/constants.h:49:
>  > >>>>>>>> warning: 'mthd_str'
>  > >>>>>>>>>>>       > defined but
>  > not used
>  > >>>>>>>>>>>       > > 
>  > >>>> ../vx_met_util/met_stats.h:20:
>  > >>>>>>>> warning:
>  > >>>>>>>>>> 'hdr_fmt_str'>  > defined but not used
>  > >>>>>>>>>>>       > > 
>  > >>>>>> ../vx_grib_classes/grib_strings.h:20:
>  > >>>>>>>> warning:>>>   > 'missing_str' defined but not used
>  > >>>>>>>>>>>       > > 
>  > >>>>>> ../vx_grib_classes/grib_strings.h:62:
>  > >>>>>>>> warning:>>>   > 'grib_code_list' defined but
>  > >> not used
>  > >>>>>>>>>>>       > > 
>  > >>>>>> ../vx_grib_classes/grib_strings.h:94:
>  > >>>>>>>> warning:>>>   > 'grib_code_list_str' defined
>  > >> but
>  > >>>>>> not used
>  > >>>>>>>>>>>       > > 
>  > >>>>>> ../vx_grib_classes/grib_strings.h:391:
>  > >>>>>>>> warning:>>>   > 'grib_level_list_str' defined
>  > >> but
>  > >>>>>> not used
>  > >>>>>>>>>>>       > > 
>  > make[3]: ***
>  > >>>> [read_grib.o]
>  > >>>>>> Error 1
>  > >>>>>>>>>>>       > > 
>  > make[2]: ***
>  > >>>> [vx_met_util_all]
>  > >>>>>> Error 2
>  > >>>>>>>>>>>       > > 
>  > make[1]: ***
>  > >> [libs]
>  > >>>> Error 2
>  > >>>>>>>>>>>       > >  make:
>  > ***
>  > >> [all] Error 2
>  > >>>>>>>>>>>       > >
>  > >>>>>>>>>>>       > >
>  > >>>>>>>>>>>       > >
>  > >>>>>>>>>>>       > > -------------
>  > --------
>  > >> --------
>  > >>>> --------
>  > >>>>>> --------
>  > >>>>>>>> --------
>  > >>>>>>>>>> ----------
>  > >>>>>>>>>>>       > ---------
>  > >>>>>>>>>>>       > >
>  > >>>>>>>>>>>       > >
>  > >>
>  > _______________________________________________>>>>>    > > Met_help mailing list
>  > >>>>>>>>>>>       > >
>  > Met_help at mailman.ucar.edu>>>>>>>>>>>       > >
>  > >>>>>> http://mailman.ucar.edu/mailman/listinfo/met_help>
>  > >>>
>  > >
>  > >
>  > > ---------------------------------------------------------------
>  > ---------
>  > >
>  > > _______________________________________________
>  > > Met_help mailing list
>  > > Met_help at mailman.ucar.edu
>  > > http://mailman.ucar.edu/mailman/listinfo/met_help


More information about the Met_help mailing list