From c075519ec835773eae0da494f8883a8f4a3223ca Mon Sep 17 00:00:00 2001 From: Ozan Karsavuran Date: Fri, 5 Mar 2021 02:10:06 +0200 Subject: [PATCH] Update README.md --- nemo/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nemo/README.md b/nemo/README.md index fe2182c..499e681 100644 --- a/nemo/README.md +++ b/nemo/README.md @@ -127,9 +127,10 @@ This helps us to compare systems in a standard manner across all combinations of The other main reason for reporting time per computational time step is to make sure that results are more reproducible and comparable. Since NEMO supports both weak and strong scalability, test case A and test case B both can be scaled down to run on smaller number of processors while keeping the memory per processor constant achieving similar -results for step time. To measure the step time, we inserted a patch which includes the `MPI_wtime()` functional call in `nemogcn.f90` file +results for step time. To measure the step time, we inserted a patch which includes the `MPI_Wtime()` functional call in [nemogcm.F90](nemogcm.F90) file for each step which also cumulatively adds the step time until the second last step. We then divide the total cumulative time by the number of time steps to average out any overhead. +It is also possible to use total time reported by XIOS server. ## Sources -- GitLab