DTC HWRF Task AOP2009 & AOP2010

1. DTC HWRF TaskAOP2009 & AOP2010 10/01/2009 Ligia Bernardet

2. AOP 2009 - I DTC HWRF Team – 1.4 FTE • Ligia – Task Lead 30% • Shaowu – Scientist 90% • Louisa – Planning and coordination 5% • Laurie – Software Engineer Support – 10% • Chris Harrop – 5% • Main Goal • Port, test, and prepare the NCEP Hurricane WRF (HWRF) modeling system for support to the community

3. AOP 2009 - II • Code Management • An agreement on HWRF code management will be drafted between EMC and DTC. The goal of this agreement is to create a framework that supports exchange between the operational and research communities.✓ • A plan for community support of POM coupler will be drafted with URI. ✓ • A plan for community support of GFDL Vortex Tracker will be drafted with GFDL. ✓ • Atmospheric Model • Atmospheric HWRF will be included in a branch (✓)of the WRF repository, tested, and added to the trunk (✗) of the WRF repository (v3.1.1+), making HWRF a compile-time and run-time configuration of WRF. These capabilities include • HWRF dynamics, including vortex-tracking moving nest • Ability to run in coupled mode • HWRF physics schemes • Support for binary I/O • Model restart

4. AOP 2009 - III •  Pre-processing • The Domain Wizard capability will be extended to support the HWRF domain configuration.✓ • Additional HWRF components • The non-WRF components of HWRF (initialization, coupler and POM ocean model) will be ported to and tested on the ESRL and NCAR DTC computer platforms.✓ More tests will be done. • Testing • A hierarchy of tests will be developed and performed to ensure that the HWRF configuration is not unintentionally modified and to asses the performance of the HWRF configuration. These tests include: • Sanity checks to be performed using the branch code before it is moved to the trunk, first just with the WRF model and then incorporating the coupler, ocean, and vortex initialization components. ✓ • Regression tests to be run before and after HWRF capabilities are added to the repository.✗ • Large test (approximately 250 cases) using repository code to verify if HWRF configuration from the repository gives results comparable to operational version, so that operational code for 2010 hurricane season can be drawn from repository.Underway.

5. AOP 2009 - IV •  WRF for Hurricanes Tutorial to occur in FY2010 • Planning will be conducted jointly with external collaborators (NCAR MMM, GFDL, AOML, URI)✓ • Begin preparations for HWRF community support: • Scientific documentation ✓ • Users’ Guide✓ • Helpdesk • Online Tutorial • Test cases

6. AOP 2010 - Remarks • Plan counted with participation of 1 Software Engineer. Don (50%) will help. • EMC HWRF Team has put considerable effort into this Task. While this was expected in the first year of the project, it is anticipated that their participation will taper off in FY 2010. • Propose increasing Ligia’s participation (concentrated until February) to perform additional tasks of: • Editing Users’ and scientific documentation. Since these documents will have contribution from multiple sources, an editor will be needed. • Assisting in preparation of classroom exercises. The increase in Ligia’s time and SE time is not really an “increased effort” but a necessity to fill gaps and meet deadlines. Proposed FY 2010 DTC HWRF Team – 2.05 FTE • Ligia – Task Lead 40% • Shaowu – Scientist 100% • Laurie – Software Engineer– 10% • Chris - Software Engineer– 5% • Don – Software Engineer - 50%

7. AOP 2010: Scenario 1 First Quarter • Participate in the preparation and result-evaluation of the Big R2O test. • Complete tests of the ported POM-TC model to assure that the HWRF ocean component has been ported successfully to wjet and Bluefire. • Prepare Vortex Initialization (VI) code for community distribution. • Setup code repositories for tracker, coupler, POM, and VI. • Merge the HWRF repository branch to the WRF repository trunk. • Work on HWRF technical and scientific documentations. • Plan Tutorial. Second Quarter • Plan Tutorial. • Finalize the HWRF documentations. Prepare tutorial materials and lectures. • Deliver the WRF for Hurricanes. • Provide HWRF user support by updating technical documentation (Users'Guide), developing and maintaining HWRF website, helpdesk, and test cases. • Conduct monthly repository testing. *** could take longer!

8. AOP 2010: Scenario 1 Third Quarter • Provide HWRF user support. • Begin work collaboratively AOML to include a high-resolution movable grid-nesting algorithm capability (three telescopic domains) in the WRF-NMM system. • Begin the work bringing HYCOM to DTC. • Conduct monthly repository testing Fourth Quarter • Provide HWRF user support. • Finalize inclusion of a high-resolution movable grid-nesting algorithm capability (three telescopic domains) in the WRF-NMM system. • Continue HYCOM effort. • Conduct monthly repository testing

9. AOP 2010: Scenario 2 • Incorporate support of MPI binary IO to WPP V3. (0.05 FTE SE) • Clean up of GFDL Tracker code. (0.1 FTE SE) • Clean up ocean initialization code. (0.1 FTE) • Develop a HWRF coupled system infrastructure at the DTC (scripts, automation, collection of data) using the GSD workflow manager framework. (0.25 FTE SE) (Mike Page) • Extend community HWRF capabilities to other basins and to realtime runs and creating new canned cases. Also expand HWRF support to more compilers and platforms. (1 FTE split SE/scientist) • Extend testing capability to reproduce EMC’s. (0.5 FTE) • Accelerate implementation of 3rd nest in HWRF to Q3. (0.25 FTE) • Complete transition of HYCOM to DTC supported code. (1 FTE split SE/scientist) • Create hurricane Reference Configurations. Use the Big R2O Test to create a baseline of performance. Test system with variations in… (1 FTE for 4 RC) • Horizontal resolution (3rd nest) • Vertical resolution • Physics • Initialization • Etc TBD