[GRASS-dev] Re: superfluous G_legal_filename etc calls

[Markus Neteler]

On Tue, Jan 27, 2009 at 10:45 PM, Markus Neteler <neteler at osgeo.org> wrote:
> I am running r.sun (6.4) on a massive grid and have some troubles with
> the libgis libraries:

Apparently I have even more (one of many Grid Engine job outputs):

cat launch_SGE_grassjob_rsun_energy.sh.e33397
doy: 160 (month: 06)
Processing day 160...
Mode 2: integrated daily irradiation
0..Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
Illegal filename.  Cannot be '.' or 'NULL'
/home/neteler/binaries/bin/rsun_photoperiod_PAT_utm32.sh: line 46:
7878 Killed                  r.sun -s --o $DEM day=$d
linkein=linke_turbidity$month numpartitions=64 horizonstep=30
horizon=pat5m_horangle insol_time=pat_insol_time$D
beam_rad=pat_beam_rad$D diff_rad=pat_diff_rad$D
refl_rad=pat_refl_rad$D glob_rad=pat_glob_rad$D
ERROR: Raster map <pat_insol_time160> not found

Is there a possibility to find out why the job was killed?
In /var/log/messages there is no trace (no OOM). I had declared that
each job gets 11GB RAM in Grid Engine. Other jobs continue (same
script, just another day of the year). GE is supposed to send me an email
in case of error but nothing happens.

Mysterious.

Markus