- 积分
- 3601
- 贡献
-
- 精华
- 在线时间
- 小时
- 注册时间
- 2012-9-8
- 最后登录
- 1970-1-1
|
登录后查看更多精彩内容~
您需要 登录 才可以下载或查看,没有帐号?立即注册
x
本帖最后由 hillside 于 2013-12-30 11:39 编辑
https://climatedataguide.ucar.edu/processing/software/overview
Climate Data Processing Software
The following is by Dennis Shea (NCAR):
A common question:
"What is the best software to use for climate data processing?"
There is no simple answer. All software tools and languages have strengths and weaknesses. For large scale data processing on a variety of data sets in assorted data formats and differing project requirements, it is unlikley that a perfect tool or language exits. Often, a combination of software tools and languages will be needed.
Climate data processing involves 3 components:
(1) file handling (I/O),
(2) processing (data manipulation and computations), and
(3) graphics (visualization).
There are three different software categories used for climate data processing and visualization:
(1) compiled languages (eg., fortran, C, C++),
(2) command line operators, viewers (NCO, CDO, ncview) , and
(3) interpreted languages (NCL, GrADS, Ferret, R, Python [CDAT/PyNIO/PyNGL/Numpy/matplotlib] and the commercial products Matlab, IDL and, to a lesser extent, PV-Wave).
Compiled languages can be much faster than the interpreted languages for large computation bound tasks. Language compilers analyze and optimize code and create machine specific execution instructions. As a result, they can perform looping (iterations) faster. For example, weather forecast and climate models are often written in fortran (usually f90). However, compiled languages lack builtin support for accessing the different data formats used in climate studies and they have no builtin graphics. Further, programming in compiled languages can be tedious.
Command line operators (CLOs) are tools that can be executed directly at the system prompt line. There are many NCO and CDO operators and there is some functional overlap. Each operator is designed to perform a specific task efficiently. For example, the NCO operator "ncra" can input one or more netCDF files, compute time averages (means) of all or selected variables on the file(s) and save the results to a netCDF file. It is not uncommon to use an NCO/CDO operator to accomplish a specific task and, then, feed the output file to a different CDO/NCO operator. Ncview is a commonly used visual browser for netCDF format files.
Interpreted languages are general purpose software tools. They include support to read and write assorted data formats; have many builtin computational functions; and, create visualizations. These tools have all the capabilities of the CLOs and ncview and can do much more. However, they do require users to enter commands interactively or via a script.
Within NCAR's Climate Analysis Section, tera-bytes of model output, observationally based data sets like the reanalysis products (ERA-Interim, MERRA, NCEP-NCAR, JRA, ...) and satellite data are analyzed, evaluated and used as the basis for publications. The data are in a variety of formats, including: netCDF-3/4, GRIB-1/2, HDF4, HDF4-EOS, HDF5, HDF5-EOS. The primary post-processing tools used are NCL and the NCO. In some cases, data created by NCL/NCO are input to R for certain statistical methods not available within NCL (eg., extreme value statistics). Depending upon the application, the CDO, IDL and Matlab are also used.
Recommendation: If a desired operation can be performed by a CLO (CDO or NCO), we recommend that the appropriate operator be used. Why? Only because it can be more convenient since no programming is necessary. However, like programming in compiled or interpreted languages, it can sometimes require users to experiment with the appropriate options.
‹ Overview: Climate Data ProcessingupRegridding Overview ›
Printer-friendly version
Researchers and Students: Become a Registered User of this site! As such, you may receive notifications when data sets are added or updated, particpate in the comments and discussion, post your own comments, questions and links, and contribute expert guidance about data sets. Create an account.
Comment Policy
We encourage constructive comments and interaction. Please remember these guidelines: Users agree to UCAR's Terms of Use and Privacy Policy. For this site, the comments are visible without logging in, but only registered and logged in users may post comments and replies. You may post questions about the dataset, share your experiences using the dataset, provide links to relevant resources, or list your publications that use the dataset. All comments will be signed with your authentic name (no pseudonyms or anonymous comments) and affiliation associated with your user profile and will be moderated; therefore they will not be immediately posted. Questions will be answered as time permits, and we encourage dataset developers or other users to chime in with answers. If you have enough expertise to offer that merits a new page in the Climate Data Guide, please see our contributions page.
Comments
#23: Gurunath chinthalu of Indian Institute of Tropical Meteorology on Tuesday, February 5, 2013 - 11:08pm said:
The scope for futher improvements in earth science data visualation and analysis exist , I feel we can take the best from softwares like grads, ferret, python , ncl and other try to build more user friendly software. Well I hope this is possible and the Atmospheric and Ocean science research community will benefit from such an exercise. |
|