release3.3

WRF Release Information

The next major WRF release, WRF Version 3.5, will be in Spring 2013. Developers seeking to have their codes for new capabilities for the next major release considered by the WRF Developers' Committee and added to the WRF repository must review Information for Code Contributors. Contributors may also write to wrfhelp@ucar.edu for information and for contacting the Developers' Committee, which oversees code contributions to the WRF system and manages the WRF repository. The Developers' Committee is described in WRF Code Repository and Release Administration.


Candidate Features— WRF Version V3.5

A partial list of potential WRF V3.5 features is shown below. However, ultimate inclusion of any code or features is dependent on the code's following preparation requirements, meeting the deadline for submission, and passing all tests. Developers may submit code for consideration for the release as long as the timeline and the procedures for contribution (see Information for Code Contributors) are followed. Developers and contributors may contact wrfhelp@ucar.edu for information on providing their code to a member of the Developers' Committee and on preparing and testing their code prior to submission.

  • Software framework improvements (e.g: ESMF V5 compatibility)
  • New/improved physics, including: Morrison-Gettleman microphysics, GRIMS shallow convection, climatological ozone/aersol input for the RRTMG radiation, new modules for sea/glacial ice for use with Noah MP LSM
  • WRFDA: New instrument observations (e.g: NPP, FY3 satellites)
  • WPS: Global MODIS-based vegetation dataset, NUDAPT 250-m urban landuse dataset
  • WRF-Chem: CAM chemistry, lightning parametization, lightning NOx production
  • WRF-Hydro hydrology package
  • HWRF: Idealized hurricane option

Timeline— V3.5

The approximate timeline for the V3.5 release was as follows. "RC" refers to the Release Committee; "DC" refers to the Developers' Committee.

September 2012

Approx. 6-mo advance date (R-6m)

  • Users notified of release and provided information on dates and on where to find further details.

October 8, 2012

  • Potential contributors to send notices to wrfhelp of intent to submit code.

    • November 12, 2012

    Approx. 4-mo advance date (R-4m)

    • New code or modifications from outside contributors intended for the release to be through required testing and to be provided to the point of contact or the DC.

    December 7, 2012

    Approx. 3-mo advance date (R-3m)

    • Repository frozen (bugfixes excepted).
    • Check on new features for the release is discussed by the RC (also by the DC).

    January 15, 2013

    • Tests for new features are included in regression test suite. Regression test data sets finalized.

    February 15, 2013

    • Remaining bug fixes implemented.
    • Full set of regression tests run on machines at NCAR.
    • Weekly RC meetings.

    March 1, 2013

    • Final round of large testing. RC and DC meetings focus on status of code and testing.

    Mid-March 2013

    • DC certifies code (final approval) for release. Code packaged and staged for release.

    Late March 2013

  • Release


    • Release Committee

    The WRF Release Committee oversees the major releases of WRF. It is described in the policies for NCAR's administration of the WRF code, found in WRF Code Repository and Release Administration.

    Jordan Powers, NCAR/NESL/MMM- Chairman
    Michael Barlage, NCAR/RAL
    Tom Black, NOAA/NCEP
    Jimy Dudhia, NCAR/NESL/MMM
    Dave Gill, NCAR/NESL/MMM
    Georg Grell, NOAA/ESRL
    Steven Peckham, NOAA/ESRL
    Don Stark, DTC
    Wei Wang, NCAR/NESL/MMM
    Jamie Wolff, DTC
    Xin Zhang, NCAR/NESL/MMM