Just another thought relating to this subject - the UNIX "at"
command run within a GRASS session has been very useful for me
when I have a resource-intensive job to do because I can schedule
it for after-hours and then continue to use GRASS in various
mapsets & locations for the rest of the day, exit and log out.
It'a a good idea to set the current region within your "at"
script or command in case you changed it. You also have to make
sure the last location/mapset you were in before logging out is
the same as what will be needed by your script or command you run
with "at".
Hi everyone, do you know how I can use the file generated by the "window
dump" function in DISPLAY TOOL, XGRASS? To view it or print? How? It
seems a binary file.
Any advance will be appreciated.
Peter Wu
Department of Geological and Environmental Studies
State University of New York at Binghamton
Does everyone know how I can use the file generated by the "window
dump" function in DISPLAY TOOL, XGRASS4.1? To view it or print? How? It
seems a binary file.
Any advance will be appreciated.
Peter Wu
Department of Geological and Environmental Studies
State University of New York at Binghamton
We have launched Grass programs and scripts from cron with good results.
Two things to watch for: one, Grass lock files (make sure they're set
and removed by the script) and two, leftover temporary files in the .tmp
directory under your mapset. The Grass script GIS.sh executes clean_temp
which cleans these files up, but you don't want to remove these files
while your script is running, but you might want it someplace in your
script after its done doing Grass stuff.
-------------------------------------------------------------------------
Randy Hills Office of Hydrology - NOHRSC
rhills@nohrsc.nws.gov National Weather Service, NOAA
voice: (612)361-6610(ext.231) 1735 Lake Drive West
fax: (612)361-6634 Chanhassen, Minnesota 55317-8582 http://www.nohrsc.nws.gov
-------------------------------------------------------------------------