登录后查看更多精彩内容~
您需要 登录 才可以下载或查看，没有帐号？立即注册
x
本帖最后由 hillside 于 2013-12-30 11:28 编辑
以下仅是摘录，欲知详情，可点击http://dust.ess.uci.edu/nco/
Welcome to the netCDF Operator (NCO) Homepage
Current NCO version is 4.3.9
NCO manipulates data stored in netCDF-accessible formats, including HDF4 and HDF5. It also exploits the geophysical expressivity of many CF (Climate & Forecast) metadata conventions, the flexible description of physical dimensions translated by UDUnits, the network transparency of OPeNDAP, the storage features (e.g., compression, chunking, groups) of HDF (the Hierarchical Data Format), and many powerful mathematical and statistical algorithms of GSL (the GNU Scientific Library). NCO is fast, powerful, and free.What is NCO?The netCDF Operators (NCO) comprise a dozen standalone, command-line programs that take netCDF or HDF files as input, then operate (e.g., derive new data, average, print, hyperslab, manipulate metadata) and output the results to screen or files in text, binary, or netCDF formats. NCO aids manipulation and analysis of gridded scientific data. The shell-command style of NCO allows users to manipulate and analyze files interactively, or with simple scripts that avoid some overhead (and power) of higher level programming environments. The NCO User's Guide illustrates their use with examples of climate data analysis:
Get NCO Binary ExecutablesNCO developers are too short-handed to provide pre-built binary executables for all platforms. Our source tarballs are always up-to-date, and work on our development systems (Ubuntu-flavored Debian GNU/Linux for x86_64) and in our high-end scientific computing environments (AIX 5 for Power4/5/6/7). We also attempt to provide (theoretically) platform-independent sources in the most common UNIX packaging formats (Debian and RPM). Below are links to these and to packages created by volunteers who port NCO to other platforms. Volunteers willing to perform regular regression testing and porting of NCO to other platforms are welcome. Previous versions of these binaries are still available by searching the directory index here. AIX on IBM mainframes- nco-4.2.5.aix53.tar.gz (): Executables AIX 5.3-compatible (last updated ). Maintained by NCO Project.
Newer (beta- or pre-release) packages are sometimes available for AIX users as described here. Thanks to NSF for supporting AIX machines at NCAR over the years.
Debian and Ubuntu GNU/Linux
Debian NCO and Ubuntu NCO homepages. ‘aptitude install nco’ installs the standard NCO for your Debian-compatible OS. NCO packages in the Debian/Ubuntu repositories (i.e., Sid and Raring) generally lag the packages distributed here by 6–12 months. Newer (beta- or pre-release) packages are often available for intrepid Debian/Ubuntu users as described here.Debian package for most recent NCO release (install with, e.g., ‘dpkg --install nco_4.3.9-1_i386.deb’):- nco_4.3.9-1_amd64.deb (): Executables AMD64-compatible (last updated )
- nco_4.3.9-1.dsc (): Description (last updated )
- nco_4.3.9-1_amd64.changes (): Changes since last deb package (last updated )
- nco_4.3.9.orig.tar.gz (): Upstream Source (last updated )
- nco_4.3.9-1.diff.gz (): Debian patch to upstream source (last updated )
Thanks to Daniel Baumann, Barry deFreese, Francesco Lovergine, Brian Mays, Rorik Peterson, and Matej Vela for their help packaging NCO for Debian over the years.
Fedora, RedHat Enterprise Linux (RHEL), and Community ENTerprise Operating System (CentOS) GNU/Linux
The Fedora NCO RPMs are usually up-to-date so that ‘yum install nco’ will install a recent version. A comprehensive list of pre-built RPMs for many OS's is here.- nco-4.3.2-1.fc20.x86_64.rpm: Executables for x86_64/Fedora Core 20-compatible environments
If not, try our own most recent (we stopped building RPMs many years ago and are looking for a volunteer to do this instead) self-built NCO RPMs (install with, e.g., ‘yum install nco-3.9.5-1.fc7.i386.rpm’): - nco-3.9.5-1.fc7.i386.rpm (): Executables for i386/Fedora Core 7-compatible environments (last updated )
- nco-3.9.5-1.fc7.src.rpm (): Source (last updated )
- nco-3.9.5-1.x86_64.rpm (): Executables for x86_64/CentOS 5-compatible environments (last updated )
Volunteers have updated and maintained fairly up-to-date NCO packages in Fedora since it was added by Ed Hill in about 2004. Thanks to Patrice Dumas, Ed Hill, and Orion Poplawski for packaging NCO RPMs over the years. Thanks to Gavin Burris and Kyle Wilcox for documenting build procedures for RHEL and CentOS.
Gentoo GNU/LinuxMac OS X/Darwin
The most up-to-date binaries are probably those in the tarball below. Those unfamiliar with installing executables from tarballs may try the (older)DMG files (you may need to add /opt/local/bin to your executable path to access those operators).- nco-4.3.8.macosx.10.8.tar.gz (): Executables MacOSX 10.6-compatible (last updated ). (NB: These executables require the MacPorts dependencies forNCO). Maintained by NCO Project.
- nco-4.0.3_x86_10.6.dmg (): For Mac OS 10.6 (last updated ). Maintained by Chad Cantwell.
- nco-4.0.7_x86_10.6.dmg (): For Mac OS 10.6 (last updated ). Maintained by Chad Cantwell.
- Fink packages for NCO: Currently NCO 3.9.5. Maintained by Alexander Hansen.
- MacPorts infrastructure for NCO: Portfile for NCO 3.9.9. Maintained by Takeshi Enomoto.
Microsoft Windows (native build, compiled with Visual Studio 2010, use this if unsure)These native Windows executables should be stand-alone, i.e., not require users to have any additional software. This is a new feature as of 20120615, please send us feedback. To build NCO from source yourself using MSVC or Qt, please see the NCO Qt/MSVC build page.Microsoft Windows (running Cygwin environment, compiled with GNU-toolchain)- nco-4.3.8.win32.cygwin.tar.gz (): Executables Cygwin-compatible (last updated ). Maintained by NCO Project.
First install curl (in the "Web" category of Cygwin setup), and point the environment variable UDUNITS2_XML_PATH to the udunits2.xml file, e.g., withexport UDUNITS2_XML_PATH='/usr/local/share/udunits/udunits2.xml'. Thanks to Mark Hadfield for creating Cygwin tarballs. Thanks to Cygnus Solutions and RedHat Inc. for developing and supporting Cygwin over the years.
Documentation and User's GuideThe NCO User's Guide is available for reading in these formats: - DVI Device Independent (kdvi, xdvi)
- HTML Hypertext (any browser)
- Info GNU Info (M-x Info, emacs)
- PDF Portable Document Format (acroread, evince, kpdf, okular, xpdf)
- Postscript Printing (ghostview, kghostview)
- TeXInfo Documentation Source code (emacs)
- Text Plain text (more)
- XML Extensible Markup Language (firefox)
nco.texi is the most up-to-date. Files nco.dvi, nco.ps, and nco.pdf are contain all the mathematical formulae (typeset with TeX) missing from the screen-oriented formats. The screen-oriented formats—nco.html, nco.info, nco.txt, and nco.xml—contain all the documentation except the highly mathematical sections.Other documentation:- This abbreviation key unlocks the mysteries of the source code abbreviations and acronyms.
FAQ: Frequently Asked QuestionsThese questions show up almost as frequently as my mother. But they are more predictable: - I still have questions, how do I contact the NCO project? The NCO project has various Q&A and discussion forums described below.
- Where can I find prebuilt NCO executables? Pre-built executables of some versions of NCO for the operating systems described above (Debian-compatible GNU/Linux, Fedora/RedHat GNU/Linux, Gentoo GNU/Linux, and Mac OS X). Otherwise, you may be on your own.
- Does NCAR support NCO? The NCAR CISL Technical Consulting Group (TCG) supports NCO like other community software packages such as lapack. No other NCAR division has coordinated NCO support. The NCAR CISL-suported executables are made available through “modules” so try module add nco. If you notice problems with the NCO installation on CISL machines, or if you would benefit from a more recent release or patch, then inform the relevant system administrators, e.g., NCAR User Support. If you have a comment, suggestion, or bug report, then contact the developers as described below.
- Is there an easy way to keep up with new NCO releases? Subscribe to the nco-announce mailing list. This list is for NCO-related announcements, not for questions. nco-announce is very low volume—one message every few months.
README/ChangeLog/TODOFiles containing useful information about the current NCO distribution: - README Platforms and software required by NCO
- ChangeLog History of NCO changes
- TODO An unordered list of features and fixes we plan for NCO
Get NCO Source CodeThe best way to acquire NCO sources is with CVS. The second best way is to download the source as a compressed tarfile:NCO's browsable CVS Repository contains up-to-the-minute sources and is the easiest way to stay synchronized with NCO features. Retrieving NCO requires some familiarity with GNU development tools, especially CVS and Make. Sourceforge provides generic instructions for accessing their CVS servers. First log into the NCO CVS server: cvs -d:pserver:anonymous@nco.cvs.sf.net:/cvsroot/nco login Hit return when asked for the CVS password. This login procedure is only required the first time you access the CVS server. Then you may retrieve any NCO distribution you wish. Usually you wish to retrieve a recent tagged (i.e., released) version. This command retrieves and places NCO version 4.3.9 (which is tagged as nco-4_3_9 due to CVS rules) into local directory nco-4.3.9:cvs -z3 -d:pserver:anonymous@nco.cvs.sf.net:/cvsroot/nco co -r nco-4_3_9 -d nco-4.3.9 nco This command retrieves the current (“bleeding edge”) development version of NCO into a local directory named nco:cvs -z3 -d:pserver:anonymous@nco.cvs.sf.net:/cvsroot/nco co -kk nco Track changes to the development version usingcd nco;cvs update -kk One difference between running a "tagged" release (e.g., nco-4_3_9) and the development version is that the tagged release operators will print a valid version number (e.g., 4.3.9) when asked to do so with the -r flag (e.g., ncks -r). The development version simply places today's date in place of the version. Once the autotools builds are working more robustly, the confusion over versions should largely disappear.Developer NCO Source DocumentationAutomated source documentation, created by the Doxygen tool is available. Some developers find this documentation helpful, as it can clarify code and data relationships in the code. Please be aware that the documentation may be slightly inaccurate and infrequently updated. Comments and suggestions are certainly welcomed on the forums.
Compilation Requirements……气象家园相关帖子： 使用nco处理大量的nc数据
|
窥视卡
雷达卡
发表于 2013-12-30 11:23:21
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
抢沙发
千斤顶
显身卡
楼主
下