1NCRCAT(1) General Commands Manual NCRCAT(1)
2
6 ncrcat - netCDF Record Concatenator
7
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] [-h]
15 [--hdr_pad sz_byt] [-L dfl_lvl] [-l path] [--mro] [--msa] [-n loop]
16 [--no_cll_msr] [--no_frm_trm] [--no_tmp_fl] [-O] [-p path] [--ppc
17 var1[, var2[,...]]= prc]] [-R] [-r] [--ram_all] [--rec_apn] [-t
18 thr_nbr] [--uio] [--unn] [-v var[,...]] [-X box] [-x] input-files out‐
19 put-file
20
22 ncrcat concatenates record variables across an arbitrary number of in‐
23 put files. The final record dimension is by default the sum of the
24 lengths of the record dimensions in the input files.
25 Input files may vary in size, but each must have a record dimension.
27 The record coordinate, if any, should be monotonic (or else non-fatal
28 warnings may be generated). Hyperslabs of the record dimension which
29 include more than one file are handled correctly. ncra supports the
30 stride argument to the -d hyperslab option for the record dimension
31 only, stride is not supported for non-record dimensions.
32 ncrcat applies special rules to ARM convention time fields (e.g.,
34 time_offset).
35
37 Concatenate files 85.nc, 86.nc, ... 89.nc along the record dimension,
38 and store the results in 8589.nc:
39 ncrcat 85.nc 86.nc 87.nc 88.nc 89.nc 8589.nc
40 ncrcat 8[56789].nc 8589.nc
41 ncrcat -n 5,2,1 85.nc 8589.nc
42 These three methods produce identical answers.
43 Assume the files 85.nc, 86.nc, ... 89.nc each contain a record coor‐
45 dinate time of length 12 defined such that the third record in 86.nc
46 contains data from March 1986, etc. NCO knows how to hyperslab the
47 record dimension across files. Thus, to concatenate data from Decem‐
48 ber, 1985--February, 1986:
49 ncrcat -d time,11,13 85.nc 86.nc 87.nc 8512_8602.nc
50 ncrcat -F -d time,12,14 85.nc 86.nc 87.nc 8512_8602.nc
51 The file 87.nc is superfluous, but does not cause an error. The -F
52 turns on the Fortran (1-based) indexing convention.
53 The following uses the stride option to concatenate all the March tem‐
55 perature data from multiple input files into a single output file
56 ncrcat -F -d time,3,,12 -v temperature 85.nc 86.nc 87.nc
57 858687_03.nc
58 Assume the time coordinate is incrementally numbered such that January,
60 1985 = 1 and December, 1989 = 60. Assuming ?? only expands to the
61 five desired files, the following concatenates June, 1985--June, 1989:
62 ncrcat -d time,6.,54. ??.nc 8506_8906.nc
63
66 ncrcat does not re-scale packed data (i.e., data stored using the
67 scale_factor and add_offset attributes recommended by the Unidat and CF
68 conventions. ncrcat just copies the data directly from the input
69 files. It copies the relevant metadata (i.e., scale_factor and
70 add_offset attributes) from the first file. Concatenating multiple
71 datasets packed with different scales is beyond its capabilities (con‐
72 catenating data packed with the same scales in multiple files works
73 fine). The workaround for cases where the scales change among files is
74 to first unpack the data in all the file using ncpdq, then to concate‐
75 nate the unpacked data using ncrcat, and finally to repack the result
76 using ncpdq.
77
80 NCO manual pages written by Charlie Zender and originally formatted by
81 Brian Mays.
82
85 Report bugs to <http://sf.net/bugs/?group_id=3331>.
86
89 Copyright © 1995-present Charlie Zender
90 This is free software; see the source for copying conditions. There is
91 NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
92 PURPOSE.
93
96 The full documentation for NCO is maintained as a Texinfo manual called
97 the NCO Users Guide. Because NCO is mathematical in nature, the docu‐
98 mentation includes TeX-intensive portions not viewable on character-
99 based displays. Hence the only complete and authoritative versions of
100 the NCO Users Guide are the PDF (recommended), DVI, and Postscript ver‐
101 sions at <http://nco.sf.net/nco.pdf>, <http://nco.sf.net/nco.dvi>, and
102 <http://nco.sf.net/nco.ps>, respectively. HTML and XML versions are
103 available at <http://nco.sf.net/nco.html> and
104 <http://nco.sf.net/nco.xml>, respectively.
105 If the info and NCO programs are properly installed at your site, the
107 command
108 info nco
110 should give you access to the complete manual, except for the TeX-in‐
112 tensive portions.
113 ncap2(1), ncatted(1), ncbo(1), ncclimo(1), nces(1), ncecat(1),
115 ncflint(1), ncz2psx(1), ncks(1), nco(1), ncpdq(1), ncra(1), ncrcat(1),
116 ncremap(1), ncrename(1), ncwa(1)
117
120 The NCO homepage at <http://nco.sf.net> contains more information.
121 NCRCAT(1)