Changes between Version 12 and Version 13 of ticket/0932_Standalone_SBC

Timestamp:

2012-04-25T09:43:36+02:00 (12 years ago)

Author:

sga

Comment:

--

ticket/0932_Standalone_SBC

@@ -34 +34 @@
 However no namelist parameters need be changed from the settings of the previous run (except perhaps nn_date0).
 In this configuration, a few routines in the standard model are overriden by new versions.
+This is achieved by creating a new sub-directory SAS_SRC which includes copies of new versions of routines.
+By specifying the order in which sub-directories are included in the build (i.e. SAS_SRC after OPA_SRC in cfg.txt), files with the same name
+in SAS_SRC are preferentially used over those in OPA_SRC.
 
-Routines replaced are:
+Routines in SAS_SRC are:
 
 nemogcm.F90
@@ -45 +48 @@
 
        The main time stepping routine now only needs to call the sbc routine (and a few utility functions).
-
-sbcmod.F90
-
-       This has been cut down and now only calculates surface forcing and the ice model required.  New surface modules
-       that can function when only the surface level of the ocean state is defined can also be added (e.g. icebergs).
 
 daymod.F90
@@ -66 +64 @@
        have been read in) are written along with relevant forcing and ice data.
 
-One new routine has been added:
+The internal workings of one routine have been completely replaced (which means that does not have to be modified):
 
-sbcsas.F90
+sbcssm.F90
 
-       This routine initialises the input files needed for reading temperature, salinity and velocity arrays at the surface.
-       These filenames are supplied in namelist namsbc_sas.  Unfortunately because of limitations with the iom module,
-       the full 3D fields from the mean files have to be read in and interpolated in time, before using just the top level.
+       This routine now initialises the input files needed for reading temperature, salinity, velocity and sea surface height
+       arrays at the surface. These filenames are supplied in namelist namsbc_sas.  Unfortunately because of limitations with the iom module,
+       the full 3D velocity fields from the mean files have to be read in and interpolated in time, before using just the top level. However an
+       option is included to read 2D velocity fields if they are available in the input file, but ln_3d_uv must be explicitly set to be false in the
+       namelist for the code to be able to use them.
        Since fldread is used to read in the data, Interpolation on the Fly may be used to change input data resolution.
 
 ----
 
+== ''' Further Discussion''' ==
+
+Some of the above changes has implications for other parts of the code (and therefore outside the remit of this branch):
+
+ * daymod currently includes a call to open the ocean restart file for writing.  The offline code (OFF_SRC) modifies this with the lk_offline key 
+    and replaces control of nitrst with code in trcrst.F90.  I wonder if control functionality for all restarts should be in its own routine and removed
+    from restart.F90, daymod.F90 and trcrst.F90.  This would mean the above SAS_SRC daymod is unnecessary.
+
+ * There are now three copies of nemogcm with repeat non-overlapping code.  I think this part of these files should be moved into a separate
+    file so there is no danger of divergence when the original OPA_SRC copy of nemogcm is modified.
+
+----
+
 == ''' Test Case ''' ==
+
+''' Note that currently the test below is out of sync with the branch and almost certainly incorrect '''
 
 A standard ORCA2 configuration is run for one year with five day mean output.