Changes between Version 17 and Version 18 of 2020WP/ENHANCE-10_acc_fix_traqsr

Timestamp:

2020-05-20T16:00:23+02:00 (4 years ago)

Author:

acc

Comment:

--

2020WP/ENHANCE-10_acc_fix_traqsr

@@ -118 +118 @@
 Part 1 has even greater inefficiencies though since it repeats some computationally expensive calculations in a 3D loop even though much of it is 2D in nature. In fact the complexity of the calculations can be reduced further by operating in log-space. 
 
-After trying a few options and iterating at the preview stage (see earlier investigations below), the final solution choose was:
-
+After trying a few options and iterating at the preview stage (see earlier investigations below), the final solution chosen is given below. Its performance, compared with the original and a minimum memory option (see earlier investigations) is shown here:
+
+[[Image(percent_cpu_qsr.4.png, 530px)]]
+[[Image(rankqsr.4.png, 530px)]]
+
+where the information is taken from the timing.output report of a 64 timestep, ORCA2_ICE_PISCES test using the SETTE test harness. Rank refers to the position of the tra_qsr routine in the list of routines sorted by CPU time (most expensive first). A higher rank, therefore, indicates improved performance relative to the rest of the code.
+
+The final code:
 {{{#!f
       CASE( np_RGB , np_RGBc )         !==  R-G-B fluxes  ==!
@@ -785 +791 @@
           !
 }}}
-[[Image(percent_cpu_qsr.3.png)]]
-[[Image(rankqsr.3.png)]]
+[[Image(percent_cpu_qsr.3.png, 530px)]]
+[[Image(rankqsr.3.png, 530px)]]
 ''...''