i.spectral in GRASS6.4

[arocha]

I'm using GRASS 6.4.0svn (2009) with wxpython and when I select Imagery/Spectral Response (i.spectral) I get this error.

* Traceback (most recent call last): File "C:/GRASS6/etc/wxpython/wxgui.py", line 521, in OnMenuCmd

menuform.GUI().ParseCommand(cmd, parentframe=self) File "C:\GRASS6\etc\wxpython\gui_modules\menuform.py", line 1809, in ParseCommand

xml.sax.parseString(getInterfaceDescription(cmd[0]).decode(e nc).encode("utf-8"), File "C:\GRASS6\etc\wxpython\gui_modules\menuform.py", line 1748, in getInterfaceDescription

raise IOError, _("Unable to fetch interface description for command '%s'.") % cmd IOError : Unable to fetch interface description for command 'i.spectral'. *

Is this something that was expected in this version or anyone has a an idea of how to fix this?

[neteler]

I see this bug in several bug reports: #639, #581, #553, #234

It is not systematic but perhaps there is a chance to reproduce it.

[cmbarton]

Reading the error message, I'm completely convinced that this is even a wxGUI problem. The error message suggests that "<command> --interface-description" is not returning anything.

I do not have any problem launching either i.spectral or v.in.ogr (trac #581) in the current svn version of GRASS 6.4 (or other versions) on Mac OS X.

I see that this may be intermittent, but perhaps it is fixed now. Does this still happen to anyone?

Michael

[cmbarton]

Replying to cmbarton:

Reading the error message, I'm completely convinced that this is even a wxGUI

This *should* read, I'm NOT completely convinced...

problem. The error message suggests that "<command> --interface-description" is not returning anything.

I do not have any problem launching either i.spectral or v.in.ogr (trac #581) in the current svn version of GRASS 6.4 (or other versions) on Mac OS X.

I see that this may be intermittent, but perhaps it is fixed now. Does this still happen to anyone?

Michael

[hamish]

(use the "wingrass" keyword so it makes it onto the WinGrass errata list and so gets more visibility)

[cmbarton]

Is this a Windows-only problem?

Michael

[hamish]

as per comments in #581,

• Can you try again with a nightly wingrass build >rev41308? I suspect that Martin may have just fixed this (or something rather similar) in SVN with r41308.

[hellik]

Replying to hamish:

as per comments in #581,

• Can you try again with a nightly wingrass build >rev41308? I suspect that Martin may have just fixed this (or something rather similar) in SVN with r41308.

i've just looked at

​http://grass.osgeo.org/grass64/manuals/html64_user/i.spectral.html

is there a example with the nc-sample-dataset for testing?

in the manuals there is

NOTES
This script needs gnuplot to be installed. 

is there a gnuplot-version in osgeo4w or in osgeo4w-based wingrass-version?

Helmut

[hamish]

Replying to cmbarton:

I do not have any problem launching either i.spectral or v.in.ogr (trac #581) in the current svn version of GRASS 6.4 (or other versions) on Mac OS X.

yeah, but what if you change language settings to something that uses chars outside the common western european language set?

[cmbarton]

I don't know. Maybe someone using another character set can check. But I'm not sure how an alternate character set would affect the launching of these 2 modules and not affect the launching of all modules.

Michael

[hamish]

and someone using a non-western European language set give it a try? is i.spectral still broken from the wxgui menu?

worksforme, Hamish

[martinl]

Replying to hamish:

and someone using a non-western European language set give it a try? is i.spectral still broken from the wxgui menu?

no problem here

[neteler]

Still failing in wxGUI (tested on Linux):

North Carolina example:

• display "lsat7_2002_20"
• start i.spectral from command line with -i -m

--> d.where and r.what zombie processes occur

CLI example:

g.region rast=lsat7_2002_10 -p
d.mon x0
d.rast lsat7_2002_40
i.spectral -i -m rast=lsat7_2002_10,lsat7_2002_20,lsat7_2002_30,lsat7_2002_40,lsat7_2002_50,lsat7_2002_70

[hamish]

The original --interface-description problem on wingrass seems fixed now.

Xmons are not available in Wingrass, so picking interactively won't work there anyway even if gnuplot was installed. I've now added a test in devbr6 (r56946) to bail out early if no Xmon is open.

Gnuplot is not shipped with our Wingrass package, so the module won't work there. If you try to run it you hit that error message first, asking you to install.

BUT:

'd.mon -L' as a command layer in the wxGUI shows all monitors as running?!

same for "grass.run_command('d.mon', flags = 'L')" from the Python shell tab. ??

I don't know of a good way for the script to test if it was called from the wxGUI or not (especially after laundering through g.parser), so the solution probably needs to be in menudata.xml.

trying MarkusN's example from comment:12 works fine for me in Linux from the command line. it also doesn't lock up from the wxGUI _without_ the -m flag, even without an Xmon open. trying from the wxGUI on linux (with an Xmon open) with the -m flag causes the zombie mayhem. Perhaps in menudata.xml the handler for i.spectral needs to be changed to OnXTerm instead of OnMenuCmd? Another idea is to write a wrapper --script for the wxGUI menu entry which forces non-interactive mode.

In addition to a number of other cleanups, I've also just added a new east_north= option in devbr6 to allow non-interactive operation (so no Xmonitor needed), and a couple new output graphics formats. I'll sync those with trunk asap.

I'm not sure how much to backport to 6.4.3, at least the group= input option is totally broken there since the i.group output text changed (but luckily the new i.group -g flag makes the parsing much easier).

Hamish

ps- interestingly enough, while reading through the Gnuplot manual I noticed that a "grass" graphics terminal exists for gnuplot which will render your plots directly to a GRASS Xmonitor. It wasn't built into my copy though so I couldn't test it.

[cmbarton]

i.spectral is a very good candidate to be implemented in a wxPlot interface like profiling and image scatterplots.

Michael