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


Ignore:
Timestamp:
2019-11-29T17:46:00+01:00 (8 months ago)
Author:
andmirek
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2019WP/HPC-12_Mocavero_mpi3

    v10 v11  
    51512)      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.  
    5252 
    53 3)      It would be good to have a logical flag controling use of this option (for now in traadv_fct.F90). 
    5453 
    5554 
    56 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. 
     55 
     56Those 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. 
    5757 
    5858