![]() In that way the return code can be used in script logic. Note that some modules (like g.findfile) exit with a status of 1 if it (for example) could not find a file, which may be exactly the test the module was run to perform. In a MS-Windows DOS box the equivalent command is " echo %errorlevel%". On UNIX (Linux, Mac OS, and Cygwin) directly after a command line module ends you can type " echo $?" and it will tell you the exit code. This is typically accompanied by an "ERROR: " message. ![]() To make the view a little more stable, with top running from the command line press "M" to sort by memory usage.Īll GRASS modules send out a return code of "0" if they exit successfully and "1" if they have exited with an error. While it won't give you many hard metrics it will give you an idea of what is happening. Top is a nice command line utility for watching a process's progression. Many modules will continue to work on these huge datasets, but processing time may make it not worth the while. While there is no set upper limit, anything bigger than 20000x20000 is considered large, and anything an order of mangnitude bigger than that will most likely end with out of memory or large file problems, especially on 32-bit platforms built without LFS support. Check that the region settings are not totally overwhelming for the raster engine.A setting of "5" is the most verbose, "0" is no debug messages.These messages are always present regardless of compiler settings.A higher debug level means you see more messages.Setting GRASS-environment variables (numbers: 1-5) g.gisenv set="DEBUG=1" For instructions on creating and applying patches the see Patches wiki page.Users should read the Mailing list etiquette page before posting questions to the grass-dev mailing list.The following command will disable the use of translated messages: Please use untranslated messages in your bug reports.Bugs should be reported in the GRASS GIS bug and wish tracker.20.6 Memory debugging of python scripts.9.7 Using kdbg (gdb graphical frontend).9.4 Saving a core dump for later analysis.3 Setting GRASS-environment variables (numbers: 1-5).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |