Next: Operational control Up: Parallel Ocean Program (POP) Previous: Testing POP   Contents


Running POP

This chapter begins with the assumption that the user has followed the instructions in the previous chapter and has successfully built a pop executable. A second assumption is that the user might want to actually run an ocean simulation with the code, thereby impressing friends and colleagues and becoming a card-carrying member of the POP user's club. Given these assumptions, the following describes all the many options for configuring an ocean simulation with POP.

POP requires some input data to run correctly. The first requirement is a file called pop_in that contains many namelists that determine options and parameter values for the run. A sample input file should have been created in the run directory, but can also be found in the input_templates directory.

In addition to the namelist input file, files will be required to initialize grids, preconditioners, fields for output and possibly other options. These will be discussed in more detail below and in later chapters.

The namelists and the model features that they control are presented below. Each namelist appears in a table whose columns contain:

The namelists are presented in approximately the order in which they are called during the initialization of a POP run. However, some regrouping has been done to bring related topics together. The actual order of the namelists within the pop_in file can be arbitrary; the code will search the file for the proper namelist to be read.

CESM1 Notes

A script for constructing the CESM1 POP2 namelist input file, pop2_in, is created during the CESM1 "configure -case" step, which invokes the CESM1 POP2 pop2_in_build.csh script. After the "configure -case" command is invoked, a script for creating pop2_in will appear in the $CASE/Buildnml/pop2.buildnml.csh script.

This script will contain a collection of pre-determined settings that were selected based on the particular $CASE configuration. A user may choose to change any of these settings, but caution should be used because many subtle interactions between the namelist variable settings are normally handled "behind the scenes" by the CESM1 POP2 setup scripts.



Subsections
  • Horizontal mixing parameterizations
  • Physical process options
  • Forcing options (ocean-only mode)
  • Running POP in coupled mode

    Next: Operational control Up: Parallel Ocean Program (POP) Previous: Testing POP   Contents

    2010-03-31