1 / 15

EMC-DTC collaboration on HWRF

EMC-DTC collaboration on HWRF. Ligia Bernardet, NOAA ESRL DTC June 17, 2009. Introducing the group. DTC Task Lead (coordination, planning etc): Ligia Bernardet Technical work: Shaowu Bao Software Engineer: Laurie Carson + new hire HWRF Team Naomi Surgi Vijay Tallapragada Young Kwon

hanzila
Download Presentation

EMC-DTC collaboration on HWRF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMC-DTC collaboration on HWRF Ligia Bernardet, NOAA ESRL DTC June 17, 2009

  2. Introducing the group • DTC • Task Lead (coordination, planning etc): Ligia Bernardet • Technical work: Shaowu Bao • Software Engineer: Laurie Carson + new hire • HWRF Team • Naomi Surgi • Vijay Tallapragada • Young Kwon • Qingfu Liu • Zhan Zhang

  3. O2R2O2RO2RO2RO2RO2RO2RO2… Goal: Create a framework to • Make HWRF available to the research community • Code, documentation, and support • Joint Hurricane Tutorial in February 2010 • Make research developments available to operations • New developments should be easy to test and to add to operational HWRF • Protect operational code

  4. Framework for R & O collaboration Use general WRF repository, because… • Not feasible for DTC to support two WRF-NMM codes (NAM and HWRF) • Once HWRF is part of the repository, it will have many new physics and options already available • General repository regularly receives contributions of new physics • Has a well-established protocol for access (developers committee, release committee, test suite etc. • Is a good framework for operations and research interactions

  5. HWRF in the WRF repository • HWRF is based on WRF v2.0 • It has many changes in the physics and dynamics • All changes need to be put in the repository, which is now in v3.1 How? • All changes are now in a branch in WRF repository • After tests and bug fixes, changes will be put in trunk

  6. HWRF versus WRF: 1) Physics • Radiation and microphysics: modified NAM packages • Boundary layer and convection: modified GFS packages • Surface and Land Surface Model: • Proposal • Add all physics to WRF repository as new packages • Do not touch existing packages

  7. HWRF versus WRF: 2) Dynamics • Ocean coupling • Moving nest changes (vortex tracking etc.) • Diffusion, momentum mixing, TKE initialization, etc. • Proposal • Some changes added as compile-time options, others in namelist • Run tests to make sure changes do not impact NAM

  8. Timeline • Drivers • O2R: WRF for Hurricanes Tutorial in February 2010 • R2O: 2010 HWRF code from repository (October 2009) • Important deadlines • So far: All HWRF code and dynamics are in branch • June 2009: Finalize code in branch • June 2009: HWRF code in repository trunk • June 2009: Upgrade repository tests • July and August 2009: Large test (many storms) of repo code • October 2009: HWRF code drawn from repo for 2010 tests • November 2009: Repository freeze to prepare for v3.2 release

  9. HWRF is a System • Beyond WRF atmospheric model: • Atmospheric vortex initialization (EMC – Qingfu Liu) • Post-processing (EMC – Huiya Chuang) • Ocean coupling (Dimitri?) • Ocean: POM-TC (Univ. Rhode Island – Isaac Ginis) • Vortex tracking (GFDL – Tim Marchok)

  10. Vortex Initialization • Done • Ported to DTC Linux and IBM machines • To do • Make platform independent • Remove unnecessary dependencies • Create scripts to compile and run • Ongoing • Support to community (documentation, tutorials, helpdesk)

  11. Post-processor • DTC has been supporting WPP (WRF Post-processor) • HWRF uses a locally modified version of WPP • EMC moving towards Unified Post • DTC would like to end support to WPP and begin supporting Unified Post • HWRF capabilities would need to be put in Unified Post • Both R & O can use Unified Post for HWRF • Identify EMC back-up support for Post

  12. Ocean Coupling • Developed at EMC by Dimitri • Needs to reside in a code repository (at EMC or at DTC?) • Changes from community (platform, bug fixes) must make it back to repository for next release • Need to identify support person (technical documentation, answer questions)

  13. Additional ongoing activities • Preparing HWRF Users’ Guide • Coordination with GFDL on support of GFDL Vortex Tracker to community (via DTC) • Coordination with URI on support of POM-TC to community (via DTC) • Coordination with NCAR / MMM on Joint Tutorial aspects, including lining up speakers for first 2 days of science

  14. DTC – EMC Collaboration 1 • Agreement that HWRF code from 2010 will be from the WRF repository – pending performance of the large test • Permission for DTC to modify WRF-NMM code to add dynamics features as namelist or compile-time options • Will not impact NAM’s performance • Future changes to WRF-NMM code in repository need to be agreed upon by both HWRF and NAM groups • EMC HWRF and NAM groups to back DTC in answering questions about model

  15. DTC – EMC Collaboration 2 • HWRF group to support Vortex Initialization • Agreement on how to proceed with Unified Post • Identify support for Unified Post • Agreement on code repository for Ocean coupler • Identify support for coupler

More Related