Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

mkmapdata.sh error

samrabin

Sam Rabin
Member
I'm trying to set up a single-point run for a half-degree cell centered at longitude 74.75, latitude 51.75. I did the following in /glade/u/home/samrabin/ctsm/tools/mkmapdata:

Code:
../site_and_regional/mknoocnmap.pl -p 74.75,51.75 -n halfdeg_NEkz
./mkmapdata.sh -r halfdeg_NEkz -f SCRIPgrid_halfdeg_NEkz_nomask_c220520.nc

Unfortunately, mkmapdata.sh crashes on the first attempted grid with the following:
Code:
forrtl: severe (408): fort: (2): Subscript #1 of the array CORNERX has value 3 which is greater than the upper bound of 2

Image              PC                Routine            Line        Source
ESMF_RegridWeight  000000000042CF62  Unknown               Unknown  Unknown
libesmf.so         00002AEB9260FFE0  esmf_gridmod_mp_c        5477  ESMF_Grid.F90
libesmf.so         00002AEB92631ACD  esmf_gridmod_mp_e        6904  ESMF_Grid.F90
libesmf.so         00002AEB92629660  esmf_gridmod_mp_e        6496  ESMF_Grid.F90
libesmf.so         00002AEB92CECCBB  esmf_regridweight        1368  ESMF_RegridWeightGen.F90
ESMF_RegridWeight  000000000041488F  MAIN__                   1145  ESMF_RegridWeightGen.F90
ESMF_RegridWeight  00000000004074E2  Unknown               Unknown  Unknown
libc-2.22.so       00002AEB97FCBA35  __libc_start_main     Unknown  Unknown
ESMF_RegridWeight  00000000004073E9  Unknown               Unknown  Unknown

See /glade/u/home/samrabin/ctsm/tools/mkmapdata/mkmapdata_halfdeg_NEkz.o4261170 for the complete mkmapdata.sh output.

Any ideas?
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Sam we are actually deprecating the use of mkmapdata for single point cases in favor of using subset_data to take from a global dataset. It's a much less complex workflow. What you can do is to start from a high resolution surface dataset and it'll take the nearest point to it. You can also override the PFT's if you know what you want to replace them with.

We might be able to debug what's going on here, but the recommended workflow is now to use subset_data (under tools/site_and_regional). So I'd really rather you try the new tool and hopefully it just works and if not, it'll be much easier to figure out what's wrong.
 

samrabin

Sam Rabin
Member
Sure, makes sense. I managed to get a run working via subset_data, but now I'm running into a different issue—see here. Thanks!
 
Top