NCO Implementation Standards
The Implementation Standards outline policies and technical standards that must be met in order to implement operational code or numerical models in the production suite running on the Weather & Climate Operational Supercomputing System (WCOSS) and maintained by NCEP Central Operations (NCO). The coding standards, examples of operational-quality scripts and code, and best practices presented have been established to enable operational stability, efficient troubleshooting and improved environmental equivalence.
Release Date: March 17, 2016
- Added module_ver variable to the Standard Environment Variables table.
- On the Cray XC40 systems, the prod_envir module is used to set production path variables. On Phase 1 & 2, symbolic links at the root level are available to production path directories.
setpdy.shdescription updated to include ability to specify the number of dates desired.
- Introduced new
- Updated the job card, J-job, ex-script, build script, modulefile, and makefile examples to use the
mail.pyutilities and to reflect changes for the Cray XC40 systems.
- The default versions (and higher) of the Intel and Cray compilers installed on the Cray XC40 systems are allowed in production on the new systems.
- Production-approved libraries on the Cray XC40 systems are in /usrx/local/prod/ and /gpfs/hps/nco/ops/nwprod/lib/.
- Removed the envir.h example and moved the variable definitions it contained into the job card example.
- Added an example version file (Example 5), an example run of the "module display prod_envir" command (Example 7), and an example build readme file (Example 10).
- Removed requirement to wrap all copies to com, nwges, and pcom in a check for
$SENDCOM. It is now optional.
National Weather Service
National Centers for Environmental Prediction
5830 University Research Court
College Park, MD 20740
Freedom of Information Act