Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: grass-6.0.cvs_src_snapshot_2005_03_05
child process exited abnormally
while executing
"exec -- d.mon start=CELL >@ stdout 2>@ stderr"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >@ stdout 2>@ stderr"
(procedure "run" line 2)
invoked from within
"run d.mon start=CELL"
invoked from within
".#menubar.#menubar#menu2.#menubar#menu2#menu4 invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tkMenuInvoke" line 47)
invoked from within
"tkMenuInvoke .#menubar.#menubar#menu2.#menubar#menu2#menu4 1
"Welcome to GRASS 6.0.cvs (2005)
GRASS homepage: http://grass.itc.it/
This version running thru: Bash Shell (/bin/bash)
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
If required, restart the graphical user interface with: d.m &
When ready to quit enter: exit
GRASS 6.0.cvs (lafay_gdal):/ext2e/data/GRASSDATA > Could not execute monitor: No such file or directory
No socket to connect to for monitor <CELL>.
Problem selecting CELL. Will try once more
No socket to connect to for monitor <CELL>.
-------------------------------------------- Managed by Request Tracker
Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: grass-6.0.cvs_src_snapshot_2005_03_05
child process exited abnormally
while executing
"exec -- d.mon start=CELL >@ stdout 2>@ stderr"
...
GRASS 6.0.cvs (lafay_gdal):/ext2e/data/GRASSDATA > Could not execute monitor: No such file or directory
No socket to connect to for monitor <CELL>.
Problem selecting CELL. Will try once more
No socket to connect to for monitor <CELL>.
The CELL driver was not ported (yet?) to GRASS 6.
Please use the PNG driver which is even more powerful.
The CELL driver has been non-functional since the switch to 5.7 (now 6). I
don't know why it still shows up as existing when you list available
monitors, but this should probably be disabled--unless there are plans to
revive the CELL driver.
Michael
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: grass-6.0.cvs_src_snapshot_2005_03_05
child process exited abnormally
while executing
"exec -- d.mon start=CELL >@ stdout 2>@ stderr"
("eval" body line 1)
invoked from within
"eval exec -- $cmd $args >@ stdout 2>@ stderr"
(procedure "run" line 2)
invoked from within
"run d.mon start=CELL"
invoked from within
".#menubar.#menubar#menu2.#menubar#menu2#menu4 invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tkMenuInvoke" line 47)
invoked from within
"tkMenuInvoke .#menubar.#menubar#menu2.#menubar#menu2#menu4 1
"Welcome to GRASS 6.0.cvs (2005)
GRASS homepage: http://grass.itc.it/
This version running thru: Bash Shell (/bin/bash)
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
If required, restart the graphical user interface with: d.m &
When ready to quit enter: exit
GRASS 6.0.cvs (lafay_gdal):/ext2e/data/GRASSDATA > Could not execute monitor:
No such file or directory
No socket to connect to for monitor <CELL>.
Problem selecting CELL. Will try once more
No socket to connect to for monitor <CELL>.
-------------------------------------------- Managed by Request Tracker
The CELL driver has been non-functional since the switch to 5.7 (now
6). I don't know why it still shows up as existing when you list
available monitors, but this should probably be disabled--unless there
are plans to revive the CELL driver.
Markus:
The CELL driver was not ported (yet?) to GRASS 6.
Please use the PNG driver which is even more powerful.
Is there any point/advantage to having a CELL driver anymore?
What could it be used for that can't be done via another path?
> The CELL driver has been non-functional since the switch to 5.7 (now
> 6). I don't know why it still shows up as existing when you list
> available monitors, but this should probably be disabled--unless there
> are plans to revive the CELL driver.
Markus:
> The CELL driver was not ported (yet?) to GRASS 6.
> Please use the PNG driver which is even more powerful.
Is there any point/advantage to having a CELL driver anymore?
What could it be used for that can't be done via another path?
Given that both the CELL and PNG drivers behave in a near-identical
manner, i.e. store values in a 2D "array" then convert the array to an
external representation upon either termination or R_close_driver(),
there should probably be some re-factoring in that area.
IOW, either:
a) merge the CELL and PNG drivers so that the CELL functionality is
essentially just another output "target" (e.g. if GRASS_PNGFILE
doesn't end in ".png" or ".ppm", it's treated as a map name), or
b) move the bulk of the PNG driver into a library; either the existing
driverlib or a new library specifically for drivers which behave like
the CELL and PNG drivers.