NAME

       ncecat - netCDF Ensemble Concatenator

SYNTAX

       ncecat  [-3]  [-4]  [-5]  [-6] [-7] [-A] [--bfr sz_byt][-C][-c] [--cmp cmp_sng] [--cnk_byt
       sz_byt][--cnk_csh  sz_byt][--cnk_dmn  nm,sz_lmn]  [--cnk_map   map]   [--cnk_min   sz_byt]
       [--cnk_plc   plc]   [--cnk_scl   sz_lmn][-D   dbg_lvl]   [-d  dim,[  min][,[  max]]]  [-F]
       [--fl_fmt=fmt] [-G gpe_dsc] [-g grp[,...]]  [--gag] [--glb att_name= att_val]]  [-H]  [-h]
       [--hdr_pad  sz_byt][--hpss_try]  [-L  dfl_lvl]  [-l  path]  [-M] [--mrd] [--msa] [-n loop]
       [--no_cll_msr] [--no_frm_trm] [--no_tmp_fl] [-O]  [-p  path]  [--ppc  var1[,  var2[,...]]=
       prc]]  [-R]  [-r] [--ram_all] [-t thr_nbr] [-u ulm_nm] [--uio] [--unn] [-v var[,...]]  [-X
       box] [-x] input-files output-file

DESCRIPTION

       ncecat concatenates an arbitrary number of input files into a single output  file.   Input
       files  are  glued together by creating a record dimension in the output file.  Input files
       must be the same size.  Each input file is stored consecutively as a single record in  the
       output  file.   Each variable (except coordinate variables) in each input file becomes one
       record  in  the  same  variable  in  the  output  file.   Coordinate  variables  are   not
       concatenated, they are instead simply copied from the first input file to the output-file.
       Thus, the size of the output file is the sum of the sizes of the input files.

       Consider five realizations, 85a.nc, 85b.nc,...  85e.nc of 1985 predictions from  the  same
       climate  model.   Then  ncecat 85?.nc 85_ens.nc glues the individual realizations together
       into the single file, 85_ens.nc.  If an input variable was dimensioned  [  lat,  lon],  it
       will  have  dimensions [ record, lat, lon] in the output file.  A restriction of ncecat is
       that the hyperslabs of the processed variables  must  be  the  same  from  file  to  file.
       Normally  this  means all the input files are the same size, and contain data on different
       realizations of the same variables.

EXAMPLES

       Consider a model experiment which generated five realizations of one  year  of  data,  say
       1985.   You  can imagine that the experimenter slightly perturbs the initial conditions of
       the problem before generating each new solution.  Assume each  file  contains  all  twelve
       months  (a seasonal cycle) of data and we want to produce a single file containing all the
       seasonal cycles.  Here the numeric filename suffix denotes the experiment number (not  the
       month):
              ncecat 85_01.nc 85_02.nc 85_03.nc 85_04.nc 85_05.nc 85.nc
              ncecat 85_0[1-5].nc 85.nc
              ncecat -n 5,2,1 85_01.nc 85.nc
       These three commands produce identical answers.  The output file, 85.nc, is five times the
       size as a single input-file.  It contains 60 months of data (which might or might  not  be
       stored in the record dimension, depending on the input files).

AUTHOR

       NCO manual pages written by Charlie Zender and originally formatted by Brian Mays.

REPORTING BUGS

       Report bugs to <http://sf.net/bugs/?group_id=3331>.

COPYRIGHT

       Copyright © 1995-present Charlie Zender
       This  is  free software; see the source for copying conditions.  There is NO warranty; not
       even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

SEE ALSO

       The full documentation for NCO is maintained as a Texinfo  manual  called  the  NCO  Users
       Guide.   Because  NCO  is mathematical in nature, the documentation includes TeX-intensive
       portions  not  viewable  on  character-based  displays.   Hence  the  only  complete   and
       authoritative  versions  of  the  NCO  Users  Guide  are  the  PDF (recommended), DVI, and
       Postscript  versions  at  <http://nco.sf.net/nco.pdf>,  <http://nco.sf.net/nco.dvi>,   and
       <http://nco.sf.net/nco.ps>,   respectively.   HTML  and  XML  versions  are  available  at
       <http://nco.sf.net/nco.html> and <http://nco.sf.net/nco.xml>, respectively.

       If the info and NCO programs are properly installed at your site, the command

              info nco

       should give you access to the complete manual, except for the TeX-intensive portions.

       ncap2(1), ncatted(1), ncbo(1), ncclimo(1),  nces(1),  ncecat(1),  ncflint(1),  ncz2psx(1),
       ncks(1), nco(1), ncpdq(1), ncra(1), ncrcat(1), ncremap(1), ncrename(1), ncwa(1)

HOMEPAGE

       The NCO homepage at <http://nco.sf.net> contains more information.

                                                                                        NCECAT(1)