Difference between revisions of "Applications"

From WikiROMS
Jump to navigationJump to search
Line 11: Line 11:
* applications can be shared with colleagues without redistributing the entire source code, thereby fostering user community use of the most up-to-date ROMS release
* applications can be shared with colleagues without redistributing the entire source code, thereby fostering user community use of the most up-to-date ROMS release


Most users configuring a typical application of the forward simulation model will need to edit only:
Most users configuring a typical application of the forward simulation model need only edit:


* a file containing the CPP definitions, e.g. ''project.h''
* a file containing the CPP definitions, e.g. ''project.h''

Revision as of 01:48, 10 May 2007

Contributed User Applications

User applications that are not distributed with the ROMS source code are invited here.

Changes to the code structure with the introduction of ROMS 3.0 make it straightforward to confine application-specific options to a small number of files maintained separately from the central code.

This approach has the advantages that:

  • users can update their central code, adding newly developed features and fixing reported bugs, without upsetting personal options for a specific project
  • users can work on more than one project using a single up-to-date code stem
  • applications can be shared with colleagues without redistributing the entire source code, thereby fostering user community use of the most up-to-date ROMS release

Most users configuring a typical application of the forward simulation model need only edit:

  • a file containing the CPP definitions, e.g. project.h
  • an input ocean.in script
  • initial, forcing and/or boundary netcdf files
  • application-specific analytical options following the templates for ana_*.F files in the User/Functionals directory.


CBLAST

Configuration and input files for a model of the southeast New England shelf during the ONR Coupled Boundary Layers and Air-Sea Transfer (CBLAST) experiment are provided here as one example of how we recommend users configure realistic applications with ROMS 3.0.

The files required to configure and run ROMS 3.0 for CBLAST are available for download from www.myroms.org at the Datasets link on the left navigation panel (under the subheading Software), or follow this link [1].

A brief description of the files follows:


cblast.h

ocean_cblast.in

The ocean_cblast.in file has relative paths to input files that assumes the following directory. You can adapt this to your own requirements. Our choice of directory hierarchy anticipates other applications with the Adjoint and 4DVAR codes for model sensitivity and data assimilation studies which would require distinct cblast.h files in each subdirectory (all controlled by a master driver script).




A description of the model configuration and results from the application of the model to data acquired during the 2002 CBLAST field season are described in:

Wilkin, J., 2006: The summertime heat budget and circulation of southeast New England shelf waters, Journal of Physical Oceanography, 36(11), 1997-2011.

The URL for full text article: http://ams.allenpress.com/perlserv/?request=get-document&doi=10.1175%2FJPO2968.1


Other results using this model set-up in a study of tidal circulation on the Nantucket Shoals are presented in:

He, R. and J. Wilkin, 2006: Barotropic tides on the southeast New England shelf: A view from a hybrid data assimilative modeling approach. Journal of Geophysical Research, 111, C08002, doi:10.1029/2005JC003254.

LATTE