New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
2013WP/2013Stream1/Configuration_Setting (diff) – NEMO

Changes between Version 11 and Version 12 of 2013WP/2013Stream1/Configuration_Setting


Ignore:
Timestamp:
2013-02-12T15:57:42+01:00 (11 years ago)
Author:
frrh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2013WP/2013Stream1/Configuration_Setting

    v11 v12  
    5959Marcello: Solution3 was partly discussed during the meeting and I found it very clever. This is very much equivalent to Solution1 but without the need to run a parser first. On the other hand, the step of running the parser can be included in the example script for job submission, but I do agree that it is less automatic.  Incidentally, perl must be installed on the machines, otherwise FCM does not work! In summary, I'm for SOLUTION3 and second choice SOLUTION1. 
    6060 
     61Richard H: As the model increases in size and content it can become increasingly difficult (and important) to be able to compare a standard configuration with some alternative/updated/modified configuration. However, the namelist is potentially a single point of reference which could be used to do this. e.g. if ALL inputs must come via a single namelist (or even via the 2 stage namelist in solution 3) then we have an easy means of finding the difference between two configurations. Initialising all namelist fields to missing data indicators in the code ensure that all input fields must be given a valid value in the namelist (or the model will crash). Allowing all/some fields to be given defaults in the FORTRAN code means that people can apply changes by modifying FORTRAN code OR namelist values, whereas defaulting everything to missing data values ensures only the namelist is an acceptable mechanism for changing inputs and gives us a single point of reference/definition for model settings.          
     62 
    6163=== Add your vote below 
    6264 
    63 SOLUTION1 "3 namelists, 1 additional step":[[BR]]SOLUTION2 "1 namelist, more initialisation in the code":[[BR]]SOLUTION3 "2 namelist, more READS in the code": Marcello[[BR]]??? 
     65SOLUTION1 "3 namelists, 1 additional step":[[BR]] 
     66SOLUTION2 "1 namelist, more initialisation in the code": (Richard H - but only if the initialisation is to missing data values!) [[BR]] 
     67SOLUTION3 "2 namelist, more READS in the code": Marcello, Richard H [[BR]]???