Topic:
Common causes for IESX crashes during gridding in Basemap. 

Description:
IESX crashes have been occasionally observed during gridding in Basemap.

Most of the following suggestions apply to GeoFrame 3.1.x, as well as 
GeoFrame 3.5.

Solution:
1.) Open a new IESX session, and try gridding again.

2.) Check space availability in the user's home directory.  Temporary files are
created during gridding for GeoFrame 3.1.x and are written to this location. 
Problems may occur if the gridding function runs out of space.

3.) Using modeling data boundaries with a large number of points (of the order
of 100) has been observed to cause crashing. Grid without the modeling data
boundaries turned on to check if your boundary is near this limit and is causing
the crashing.

4.) Clean up the CPS files in the following directories.

In the Runtime geoframe_sun directory located in the user's home directory,
remove all CPS report files (cpswork*.rep).

In the project's CPS directory, remove the session files (cpswork*.lcps) and
data files generated by Basemap (xyzN.dcps, outgrid1N.scps, etc, where N is a
small interger).  In rare cases, it will be necessary to also remove the CPS/GF
cache files (.cps_sm_set_cache.lcps, .gf_N.scps, where N is a large interger 
{GF DI ID}).  If a CPS directory was not defined for your project, these files
will be located in the project's Default directory.

5.) If GeoFrame was recently installed or upgraded, check whether it was
installed properly. In particular, make sure that CPS bulk files are installed
(regardless of whether you have CPS licenses or not), since gridding in Basemap
Plus uses CPS gridding algorithms. As a quick check do the following:

a.) Open a GeoFrame xterm 
b.) cd $GF_HOME 
c.) cd geoframe_3#_sun  (Insert proper version number in place of # sign)
d.) more GeoFrame_Runtime.csh

    Does it say  setenv CPS_INSTALLED "1" or   setenv CPS_INSTALLED "0"?
    If it is "0", then the bulk files were not installed.





Last Modified on: 08-JUN-99