Hello all
I recently posted that r.surf.contour in grass5.0beta2 had problems on our SGI
Origin 2000. It was using up memory (over 512 MB) and finally crashing with an
out of memory message. Today I ran the command in fast mode, which is supposed
to be more memory intensive, and it ran without taking up hardly any memory at
all. Furthermore, using the same raster contour map on a SGI Indy (with 64 MB
RAM) running grass4.2, the fast mode finished in about 15 minutes. On the
5.0beta2 system it took over 2 and a half hours!! Not only did it take 900%
longer but the resulting map was empty.
Has anyone else had a similar experience?
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
Hello all,
I've found the bug in i.rectify for GRASS 5b2. The bug is in the
routine
write_map, in the source file write.c. I do not know if there is a bugfixes site
or any standard procedure to report bugs and to submit bugfixes. Anyhow here
attached you can find a correct version of the file write.c. To fix the i.rectify
module copy this file in $GRASS_SRC/src/imaging/i.rectify/ and recompile the
module.
Incidentally I report that I found some problems in the i.points3 module. It seems
that
it is not possible to set the GCPs.
bye
LP
(attachments)
WRITE.C (1.91 KB)
I can confirm that r.surf.contour seems to be broken on Linux platform as
well.
On Fri, 13 Aug 1999, Justin Hickey wrote:
Hello all
I recently posted that r.surf.contour in grass5.0beta2 had problems on our SGI
Origin 2000. It was using up memory (over 512 MB) and finally crashing with an
out of memory message. Today I ran the command in fast mode, which is supposed
to be more memory intensive, and it ran without taking up hardly any memory at
all. Furthermore, using the same raster contour map on a SGI Indy (with 64 MB
RAM) running grass4.2, the fast mode finished in about 15 minutes. On the
5.0beta2 system it took over 2 and a half hours!! Not only did it take 900%
longer but the resulting map was empty.
Has anyone else had a similar experience?
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!