Changes between Version 10 and Version 11 of 2019WP/HPC-12_Mocavero_mpi3

Timestamp:

2019-11-29T17:46:00+01:00 (4 years ago)

Author:

andmirek

Comment:

--

2019WP/HPC-12_Mocavero_mpi3

@@ -51 +51 @@
 2)      Because the implementation is limited to only one routine it will be difficult to test impact on performance, moreover in the case of problems debugging of the code will be difficult because for one routine different approach to exchange messages will be used. 
 
-3)      It would be good to have a logical flag controling use of this option (for now in traadv_fct.F90).
 
 
-Those two issues should be raised with the whole system team for discussion and potentially all centres should test if the code compiles/runs without any issues, BEFORE the decision to merge this development into the trunk is made. This is a change to a major component of NEMO and not only SETTE tests and test cases, but also operational configurations used in the Centres should be tested if possible.
+
+Those two issues should be raised with the whole system team for discussion and potentially all centres should test if the code compiles/runs without any issues, BEFORE the decision to merge this development into the trunk is made. It would be good to have a logical flag controling use of this option (for now in traadv_fct.F90). This is a change to a major component of NEMO and not only SETTE tests and test cases, but also operational configurations used in the Centres should be tested if possible.