1 |
v2_cs510_Brix |
2 |
Optimized solution described in Brix et al. (2015) |
3 |
|
4 |
v3_cs510_Brix |
5 |
Unpublished ECCO-Darwin v3 with linear piston velocity |
6 |
|
7 |
v3_cs510_latest |
8 |
Same as above with newer (checkpoint66o 2018/01/30) MITgcm code |
9 |
|
10 |
v4_llc270 |
11 |
Optimized solution described in Carroll et al. (submitted 2019) |
12 |
|
13 |
v5_llc270 |
14 |
Inclusion of LOAC (Land-Ocean-Aquatic-Coastal) forcing and |
15 |
other improvements |
16 |
|
17 |
**Team Development Process** |
18 |
|
19 |
When updating ECCO-Darwin code/setup, or anything that may impact ECCO-Darwin: |
20 |
|
21 |
1.) Check in readme.txt file(s) with updated instructions, along with any other input files that are needed. |
22 |
|
23 |
2.) Test updated ECCO-Darwin from scratch by checking out fresh MITgcm code, |
24 |
and following the instructions line-by-line in the readme.txt file(s). |
25 |
|
26 |
3.) Once test is successful, add a full description of changes to MITgcm_contrib/ecco_darwin/tag-index. |
27 |
Include the date and list all specific changes. |
28 |
|
29 |
Example: |
30 |
|
31 |
05/03/19 |
32 |
- To make initialization and pickups more robust: |
33 |
- remove pickupSuff from data |
34 |
- remove PTRACERS_Iter0 and PTRACERS_initialFile from data.ptracers |
35 |
- delete pickup_dic.0000000001.data so that it does not get used for |
36 |
initialization because of above changes |
37 |
|