New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
WorkingGroups/HPC/Mins_2021_02_22 (diff) – NEMO

Changes between Version 3 and Version 4 of WorkingGroups/HPC/Mins_2021_02_22


Ignore:
Timestamp:
2021-02-26T17:25:47+01:00 (3 years ago)
Author:
epico
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGroups/HPC/Mins_2021_02_22

    v3 v4  
    2727The discussion started recalling the undoubted benefits that the mixed precision approach has in terms of reduction of CPU time, reduction of data movement and reduction of I/O. The loss of accuracy can be fine tuned by means of the application of a tool which provides the user/developer with the list of variables to be kept in double precision. 
    2828 
    29 The ECMWF has developed a single precision version of NEMO 4.0.4 keeping very few variables in double precision and has experienced good results with acceptable loss of accuracy for short term predictions with NEMO SP (single precision) even in a coupled configuration. In contrast, the mixed precision trunk from the BSC keeps more variables in double precision to reduce the loss of accuracy and support longer runs.  
     29The ECMWF has developed a single precision version of NEMO 4.0.3 keeping very few variables in double precision and has experienced good results with acceptable loss of accuracy for short term predictions with NEMO SP (single precision) even in a coupled configuration. In contrast, the mixed precision trunk from the BSC keeps more variables in double precision to reduce the loss of accuracy and support longer runs.  
    3030 
    3131It was clearly stated that the double precision version of NEMO will not be affected by these changes, neither its results nor its computational performance.