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][--cnk_byt
10       sz_byt][--cnk_csh   sz_byt][--cnk_dmn   nm,sz_lmn]   [--cnk_map    map]
11       [--cnk_min  sz_byt]  [--cnk_plc plc] [--cnk_scl sz_lmn][-D dbg_lvl] [-d
12       dim,[ min][,[ max]][,[ stride[[,[ subcycle]]]]] [-F] [--fl_fmt=fmt] [-G
13       gpe_dsc]  [-g  grp[,...]]   [--glb  att_name= att_val]] [-h] [--hdr_pad
14       sz_byt] [-L dfl_lvl] [-l path] [--mro] [--msa] [-n loop] [--no_cll_msr]
15       [--no_frm_trm]  [--no_tmp_fl] [-O] [-p path] [--ppc var1[, var2[,...]]=
16       prc]] [-R]  [-r]  [--ram_all]  [--rec_apn]  [-t  thr_nbr]  [--unn]  [-v
17       var[,...]]  [-X box] [-x] input-files output-file
18

DESCRIPTION

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

EXAMPLES

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

CAVEAT

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

AUTHOR

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

REPORTING BUGS

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

SEE ALSO

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

HOMEPAGE

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