Re: [GRASS-user] r.mapcalc appears to have changed behavior
Nice to know I can remove one possibility from my list of computing worries :-) regards, shane. On Sat, 2011-10-01 at 00:51 -0700, Michael Barton wrote: > Fortunately, upgrading GRASS should have no effect on the region settings for > maps. > > Michael > > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice:480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Sep 30, 2011, at 11:35 PM, Shane Litherland wrote: > > > Jim, et al., > > > > I am not an authority on GRASS, but it may not have been you that 'did > > that' - if you were using an earlier version and did a significant > > upgrade or a fresh install of a newer version of GRASS, some fine > > details like this might end up with new default values (?) I recall > > doing a few re-installs/upgrades and having to keep a close eye on user > > settings, mapset locations, etc when starting up a newer GRASS. > > > > May not be what happened in your case, but worth keeping in mind if/when > > you are moving around GRASS versions or using it on other computers etc, > > check up on some of the environment variables as you go. Help docs have > > info on how to find the gory detail :-) > > > > > > > > From: Jim Mochel > > Subject: Re: [GRASS-user] r.mapcalc appears to have changed behavior > > To: Michael Barton > > Cc: grass-user grass-user > > Message-ID: > > > > Content-Type: text/plain; charset="iso-8859-1" > > > > Thank you. ! > > > > I am not sure how I did that but I am sure it seemed like a good idea at > > the > > time :-) > > > > Jim > > > > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.mapcalc appears to have changed behavior
Jim, et al., I am not an authority on GRASS, but it may not have been you that 'did that' - if you were using an earlier version and did a significant upgrade or a fresh install of a newer version of GRASS, some fine details like this might end up with new default values (?) I recall doing a few re-installs/upgrades and having to keep a close eye on user settings, mapset locations, etc when starting up a newer GRASS. May not be what happened in your case, but worth keeping in mind if/when you are moving around GRASS versions or using it on other computers etc, check up on some of the environment variables as you go. Help docs have info on how to find the gory detail :-) From: Jim Mochel Subject: Re: [GRASS-user] r.mapcalc appears to have changed behavior To: Michael Barton Cc: grass-user grass-user Message-ID: Content-Type: text/plain; charset="iso-8859-1" Thank you. ! I am not sure how I did that but I am sure it seemed like a good idea at the time :-) Jim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.mapcalc appears to have changed behavior
Fortunately, upgrading GRASS should have no effect on the region settings for maps. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Sep 30, 2011, at 11:35 PM, Shane Litherland wrote: > Jim, et al., > > I am not an authority on GRASS, but it may not have been you that 'did > that' - if you were using an earlier version and did a significant > upgrade or a fresh install of a newer version of GRASS, some fine > details like this might end up with new default values (?) I recall > doing a few re-installs/upgrades and having to keep a close eye on user > settings, mapset locations, etc when starting up a newer GRASS. > > May not be what happened in your case, but worth keeping in mind if/when > you are moving around GRASS versions or using it on other computers etc, > check up on some of the environment variables as you go. Help docs have > info on how to find the gory detail :-) > > .... > > From: Jim Mochel > Subject: Re: [GRASS-user] r.mapcalc appears to have changed behavior > To: Michael Barton > Cc: grass-user grass-user > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Thank you. ! > > I am not sure how I did that but I am sure it seemed like a good idea at > the > time :-) > > Jim > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.mapcalc appears to have changed behavior
Thank you. ! I am not sure how I did that but I am sure it seemed like a good idea at the time :-) Jim On Tue, Sep 27, 2011 at 1:02 AM, Michael Barton wrote: > It looks like for the 2nd calculation, your computational region is set to > extents of 0W - 1E, 0S - 1N, with a resolution of 1. > > So r.mapcalc is only operating on a single 1x1 cell that is outside the > area of your raster map. > > Michael > > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Sep 27, 2011, at 11:50 PM, < > grass-user-requ...@lists.osgeo.org> wrote: > > > Date: Mon, 26 Sep 2011 23:19:11 -0400 > > From: Jim Mochel > > Subject: [GRASS-user] r.mapcalc appears to have changed behavior > > To: grass-user@lists.osgeo.org > > Message-ID: > > r9e7rrwzbvff_fybmntep...@mail.gmail.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > I had made a number of scripts that worked fine in the 6.4.0 build 6 but > > appear to have problems with the same code in later revisions: > > > > The method used to take about 6-8 secs and produce about what you would > > expect on the screen. Now the same calculation takes 0 seconds the file > is > > radically changed. See the before and after below. > > > > Any help would be greatly appreciated. > > Thanks > > Jim Mochel > > > > r.mapcalc na_dem_sub_20 = na_dem_input - 20 > > > > > > > ++ > > | Layer:na_dem Date: Sat Sep 24 17:37:59 2011 > > | > > | Mapset: PERMANENT Login of Creator: jmochel > > | > > | Location: wgs84 > > | > > | DataBase: /home/jmochel/grassdata > > | > > | Title: ( na_dem ) > > | > > | Timestamp: none > > | > > > || > > | > > | > > | Type of Map: raster Number of Categories: 65535 > > | > > | Data Type:CELL > > | > > | Rows: 8384 > > | > > | Columns: 9102 > > | > > | Total Cells: 76311168 > > | > > |Projection: x,y > > | > > |N:4384500S: -3999500 Res: 1000 > > | > > |E:4639500W: -4462500 Res: 1000 > > | > > | Range of data:min = 0 max = 65535 > > | > > | > > | > > | Data Description: > > | > > |generated by r.in.gdal > > | > > | > > | > > | Comments: > > | > > |r.in.gdal input="/home/jmochel/gis/raw-data/hydo1k/na_dem.bil" > outpu\ > > | > > |t="na_dem" > > | > > | > > | > > > ++ > > > > > > r.info map=na_dem_sub_20 > > > > > ++ > > | Layer:na_dem_sub_20 Date: Mon Sep 26 23:06:03 2011 > > | > > | Mapset: PERMANENT Login of Creator: jmochel > > | > > | Location: wgs84 > > | > > | DataBase: /home/jmochel/grassdata > > | > > | Title: ( na_dem_sub_20 ) > > | > > | Timestamp: none > > | > > > || > > | > > | > > | Type of Map: raster Number of Categories: 610 > > | > > | Data Type:CELL > > | > > | Rows: 1 > > | > > | Columns: 1 > > | > > | Total Cells: 1 > > | > > |Projection: x,y > > | > > |N: 1S: 0 Res: 1 > > | > > |E: 1W: 0 Res: 1 > > | > > | Range of data:min = 610 max = 610 > > | > > | > > | > > | Data Description: > > | > > |generated by r.mapcalc > > | > > | > > | > > | Comments: > > | > > |na_dem_input@PERMANENT - 20 > > | > > | > > | > > > ++ > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.mapcalc appears to have changed behavior
It looks like for the 2nd calculation, your computational region is set to extents of 0W - 1E, 0S - 1N, with a resolution of 1. So r.mapcalc is only operating on a single 1x1 cell that is outside the area of your raster map. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Sep 27, 2011, at 11:50 PM, wrote: > Date: Mon, 26 Sep 2011 23:19:11 -0400 > From: Jim Mochel > Subject: [GRASS-user] r.mapcalc appears to have changed behavior > To: grass-user@lists.osgeo.org > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > I had made a number of scripts that worked fine in the 6.4.0 build 6 but > appear to have problems with the same code in later revisions: > > The method used to take about 6-8 secs and produce about what you would > expect on the screen. Now the same calculation takes 0 seconds the file is > radically changed. See the before and after below. > > Any help would be greatly appreciated. > Thanks > Jim Mochel > > r.mapcalc na_dem_sub_20 = na_dem_input - 20 > > > ++ > | Layer:na_dem Date: Sat Sep 24 17:37:59 2011 > | > | Mapset: PERMANENT Login of Creator: jmochel > | > | Location: wgs84 > | > | DataBase: /home/jmochel/grassdata > | > | Title: ( na_dem ) > | > | Timestamp: none > | > || > | > | > | Type of Map: raster Number of Categories: 65535 > | > | Data Type:CELL > | > | Rows: 8384 > | > | Columns: 9102 > | > | Total Cells: 76311168 > | > |Projection: x,y > | > |N:4384500S: -3999500 Res: 1000 > | > |E:4639500W: -4462500 Res: 1000 > | > | Range of data:min = 0 max = 65535 > | > | > | > | Data Description: > | > |generated by r.in.gdal > | > | > | > | Comments: > | > |r.in.gdal input="/home/jmochel/gis/raw-data/hydo1k/na_dem.bil" outpu\ > | > |t="na_dem" > | > | > | > ++ > > > r.info map=na_dem_sub_20 > > ++ > | Layer:na_dem_sub_20 Date: Mon Sep 26 23:06:03 2011 > | > | Mapset: PERMANENT Login of Creator: jmochel > | > | Location: wgs84 > | > | DataBase: /home/jmochel/grassdata > | > | Title: ( na_dem_sub_20 ) > | > | Timestamp: none > | > || > | > | > | Type of Map: raster Number of Categories: 610 > | > | Data Type:CELL > | > | Rows: 1 > | > | Columns: 1 > | > | Total Cells: 1 > | > |Projection: x,y > | > |N: 1S: 0 Res: 1 > | > |E: 1W: 0 Res: 1 > | > | Range of data:min = 610 max = 610 > | > | > | > | Data Description: > | > |generated by r.mapcalc > | > | > | > | Comments: > | > |na_dem_input@PERMANENT - 20 > | > | > | > ++ ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.mapcalc appears to have changed behavior
Jim wrote: > I had made a number of scripts that worked fine in the 6.4.0 build 6 > but appear to have problems with the same code in later revisions: > The method used to take about 6-8 secs and produce about what you would > expect on the screen. Now the same calculation takes 0 seconds the file > is radically changed. See the before and after below. the computational region is wrong. use g.region to fix it. > r.mapcalc na_dem_sub_20 = na_dem_input - 20 to match the region to the input map, first run: g.region rast=na_dem_input compare: > Rows: 8384 > Columns: 9102 ... > Rows: 1 > Columns: 1 > Total Cells: 1 Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
