Changes between Version 13 and Version 14 of 2019WP/HPC-12_Mocavero_mpi3
- Timestamp:
- 2019-11-29T22:42:33+01:00 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2019WP/HPC-12_Mocavero_mpi3
v13 v14 58 58 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. 59 59 60 {{{ ''A compiler key can be easily introduced to control the use of new communications, depending on performance achieved on different systems and configurations.''}}}60 {{{A compiler key can be easily introduced to control the use of new communications, depending on performance achieved on different systems and configurations.}}} 61 61 62 62 I personally would propose a different strategy, which requires more development before merging this change into the trunk, but avoids potential problem outlined in point 1 and addresses point 2.