ESMF_RegridWeightGen contains an undetermined bug that was introduced after compass version 1.8.0-alpha.2. This bug only seems to exist when using the 'conserve' mapping method to interpolate at high resolution. The bug was discovered using conservative mapping to interpolate a 150 m data product onto a 1-10km MALI mesh. The bug was not triggered interpolating the same 150 m data product onto a 4-40 km MALI mesh of the same domain. 'Bilinear' and 'patch' mapping methods worked successfully with the 1-10km mesh, so the issue seems to be solely with the 'conserve' mapping option.
The bug occurs when using the command: srun -n 128 ESMF_RegridWeightGen --source BedMachineGreenland-v5.scrip.nc --destination UummannaqDisko_scrip.nc --weight gridded_to_MPAS_weights.nc --method conserve --netcdf4 --dst_regional --src_regional --ignore_unmapped
When run as part of a bash script, ESMF_RegridWeightGen gets stuck indefinitely and will not produce any output or progress for the duration of a 12 hour job. If run in isolation on an interactive node, ESMF_RegridWeightGen produces a general segmentation fault.
This issue does not occur with compass version 1.8.0-alpha.2 (tested at 52b6a6c), but does occur with compass 1.9.0-alpha.1. It seems likely the bug was introduced with the update of ESMF here: f995c42
ESMF_RegridWeightGen contains an undetermined bug that was introduced after compass version 1.8.0-alpha.2. This bug only seems to exist when using the 'conserve' mapping method to interpolate at high resolution. The bug was discovered using conservative mapping to interpolate a 150 m data product onto a 1-10km MALI mesh. The bug was not triggered interpolating the same 150 m data product onto a 4-40 km MALI mesh of the same domain. 'Bilinear' and 'patch' mapping methods worked successfully with the 1-10km mesh, so the issue seems to be solely with the 'conserve' mapping option.
The bug occurs when using the command:
srun -n 128 ESMF_RegridWeightGen --source BedMachineGreenland-v5.scrip.nc --destination UummannaqDisko_scrip.nc --weight gridded_to_MPAS_weights.nc --method conserve --netcdf4 --dst_regional --src_regional --ignore_unmappedWhen run as part of a bash script, ESMF_RegridWeightGen gets stuck indefinitely and will not produce any output or progress for the duration of a 12 hour job. If run in isolation on an interactive node, ESMF_RegridWeightGen produces a general segmentation fault.
This issue does not occur with compass version 1.8.0-alpha.2 (tested at 52b6a6c), but does occur with compass 1.9.0-alpha.1. It seems likely the bug was introduced with the update of ESMF here: f995c42