1NCRCAT(1)                   General Commands Manual                  NCRCAT(1)
2
3
4

NAME

6       ncrcat - netCDF Record Concatenator
7

SYNTAX

9       ncrcat  [-3]  [-4]  [-5]  [-6] [-7] [-A] [--bfr sz_byt] [-C] [-c] [--cb
10       y1,y2,m1,m2,tpd] [--cmp cmp_sng] [--cnk_byt sz_byt] [--cnk_csh  sz_byt]
11       [--cnk_dmn  nm,sz_lmn]  [--cnk_map  map]  [--cnk_min sz_byt] [--cnk_plc
12       plc]  [--cnk_scl  sz_lmn][-D  dbg_lvl]  [-d  dim,[   min][,[   max]][,[
13       stride[[,[   subcycle[[,[   interleave]]]]]]  [-F]  [--fl_fmt=fmt]  [-G
14       gpe_dsc] [-g grp[,...]]  [--glb  att_name=  att_val]]  [-h]  [--hdr_pad
15       sz_byt] [-L dfl_lvl] [-l path] [--mro] [--msa] [-n loop] [--no_cll_msr]
16       [--no_frm_trm] [--no_tmp_fl] [-O] [-p path] [--ppc var1[,  var2[,...]]=
17       prc]]  [-R]  [-r]  [--ram_all] [--rec_apn] [-t thr_nbr] [--uio] [--unn]
18       [-v var[,...]]  [-X box] [-x] input-files output-file
19

DESCRIPTION

21       ncrcat concatenates record variables across an arbitrary number of  in‐
22       put  files.   The  final  record dimension is by default the sum of the
23       lengths of the record dimensions in the input files.
24
25       Input files may vary in size, but each must have  a  record  dimension.
26       The  record  coordinate, if any, should be monotonic (or else non-fatal
27       warnings may be generated).  Hyperslabs of the record  dimension  which
28       include  more  than  one file are handled correctly.  ncra supports the
29       stride argument to the -d hyperslab option  for  the  record  dimension
30       only, stride is not supported for non-record dimensions.
31
32       ncrcat  applies  special  rules  to  ARM  convention time fields (e.g.,
33       time_offset).
34

EXAMPLES

36       Concatenate files 85.nc, 86.nc,  ...  89.nc along the record dimension,
37       and store the results in 8589.nc:
38              ncrcat 85.nc 86.nc 87.nc 88.nc 89.nc 8589.nc
39              ncrcat 8[56789].nc 8589.nc
40              ncrcat -n 5,2,1 85.nc 8589.nc
41       These three methods produce identical answers.
42
43       Assume  the files 85.nc, 86.nc,  ...  89.nc each contain a record coor‐
44       dinate time of length 12 defined such that the third  record  in  86.nc
45       contains  data  from  March  1986, etc.  NCO knows how to hyperslab the
46       record dimension across files.  Thus, to concatenate data  from  Decem‐
47       ber, 1985--February, 1986:
48              ncrcat -d time,11,13 85.nc 86.nc 87.nc 8512_8602.nc
49              ncrcat -F -d time,12,14 85.nc 86.nc 87.nc 8512_8602.nc
50       The  file  87.nc  is  superfluous, but does not cause an error.  The -F
51       turns on the Fortran (1-based) indexing convention.
52
53       The following uses the stride option to concatenate all the March  tem‐
54       perature data from multiple input files into a single output file
55              ncrcat  -F  -d  time,3,,12  -v  temperature  85.nc  86.nc  87.nc
56              858687_03.nc
57
58       Assume the time coordinate is incrementally numbered such that January,
59       1985  =  1  and  December, 1989 = 60.  Assuming ??  only expands to the
60       five desired files, the following concatenates June, 1985--June, 1989:
61              ncrcat -d time,6.,54. ??.nc 8506_8906.nc
62
63

CAVEAT

65       ncrcat does not re-scale packed  data  (i.e.,  data  stored  using  the
66       scale_factor and add_offset attributes recommended by the Unidat and CF
67       conventions.  ncrcat just copies  the  data  directly  from  the  input
68       files.   It  copies  the  relevant  metadata  (i.e.,  scale_factor  and
69       add_offset attributes) from the  first  file.   Concatenating  multiple
70       datasets  packed with different scales is beyond its capabilities (con‐
71       catenating data packed with the same scales  in  multiple  files  works
72       fine).  The workaround for cases where the scales change among files is
73       to first unpack the data in all the file using ncpdq, then to  concate‐
74       nate  the  unpacked data using ncrcat, and finally to repack the result
75       using ncpdq.
76
77

AUTHOR

79       NCO manual pages written by Charlie Zender and originally formatted  by
80       Brian Mays.
81
82

REPORTING BUGS

84       Report bugs to <http://sf.net/bugs/?group_id=3331>.
85
86
88       Copyright © 1995-present Charlie Zender
89       This is free software; see the source for copying conditions.  There is
90       NO warranty; not even for MERCHANTABILITY or FITNESS FOR  A  PARTICULAR
91       PURPOSE.
92
93

SEE ALSO

95       The full documentation for NCO is maintained as a Texinfo manual called
96       the NCO Users Guide.  Because NCO is mathematical in nature, the  docu‐
97       mentation  includes  TeX-intensive  portions not viewable on character-
98       based displays.  Hence the only complete and authoritative versions  of
99       the NCO Users Guide are the PDF (recommended), DVI, and Postscript ver‐
100       sions at <http://nco.sf.net/nco.pdf>, <http://nco.sf.net/nco.dvi>,  and
101       <http://nco.sf.net/nco.ps>,  respectively.   HTML  and XML versions are
102       available         at          <http://nco.sf.net/nco.html>          and
103       <http://nco.sf.net/nco.xml>, respectively.
104
105       If  the  info and NCO programs are properly installed at your site, the
106       command
107
108              info nco
109
110       should give you access to the complete manual, except for  the  TeX-in‐
111       tensive portions.
112
113       ncap(1), ncap2(1), ncatted(1), ncbo(1), ncclimo(1), nces(1), ncecat(1),
114       ncflint(1), ncks(1), nco(1), ncpdq(1), ncra(1), ncrcat(1),  ncremap(1),
115       ncrename(1), ncwa(1)
116
117

HOMEPAGE

119       The NCO homepage at <http://nco.sf.net> contains more information.
120
121
122
123                                                                     NCRCAT(1)
Impressum