| 1 |
<!-- $Header$ |
| 2 |
|
| 3 |
Purpose: NCO news archive |
| 4 |
|
| 5 |
Usage: |
| 6 |
http://www.cgd.ucar.edu/cms/nco/nco_news.shtml |
| 7 |
file:/home/zender/nco/doc/nco_news.shtml |
| 8 |
/bin/cp -f ~/nco/doc/nco_news.shtml /web/web-data/cms/nco/nco_news.shtml |
| 9 |
|
| 10 |
scp -p ~/nco/doc/nco_news.shtml dust.ess.uci.edu:/var/www/html/nco/nco_news.shtml |
| 11 |
scp -p ~/nco/doc/nco_news.shtml nco.sf.net:/home/project-web/nco/htdocs/nco_news.shtml |
| 12 |
--> |
| 13 |
|
| 14 |
<!doctype html public "-//W3C//DTD HTML 3.2//EN"> |
| 15 |
<html> |
| 16 |
<head> |
| 17 |
<title>NCO Homepage</title> |
| 18 |
<meta name="GENERATOR" content="Mozilla/3.04Gold (X11; I; Linux 2.0.0 i686) [Netscape]"> |
| 19 |
<meta name="Author" content="Charles S. Zender"> |
| 20 |
<meta name="Keywords" content="NCO Homepage, netCDF, netCDF |
| 21 |
operator, GCM, HDF, scientific data"> |
| 22 |
</head> |
| 23 |
<body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#008080" alink="#FF0000"> |
| 24 |
|
| 25 |
<dt><a name="News"></a></dt> |
| 26 |
<h2>NCO News and Announcements from 20030624 (version 2.8.3) and earlier</h2> |
| 27 |
|
| 28 |
<a name="20030624"></a> |
| 29 |
<p>2003/06/24: A potpurri of old news which is no longer needed on the homepage |
| 30 |
<ul> |
| 31 |
<li>As of version 2.8.3, <a href="./nco.html#ncap"><tt>ncap</tt></a> consumes significantly less memory than before. |
| 32 |
<li>New “binary” operator <a href="./nco.html#ncbo"><tt>ncbo</tt></a> does file addition, subtraction, multiplication, and division |
| 33 |
<li><tt>ncap</tt> adds user-invokable type conversion functions <tt>char()</tt>, <tt>short()</tt>, <tt>int()</tt>, <tt>float()</tt>, <tt>double()</tt>.</li> |
| 34 |
<li><tt>libnco_c++</tt> reads into and writes from type <tt>long double</tt></li> |
| 35 |
<li>Developer code has fully integrated <tt>autoconf</tt>/<tt>libtool</tt> |
| 36 |
build procedure</li> |
| 37 |
<li>NCO allows <tt>ncap</tt> to unpack variables stored |
| 38 |
with <tt>scale_factor</tt> and <tt>add_offset</tt> convention</li> |
| 39 |
<li>NCO includes <tt>ncap</tt>, a scriptable operator |
| 40 |
capable of performing arbitrary arithmetic operations</li> |
| 41 |
<li>NCO code includes libnco_c++, a new C++ interface to netCDF</li> |
| 42 |
<li>NCO now supports multithreading with OpenMP-compliant compilers</li> |
| 43 |
<li>NCO code contains working packing and unpacking primitives</li> |
| 44 |
</ul> |
| 45 |
|
| 46 |
<a name="20020203"></a> |
| 47 |
<p>2002/02/03: |
| 48 |
NCO version 2.2 is released. |
| 49 |
Differences with version 2.0 |
| 50 |
<ul> |
| 51 |
<li><tt>ncap</tt>, the netCDF Arithmetic Processor</li> |
| 52 |
<li><tt>libnco_c++</tt>, a C++ API for libnetcdf</li> |
| 53 |
<li>Various minor bugfixes introduced in 2.X releases</li> |
| 54 |
</ul> |
| 55 |
|
| 56 |
<a name="20010507"></a> |
| 57 |
<p>2001/05/07: |
| 58 |
NCO version 2.0 is released. |
| 59 |
Differences with version 1.2.2 are completely internal and oriented |
| 60 |
toward enhancing I/O performance and modernizing the NCO API: |
| 61 |
<ul> |
| 62 |
<li>NCO 2.x is now completely based on the netCDF 3.x API. |
| 63 |
NCO 1.2.x will continue to be maintained for its |
| 64 |
ability to work with HDF4 files, but no new features |
| 65 |
will be added.</li> |
| 66 |
</ul> |
| 67 |
|
| 68 |
<a name="20010211"></a> |
| 69 |
<p>2001/02/11: |
| 70 |
NCO version 1.2.2 is released. |
| 71 |
Differences with version 1.2.1 include three new features and one bugfix: |
| 72 |
<ul> |
| 73 |
<li>Weights are allowed with <tt>ncwa</tt> in min/max/ttl operations. |
| 74 |
New "var:att" syntax allows <tt>ncrename</tt> to rename attributes for |
| 75 |
specific variables rather than whole file, e.g.,<br> |
| 76 |
<pre>ncrename -a os_name:eunuchs,unix in.nc out.nc</pre> |
| 77 |
Previously, <tt>ncrename</tt> would rename the same attribute for all |
| 78 |
variables in a file.</li> |
| 79 |
|
| 80 |
<li><tt>ncks</tt> has new <tt>-q</tt> option to allow for printing |
| 81 |
arrays without printing associated dimensions |
| 82 |
|
| 83 |
<li>The build system has been modified so that |
| 84 |
<tt>make HDF4=Y</tt> will build NCO with HDF4 compatibility |
| 85 |
(previously this had to be done by hand).</li> |
| 86 |
|
| 87 |
<li>The internal representations of <tt>NC_CHAR</tt> and |
| 88 |
<tt>NC_BYTE</tt> data have been swapped in order to agree with the |
| 89 |
netCDF standard. |
| 90 |
The effects of this last change should not be visible to the user.</li> |
| 91 |
</ul> |
| 92 |
|
| 93 |
<a name="20000828"></a> |
| 94 |
<p>2000/08/28: |
| 95 |
NCO version 1.2.1 is released. |
| 96 |
Differences with version 1.2 include one new feature and one bugfix. |
| 97 |
|
| 98 |
<p>1. Operators now perform automatic type conversion of integers to |
| 99 |
doubles before arithmetic. |
| 100 |
This feature allows <tt>ncwa</tt>, <tt>ncra</tt>, and <tt>ncea</tt> |
| 101 |
to handle averaging of longs, shorts, bytes, and chars in a more |
| 102 |
satisfactory manner. |
| 103 |
One immediate benefit is that <tt>ncwa</tt> no longer |
| 104 |
complains when user's try to apply weights (e.g., gaussian weights) |
| 105 |
all less than one to the averaging of an integer (e.g., <tt>nlons</tt>). |
| 106 |
Formerly <tt>ncwa</tt> would issue a warning, a workaround, and then |
| 107 |
dump core (because weights converted to integers were all zeros). |
| 108 |
Now that arithmetic is performed in double precision (rather than |
| 109 |
in the precision of the variable), <tt>ncwa</tt> handles this |
| 110 |
situation correctly. |
| 111 |
|
| 112 |
<p>2. A bug introduced in NCO 1.2 which broke the <tt>-x</tt> switch has been fixed |
| 113 |
|
| 114 |
<p>3. Thanks to Henry Butowsky for implementing the type conversion feature |
| 115 |
<br>Thanks to Ethan Davis for improving the build procedure |
| 116 |
|
| 117 |
<a name="20000730"></a> |
| 118 |
<p>2000/07/30: |
| 119 |
nco-1.2 is released. |
| 120 |
Summary of new features and user-visible changes: |
| 121 |
<ul> |
| 122 |
<li>The names of three of the operators have been made somewhat obsolete |
| 123 |
because they are no longer just arithmetic averagers. |
| 124 |
<b>ncra</b>, <b>ncea</b>, and <b>ncwa</b> have all been given |
| 125 |
brain transplants so that the type of operation they perform may be |
| 126 |
specified on the command line. |
| 127 |
The following operations are now supported by the new |
| 128 |
<tt>-y</tt> switch: average (default), total, minimum, maximum, |
| 129 |
root-mean-square, square of the mean, mean of the squares, square |
| 130 |
root. |
| 131 |
For example, |
| 132 |
<pre> |
| 133 |
ncra -O -y rms -n 12,4,1 h0001.nc 2000_rms.nc # Root-mean-square |
| 134 |
ncea -O -y min -n 12,4,1 h0001.nc 2000_min.nc # Minimum |
| 135 |
ncwa -O -y max -a lon,lat h0001.nc 200001_max_x.nc # Maxima |
| 136 |
</pre> |
| 137 |
Averaging is still the default so no existing usage needs to be modified. |
| 138 |
It is also possible to compute spatial and temporal variances and |
| 139 |
standard deviations using a combination of three or four NCO commands.</li> |
| 140 |
|
| 141 |
<li>All operators may now be |
| 142 |
<a href="http://www.unidata.ucar.edu/packages/dods">DODS</a></dd> clients. |
| 143 |
DODS enables network transparent data access to any DODS server. |
| 144 |
Thus DODS-enabled NCO can operate on remote files accessible through |
| 145 |
any DODS server without transferring the files. |
| 146 |
Only the required data (e.g., the variable or hyperslab specified) are |
| 147 |
transferred. |
| 148 |
See the <a href="./nco.html">Users Guide</a> for complete details.</li> |
| 149 |
|
| 150 |
<li>Fortran compatibility has been dropped. |
| 151 |
If a volunteer wants to continue to maintain the option to perform |
| 152 |
arithmetic in Fortran for reasons of speed, contact the project.</li> |
| 153 |
</ul> |
| 154 |
|
| 155 |
Summary of administrative changes: |
| 156 |
<ul> |
| 157 |
<li>NCO is now an Open Source project licensed under the GPL. |
| 158 |
These new capabilities are the result of contributions from Henry |
| 159 |
Butowski, Bill Kocik, and Roland Schweitzer. |
| 160 |
For more information on how to contribute to NCO, |
| 161 |
visit the <a href="http://sf.net/projects/nco">NCO |
| 162 |
administration homepage</a>.</li> |
| 163 |
|
| 164 |
<li>New NCO releases and important announcements will be made on the |
| 165 |
netCDF list and on the new |
| 166 |
<a href="http://lists.sf.net/mailman/listinfo/nco-announce"><tt>nco-announce</tt></a> |
| 167 |
mailing list.</li> |
| 168 |
|
| 169 |
<li>Questions, suggestions, ideas, and pleas for help should be posted to |
| 170 |
the appropriate discussion forum at the NCO administration site. |
| 171 |
NCO developers monitor these open forums, and your message will get a |
| 172 |
quicker response if it is posted on one of these forums: |
| 173 |
<ul> |
| 174 |
<li><a href="http://sf.net/forum/forum.php?forum_id=9829">Open |
| 175 |
Discussion Forum</a>: General discussion, discussion of tips, tricks, |
| 176 |
future directions for NCO.</li> |
| 177 |
<li><a href="http://sf.net/forum/forum.php?forum_id=9830">Help |
| 178 |
Forum</a>: Installation problems, user's questions (e.g., "How do I |
| 179 |
average x and y...?")</li> |
| 180 |
<li><a href="https://sf.net/p/nco/discussion/9831">Developers |
| 181 |
forum</a>: Discussion of patches, technical questions related to |
| 182 |
modifying NCO, and discussion of specific items on the |
| 183 |
<a href="./TODO">TODO list</a> and how best to address them</li> |
| 184 |
</ul></li> |
| 185 |
</ul> |
| 186 |
Note: You must first |
| 187 |
<a href="https://sf.net/account/register.php">register</a> |
| 188 |
in order to post to these forums. |
| 189 |
Once registered you may choose to "monitor" the forums and to receive |
| 190 |
email when there are any postings. |
| 191 |
|
| 192 |
<a name="20000515"></a> |
| 193 |
<p>2000/05/15: |
| 194 |
nco-1.1.48 fixes a bug introduced in nco-1.1.15 (November 1998) with |
| 195 |
<tt>ncdiff</tt> version 1.5. |
| 196 |
That bug could cause incorrect answers when the broadcast feature was |
| 197 |
used and dimensions were defined in a certain order (that appears to |
| 198 |
be favored by oceanographers). |
| 199 |
All NCO users are urged to upgrade NCO in order to avoid the potential |
| 200 |
<tt>ncdiff</tt> bug as well as to take advantage of the new features |
| 201 |
in <tt>ncra</tt> and <tt>ncrcat</tt>. |
| 202 |
|
| 203 |
<a name="20000510"></a> |
| 204 |
<p>2000/05/10: |
| 205 |
nco-1.1.47 adds capability of <tt>ncra</tt>, and <tt>ncrcat</tt> to handle |
| 206 |
superfluous initial files. These multifile operators used to require |
| 207 |
that hyperslabs along the record dimension contain valid points in the |
| 208 |
first input file, although superfluous trailing files were allowed. |
| 209 |
Now superfluous files are also allowed anywhere in the file argument |
| 210 |
list for coordinate value hyperslabs (e.g., <tt>-d time,2.0,3.0</tt>), |
| 211 |
and at the beginning and end of the file argument list for dimension |
| 212 |
index hyperslabs (e.g., <tt>-d time,2,3</tt>). |
| 213 |
This can dramatically simplify analysis of file collections when the |
| 214 |
location of certain record coordinates or indices is not known a |
| 215 |
priori, or is tedious to compute. |
| 216 |
Users may now operate on specific segments of a timeseries |
| 217 |
(e.g., February values) without knowing which files contain February. |
| 218 |
Simply input the entire timeseries of files to the operators |
| 219 |
and they will automagically find and operate on only the February |
| 220 |
values. |
| 221 |
For example, |
| 222 |
<p><tt>ncra -O -d time,2.0,3.0 -n 1000,4,1 h0001.nc feb.nc</tt></p> |
| 223 |
<p><tt>ncrcat -O -F -d time,2,,12 -n 1000,4,1 h0037.nc feb.nc</tt></p> |
| 224 |
|
| 225 |
<p>Sylvia Murphy of the NCAR |
| 226 |
<a href="http://www.cgd.ucar.edu/csm/cmps/cmps_home.html">Community |
| 227 |
Climate System Model Support Network</a> organized a workshop in |
| 228 |
February, 2000 which devoted some time to NCO. |
| 229 |
Here are links to the very useful |
| 230 |
<a href="http://www.cgd.ucar.edu/csm/support/Document/pdf/nco.pdf">pamphlet</a> |
| 231 |
and |
| 232 |
<a href="http://www.cgd.ucar.edu/csm/support/Document/shows/nco/nco_files/v3_document.htm">slide presentation</a> |
| 233 |
she developed to introduce and to summarize the NCO operators. |
| 234 |
The pamphlet is an excellent primer on NCO's capabilities, though not |
| 235 |
as definitive as the <a href="./nco.html">Users Guide</a>. |
| 236 |
|
| 237 |
<a name="20000305"></a> |
| 238 |
<p>2000/03/05: |
| 239 |
Source and prebuilt binary executable <a href="http://www.rpm.org">RPM</a>s for NCO are now available for <a href="#Download">download</a>. |
| 240 |
|
| 241 |
<a name="20000126"></a> |
| 242 |
<p>2000/01/26: |
| 243 |
Fixed longstanding NCO bug which caused infrequent but unpredictable |
| 244 |
core dumps on machines with PIDs longer than 6 digits, e.g., all |
| 245 |
recent SGI machines. |
| 246 |
A core dump could occur on these machines when the PID was seven |
| 247 |
digits long and the filename length was one less than a multiple of |
| 248 |
eight. |
| 249 |
Kudos to Juliana Rew and Brian Eaton for identifying this bug. |
| 250 |
It is recommended that all users upgrade to the the new version. |
| 251 |
NCO is now distributed under the terms of the GNU General Public |
| 252 |
License (GPL). |
| 253 |
|
| 254 |
<a name="19991226"></a> |
| 255 |
<p>1999/12/26: |
| 256 |
Added support for printing character arrays as strings in <tt>ncks</tt>. |
| 257 |
Added documentation and examples of stride capability to <tt>ncks</tt>, |
| 258 |
<tt>ncra</tt>, and <tt>ncrcat</tt> portions of Users Guide. |
| 259 |
|
| 260 |
<a name="19991214"></a> |
| 261 |
<p>1999/12/14: |
| 262 |
Added feature to <tt>ncatted</tt> so that C-language escape sequences |
| 263 |
may be used in editing character attributes. |
| 264 |
Text formatting of attributes now supports <tt>\n</tt>, <tt>\t</tt>, |
| 265 |
and most other <tt>printf</tt>-style sequences. |
| 266 |
See the <a href="./nco.html">Users Guide</a> for details. |
| 267 |
|
| 268 |
<a name="19991206"></a> |
| 269 |
<p>1999/12/06: |
| 270 |
Fixed bug in <tt>ncatted</tt> so that character-valued attributes |
| 271 |
(strings) may contain commas, and be of zero length. |
| 272 |
Formerly <tt>ncatted</tt> would drop all text after the first comma. |
| 273 |
|
| 274 |
<a name="19991004"></a> |
| 275 |
<p>1999/10/04: |
| 276 |
The build configuration has been simplified and made more robust. |
| 277 |
Now typing <tt>make test</tt> will invoke a self-test where NCO |
| 278 |
attempts to download a small (~65 kb) file on which to perform a |
| 279 |
battery of NCO tests. |
| 280 |
If the equations output by the <tt>make test</tt> command are |
| 281 |
numerically accurate, then you can have high confidence that NCO is |
| 282 |
installed and working correctly. |
| 283 |
|
| 284 |
<a name="19990831"></a> |
| 285 |
<p>1999/08/31: |
| 286 |
A bug involving <tt>ncwa</tt>, weights, and missing values has been |
| 287 |
identified and fixed. |
| 288 |
When <tt>ncwa</tt> was used to average variables with user-specified |
| 289 |
weights (i.e., <IT>-w wgt</IT> was used) and <IT>every</IT> value in a |
| 290 |
target hyperslab was the missing value (i.e., <IT>missing_value</IT>), |
| 291 |
then <tt>ncwa</tt> would erroneously set the average value of the |
| 292 |
target hyperslab to 0.0 rather than to <IT>missing_value</IT>. |
| 293 |
Thus some values which should have been <IT>missing_value</IT> in the |
| 294 |
output file were, instead, set to 0.0. |
| 295 |
No operators besides <tt>ncwa</tt> were affected by this bug. |
| 296 |
This bug is fixed in nco-1.1.38. |
| 297 |
|
| 298 |
A new feature has been implemented in <tt>ncwa</tt>. |
| 299 |
<tt>ncwa</tt> used to exit with an error whenever it was called |
| 300 |
without any user-specified dimensions to average, i.e., when the |
| 301 |
<tt>-a</tt> was not invoked. |
| 302 |
Now when <tt>ncwa</tt> is invoked without any user-specified |
| 303 |
dimensions, it averages over all dimensions. |
| 304 |
Thus the behavior of <tt>-a</tt> is now analogous to that of |
| 305 |
<tt>-d</tt> and of <tt>-v</tt>. |
| 306 |
See the <a href="./nco.html">Users Guide</a> for details. |
| 307 |
|
| 308 |
<a name="19990829"></a> |
| 309 |
<P>1999/08/29: |
| 310 |
NCO now builds completely with pure C source files by default. |
| 311 |
In the past, NCO used Fortran routines to perform floating point |
| 312 |
arithmetic and pure C builds could be manually enabled by specifying |
| 313 |
-DC_ONLY in the build environment. |
| 314 |
The interface between Fortran and C, however, was very difficult to |
| 315 |
maintain on the wide variety of platforms supported by NCO. |
| 316 |
Now pure C builds are the default and Fortran arithmetic must be |
| 317 |
manually enabled by specifying -DUSE_FORTRAN_ARITHMETIC in the build |
| 318 |
environment. |
| 319 |
See the <A HREF="http://www.cgd.ucar.edu/cms/nco/nco.html">Users Guide</A> for details. |
| 320 |
The Fortran code is no longer supported and will probably be |
| 321 |
deprecated in future releases. |
| 322 |
|
| 323 |
<a name="19990805"></a> |
| 324 |
<P>1999/08/05: |
| 325 |
NCAR users will be pleased to know that NCO now takes advantage |
| 326 |
of the local <TT>msrcp</TT> command, if it exists in a standard |
| 327 |
location on the local network. |
| 328 |
This allows all operators to retrieve files from the NCAR mass storage |
| 329 |
unit when <TT>msrcp</TT> is available on the local system. |
| 330 |
This change is transparent to the user, so that commands should still |
| 331 |
specify the paths to the files on the mass store with, e.g., |
| 332 |
<TT>ncks -O -R -l ./ /ZENDER/nc/in.nc foo.nc</TT>. |
| 333 |
See the <A HREF="http://www.cgd.ucar.edu/cms/nco/nco.html">Users Guide</A> for more details. |
| 334 |
|
| 335 |
<a name="19990703"></a> |
| 336 |
<P>1999/07/03: |
| 337 |
<TT>ncatted</TT> now replaces missing values of variables whose |
| 338 |
<IT>missing_value</IT> attribute is changed. |
| 339 |
When the internal floating point representation of a missing value, |
| 340 |
e.g., 1.0e36, differs between machines then netCDF files produced |
| 341 |
on those machines will have incompatible missing values. |
| 342 |
<TT>ncatted</TT> now changes the <IT>missing_value</IT> attribute |
| 343 |
and the missing data self-consistently. |
| 344 |
This allows the user to change the missing values in files from |
| 345 |
different machines to a single value so that the files may then be |
| 346 |
concatenated together, e.g., by <TT>ncrcat</TT>, without losing |
| 347 |
any information. |
| 348 |
|
| 349 |
<a name="19990509"></a> |
| 350 |
<P>1999/05/09: |
| 351 |
<TT>ncks</TT> now alphabetizes output by default. |
| 352 |
To turn off alphabetization and return to the previous behavior |
| 353 |
(variables reported in the order they were written to disk) simply |
| 354 |
specify <TT>`-a'</TT> on the command line. |
| 355 |
Yes, that means the behavior of <TT>`-a'</TT> has been toggled. |
| 356 |
|
| 357 |
<P> |
| 358 |
<TT>ncrcat</TT> and <TT>ncra</TT> now support a <IT>stride</IT> in the |
| 359 |
record dimension (and only the record dimension!), e.g., |
| 360 |
<TT>ncra -d time,1,100,12 in1.nc in2.nc ... out.nc</TT> |
| 361 |
should now work correctly. |
| 362 |
Strides in any dimension remain available with <TT>ncks</TT>, of |
| 363 |
course. |
| 364 |
|
| 365 |
<P> |
| 366 |
<TT>ncrcat</TT> and <TT>ncra</TT> now support index-based |
| 367 |
hyperslabbing in the record dimension across files, e.g., |
| 368 |
<TT>ncra -d time,1,100 in1.nc in2.nc ... out.nc</TT> |
| 369 |
The <A HREF="http://www.cgd.ucar.edu/cms/nco/nco.html">Users Guide</A> claimed this feature had already been implemented, |
| 370 |
but, due to an oversight, that was not true. |
| 371 |
Attempting to use this new feature in older versions of NCO resulted |
| 372 |
in an "index out of range" error. |
| 373 |
Thanks to John Truesdale <[email protected]> for pointing this out. |
| 374 |
|
| 375 |
<a name="19990420"></a> |
| 376 |
<P>1999/04/20: |
| 377 |
Fixed bug where <TT>ncrcat</TT> and <TT>ncra</TT> omitted the last slice of the |
| 378 |
record dimension when <TT>`-F'</TT> (Fortran indexing) was user-specified AND |
| 379 |
user-specified hyperslab information was provided for some |
| 380 |
dimensions BUT not for the record dimension. This bug only |
| 381 |
affected <TT>ncrcat</TT> and <TT>ncra</TT> and only under these conditions. Thanks |
| 382 |
to John Sheldon <[email protected]> for pointing this out. |
| 383 |
|
| 384 |
<a name="19990404"></a> |
| 385 |
<P>1999/04/04: |
| 386 |
By default, extracted variables appear in the same order |
| 387 |
in which they were written to the source netCDF file. |
| 388 |
However, this order is often essentially random, making it hard to |
| 389 |
locate a particular variable in a dump of many variables. |
| 390 |
To help address this, <TT>ncks</TT> will now alphabetize variables. |
| 391 |
Simply specify <TT>`-a'</TT> on the command line. |
| 392 |
|
| 393 |
<a name="19990121"></a> |
| 394 |
<P>1999/01/21: |
| 395 |
An optional token has been added to NCO which eliminates |
| 396 |
all netCDF 3.x calls and thus restores compatibility of NCO with HDF |
| 397 |
files. |
| 398 |
|
| 399 |
<a name="19981202"></a> |
| 400 |
<P>1998/12/02: |
| 401 |
<TT>ncwa</TT> has been updated again since a user |
| 402 |
discovered a bug which occurred when a weight (<TT>`-w'</TT>) and a |
| 403 |
mask (<TT>`-m'</TT>) were both given to <TT>ncwa</TT>. Unfortunately, |
| 404 |
<TT>ncwa</TT> sometimes produced incorrect answers in this scenario so |
| 405 |
if you ever used weights and masks at the same time you are strongly |
| 406 |
urged to upgrade your NCO and rerun the commands. This bug only |
| 407 |
affected variables averaged with both the weight and mask options |
| 408 |
enabled at the same time, no other variables would have been affected. |
| 409 |
|
| 410 |
<P>The <TT>`-n'</TT> and <TT>`-W'</TT> normalization options to |
| 411 |
<TT>ncwa</TT> have been removed, possibly permanently, but at least |
| 412 |
until their implementation is simplified and redesigned. The |
| 413 |
<TT>`-N'</TT> option to <TT>ncwa</TT> remains the same. All the new |
| 414 |
behavior is fully documented in the rewritten and expanded |
| 415 |
<TT>ncwa</TT> section in the |
| 416 |
<A HREF="http://www.cgd.ucar.edu/cms/nco/nco.html">NCO Users |
| 417 |
Guide</A>. |
| 418 |
|
| 419 |
<a name="19981104"></a> |
| 420 |
<P>1998/11/24: |
| 421 |
Choose whether to weight your coordinates in <TT>ncwa</TT> |
| 422 |
A <TT>`-I'</TT> switch has been added to <TT>ncwa</TT>. |
| 423 |
Henforth, by default, <TT>ncwa</TT> applies weights or masks to |
| 424 |
coordinate variables just like any other variable. |
| 425 |
Previously, <TT>ncwa</TT> did not weight coordinate variables at all, |
| 426 |
and always produced simple arithmetic averages of coordinate |
| 427 |
variables. |
| 428 |
Use <TT>`ncwa -I'</TT> to recover the old behavior (i.e., arithmetic |
| 429 |
rather than masked, weighted averages of coordinate variables). |
| 430 |
A problem where <TT>ncwa</TT> would refuse to average variables which |
| 431 |
did not contain any of the averaged dimensions has also been fixed. |
| 432 |
|
| 433 |
<a name="19980707"></a> |
| 434 |
<P>1998/07/07: |
| 435 |
Reduce bloating! |
| 436 |
The <TT>`-h'</TT> switch has been enabled on all operators. |
| 437 |
Using this switch suppresses the automatic history feature in NCO. |
| 438 |
Now you can decide whether each change to a file warrants an |
| 439 |
additional line in the history attribute. |
| 440 |
The functionality of the old <TT>`ncks -h'</TT> switch is now |
| 441 |
invoked with <TT>`ncks -m'</TT> (the mnemonic is `metadata'). |
| 442 |
<HR></P> |
| 443 |
|
| 444 |
</BODY> |
| 445 |
</HTML> |