[winGRASS] some really slooooowwww functions
Matt & Kim
patawi at polarcom.com
Tue Jan 29 07:36:48 EST 2002
Hi All,
This is my first post to wingrass, though I've been a lurker on
the main grass channel for a year so and have opened my mouth
there once or twice. I'm a GIS professional (ArcInfo, plus a
smattering of others) and am trying to get seriously acquainted
with grass. My coding ability in anything other than Arc Macro
Language or dos/nt cmd files is pretty close to nil, sorry.
Cheers.
I'm sure I'll have more questions later, but at the moment there
are only 2. I have no idea if they are related.
1) When running many grass commands instead of the expected
output I get:
grass5.0.0pre2_i686-pc-cygwin_bin.tar.gz: No such file or directory
for example:
GRASS:/usr/local > g.setproj
WARNING! A projection file '/home/obelix1/g-data/yk/PERMANENT/PROJ_INFO'
[...snip...]
Please specify projection name
Enter 'list' for the list of available projections
Hit RETURN to cancel request
>list
grass5.0.0pre2_i686-pc-cygwin_bin.tar.gz: No such file or directory
For the above session a text file containing the expected
output can be found in
D:\cygwin\home\Obelix1\g-data\yk\landsat7\.tmp\OBELIX\1396.0
In an attempt to remedy the situation I uninstalled grass5pre2
(using the uninstall script) and installed grass5pre3 by simply
unpacking the archive into /usr/local/grass5 and symlinking
the grass5 startup script to /usr/local/bin/grass5.
The error message remains the same. Note the 'pre2' in the
filename. The pre2 archive no longer exists anywhere on my
harddrive.
-----
2) I've been trying to bring in some GeoTiff imagery and it is
taking an incredibly long time, over 12 hours for a single 17.6mb
image using r.in.tiff. This can't be normal (right? please?)
Task manager reported ~150mb of ram being used and 99%
CPU utilization (figures from memory and before I upgraded
to pre3).
Right now I am using r.in.tiff on a 4.4mb geotiff. At about
the 12 minute mark Task Manager reports:
r.in.tiff
cpu% : 99 (range is 85-99)
cpu time : 09:00
memory : 69,040 K (going up, very slowly)
processes : 42
memory usage : 374,094 K / 1,277,936 K
The cdrom drive where the source image lies spins up every 5
minutes or so. (In previous tests the same slowness is observed
on images on the harddrive and within the cygwin directory
tree).
-----
Host system:
Windows 2000, service pack2
512mb ram
40gb IDE harddrive (8gb FAT, 10GB NTFS, rest unassigned)
abit kt7a-raid motherboard
athlon 1100mhz cpu
$uname -a
CYGWIN_NT-5.0 OBELIX 1.3.6(0.47/3/2) 2001-12-08 17:02 i686 unknown
$ df
Filesystem 1k-blocks Used Available Use% Mounted on
D:\cygwin\bin 10241404 7761544 2479860 76% /usr/bin
D:\cygwin\lib 10241404 7761544 2479860 76% /usr/lib
D:\cygwin 10241404 7761544 2479860 76% /
c: 10223368 9758616 464752 96% /cygdrive/c
d: 10241404 7761544 2479860 76% /cygdrive/d
e: 498224 498224 0 100% /cygdrive/e
-------------------------------
thanks in advance for any assistance you can provide,
-matt wilkie
whitehorse, yukon, canada
More information about the grass-windows
mailing list