Changes between Initial Version and Version 13 of Ticket #1911
- Timestamp:
- 2018-06-30T11:46:34+02:00 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1911
- Property Status changed from new to assigned
- Property Severity changed from to minor
- Property Wp_comment changed from to strategy of implementation and design of the targeted code ~OK. Two big steps: (1) transform the leap-frog scheme (MLF) to be consistent with a 2-level time-stepping environment ; (2) introduce the RK3 scheme. Step 1 expected to be ready for the 2018 merge party whereas Step (2) is not assured at that time.
- Property Summary changed from ENHANCE-05_Gurvan — RK-3 time stepping to ENHANCE-04(2017WP) — MLF and RK3 time stepping
- Property Priority changed from normal to high
- Property Milestone changed from 2017 WP to 2018 release-4.0
- Property Keywords FBS RK3 added; time stepping scheme removed
- Property Type changed from Development to Task
-
Ticket #1911 – Description
initial v13 9 9 = Implementation 10 10 \\ 11 In practice the work is to : 12 • add all time varying fields as argument of all DYN and TRA routines (as RK3 schemes uses the same tendency terms as the MLF scheme, but it calls them 3 times by time step) 13 • introduce a stpRK3.F90 time-stepping module (which will contain a stp_RK3 routine) 14 • move the existing MLF scheme (step.F90) in stpMLF.F90 module (containing stp routine renamed stp_MLF) 15 • change the CALL to stp routine in memogcm.F90 by a CALL to either stp_MLF or stp_RK3 depending of namelist parameters 11 Chosen strategy : keep both MLF and RK3 time-stepping in the code. This means : first transform the LF scheme to be consistent with a 2-level time-stepping environment, and then introduce the RK3 scheme. 16 12 \\