This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
library:computing:xios_impi_troubles [2017/08/03 12:45] 84.88.184.232 [Issue 3:] |
library:computing:xios_impi_troubles [2024/06/18 11:15] 84.88.52.107 old revision restored (2024/06/01 21:17) |
||
---|---|---|---|
Line 70: | Line 70: | ||
===== NEMO-XIOS @ MN4 ===== | ===== NEMO-XIOS @ MN4 ===== | ||
- | ==== Issue 1: ==== | + | ==== Issue 1: NEMO fails to read input files ==== |
**Environment: | **Environment: | ||
Line 126: | Line 126: | ||
</ | </ | ||
- | **Actions taken:** Operations had observed this error using NEMO standalone and NeTCDF | + | **Actions taken:** Operations had observed this error using NEMO standalone and NetCDF |
- | **Diagnosis: | + | After looking for differences between NetCDF 4.4.0 and NetCDF 4.2 configurations (using nc-config & nf-config commands), we found out that while NetCDF 4.4.0 was compiled with no support for nc4 nor P-NetCDF (a library used that gives parallel I/O support for classic NetCDF files), while NetCDF was supporting this features. Then operations compiled again NetCDF without linking P-NetCDF, and this error disappeared. |
- | **Solution: | + | In order to know more about the source of this bug, we compared the behavior of two NEMO executables, |
+ | |||
+ | We did a comparison of the functions included in both binaries through the nm command, and we found that they were identical. Then we did a more in deep comparison of both binaries with objdump and we found out little differences, | ||
+ | |||
+ | **Diagnosis: | ||
+ | |||
+ | **Solution: | ||
**More information: | **More information: |