Post on 08-Jan-2018
description
Toward GSI Community Code
Louisa Nance, Ming Hu, Hui Shao, Laurie Carson, Hans Huang
Goals for Community GSI Code
• Provide current operational GSI capability to the research community (O2R)
• Provide a framework for distributed development of new capabilities & advances in data assimilation (R2O)
Operational GSI should be the center piece of the Community GSI Code to allow efficient testing of the impact of new capabilities
GSI Testing and Porting
• Installed GSI on multiple platforms with various compilers– GSD Supercomputer (Linux clusters with both pgi
and intel compilers)– NCAR IBM supercomputers (xlf)– Single Linux workstation (pgi6 and pgi7)
• Tested with both ARW & NMM cores (netcdf format)
• Tested using both single processor and a large number of processors
Configure and Compile Tools
• ConfigureConfigure script produces configure.gsi, which includes computer system information needed for compiling
• Compiling Libraries and GSI– compile all_libs– compile single-library– compile nam_gsi …
Community codes need to be user friendly and portable
GSI Users Pagehttp://www.dtcenter.org/com-GSI/users/
Completed overall structure of web site Populated with available materials
GSI Users Guide
• Finished draft of the GSI Users Guide
• Update to match released GSI version
• Final review
(RED = work in progress)
Users Guide needs to be updated with each new release to the community
On-line tutorial (Beta release)
Success of this structure will depend on communication and collaboration between all GSI code developers and DTC
OperationalRepository
Community Repository
Developers
release
GSD
MMM
Community
EMC DTC Code Management
Plan
GMAO
Others?
Community GSI Code RepositoryProposed Structure
Community GSI Code Repositoryhttps://gsi.fsl.noaa.gov/svn/comgsi
• Subversion server– Server at NOAA/ESRL/GSD, outside firewall– Maintained by NOAA/ESRL/GSD IT staff– Currently accessible from NCAR (bluefire and bay-
mmm) and NOAA (wjet)– Backed up twice daily
• Evolution of trunk– Started with global operational version Q4FY08– Merged global operational version Q1FY09– Added necessary changes for running on Linux
cluster– Added changes for ARW core
GSI Regression Test Suite
Based on JME scripts (ksh, perl) Include 6 test cases now, but easy to extend
Tested on NCAR IBM (bluefire) Cases selected through configure file Verify all test cases and then produce a
summary
Case
# Analysis
time Background
source Background
format Background
error CPU
# Single obs test
comment
1 2007081500 ARW netcdf Global 8 True T8 domain 2 2007081500 ARW netcdf NAM 8 True T8 domain 3 2007122000 ARW binary NAM 12 False EMC case 4 2007122000 ARW netcdf NAM 12 False EMC case 5 2007122000 NMM binary NAM 12 False EMC case 6 2007122000 NMM netcdf NAM 12 False EMC case
Community GSI Code Management Plan
•A plan for how the code will be stored and supported in a repository under a version control.• A policy on who can check-in new code to the community-contributed repository, as well as testing requirements and approval process• A schedule for syncing repositories if multiple repositories exist.•Release schedules and testing requirements.
Key Issues
Code development & maintenance - • Syncing NCEP and Community GSI repositories• Contents of the repositories (e.g., libraries…)• Communications between the various developer
groups and DTC– Email lists?– Periodic meetings?
• How does GMAO fit into picture?• Observations not currently included in NCEP
prepbufr files
Key IssuesUser Support - • Release schedule
– Frequency– Pre-release testing – who will contribute?
• Resident tutorials– Timing & frequency
• 1 or 2 per year?• Part of WRF or separate?
– Developer participation• Lectures• Instructors for hands-on practical sessions
• Helpdesk– DTC will serve as frontline– Need commitment from all developers to provide assistance
when necessary• EMC – one contact point or subject matter experts?