1 | ICB |
---|
2 | --- |
---|
3 | |
---|
4 | ICB is a very idealized configuration used to test and debug the icb module. |
---|
5 | The configuration is box with a shallow shelf (40m) on the east and west part of the domain with a deep central trough (> 100m). |
---|
6 | ICB are generating using the test capability of the icb model along a E-W line (this can easily be tuned). |
---|
7 | |
---|
8 | In this configuration, ONLY the ICB module is activated. It means that: |
---|
9 | - SI3 is OFF |
---|
10 | - NO atmospheric fluxes. See usr routine in MY_SRC. |
---|
11 | - NO time variation of ocean properties. T, S, U, V, ssh (...) are intialized and never changed in time. This is achieved by simplifying the step.F90 routine in MY_SRC. |
---|
12 | |
---|
13 | Resolution and Initial condition are: |
---|
14 | - Homogeneous S (34) |
---|
15 | - Spatially constant T set to 2 over the first 2 levels and 1 below |
---|
16 | - Spatially constant (U,V) set to (1,0) over the first 2 levels and (0,1) below |
---|
17 | - e3 is set to 10m |
---|
18 | - iceberg thicness is set to 100 in the class tested (10 level affected). |
---|
19 | - iceberg density is set to 1026 as the ocean reference density => icb tikness = icb draft (easier to evaluate the output) |
---|
20 | |
---|
21 | Results expected are: |
---|
22 | - ln_M2016 = F => icb moving along the W direction only and pilling up on the W side of the domain. |
---|
23 | - ln_M2016 = T => icb on shallow bank move at 45 degrees (NW) and 76 degrees (NNNNW) in the deeper through. |
---|
24 | - ln_M2016 = T and ln_icb_grd = T => as before but now icb cannot move onto the shallow bank on the W and migrate northward along the shelf break. Some get stuck at specific point because of the grounding law (they always get back to there intial position at every time step). |
---|
25 | |
---|
26 | This set up allow us to easily test various option of the ICB code as: |
---|
27 | - ln_M2016 (use properties in depth to compute dyn and thd) |
---|
28 | - ln_icb_grd (use icb bottom level of the icb (tail) to ground the icb or not) |
---|
29 | |
---|
30 | It can also help us to: |
---|
31 | - reproduce bugs (interpolation issue for example) |
---|
32 | - develop and test new functionalities (new grounding scheme for exemple) |
---|
33 | - evaluate ICB performance alone |
---|
34 | |
---|
35 | The side effect of the implementation is that: |
---|
36 | - the run.stat (if produced) is meaningless as NEMO tracer and dynamics are not computed |
---|
37 | |
---|
38 | |
---|