1NCECAT(1) General Commands Manual NCECAT(1)
2
3
4
6 ncecat - netCDF Ensemble Concatenator
7
9 ncecat [-A] [-C] [-c] [-D dbg] [-d dim,[ min][,[ max]]] [-F] [-h] [-l
10 path] [-n loop] [-O] [-p path] [-R] [-r] [-v var[,...]] [-x] input-
11 files output-file
12
14 ncecat concatenates an arbitrary number of input files into a single
15 output file. Input files are glued together by creating a record
16 dimension in the output file. Input files must be the same size. Each
17 input file is stored consecutively as a single record in the output
18 file. Thus, the size of the output file is the sum of the sizes of the
19 input files.
20
21 Consider five realizations, 85a.nc, 85b.nc, 85e.nc of 1985 predictions
22 from the same climate model. Then ncecat 85?.nc 85_ens.nc glues the
23 individual realizations together into the single file, 85_ens.nc. If
24 an input variable was dimensioned [ lat, lon], it will have dimensions
25 [ record, lat, lon] in the output file. A restriction of ncecat is
26 that the hyperslabs of the processed variables must be the same from
27 file to file. Normally this means all the input files are the same
28 size, and contain data on different realizations of the same variables.
29
31 Consider a model experiment which generated five realizations of one
32 year of data, say 1985. You can imagine that the experimenter slightly
33 perturbs the initial conditions of the problem before generating each
34 new solution. Assume each file contains all twelve months (a seasonal
35 cycle) of data and we want to produce a single file containing all the
36 seasonal cycles. Here the numeric filename suffix denotes the experi‐
37 ment number (not the month):
38 ncecat 85_01.nc 85_02.nc 85_03.nc 85_04.nc 85_05.nc 85.nc
39 ncecat 85_0[1-5].nc 85.nc
40 ncecat -n 5,2,1 85_01.nc 85.nc
41 These three commands produce identical answers. The output file,
42 85.nc, is five times the size as a single input-file. It contains 60
43 months of data (which might or might not be stored in the record dimen‐
44 sion, depending on the input files).
45
46
48 NCO manual pages written by Charlie Zender and Brian Mays.
49
50
52 Report bugs to <http://sf.net/bugs/?group_id=3331>.
53
54
56 Copyright © 1995-2004 Charlie Zender
57 This is free software; see the source for copying conditions. There is
58 NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
59 PURPOSE.
60
61
63 The full documentation for NCO is maintained as a Texinfo manual called
64 the NCO User's Guide. Because NCO is mathematical in nature, the docu‐
65 mentation includes TeX-intensive portions not viewable on character-
66 based displays. Hence the only complete and authoritative versions of
67 the NCO User's Guide are the PDF (recommended), DVI, and Postscript
68 versions at <http://nco.sf.net/nco.pdf>, <http://nco.sf.net/nco.dvi>,
69 and <http://nco.sf.net/nco.ps>, respectively. HTML and XML versions
70 are available at <http://nco.sf.net/nco.html> and
71 <http://nco.sf.net/nco.xml>, respectively.
72
73 If the info and NCO programs are properly installed at your site, the
74 command
75
76 info nco
77
78 should give you access to the complete manual, except for the TeX-
79 intensive portions.
80
81
83 The NCO homepage at <http://nco.sf.net> contains more information.
84
85
86
87 NCECAT(1)