May 7, 2015

Performance

• new model configurations (as exploratory options) are coming online

• i/o issues are also important to us

• performance may be better optimized if we use multples of 16 levels

  • (advice has been updated: sufficient if number of levels is a multiple of 8)

• ensemble strategies may present new challenges. Would like some assistance in optimization

Land

• single biggest challenge is orographic downscaling

• interest in common datasets for verification/validation

• land group recommend test configuration of ALM with prescribed phenology for testing

Software Engineering

• atmosphere team will begin providing many more climate changing modifications to master.

• appropriate strategy for testing, evaluation and providing new baseline sims, etc need to be established

• perhaps start testing atmosphere only with data ocean and data atmosphere?

Ocean/Cryo

• time to begin doing short simulations with MPAS-Ocean (prescribed sea ice)

• interest in common datasets for verification/validation 

• interest in exploring "alternate data atmospheres"(not CORE.v2) to drive ocean model

  • ACME atmosphere

  • alternate observational datasets (e.g. CERES-EBAF-Surface) for radiative fluxes.

Workflow

• improved communications are needed. There is some uncertainty in the atmosphere team about how "showstoppers" identified at Discussion about atmosphere group priorities for diagnostics in Y1Q3 are being handled by the workflow team. It is clear that some have already been fixed and others are being worked on. But it is not yet clear whether all are being worked on or what is the schedule for completion. We will have some follow up phone calls to resolve this.

• One of the showstoppers specifies the need for an observational data repository, with datasets fixed to be CF Compliant and that satisfy minimal ACME standards. (see Requirements for Observational Datasets to be used for ACME science). @Jeffrey Painter (Unlicensed) notes that it would take a lot of work to fix all the datasets currently used by the NCAR NCL scripts. @Phil Rasch (pnl.gov) (Unlicensed) agreed, and indicated that the atmosphere team were not specific enough in our request. What in fact we hoped for was:

  • a single official obs dataset repository (which could be mirrored) that was backed up, and supported versioning, etc

  • as new or updated datasets were committed to that respository that those datasets satisfied the miniminal ACME standards described at Requirements for Observational Datasets to be used for ACME science

• part of improved communication is a better method for issue tracking. @Dean N. Williams (Unlicensed) anticipates a better proposed solution in about 3 months time, in the meantime we will improvise.