Re: [GRASS-user] GRASS pygrass - composite
On 11/02/2015 14:55, Pierric de Laborie wrote: Dear Pietro, I ran the same command with the highest level of verbose. Unfortunately it didn't give much more information when blocking at the problematic step. I also started the same command from GRASS GUI on another debian machine and it got stuck also. It is like the installation on Debian Wheezy doesn't fully work (?) GRASS 7.0.0svn (222):~/Grass_test g.gisenv set="DEBUG=5" D1/1: G_set_program_name(): g.gisenv D1/5: G_set_program_name(): g.gisenv D2/5: G_option_to_separator(): key = separator - sep = '/' GRASS 7.0.0svn (222):~/Grass_test r.composite red=B5@PERMANENT green=B4@PERMANENT blue=B3@PERMANENT output=mycompo D1/5: G_set_program_name(): r.composite D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/cell/mycompo D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: file open: read (mode = r) D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 1 D3/5: region item: zone: 32 D3/5: region item: north: 3948015 D3/5: region item: south: 0 D3/5: region item: east: 841215 D3/5: region item: west: 0 D3/5: region item: cols: 841215 D3/5: region item: rows: 3948015 D3/5: region item: e-w resol: 1 D3/5: region item: n-s resol: 1 D3/5: region item: top: 1.000 D3/5: region item: bottom: 0.000 This one input raster is huge. 840,000x394,000 = 331,000,000,000 pixels. That's probably not what you want. If you have your region set to match this raster (rather than the others, which seem to be normal size) then that would certainly cause the machine to lock up. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS pygrass - composite
I wonder if there is any idea/intention to built in kind of a check mechanism for modules applicable to raster data. This, and the Εxtent concept as well, are most frequent problems/inattentions. Nikos On 12.02.2015 10:33, Pierric de Laborie wrote: Thanks for your input. This was probably the reason why. Grass defaulted the region to the raster with the highest resolution. 2015-02-12 9:23 GMT+01:00 Micha Silver mi...@arava.co.il: On 11/02/2015 14:55, Pierric de Laborie wrote: Dear Pietro, I ran the same command with the highest level of verbose. Unfortunately it didn't give much more information when blocking at the problematic step. I also started the same command from GRASS GUI on another debian machine and it got stuck also. It is like the installation on Debian Wheezy doesn't fully work (?) GRASS 7.0.0svn (222):~/Grass_test * g.gisenv set=DEBUG=5 * D1/1: G_set_program_name(): g.gisenv D1/5: G_set_program_name(): g.gisenv D2/5: G_option_to_separator(): key = separator - sep = '/' GRASS 7.0.0svn (222):~/Grass_test * r.composite red=B5@PERMANENT green=B4@PERMANENT blue=B3@PERMANENT output=mycompo* D1/5: G_set_program_name(): r.composite D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/cell/mycompo D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: file open: read (mode = r) D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 1 D3/5: region item: zone: 32 D3/5: region item: north: 3948015 D3/5: region item: south: 0 D3/5: region item: east: 841215 D3/5: region item: west: 0 D3/5: region item: cols: 841215 D3/5: region item: rows: 3948015 D3/5: region item: e-w resol: 1 D3/5: region item: n-s resol: 1 D3/5: region item: top:1.000 D3/5: region item: bottom: 0.000 This one input raster is huge. 840,000x394,000 = 331,000,000,000 pixels. That's probably not what you want. If you have your region set to match this raster (rather than the others, which seem to be normal size) then that would certainly cause the machine to lock up. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user -- Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS pygrass - composite
On Thu, Feb 12, 2015 at 3:33 AM, Pierric de Laborie pierric.delabo...@gmail.com wrote: Grass defaulted the region to the raster with the highest resolution. GRASS is not doing anything like that. The computation region is always set by the user (typically using g.region) except for the case when Location or Mapset are created and used for the first time. When Location is created based on data, the region is set to match the data (when requested). This applies to computational region in PERMANENT Mapset and Location's default computational region. Alternative is, for example, a manual settings in Location Wizard when creating new Location manually. For new Mapsets, Location's default region is used. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS pygrass - composite
Thanks for your input. This was probably the reason why. Grass defaulted the region to the raster with the highest resolution. 2015-02-12 9:23 GMT+01:00 Micha Silver mi...@arava.co.il: On 11/02/2015 14:55, Pierric de Laborie wrote: Dear Pietro, I ran the same command with the highest level of verbose. Unfortunately it didn't give much more information when blocking at the problematic step. I also started the same command from GRASS GUI on another debian machine and it got stuck also. It is like the installation on Debian Wheezy doesn't fully work (?) GRASS 7.0.0svn (222):~/Grass_test * g.gisenv set=DEBUG=5 * D1/1: G_set_program_name(): g.gisenv D1/5: G_set_program_name(): g.gisenv D2/5: G_option_to_separator(): key = separator - sep = '/' GRASS 7.0.0svn (222):~/Grass_test * r.composite red=B5@PERMANENT green=B4@PERMANENT blue=B3@PERMANENT output=mycompo* D1/5: G_set_program_name(): r.composite D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/cell/mycompo D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: G_file_name(): path = /tmp/grassdata/222/PERMANENT/WIND D2/5: file open: read (mode = r) D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 1 D3/5: region item: zone: 32 D3/5: region item: north: 3948015 D3/5: region item: south: 0 D3/5: region item: east: 841215 D3/5: region item: west: 0 D3/5: region item: cols: 841215 D3/5: region item: rows: 3948015 D3/5: region item: e-w resol: 1 D3/5: region item: n-s resol: 1 D3/5: region item: top:1.000 D3/5: region item: bottom: 0.000 This one input raster is huge. 840,000x394,000 = 331,000,000,000 pixels. That's probably not what you want. If you have your region set to match this raster (rather than the others, which seem to be normal size) then that would certainly cause the machine to lock up. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS pygrass - composite
Dear Pierric, On Wed, Feb 11, 2015 at 10:02 AM, Pierric de Laborie pierric.delabo...@gmail.com wrote: I don't understand why Grass seems to get stuck on the following Python command : r.composite(red=B4,green=B3,blue=B2,output=mycomposite,quiet=QUIET,overwrite=OVR) Have you tried to run the same command in BASH in a normal GRASS shell? Does it work? if yes, can you run a python interpreter inside the GRASS shell and see if calling the module from pygrass it works or not. Just some ideas to understand where could be the problem. All the best Pietro ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS pygrass - composite
I have just tried to start the same command from the GRASS shell (same machine and same GRASS database and location) and it gets stuck also. GRASS 7.0.0svn (222):~/Grass_test r.composite red=B5@PERMANENT green=B4@PERMANENT blue=B3@PERMANENT output=mycompo Creating color table for output raster map... 0..6..12..18..25..31..37..43..50..56..62..68..75..81..87..93..100 Writing raster map mycompo... 0.. Running the same command in GRASS GUI (command shell) on Windows works fine and creates a composite in a few seconds. I am starting to think that it is due to the way I installed Grass on this Linux machine (I used the following link http://grasswiki.osgeo.org/wiki/Compile_and_Install#GRASS_7_on_Debian_Wheezy ) Thanks 2015-02-11 10:42 GMT+01:00 Pietro peter.z...@gmail.com: Dear Pierric, On Wed, Feb 11, 2015 at 10:02 AM, Pierric de Laborie pierric.delabo...@gmail.com wrote: I don't understand why Grass seems to get stuck on the following Python command : r.composite(red=B4,green=B3,blue=B2,output=mycomposite,quiet=QUIET,overwrite=OVR) Have you tried to run the same command in BASH in a normal GRASS shell? Does it work? if yes, can you run a python interpreter inside the GRASS shell and see if calling the module from pygrass it works or not. Just some ideas to understand where could be the problem. All the best Pietro ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
