Changes between Version 2 and Version 3 of ticket/1358
- Timestamp:
- 2014-11-06T15:57:37+01:00 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ticket/1358
v2 v3 13 13 === Description === 14 14 15 The NEMO offline observationo operator needs to be updated, refactored and simplified. To allow the code to compile, the custom `nemogcm.F90` must be updated to make it compatible with the latest version of OPA `nemogcm.F90`. The primary refactoring involves renaming the sub-directory containing the code from **OOO_SRC** to **SAO_SRC**, representing the name "**S**tand **A**lone **O**bservation operator" which should make the purpose of the package clearer. A side effect of this change is that NEMO uses a hungarian notation esque naming convention to reduce pollution of the global namespace and to diagnose the origin of a piece of code,these will have to be updated from ooo to sao or be dropped. Other less obvious refactorings will present themselves during the development cycle. A suite of use-cases has been written to test the functionality of the compiled executable, these will be used ahead of every commit to ensure that functionality has not been affected by the refactoring process. There is also a suggestion by the external reviewer during the previous development cycle to change the way the I/O is controlled from the custom read/write code which is already in place to a more common framework seen in other stand alone executables such as **OFF_SRC**.15 The NEMO offline observationo operator needs to be updated, refactored and simplified. To allow the code to compile, the custom `nemogcm.F90` must be updated to make it compatible with the latest version of OPA `nemogcm.F90`. The primary refactoring involves renaming the sub-directory containing the code from **OOO_SRC** to **SAO_SRC**, representing the name "**S**tand **A**lone **O**bservation operator" which should make the purpose of the package clearer. A side effect of this change is that NEMO uses a hungarian notation style naming convention to reduce potential conflicts in the global namespace and also to ease location of a piece of code, in the context of OOO_SRC these will have to be updated from ooo to sao or be dropped. Other less obvious refactorings will present themselves during the development cycle. A suite of use-cases has been written to test the functionality of the compiled executable, these will be used ahead of every commit to ensure that functionality has not been affected by the refactoring process. There is also a suggestion by the external reviewer during the previous development cycle to change the way the I/O is controlled from the custom read/write code which is already in place to a more common framework seen in other stand alone executables such as **OFF_SRC**. 16 16 17 17 ---- 18 18 === Use cases === 19 19 20 The NEMO observation operator is a well used piece of code which has been extensively tested, as such, these use cases do not intend to be a complete suite of possible uses of the observation operator code. 20 The NEMO observation operator is a well used piece of code which has been extensively tested, as such, these use cases do not intend to be a complete suite of possible uses of the observation operator code. They are intended to cover the 21 functionality expected by running it in stand alone mode. 21 22 22 23 * Sea surface temperature cases