This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
library:computing:xios_impi_troubles [2026/03/19 18:50] 84.88.52.107 old revision restored (2026/03/13 22:04) |
library:computing:xios_impi_troubles [2026/05/08 08:10] (current) 84.88.52.107 old revision restored (2026/03/19 21:23) |
||
|---|---|---|---|
| Line 196: | Line 196: | ||
| - | **Actions taken:** Given that the error is a floating invalid we disabled the -fpe0 flag, but we still were having the same problem. Then we disabled compiler optimizations (use -O0) and the problem disappeared, | + | **Actions taken:** Given that the error is a floating invalid we disabled the -fpe0 flag, but we still were having the same problem. Then we disabled compiler optimizations (use -O0) and the problem disappeared, |
| - | Update: Using the new NetCDF 4.2 installed by Ops and key netcdf_par for XIOS2 the model can run using O3. We have to investigate further this issue. | + | **Diagnosis:** |
| - | **Diagnosis: | + | **Solution: |
| - | + | ||
| - | **Solution: | + | |
| ==== Issue 3: MPI kills XIOS when writing model output ==== | ==== Issue 3: MPI kills XIOS when writing model output ==== | ||
| Line 261: | Line 259: | ||
| We tried an alternative solution, which was to __increment the number of XIOS servers__ in order to reduce the number of messages sent to the same process and by the moment it seems that it is effective. | We tried an alternative solution, which was to __increment the number of XIOS servers__ in order to reduce the number of messages sent to the same process and by the moment it seems that it is effective. | ||
| - | **Diagnosis: | + | **Diagnosis: |
| **Solution: | **Solution: | ||
| Line 284: | Line 282: | ||
| **Problem: | **Problem: | ||
| - | **Actions taken: | + | **Actions taken:** |
| **Diagnosis: | **Diagnosis: | ||
| - | **Solution: | + | **Solution: |