Opened 15 years ago

Last modified 15 years ago

#402 closed upgrade

Input NetCDF files for BIO_TOY test case — at Initial Version

Reported by: arango Owned by: arango
Priority: major Milestone: Release ROMS/TOMS 3.4
Component: Nonlinear Version: 3.4
Keywords: Cc:

Description

Added grid, initial conditions, and forcing Netcdf files for the BIO_TOY test case. It includes initial conditions for BIO_FENNEL, ECOSIM, NEMURO, and all NPZD models (NPZD_FRANKS, NPZD_IRON, and NPZD_POWELL). All the NetCDF files are now under svn control and located in the Data/ROMS/Grid, Data/ROMS/Initial, and Data/ROMS/Forcing sub-directories, respectively.

  • The grid is a 5x5 double periodic domain sampled from the North Esstern North Atlantic (NENA) application. The grid is:
    ROMS/Data/Grid/bio_toy_grd.nc
    
  • There are several initial conditions files according to ecosystem model. The fields are horizontally uniform which render ROMS into 1D vertical model. These files are:
    ROMS/Data/Initial/bio_toy_ini_fennel.nc     BIO_FENNEL
    ROMS/Data/Initial/bio_toy_ini_ecosim.nc     ECOSIM
    ROMS/Data/Initial/bio_toy_ini_nemuro.nc     NEMURO
    ROMS/Data/Initial/bio_toy_ini_npzd.nc       any NPZD model
    
  • The forcing data is from a typical year (days 0.5 to 364.5) ECMWF 40-year re-analysis. The time coordinate has the cycle_length attribute with a 365 value. Therefore, this application can be run for several year with a prepetual annual forcing cycle. This file is
    ROMS/Data/Forcing/bio_toy_frc.nc
    

The user may want to change a particular initial condition field to a desired value. It is very easy to copy any of these files to a new one and use any NetCDF program to change the field values.

  • I also fixed few documentation typos. Many thanks to Kate Hedström and David Robertson for bringing this to my attention.

Many thanks to Cristina Schultz and John Wilkin for bringing this to my attention. I think that it is better to have these NetCDF files under svn control so we don't forget them in the future.

Change History (0)

Note: See TracTickets for help on using tickets.