You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ReadMe.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,34 +27,30 @@ Both are implemented in the `Fortran`-based Framework for Aquatic Biogeochemical
27
27
28
28
## Description
29
29
30
-
-`OxyPOM` simulates oxygen consumption and production in aquatic ecosystems [(Holzwarth and Wirtz, 2018)](https://doi.org/10.1016/j.ecss.2018.01.020) and resolves key biogeochemical processes as photosynthesis, respiration, mineralization, and nitrification.
30
+
-`OxyPOM` simulates oxygen consumption and production in aquatic ecosystems [(Holzwarth and Wirtz, 2018)](https://doi.org/10.1016/j.ecss.2018.01.020) and resolves key biogeochemical processes as photosynthesis, respiration, mineralization, and nitrification.
31
31
32
-
-`DiaMO` is a simplification of `OxyPOM` useful when a complete representation of bio-geochemical dynamics is not needed,
32
+
-`DiaMO` is a simplification of `OxyPOM` useful when a complete representation of bio-geochemical dynamics is not needed,
33
33
34
34
The code of these models is located in the directory `./src` (e.g., `./src/oxypom` and `./src/diamo`), and future code developed as part of this model should be here included.
35
35
36
36
Together with `OxyPOM` and `DiaMO`, this repository includes the model `oxypom/light`: a second order correction for the calculation of photosynthetically active radiation depth profiles.
37
37
38
38
## Requirements
39
39
40
-
-This model requires:
40
+
- This model requires:
41
41
42
-
-`FABM` (v1 or above) available in [fabm github](https://github.com/fabm-model/fabm/).
43
-
It can be cloned using `git clone https://github.com/fabm-model/fabm.git fabm`.
42
+
-`FABM` (v1 or above) available in [fabm github](https://github.com/fabm-model/fabm/).
43
+
It can be cloned using `git clone https://github.com/fabm-model/fabm.git fabm`.
44
44
45
-
-The physical driver:
46
-
-`GOTM` (v6.0 latest stable release) available in [gotm github](https://github.com/orgs/gotm-model/repositories).
47
-
It can be cloned using via `git clone --recursive https://github.com/gotm-model/code.git -b v6.0 gotm6`.
45
+
- The physical driver:
46
+
-`GOTM` (v6.0 latest stable release) available in [gotm github](https://github.com/orgs/gotm-model/repositories).
47
+
It can be cloned using via `git clone --recursive https://github.com/gotm-model/code.git -b v6.0 gotm6`.
48
48
49
49
The following is not required to build and run the model but it is for running the test case:
50
50
51
-
-The script for downloading forcing and validation data requires the following shell commands:
51
+
- The script for downloading forcing and validation data requires the shell commands`wget`, `unzip`, and `sed`.
52
52
53
-
-`wget`
54
-
-`unzip`
55
-
-`sed`
56
-
57
-
- The scripts for generating forcing files setup and plotting routines for model validation require: -`R` (v4.3 or above) available in [r home](https://www.r-project.org/) with the library [`ncdf4`](https://cran.r-project.org/web/packages/ncdf4/index.html) installed.
53
+
- The scripts for generating forcing files setup and plotting routines for model validation require `R` (v4.3 or above) available in [r home](https://www.r-project.org/) with the library [`ncdf4`](https://cran.r-project.org/web/packages/ncdf4/index.html) installed.
58
54
59
55
## Testcases
60
56
@@ -66,7 +62,7 @@ Currently, we include the testcase "Estuary".
66
62
67
63
This setup uses the physical driver `GOTM` to simulate the water column dynamics in the Elbe estuary in 2005-2024.
68
64
69
-
1. To run the testcase go to the directory `.\testcases`.
65
+
1. To run the testcase go to the directory `./testcases`.
70
66
71
67
The model is build with the script `gotm-installation.sh`, in where these variables must be defined: - `GOTM_DIR` base directory of GOTM source code - `FABM_DIR` base directory of FABM source code - `OXYPOM_DIR` base directory of OxyPOM source code
72
68
@@ -78,10 +74,10 @@ By default they are:
78
74
export OXYPOM_DIR=$HOME/tools/oxypom/src
79
75
```
80
76
81
-
2. The script `gotm-installation.sh` creates the directory `.\build` with the building files, and a copy of `gotm` executable in the `.\estuary` directory.
82
-
Now move to the directory `.\estuary`.
77
+
2. The script `gotm-installation.sh` creates the directory `./build` with the building files, and a copy of `gotm` executable in the `./estuary` directory.
78
+
Now move to the directory `./estuary`.
83
79
84
-
3. The script `get_data.sh` download and unzip the forcing and validation data from [kuestendaten.de](https://www.kuestendaten.de) in a newly created directory `.\data`.
80
+
3. The script `get_data.sh` download and unzip the forcing and validation data from [kuestendaten.de](https://www.kuestendaten.de) in a newly created directory `./data`.
85
81
The downloaded files are used under license [DL-DE->Zero-2.0](https://www.govdata.de/dl-de/zero-2-0).
86
82
87
83
4. The script `setup_data.R` formatted the data to be read by `GOTM`. It generates the file `meteofile.csv`.
@@ -101,9 +97,9 @@ This setup uses the physical driver `GOTM` to simulate the water column dynamics
101
97
102
98
Follow steps 1-2 of the estuary testcase.
103
99
104
-
Now move to the directory `.\light`.
100
+
Now move to the directory `./light`.
105
101
106
-
-The script `model_comparison.R` analyses the model output.
102
+
- The script `model_comparison.R` analyses the model output.
107
103
108
104
If everything is correct, the figure `light_validation.png` should be produced.
109
105
It displays a comparison of simulations using the default light implementation with the provided by `oxypom/light`.
@@ -124,7 +120,7 @@ We recommend to use latest git commit an branch main version of the model.
124
120
We appreciate your feedback, bug reports and improvement suggestions on our GitLab [issue tracker](https://codebase.helmholtz.cloud/dam-elbextreme/oxypom/-/issues).
125
121
We also welcome your contributions, subject to our Contributor Covenant [code of conduct](https://codebase.helmholtz.cloud/dam-elbextreme/oxypom/-/blob/main/doc/contributing/code_of_conduct.md) and our [Contributor License Agreement](https://codebase.helmholtz.cloud/dam-elbextreme/oxypom/-/blob/main/doc/contributing/contributing-license.md).
126
122
127
-
The best way to contribute is by (1) creating a fork off our repository, (2) committing your changes on your fork and then (3) creating a pull request ("PR") to push your changes back to us.
123
+
The **best way to contribute** is by (1) creating a fork off our repository, (2) committing your changes on your fork and then (3) creating a pull request ("PR") to push your changes back to us.
128
124
129
125
To file an issue or to contribute, you are asked to (1) authenticate with an existing identity and (2) to register on the HIFIS GitLab instance and sign in.
0 commit comments