Changes between Version 71 and Version 72 of ticket/1851/General

Timestamp:

2017-04-20T15:45:14+02:00 (7 years ago)

Author:

frrh

Comment:

--

ticket/1851/General

@@ -578 +578 @@
    * MEDUSA calls trcini which  calls zps_hde using trn. Should it really be doing that? Why doesn't it use trb?
    * MEDUSA seems to update gtru/v after trc_rad and before trc_trp. Is that analogous to main NEMO?
-   * MEDUSA calculates fo everything including the first 2 tracers which are T and S(aren't they?) Why does it do that? These presumably shouldn't need recalculation since MEDUSA doesn't directly update them and in fact only ever influences them indirectly via a full coupled model!? 
-
-
+   * MEDUSA calculates everything including the first 2 tracers which are T and S(aren't they?) Why does it do that? These presumably shouldn't need recalculation since MEDUSA doesn't directly update them and in fact only ever influences them indirectly via a full coupled model!? 
+
+It turns out that this gtru/v issue has ALREADY been fixed in the vn3.6_STABLE branch. But since that has not been merged into the GO6 branch since July 2016 the fix is missing (along with 50+ other updates). So we need that in GO6 somehow. Looking at the solution, I was right about my suspicions about inappropriate use of time level data and positioning of calculations. The solution has simply been to shiff the location of the call, delete an inappropriate duplicate call at startup and change the time level of data used. So there's no need for extra dump variables.