Error in projectionPointInt when run Spatial-Allocator

Hello, everyone!
I’m master course student in Korea.
I got some error when I run Spatial-Allocator program(generate_surrogate100_pop.csh)
error message is :
Generate Population surrogate = 100
Surrogate Creator Version 4.3, 01/20/2017

EV: OUTPUT_FILE_TYPE=RegularGrid
Setting output grid

EV: OUTPUT_FILE_TYPE=RegularGrid
Reading Regular Grid

EV: OUTPUT_GRID_NAME=KOREA
WARNING: Environment variable: MAX_LINE_SEG, not set
MAX_LINE_SEG not set, discretization intervals disabled
griddesc file name = /home/out2/mcip/KOREA/GRIDDESC

Ellipsoid var = OUTPUT_FILE_ELLIPSOID
EV: OUTPUT_FILE_ELLIPSOID=+a=6370000.0,+b=6370000.0
Ellipsoid=+a=6370000.0,+b=6370000.0
EV: OUTPUT_GRID_NAME=KOREA
Not using BB optimization

EV: OUTPUT_FILE_NAME=/home/phy/Spatial-Allocator/output/KOREA/grid_KOREA_100
EV: WEIGHT_ATTR_LIST=POP
EV: FILTER_FILE=NONE
Filter File= NONE
Reading data polygons

EV: DATA_FILE_ELLIPSOID=+a=6370000.0,+b=6370000.0
Ellipsoid=+a=6370000.0,+b=6370000.0
EV: DATA_FILE_MAP_PRJN=+proj=latlong
EV: DATA_FILE_NAME_TYPE=ShapeFile
EV: DATA_FILE_NAME=/home/phy/Spatial-Allocator/data/korea/TL_SCCO_SIG
WARNING: Environment variable: MAX_LINE_SEG, not set
MAX_LINE_SEG not set, discretization intervals disabled
max_line_seg=

Reading Shapefile /home/phy/Spatial-Allocator/data/korea/TL_SCCO_SIG
Shapefile Type: 5 Polygon # of Shapes: 250

Input projection:

args[1]=+a=6370000.0

args[2]=+b=6370000.0

param 0 = +proj=latlong,
PROJ args=+proj=latlong+a=6370000.0+b=6370000.0

Output projection:

args[1]=+a=6370000.0

args[2]=+b=6370000.0

setting Lambert Conic Conformal – 2SP parameters
PROJ args=+proj=lcc+a=6370000.0+b=6370000.0+lat_1=30.000000+lat_2=60.000000+lon_0=126.000000+lat_0=38.000000+units=m

ERROR in /home/phy/Spatial-Allocator/bin/64bits/srgcreate.exe: Error in projectionPointInt: p.u=HUGE_VAL. Exiting…
0.001u 0.002s 0:00.00 0.0% 0+0k 0+0io 0pf+0w
Error generating surrogate for category 100

I think there is a problem about map projection point.
But I can’t find problem… :frowning:
How can I solve this problem???

@phy To close this ticket, can you update this ticket with the solution we assisted? Thanks.