TRUSTING IPSLCM7 at TGCC irene-amd

by J. Ghattas and Th. Lurton, IPSL, 2025.
This trusting evaluates the technical issues with the coupled configuration IPSLCM7 at irene-amd/TGCC.

Each line in the grey table corresponds to a specific installation of IPSLCM7 and all related tests. The revision number of
modipsl is set in column 2 and the revsion numbers for the other components are listed in the end of the line.
The 7th column shows the reference revision of modipsl which is used for comparing results for the individual tests.

The different tests listed in the table below are given on following syntax:
XXXXyz : XXXX= config, y=p/d compilation in prod or debug mode, z=1 or 2 for different tests with different PeriodLength.
For example
icoCMp1 - config IPSLCM7, ico geometry, with production mode compiled executable test 1 with PeriodLength=5D, total length 10 days.
icoCMp2 - config IPSLCM7, ico geometry, with production mode compiled executable test 2 with PeriodLength=10D, total length 10 days.
icoCMd1 - config IPSLCM7, ico geometry, with debug mode compiled executable test 1 with PeriodLength=1D, total length 2 days.

The tests of type XXp1 = XXp2 are validating the restartability of the model. Both tests have the same total length but different PeriodLength. The results should be the same in the end of the run.
The RealCpu time noted for each test concerns the last executed period only.

There are 3 levels of trusting for IPSLCM7:
* level 1: only -debug runs, and with ORCHIDEE_4 are compiled and launched. Therefore no restartability is tested out. This is scheduled to occur once a week (on Wednesdays at night).
* level 2: -debug runs with ORCHIDEE_2_2 are added to the list. Still no restartability is tested. The level 2 trustings occur once every two weeks, at night on weekends.
* level 3: the whole of the experiment set is compiled and launched. This comprehensive trusting occurs once every other week, at night on weekends, alternating with the scheduled level 2 trustings.