Sequential CCSM – CCSM/ESMF Stage-1 Meeting

April 11th, 2006, 3:00-4:30pm

Chapman conference room

More on high level picture (Didn't finish)
Agenda:

  1. Briefly review Last meeting, Mar 3rd
  2. Initialization and allowance for components to ask driver for a change in coupling interval.
  3. Some changes to shr_inputinfo_mod and shr_timemgr_mod (part way)
  4. Options for time-averaging... (next time)
  5. (Note time-averaging needs to be done in components as well as driver [averaging ice/atm data up to daily for ocean])
  6. Next meeting? 4 weeks – May 10th
  7. Cam commits: Mariana's, shr_file_mod use, shr_timemgr and shr_inputinfo usage
  8. Who can help code-review of shr code? Brian and Tony
    Action items:
  1. Initialization – allowance for components to ask driver for a change in coupling interval...
    No preference was shown by folks with either of these options

Alturnatives:

  1. Changes to shr_timemgr_mod.F90 (See details of namelist behavior)
  1. Run loop alturnative – run driver at atm/lnd internal time-step
    In this case, we use the straightforward CAM component that just runs over a single time step and doesn't do time-averaging. At initialization, the time-step from atm and lnd would have to be sent up from the components, and used for the driver-time-step. Below I also assume that ice and ocean do not do any time-averaging. Adding time-averaging for ice and ocean should be done for completeness, but would add more complexity at the driver level.
    Assume: