Version 3 (modified by vigilant, 15 years ago) (diff) |
---|
Previous NEMOVAR code organization
The current repository structure (csee figure below) is divided into two main folders: nemo and nemovar. The source code of nemovar folder is divided into two other folders: tam (for tangent and adjoint module) and inner (for assimilation and test module engines). The re-organization of the code aims at achieving a mirror-like between nemo and nemovar source code. For instance, we do not realise easily that the current nemovar code is only dealing with the ocean component OPA. In addition, althought the final goal of the project is to implement 4DVar assimilation, the tangent and the adjoint modules could be used for other purposes. Thus, to prepare further development and follow the flexibility spirit of the NEMO platform, it is appropriate to separate what is specific to 4DVar assimilation from what is not.
New NEMOVAR code organization
The project will work with two repositories (see figure below):
- a NEMOBASE repository, with an official NEMO released version (currently the L3.0)
- a NEMOVAR repository, with all development related to the nemovar project including new and modified files for NEMO.
The building process will link both repositories, if any redundancy is found NEMOVAR files will overwrite NEMOBASE files in the build folder.
Attachments (5)
-
trunk.png
(53.1 KB) -
added by vigilant 15 years ago.
older code structure
-
git-struct.png
(9.1 KB) -
added by vigilant 15 years ago.
two repositories structure
-
nemovar.png
(18.8 KB) -
added by vigilant 15 years ago.
nemovar code structure
-
nemobase.2.png
(23.4 KB) -
added by vigilant 15 years ago.
nemobase code structure
-
nemobase.png
(23.4 KB) -
added by vigilant 15 years ago.
nemobase code structure
Download all attachments as: .zip