1 / 4

Enhancing HWRF Code Management: Lessons from Current Repository Structure

In this presentation by Ligia Bernardet at the HFIP Ensemble Team meeting, we explore the current structure of the HWRF code repository, hosted by DTC. The trunk contains essential scripts, namelists, and source code, with a top-level makefile that builds all components. HWRF’s architecture consists of eight community repository links, allowing for additional components like the EnKF directory. We focus on effective maintenance, straightforward administration, and safeguarding operational integrity while maximizing accessibility and minimizing labor for developers. Our requirements are tailored to derive the optimal solution.

sal
Télécharger la présentation

Enhancing HWRF Code Management: Lessons from Current Repository Structure

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. GSI-hybrid code management: what can we learn from learn from HWRF? Ligia Bernardet 09 January 2012 HFIP Ensemble Team meeting

  2. Current HWRF Repository Structure • HWRF code repository hosted by DTC • Trunk contains scripts, namelists, and source code • Source directory build system: top makefile builds all components • The eight components of HWRF are “links” to the community repositories • A EnKF directory can be added as another component

  3. HWRF components sync sync * libraries, vortex initialization, tools

  4. EnKF code repository requirements • Maintained and administered in a straightforward way • Provides reliable, almost un-interrupted access, backed-up • Provides access to all developers • Requires least amount of labor • Has safeguards to prevent damaging operational code by outside contributions • Has framework that minimizes errors when merging code between development and trunk Our requirements should lead us to the best solution!

More Related