[winGRASS] some really slooooowwww functions

[Andreas Lange]

Matt & Kim wrote:
...
> 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.
> 

This problem was reported several times lately. But i had no time to
look into this. It is a mystery to me, it works flawlessly on my machine
(W2K SP2, latest cygwin). 

> -----
> 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).
> 

This is very strange too, as i imported _really_ big files (250 MB) with
r.in.tiff. But reading them directly off the CD is not a good idea. It
should not make any difference if the file is within the cygwin tree or
elsewhere on a disk drive (/cygwin/D/.. etc). But i don't know much
about the innards of the cygwin library, so i have no idea... I will do
some tests over here in the next time. But don't be too dissapointed if
i can't help you, its my experience that free software and proprietary
systems like Windows do not mix very well. 

Andreas
-- 
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
url: http://mitglied.tripod.de/AndreasLange
mail: Andreas.Lange_at_Rhein-Main.de - A.C.Lange_at_GMX.net