| Version 7 (modified by techene, 3 years ago) (diff) |
|---|
Name and subject of the action
Last edition: Wikinfo(changed_ts)? by Wikinfo(changed_by)?
The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.
Summary
| Action | RK3 stage 1 |
|---|---|
| PI(S) | Gurvan et Sibylle |
| Digest | Run a GYRE configuration with new RK3 scheme |
| Dependencies | If any |
| Branch | source:/NEMO/branches/2021/dev_r14318_RK3_stage1 |
| Previewer(s) | Gurvan |
| Reviewer(s) | Names |
| Ticket | #2605 |
Description
RK3 time stepping implementation for NEMO includes at this stage dynamic and active tracers implementation, time spitting single first with 2D mode integration.
...
Implementation
RK3 implementation is splitted up into :
- code preparation
- dynamic and active tracers (barocline)
- vertical physics (TKE) ?
- barotropic mode (barotrope)
- mass forcing
- passive tracers
Code preparation In order to preserve constancy property velocity for momentum and active tracers must be the same. Advection routines in flux form are modified to take (u,v,w) as an input argument. In order to use advection routines for the barotropic mode we need the possibility to de-activate vertical advection computation. Advection routines in flux and vector form are modified to take an optional argument (no_zad) to do so.
Barocline part For sake of simplicity we started to implement RK3 regarding a GYRE configuration validation with no barotrope mode (ssh, uu_b, un_adv are set to zero at each time step). Forcing have been removed except winds and heat flux. key_qco is active and vertical physics is modeled as constant with high viscosity coefficients.
- Prepare routines
- Change eos divhor and sshwzv interface.
- Add RK3 time stepping routines
- rk3stg deals with time integration at N+1/3, N+1/2 and N+1
- stprk3 orchestrates
Barotrope part In order to validate 2D mode implementation we remove above zero forcing for barotropic variables mass forcing remains to zero.
- Prepare routines
- Change dynadv, dynvor, dynspg_ts
- Add RK3 2D mode time stepping routines
- rk3ssh prepare 2D forcing, get dynamics 2D RHS from 3D trends, integrate 2D mode
...
Implementation details
Code preparation
3D velocity can be a pointer
OCE
|-- oce.F90
REAL(wp), PUBLIC, ALLOCATABLE, SAVE, DIMENSION(:,:,:,:), TARGET :: uu , vv !: horizontal velocities [m/s]
REAL(wp), PUBLIC, ALLOCATABLE, SAVE, DIMENSION(:,:,:) , TARGET :: ww !: vertical velocity [m/s]
3D velocity added as an input argument of advective routines
OCE
|--DYN
|-- dynadv.F90
SUBROUTINE dyn_adv( kt, Kbb, Kmm, puu, pvv, Krhs, pau, pav, paw )
Documentation updates
...
Preview
...
Tests
...
Review
...
