Re: [GRASS-user] Mapset access - grass-6.4.0RC4
Luís wrote: [Errno 2] No such file or directory: '/media/WORKSPACE_2/Workspace/L7ETM204033/\n20090225_GAP' /media/WORKSPACE_2/Workspace/L7ETM204033/\n20090225_GAP is a wrong path. Location: L7ETM204033 Mapset: 20090225_GAP an extra newline character (\n) snuck in there somehow. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] m.eigensystem segfaults under Jaunty (beta)
m.eigensystem, compiled against latest grass6_dev _AND_ grass-6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. Greetings, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] m.eigensystem segfaults under Jaunty (beta)
On Mon, 2009-04-13 at 13:52 +0200, Nikos Alexandris wrote: m.eigensystem, compiled against latest grass6_dev _AND_ grass-6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. Example with spearfish landsat data below (tried with other data as well): # launch fresh-baked grass6_dev grass65 /geo/grassdb/nc_spm_08/PERMANENT/ # one-liner using 3 bands (echo 3; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% Segmentation fault (core dumped) # extra-info # intentionally provide _4_ instead of _3_ in echo # m.eigensystem aborts because of incomplete input... (echo 4; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% Incomplete input file --- Cheers, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] m.eigensystem segfaults under Jaunty (beta)
OK, I should start at some point practicing debug-ing. Though, unknown territory for me the G_* messages below. Nikos: m.eigensystem, compiled against latest grass6_dev _AND_ grass-6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. Example with spearfish landsat data below (tried with other data as well): # one-liner using 3 bands (echo 3; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% Segmentation fault (core dumped) # setting debug level 5 g.gisenv set=DEBUG=5 # output of the above one-liner D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 99 D3/5: region item: zone: 0 D3/5: region item: north: 221230 D3/5: region item: south: 219580 D3/5: region item: east: 639530 D3/5: region item: west: 637740 D3/5: region item: cols: 179 D3/5: region item: rows: 165 D3/5: region item: e-w resol: 10 D3/5: region item: n-s resol: 10 D3/5: region item: top:1 D3/5: region item: bottom: 0 D3/5: region item: cols3: 179 D3/5: region item: rows3: 165 D3/5: region item: depths: 1 D3/5: region item: e-w resol3: 10 D3/5: region item: n-s resol3: 10 D3/5: region item: t-b resol: 1 D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 99 D3/5: region item: zone: 0 D3/5: region item: north: 228513 D3/5: region item: south: 214975.5 D3/5: region item: east: 645012 D3/5: region item: west: 629992.5 D3/5: region item: cols: 527 D3/5: region item: rows: 475 D3/5: region item: e-w resol: 28.5 D3/5: region item: n-s resol: 28.5 D3/5: region item: format: 0 D3/5: region item: compressed: 1 D3/5: create window mapping (179 columns) D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 99 D3/5: region item: zone: 0 D3/5: region item: north: 228513 D3/5: region item: south: 214975.5 D3/5: region item: east: 645012 D3/5: region item: west: 629992.5 D3/5: region item: cols: 527 D3/5: region item: rows: 475 D3/5: region item: e-w resol: 28.5 D3/5: region item: n-s resol: 28.5 D3/5: region item: format: 0 D3/5: region item: compressed: 1 D3/5: create window mapping (179 columns) D2/5: G__read_Cell_head D2/5: G__read_Cell_head_array D3/5: region item: proj: 99 D3/5: region item: zone: 0 D3/5: region item: north: 228513 D3/5: region item: south: 214975.5 D3/5: region item: east: 645012 D3/5: region item: west: 629992.5 D3/5: region item: cols: 527 D3/5: region item: rows: 475 D3/5: region item: e-w resol: 28.5 D3/5: region item: n-s resol: 28.5 D3/5: region item: format: 0 D3/5: region item: compressed: 1 D3/5: create window mapping (179 columns) r.covar: complete ... 100% Segmentation fault (core dumped) --- Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] m.eigensystem segfaults under Jaunty (beta)
On Mon, Apr 13, 2009 at 3:05 PM, Nikos Alexandris nikos.alexand...@felis.uni-freiburg.de wrote: On Mon, 2009-04-13 at 13:52 +0200, Nikos Alexandris wrote: m.eigensystem, compiled against latest grass6_dev _AND_ grass-6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. Example with spearfish landsat data below (tried with other data as well): # launch fresh-baked grass6_dev grass65 /geo/grassdb/nc_spm_08/PERMANENT/ # one-liner using 3 bands (echo 3; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% Segmentation fault (core dumped) Here's my take: GRASS 6.5.svn (nc_spm_07):~ (echo 3; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% ERROR: No non-null values Incomplete input file BUT: GRASS 6.5.svn (nc_spm_07):~ g.region rast=lsat7_2002_10 GRASS 6.5.svn (nc_spm_07):~ (echo 3; r.covar lsat7_2002_10,lsat7_2002_20,lsat7_2002_30) | m.eigensystem r.covar: complete ... 100% E 2134.5009768265 0.0098.07 V 0.5053399527 0.00 V 0.5791606282 0.00 V 0.8626950892 0.00 ... Does it work for you if you set the region to the lsat7_2002_10 map? If yes, then m.eigensystem just suffers from not trapping bad input. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Multiple to one question
I am trying to set up a new project in Grass, and I have a question about the best approach. I have different vector locations, and at each one there were multiple samples taken. At the moment I have each sample as a row in a data base. My question is how best to put this data into a set of vector points. I believe that I can do it in either of two ways (of not others). 1) I can create a vector point at each location, then I think that I can have multiple cats for that object. So I think I can do cat=1,3,6 for a given location. Will that work OK? 2) I can just create different vector objects, that happen to be at the identical location, and have each one point to a different cat. If the above is not clear, here is a bit more detailed example. At location A there was a sample collected on 1/1 with a value of 2.1, on 2/2 with a value of 2.2 and on 3/3 with a value of 3.3 The above data is already 3 rows in a database. I want to be able to display data about point A (say, average value or things like that). Should I just create a vector point A and then do cat=1,2,3 or should I create 3 different vector points at A, each one having a different cat? Any guidance about the benefits or limitations each approach (or any other approach to consider) would be greatly appreciated. Thanks, --Adam ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] m.eigensystem segfaults under Jaunty (beta)
Nikos: On Mon, 2009-04-13 at 13:52 +0200, Nikos Alexandris wrote: m.eigensystem, compiled against latest grass6_dev _AND_ grass-6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. It works fine with Ubuntu Intrepid! So, something in Jaunty doesn't like m.eigensystem (fortran code?)! Cheers, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] m.eigensystem segfaults under Jaunty (beta)
Nikos Alexandris wrote: m.eigensystem, compiled against latest grass6_dev _AND_ grass -6.4.0RC4 source code, segfaults under Ubuntu-J 64-bit Beta. It works fine with Ubuntu Intrepid! So, something in Jaunty doesn't like m.eigensystem (fortran code?)! any chance of debugging? (gdb, etc) how far does it get? (if no idea you might try to cut and paste in some print strings from elsewhere in the code with little made it to line 110) comments then recompile. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
