The logical variable write_a_restart is used in many places to control whether a restart file is written, but there are three places where it is not used, and a restart file is written unconditionally. These are:

1. subroutine ice_model_end in src/ice_sis/ice_type.F90
2. subroutine ocean_sfc_end in src/mom5/ocean_core/ocean_sbc.F90
3. subroutine ocean_velocity_end in src/mom5/ocean_core/ocean_velocity.F90. In this last case, write_a_restart is used incorrectly in subroutine ocean_veclocity_chksum in the same file.

Document the reproducibility flags that were used in testing https://github.com/penguian/1deg_jra55_ryf migration from NCI Raijin to Gadi.

Using these flags with the Intel 2019.3.199 compilers produced identical output on Raijin and Gadi. See "repro group 4" in the report summary for results.

To test scalability and performance on Gadi, vary both the compiler flags and the layout. To better understand the performance of the code, also expand the options available in MOM_run.csh to cater to Score-P, Scalasca and Valgrind.