Hi...
I am just wondering how a python script is processed in GRASS?
After launching a script (via launch script from inside GRASS) that calls different GRASS-modules
and another self-written python-script, it takes very long to start. With 'start' I mean that I see
actually the output text in the GUI what is processed. To me it seems the script is checked before
it is processed which takes similarly long as the processing itself.
Can anyone explain in simple words how it works, respectively what happens before I see
the status-output-text in the GUI (what I refer as 'processing')?
I am working on GRASS 6.5SVN on Mac OS X 10.6.8
Best regards,
Johannes
Hi,
2012/5/6 Johannes Radinger <jradinger@gmx.at>:
I am just wondering how a python script is processed in GRASS?
After launching a script (via launch script from inside GRASS) that calls different GRASS-modules
how the script is launched? From wxGUI (File | Launch script)?
and another self-written python-script, it takes very long to start. With 'start' I mean that I see
actually the output text in the GUI what is processed. To me it seems the script is checked before
it is processed which takes similarly long as the processing itself.
I have tested very simple script and it worked as expected. The script
is launched in the same way as other (GRASS commands) [1]. Can you
elaborate a little bit more, any sample script or so?
Martin
[1] http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/gui/wxpython/lmgr/frame.py#L634
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa