Re: [GRASS-user] v.whar.vect does not respond
Nikos wrote: + exec v.distance from=burned_area_sample_1_points to=sample_1_grid column=gridcell to_column=cat upload=to_attr dmax=0.0 from_layer=1 to_layer=1 100% 100% 100% ## Here it waits... waits... maybe just wait? I am _sure_ it did not take too long some last time when I tried this with the same map(s) ## Hamish: ok so v.distance is taking a very long time. can you try with v.what.vect --vebose ? that should give some more messages from v.distance instead of just 100% 100% 100%. # almost the same as above # executing the script with -x v.what.vect test_1 col=gridcell qvect=sample_1_grid qcol=cat --v + [ -z /usr/local/grass-6.5.svn ] + [ test_1 != @ARGS_PARSED@ ] + exec g.parser /usr/local/grass-6.5.svn/scripts/v.what.vect test_1 col=gridcell qvect=sample_1_grid qcol=cat --v + [ -z /usr/local/grass-6.5.svn ] + [ @ARGS_PARSED@ != @ARGS_PARSED@ ] + exec v.distance from=test_1 to=sample_1_grid column=gridcell to_column=cat upload=to_attr dmax=0.0 from_layer=1 to_layer=1 Finding nearest lines... 100% 100% Finding nearest areas... 100% # not much... also, you can turn on the debug messages: g.gisenv set=DEBUG=1 ok, DEBUG=2 did the trick and shows lots of update messages: ---%--- D2/2: SQL: update test_1 set gridcell = 1276 where cat = 194 ... D2/2: SQL: update test_1 set gridcell = 1277 where cat = 205 D2/2: SQL: update test_1 set gridcell = 1277 where cat = 206 D2/2: SQL: update test_1 set gridcell = 1277 where cat = 207 ---%--- Seems to work fine but slow(er)!? # off-topic: DEBUG=3 creates some impressive visual effect where, at some points, you see the output scrolling from top to bottom :-) # Thanks, Nikos I see one in v.distance G_debug(3, SQL: %s, db_get_string(stmt)); maybe more DB troubles? ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] v.whar.vect does not respond
Since last update of grass6_devel (a few days back) v.what.vect does not work anymore!? It starts counting some percentages and then... that was it. It just stays there... Anyone had/has issues with it before I spend time on trying to debug? Kind regards, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.whar.vect does not respond
On Mon, May 4, 2009 at 5:19 PM, Nikos Alexandris nikos.alexand...@felis.uni-freiburg.de wrote: Since last update of grass6_devel (a few days back) v.what.vect does not work anymore!? It starts counting some percentages and then... that was it. It just stays there... Anyone had/has issues with it before I spend time on trying to debug? I tried in Spearfish: g.copy vect=archsites,myarchsites v.db.addcol myarchsites col=owner varchar(25) v.what.vect myarchsites qvect=fields column=owner qcolumn=label # verification: v.db.select myarchsites No problem... Add -x to the first line in the v.what.vect script to see the script execution stepwise. Then you'll see where is stops: http://grass.osgeo.org/wiki/GRASS_Debugging#Shell_script_debugging Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.whar.vect does not respond
On Mon, 2009-05-04 at 21:45 +0200, Markus Neteler wrote: On Mon, May 4, 2009 at 5:19 PM, Nikos Alexandris nikos.alexand...@felis.uni-freiburg.de wrote: Since last update of grass6_devel (a few days back) v.what.vect does not work anymore!? It starts counting some percentages and then... that was it. It just stays there... Anyone had/has issues with it before I spend time on trying to debug? I tried in Spearfish: g.copy vect=archsites,myarchsites v.db.addcol myarchsites col=owner varchar(25) v.what.vect myarchsites qvect=fields column=owner qcolumn=label # verification: v.db.select myarchsites No problem... Add -x to the first line in the v.what.vect script to see the script execution stepwise. Then you'll see where is stops: http://grass.osgeo.org/wiki/GRASS_Debugging#Shell_script_debugging Markus Just a quick feedback before doing real-testing: I have some point vectors (created last week) and v.what.vect indeed works fine on/with them. Now, if I take one of those point vectors (g.copy), drop a column just for fun (v.db.dropcol), add it back again (v.db.addcol column='test integer') v.what.vect does not work anymore on the _newly_ added column. Will test on spearfish data to see if I can replicate this. Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.whar.vect does not respond
Nikos: Since last update of grass6_devel (a few days back) v.what.vect does not work anymore!? It starts counting some percentages and then... that was it. It just stays there... Markus N: I tried in Spearfish: g.copy vect=archsites,myarchsites v.db.addcol myarchsites col=owner varchar(25) v.what.vect myarchsites qvect=fields column=owner qcolumn=label # verification: v.db.select myarchsites No problem... Yep, no problem at all with Spearfish. Add -x to the first line in the v.what.vect script to see the script execution stepwise. Then you'll see where is stops: http://grass.osgeo.org/wiki/GRASS_Debugging#Shell_script_debugging I added -x but doesn't look very helpful as it get's (if it really stucks) after counting the progress-percentages of whatever process they refer to. ( For some modules I think it would be nice, if it is possible, to have sort of a progress indicator... just to know it's running and have a rough estimation of how long it will take to complete. ) The problem appears in a (at least one) map which I recreated today since it was not working at all (due to database locked message). The steps were: # rasterise some map r.to.vect input=burned_area_landsat_sample_1.rgb output=burned_area_sample_1_points feature=point # some info v.info burned_area_sample_1_points ---%--- Number of points: 99449 ---%--- # drop/add some column(s) v.db.dropcol map=burned_area_sample_1_points column=value v.db.dropcol map=burned_area_sample_1_points column=label v.db.addcol burned_area_sample_1_points column=gridcell integer # carry over from an area-vector to the point-vector the _cat_ numbers v.what.vect burned_area_sample_1_points col=gridcell qvect=sample_1_grid qcol=cat + [ -z /usr/local/grass-6.5.svn ] + [ burned_area_sample_1_points != @ARGS_PARSED@ ] + exec g.parser /usr/local/grass-6.5.svn/scripts/v.what.vect burned_area_sample_1_points col=gridcell qvect=sample_1_grid qcol=cat + [ -z /usr/local/grass-6.5.svn ] + [ @ARGS_PARSED@ != @ARGS_PARSED@ ] + exec v.distance from=burned_area_sample_1_points to=sample_1_grid column=gridcell to_column=cat upload=to_attr dmax=0.0 from_layer=1 to_layer=1 100% 100% 100% ## Here it waits... waits... maybe just wait? I am _sure_ it did not take too long some last time when I tried this with the same map(s) ## Currently I am watching the same process ran via strace! It throws out numerous lseek/lread messages. I'll give it some time but something is wrong because it takes too much time. Was there change recently in v.db.addcol or something related to v.db.dropcol? Nikos Regards, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.whar.vect does not respond
On Tue, 2009-05-05 at 01:13 +0200, Nikos Alexandris wrote: Nikos: Since last update of grass6_devel (a few days back) v.what.vect does not work anymore!? It starts counting some percentages and then... that was it. It just stays there... [...] Currently I am watching the same process ran via strace! It throws out numerous lseek/lread messages. I'll give it some time but something is wrong because it takes too much time. I was wrong about v.what.vect not working. Via strace I was ensured that something is going-on and I have to wait. Finally the process completed successfully. But I wonder why it took so much more than last time. Anyhow, sorry for the noise and thanks for the feedback. I learned about strace this time :-) Cheers, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.whar.vect does not respond
Nikos wrote: + exec v.distance from=burned_area_sample_1_points to=sample_1_grid column=gridcell to_column=cat upload=to_attr dmax=0.0 from_layer=1 to_layer=1 100% 100% 100% ## Here it waits... waits... maybe just wait? I am _sure_ it did not take too long some last time when I tried this with the same map(s) ## Currently I am watching the same process ran via strace! It throws out numerous lseek/lread messages. I'll give it some time but something is wrong because it takes too much time. ok so v.distance is taking a very long time. can you try with v.what.vect --vebose ? that should give some more messages from v.distance instead of just 100% 100% 100%. also, you can turn on the debug messages: g.gisenv set=DEBUG=1 turn it up to 2,3,.. to get more messages. set it back to 0 to turn them off. I see one in v.distance G_debug(3, SQL: %s, db_get_string(stmt)); maybe more DB troubles? Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
