> It means that there's something to fix in the module? Or is a grass issue?
tested here again: GRASS Version: 7.1.svn GRASS SVN revision: 64291 Build date: 2015-01-24 Build platform: i686-pc-mingw32 GDAL: 1.11.1 PROJ.4: 4.8.0 GEOS: 3.4.2 SQLite: 3.7.17 Python: 2.7.4 wxPython: 2.8.12.1 Platform: Windows-7-6.1.7601-SP1 (OSGeo4W) as r.massmov doesn't show any (re)action, it's hard to say; but I assume a fix in r.massmov is needed. a quick test with different debug levels: g.gisenv set=DEBUG=3 g.gisenv set=DEBUG=5 C:\>r.massmov C:\> C:\>r.massmov --help C:\> C:\>r.massmov --ui C:\> if you try to invoke the module, unfortunately nothing happens: no error message, no debug message, ... maybe something with parallelization in windows? ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/r-massmov-tp5181466p5183520.html Sent from the Grass - Users mailing list archive at Nabble.com. _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
