When running cm4twc on JASMIN for a long simulation period (12 years) on a small region, the run crashes after ~7 simulated years because it runs out of memory. After restarting the run where it stopped, it runs to completion the second time around.
For a period of (1x2+10) years, the temporal resolutions of the components are:
SL: hourly
SS: hourly
OW: 15-minute
For a region spanning (56.0, 57.5) degN, (-5.5, -2.5) degE, the spatial resolutions of the components are:
The fixed memory leak related to ESMF use in cf-python certainly eliminated the main memory leak in cm4twc, but it seems that there is/are (an)other memory leak(s) still present.
When running
cm4twc
on JASMIN for a long simulation period (12 years) on a small region, the run crashes after ~7 simulated years because it runs out of memory. After restarting the run where it stopped, it runs to completion the second time around.For a period of (1x2+10) years, the temporal resolutions of the components are:
For a region spanning (56.0, 57.5) degN, (-5.5, -2.5) degE, the spatial resolutions of the components are:
SLURM configuration used on JASMIN were:
The fixed memory leak related to
ESMF
use incf-python
certainly eliminated the main memory leak incm4twc
, but it seems that there is/are (an)other memory leak(s) still present.