A Simple Guide on How to Run CFSV2

A Simple Guide on How to Run CFSV2

<p> A simple guide to run the “pre-implementation” version of the Climate Forecast System V2 Shrinvas Moorthi, GCWMB, EMC/NCEP Public Release: 1 June 2010</p><p>These scripts have been designed for NCEP operations to run CFS version 2 seasonal forecasts at T126l64 resolution, as well as for developers and researchers to run hindcasts or forecasts of virtually any length, from weeks to multi-century runs. The scripts were developed to run on IBM P6 machines, and may need to be modified to run on other platforms. A very simple interface has been created for non operational users. Values for all parameters default to operational settings. Many optional variables can be set via the script "submit_cfsv2.sh" in the sub directory “exp”. While one can execute this script to submit the CFS run, an even simpler way would be to execute the script "mysubmit.sh" which demonstrates the use of the script "submit_cfsv2.sh". The user must specify a minimum number of variables in “mysubmit.sh”, to make a climate run with CFSV2. The user must define the date of the initial condition; the directory where the initial conditions files reside; paths to the script directory (HOMEcfs); a config file (cfsv2_config, which defines many defaults depending on whether the run is production or development) and the user account name. The variable "SUBMIT_POST" should be set to "YES" if one wants the forecast step to submit the post (post processor) step. Otherwise, the user must submit the post manually. The length of the forecast can be set either in the units of months (LENMON), or days (LENDAY) or hours (LENHR). If the length is in months, then the forecast continues to the end of the month. The default value for all these 3 parameters is set to “0”. The user must specify one of them. The post job creates gridded GRIB files for both the atmosphere and ocean at a default interval of 6 hours. It also calculates monthly means of pgb, flx, ipv, and ocn files if a month has completed. It also extracts time series of 80 pre-selected variables. For more information on what these files and time series are, please refer to the CFSR paper (supplemental section) at: http://journals.ametsoc.org/doi/pdf/10.1175/2010BAMS3001.1 The archiving and deletion scripts are yet to be written. COMDSK is the directory in which the forecast files are written. In the “ini” sub directory we have provided a single set of initial conditions for 2009121200 for the purpose of testing the scripts. We have also provided a single one month forecast (LENMON=1) from this initial condition. The output from this run is in: /mtb/noscrub/wx23sm/cfs. Please be advised that the codes and scripts may change internally before implementation. We will not be updating the public release scripts with these changes until after the CFS is implemented. The source and scripts will be made available to the general public on June 1, 2010, via the CFS website at http://cfs.ncep.noaa.gov Very limited support for running these scripts is available by sending email to only: [email protected] Reference for CFS v2: Saha, Suranjana, Shrinivas Moorthi, Hua-Lu Pan, Xingren Wu, Jiande Wang, Sudhir Nadiga, Patrick Tripp, David Behringer, Yu-Tai Hou, Hui-ya Chuang, Mark Iredell, Michael Ek, Jesse Meng and Rongqian Yang, 2010: The NCEP Climate Forecast System Version 2. To be submitted to the J. Climate.</p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    1 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us