Problem generating mapping files for rectilinear case

[mvhulten]

In the branch dev_grids creation of 3-km and 12-km curvilinear and rectilinear mapping files works.

However, in the rectilinear case, first creating the grid file and then creating the mapping files results in errors on eight of 128 processors, namely all those numbered $$16 n$$ for any legal $$n$$, e.g.

Creating conservative remapping files for your grid EUR-regLonLat01deg...
 Starting weight generation with these inputs: 
   Source File: 
 /p/largedata2/detectdata/CentralDB/projects/z04/lnd/clm2/mappingdata/grids/SCRI
 Pgrid_0.5x0.5_AVHRR_c110228.nc
   Destination File: ../mkmapgrids/EUR-regLonLat01deg_659792_grid.nc
   Weight File: 
 /p/scratch/cdetect/vanhulten1/testing/eCLM_static-file-gen.25324_recta/mkmapdat
 a/map_SCRIPgrid_0.5x0.5_AVHRR_c110228.nc_to_EUR-regLonLat01deg_nomask_aave_da_c
 250324.nc
   Source File is in SCRIP format
   Source Grid is a global grid
   Source Grid is a logically rectangular grid
   Use the center coordinates of the source grid to do the regrid
   Destination File is in SCRIP format
   Destination Grid is a regional grid
   Destination Grid is a logically rectangular grid
   Use the center coordinates of the destination grid to do the regrid
   Regrid Method: conserve
   Pole option: NONE
   Ignore unmapped destination points
   Output weight file in NetCDF4 file format
   Line Type: greatcircle
   Norm Type: dstarea
   Extrap. Method: none
 
 ERROR: Problem on processor           80 
 . Please see the PET*.RegridWeightGen.Log files for a traceback.

Respective Log file:

20250324 160705.279 INFO             PET080 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
20250324 160705.279 INFO             PET080 !!! THE ESMF_LOG IS SET TO OUTPUT ALL LOG MESSAGES !!!
20250324 160705.279 INFO             PET080 !!!     THIS MAY CAUSE SLOWDOWN IN PERFORMANCE     !!!
20250324 160705.279 INFO             PET080 !!! FOR PRODUCTION RUNS, USE:                      !!!
20250324 160705.279 INFO             PET080 !!!                   ESMF_LOGKIND_Multi_On_Error  !!!
20250324 160705.279 INFO             PET080 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
20250324 160705.279 INFO             PET080 Running with ESMF Version   : 8.5.0
20250324 160705.279 INFO             PET080 ESMF library build date/time: "Dec 14 2023" "15:50:40"
20250324 160705.279 INFO             PET080 ESMF library build location : /dev/shm/swmanage/jurecadc/ESMF/8.5.0/intel-para-2023a/esmf-8.5.0/
20250324 160705.279 INFO             PET080 ESMF_COMM                   : mpich2
20250324 160705.279 INFO             PET080 ESMF_MOAB                   : enabled
20250324 160705.279 INFO             PET080 ESMF_LAPACK                 : enabled
20250324 160705.279 INFO             PET080 ESMF_NETCDF                 : enabled
20250324 160705.279 INFO             PET080 ESMF_PNETCDF                : disabled
20250324 160705.279 INFO             PET080 ESMF_PIO                    : enabled
20250324 160705.279 INFO             PET080 ESMF_YAMLCPP                : enabled
20250324 160705.715 ERROR            PET080 ESMF_Grid.F90:5532 ESMF_GridCreate Wrong argument specified  -  Couldn't find a consistent ordering of corners around each cell in file to be able to arrange them into a logically rectangular Grid.
20250324 160705.715 ERROR            PET080 ESMF_Grid.F90:6925 ESMF_GridCreateFrmScrip Wrong argument specified  - Internal subroutine call returned Error
20250324 160705.715 ERROR            PET080 ESMF_Grid.F90:6520 ESMF_GridCreateFrmNCFile Wrong argument specified  - Internal subroutine call returned Error
20250324 160705.715 ERROR            PET080 ESMF_RegridWeightGen.F90:1384 ESMF_RegridWeightGenFile Wrong argument specified  - Internal subroutine call returned Error
20250324 160705.715 INFO             PET080 Finalizing ESMF

What does the error about corners mean and does that result in wrong arguments in the other ESMF_* scripts?

See /p/scratch/cdetect/vanhulten1/testing/eCLM_static-file-gen.25324_recta/mkmapdata/.

[mvhulten]

Looking back in my other rectilinear regridding data creation attempts, it seems I have never tested that.

Rectilinear grids had (have?) a low priority.