@Article{hack:ncar,
  author = {James J. Hack and James M. Rosinski and David L. Williamson and
  Byron A. Boville and John E. Truesdale},
  title = {Computational design of the {NCAR} community climate model},
  journal = {Parallel Computing},
  year = {1995},
  volume = {21},
  pages = {1545--1569},
  publisher = {North-Holland (Elsevier Scientific)},
  keywords = {parallel computing, scientific computing, weather prediction,
  global climate model, parallel I/O, pario-bib},
  comment = {There is some discussion of I/O issues. This weather code does
  some out-of-core work, to communicate data between time steps. They also dump
  a 'history' file every simulated day, and periodic checkpoint files. They are
  flexible about the layout of the history file, assuming postprocessing will
  clean it up. The I/O is not too much trouble on the Cray C90, where they get
  350 MBps to the SSD for the out-of-core data. The history I/O is no problem.
  On distributed-memory machines with no SSD, out-of-core was impractical and
  the history file was only written once per simulated month. 'The most
  significant weakness in the distributed-memory implementation is the
  treatment of I/O, [due to] file system maturity....' See hammond:atmosphere
  and jones:skyhi in the same issue.}
}

