@InProceedings{galbreath:applio,
  author = {N. Galbreath and W. Gropp and D. Levine},
  title = {Applications-Driven Parallel {I/O}},
  booktitle = {Proceedings of Supercomputing '93},
  year = {1993},
  pages = {462--471},
  publisher = {IEEE Computer Society Press},
  address = {Portland, OR},
  later = {galbreath:bapplio},
  keywords = {parallel I/O, pario-bib},
  comment = {They give a useful overview of the I/O requirements of many
  applications codes, in terms of input, output, scratch files, debugging, and
  checkpointing. They also describe their architecture-independent I/O
  interface that provides calls to read and write entire arrays, with some
  flexibility in the format and distribution of the array. Curious centralized
  control method. Limited performance evaluation. They're trying to keep the
  I/O media, file layout, and I/O architecture transparent to the user.
  Implementation decides which processors actually do read/write. Data
  formatted or unformatted; file sequential or parallel; can specify
  distributed arrays with ghost points. Runs on lots of platforms; will also be
  implementing on IBM SP-1 with disk per node, 128 nodes. Their package is
  freely available via ftp. Future: buffer-size experiments, unstructured data,
  use parallel file internally and then seqeuentialize on close.}
}