[GRASS-user] Possible Grass Bug

GRASS GRASS user
1

Dear Grass members,

I apologize for any inconvenience but I am not familiar with the bug system in Grass GIG. Please let me know if this e-mail needs to be sent to a different address.

Recently, I started working with Grass GIS (version 7.4.0). At the moment, I am following the tutorial ``NCSU GIS/MEA582: Geospatial Modeling and Analysis". I came across the command ``d.mon" that does not work the way it is supposed to work. The issue is that d.mon start=wx0 does not initiate a new display window, nor does d.mon stop=wx0 terminate an existing window. Also, ``d.mon -l" or ``d.mon -p" show nothing. In all cases the commands are written in the CONSOLE window in the Layer Manager sub-window and when the Enter button is hit the following error message appears that ``Command 'd.mon' not yet implemented in the WxGUI. Try adding it as a command layer instead." It, also, needs to be mentioned that the ``d.rast map=elevation" shows the elevation map just fine. It is the d.mon that is not working! Please let me know if you need further information.

P.S. I am running Grass GIS 7.4.0 on Ubuntu trsuty 14.04 (32 bit).

Sincerely,
Nozhan Balafkan

2

On Sat, 30 Jun 2018, ubuntu wrote:

I came across the command ``d.mon" that does not work the way it is
supposed to work. The issue is that d.mon start=wx0 does not initiate a
new display window, nor does d.mon stop=wx0 terminate an existing window.
Also, ``d.mon -l" or ``d.mon -p" show nothing. In all cases the commands
are written in the CONSOLE window in the Layer Manager sub-window and when
the Enter button is hit the following error message appears that ``Command
'd.mon' not yet implemented in the WxGUI. Try adding it as a command layer
instead." It, also, needs to be mentioned that the ``d.rast map=elevation"
shows the elevation map just fine. It is the d.mon that is not working!
Please let me know if you need further information.

Nozhan,

   How do you start grass? The default is to start with the GUI. In this case
you already have the monitor wx0 running. Just for giggles, start grass with
'grass text'. When it loads apply the monitor display command 'd.mon
start=wx0' and when you're finished, use 'd.mon stop=wx0' to close the
monitor then enter 'exit' on the grass command line to kill the application.

Regards,

Rich

3

On Sun, 1 Jul 2018, ubuntu wrote:

What is the difference between the console at the layer manager tab and
the GRASS 7.4.0 (nc_spm_08_grass7):~ > at the ubuntu terminal? when should
I use the console and when the other one? And what is the difference
between wx0,1,2, ... windows and the Grass GIS Map Display window (the one
that loads along with the layer manager)?

Nozhan,

   You will find that you have more control working at the console,
particularly when the wxGUI does not recognize files you want to use. The
GUI can be quite useful, but working at the console is preferred by those
who are used to working on consoles in linux, *BSD, and various unices.
Also, you can write scripts to perform repetative or complex processes and
run them from the command line. The GUI does not support this.

   Either on a 'getting started' or wiki page is a list of commands to start
grass. In your installation 'grass' and 'grass74' are synonymous. If you run
multiple versions (e.g., 7.4.x and 7.5svn) then you want to assign each to a
unique name.

Regards,

Rich

4

Dear Nozhan,

d.mon can only be called from the black terminal window that also opens when you open GRASS GIS. If you then want to display raster or vector maps, you will also need to write the commands in the black terminal.

If you want to display maps in the GUI (layer manager + map display) just use buttons, or go to data catalog and browse the map you want to display.

HTH,
Vero

El sáb., 30 jun. 2018 16:06, ubuntu <nozhan.balafkan@gmail.com> escribió:

Dear Grass members,

I apologize for any inconvenience but I am not familiar with the bug
system in Grass GIG. Please let me know if this e-mail needs to be sent
to a different address.

Recently, I started working with Grass GIS (version 7.4.0). At the
moment, I am following the tutorial NCSU GIS/MEA582: Geospatial Modeling and Analysis". I came across the command d.mon" that does not
work the way it is supposed to work. The issue is that d.mon start=wx0
does not initiate a new display window, nor does d.mon stop=wx0
terminate an existing window. Also, d.mon -l" or d.mon -p" show
nothing. In all cases the commands are written in the CONSOLE window in
the Layer Manager sub-window and when the Enter button is hit the
following error message appears that Command 'd.mon' not yet implemented in the WxGUI. Try adding it as a command layer instead." It, also, needs to be mentioned that the d.rast map=elevation" shows the
elevation map just fine. It is the d.mon that is not working! Please let
me know if you need further information.

P.S. I am running Grass GIS 7.4.0 on Ubuntu trsuty 14.04 (32 bit).

Sincerely,
Nozhan Balafkan

grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

5

Hi Nozhan,

[always keep discussion on the list for others to step in and/or benefit from it]

IMHO, GRASS GIS is quite versatile and allows multiple types of use(r)s :slight_smile:

You can use GRASS from the GUI only searching commands in the menu, write commands in the (simple) console tab, write commands in the black terminal only (combining commands with bash language if in Linux), you can write your scripts in bash or python and execute them without starting GRASS explicitly, or use GRASS from Python through grass-session library… and maybe some others…

Personally, I use the black terminal only and when I need to visualize any result I open a monitor with d.mon. If you use the GUI, you already have a “monitor” which is the map display window, thus d.mon does not work in the GUI simple console but d.rast, d.vect and others do. In my opinion, the GUI simple console is useful when someone is learning to use GRASS GIS; once the user gets used to commands, black terminal is the best. It’s a matter of taste, habit, convenience :wink:

Let us know if there’s anything you think we could enhance in the documentation. Also, text snippets are welcome :slight_smile:

Cheers,

Vero

El dom., 1 jul. 2018 a las 9:14, ubuntu (<nozhan.balafkan@gmail.com>) escribió:

Dear Veronica,

Thank you for the response but I am still confused about one thing. Based on my experience, I can type in ‘d.rast map=elevation’ at both black terminal and the console tab and both commands show the elevation map just fine (although in case of the black terminal you need to type in the command ‘d.mon start=wx0’ first). So, back to your response, if the black terminal is the place for the Grass commands to be typed in, then what is the role of the console tab at the bottom of the layer manager window? (It appears they are doing the same job!)

Sincerely,

Nozhan

On 07/01/2018 03:16 AM, Veronica Andreo wrote:

Dear Nozhan,

d.mon can only be called from the black terminal window that also opens when you open GRASS GIS. If you then want to display raster or vector maps, you will also need to write the commands in the black terminal.

If you want to display maps in the GUI (layer manager + map display) just use buttons, or go to data catalog and browse the map you want to display.

HTH,
Vero

El sáb., 30 jun. 2018 16:06, ubuntu <nozhan.balafkan@gmail.com> escribió:

Dear Grass members,

I apologize for any inconvenience but I am not familiar with the bug
system in Grass GIG. Please let me know if this e-mail needs to be sent
to a different address.

Recently, I started working with Grass GIS (version 7.4.0). At the
moment, I am following the tutorial NCSU GIS/MEA582: Geospatial Modeling and Analysis". I came across the command d.mon" that does not
work the way it is supposed to work. The issue is that d.mon start=wx0
does not initiate a new display window, nor does d.mon stop=wx0
terminate an existing window. Also, d.mon -l" or d.mon -p" show
nothing. In all cases the commands are written in the CONSOLE window in
the Layer Manager sub-window and when the Enter button is hit the
following error message appears that Command 'd.mon' not yet implemented in the WxGUI. Try adding it as a command layer instead." It, also, needs to be mentioned that the d.rast map=elevation" shows the
elevation map just fine. It is the d.mon that is not working! Please let
me know if you need further information.

P.S. I am running Grass GIS 7.4.0 on Ubuntu trsuty 14.04 (32 bit).

Sincerely,
Nozhan Balafkan

grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

6

* Rich Shepard <rshepard@appl-ecosys.com> [2018-06-30 16:04:33 -0700]:

On Sun, 1 Jul 2018, ubuntu wrote:

What is the difference between the console at the layer manager tab and
the GRASS 7.4.0 (nc_spm_08_grass7):~ > at the ubuntu terminal? when should
I use the console and when the other one? And what is the difference
between wx0,1,2, ... windows and the Grass GIS Map Display window (the one
that loads along with the layer manager)?

Nozhan,

You will find that you have more control working at the console,
particularly when the wxGUI does not recognize files you want to use. The
GUI can be quite useful, but working at the console is preferred by those
who are used to working on consoles in linux, *BSD, and various unices.
Also, you can write scripts to perform repetative or complex processes and
run them from the command line. The GUI does not support this.

Please note that (Python) scripting is possible via the GUI as well. There is a
Python tab and a simple Python script editor integrated (since at least
version 7.4). Simple examples are also included. I don't use them, so I don't
have an opinion about their usability.

There is also the wxGUI Graphical Modeler. It too has the script
editor integrated. In 2008, I requested for such an option:
https://trac.osgeo.org/grass/ticket/131. Not speaking Python at the time,
I asked for help to learn. I think it can be a good starting point in Python
scripting for GRASS GIS. The 'Help' menu offers links to various
resources. Adding one or two more resources, like
https://github.com/wenzeslaus/python-grass-addon, is meaningful.

Nikos

Either on a 'getting started' or wiki page is a list of commands to start
grass. In your installation 'grass' and 'grass74' are synonymous. If you run
multiple versions (e.g., 7.4.x and 7.5svn) then you want to assign each to a
unique name.

7

On Tue, 3 Jul 2018, Nikos Alexandris wrote:

Please note that (Python) scripting is possible via the GUI as well.

There is also the wxGUI Graphical Modeler.

Nikos,

   I've known about python integration but was not aware of the
g.gui.modeler. Since GRASS is only one of the tools I use, and not on all
projects, I would like to learn when it would be more appropriate to use a
python or wxGUI Graphical Modeler rather than a bash shell script.

   I'm not challenging the use of python or g.gui.modeler. I want to
determine whether either (or both) have advantages -- to me -- over writing
a shell script and using it directly rather than as input to wx.gui.modeler
or a python script.

   After reading the g.gui.modeler page I understand what it does but its
advantages over a plain shell script are not obvious to me. Pointers to more
information might provide the answers.

Best regards,

Rich

8

Rich Shepard:

I've known about python integration but was not aware of the
g.gui.modeler. Since GRASS is only one of the tools I use, and not on all
projects, I would like to learn when it would be more appropriate to use a
python or wxGUI Graphical Modeler rather than a bash shell script.

I'm not challenging the use of python or g.gui.modeler. I want to
determine whether either (or both) have advantages -- to me -- over writing
a shell script and using it directly rather than as input to wx.gui.modeler
or a python script.

Thanks Richard. I too, wonder what others think about this.

In short, from my learning efforts and practical experiences, always within the
GRASS GIS framework, I think:

- Python is best for scientific cross-platform tools. Likely, it will
  run on any known operating system.

- the Graphical Modeler is a great way to overview and learn about process at
  a glance.

- Bash shell scripts are great to glue different tools together. Complex
  work flows and more than 100 to 200 lines of code, may become hard to
  maintain. And likely it won't run everywhere, if this matters.

In support,

- Python is the default scripting language for GRASS GIS. As well, the
  huge amount of Python libraries and tools speaks for itself.

- After all, we always try to visualise (data,) processes (and
  information). Why not with a native GRASS GIS tool? -- This is (also)
  a reminder to myself!

- Just an example, obviously not an ideal one: the shell script
  https://gitlab.com/NikosAlexandris/r.internal.sh/blob/master/r.internal
  seems, to me, overall easier to (re-)implement in Python.

After reading the g.gui.modeler page I understand what it does but its
advantages over a plain shell script are not obvious to me. Pointers to more
information might provide the answers.

In the past, while beginning scripting in Python, the GUI modeler helped
me understand easier and learn better. The visual representation of and the
code behind a model, were easier to grasp than reading only a program.

A life-long learner, Nikos