[GRASS-SVN] r69252 - grass-addons/grass7/imagery/i.segment.uspo

[svn_grass at osgeo.org]

Author: mlennert
Date: 2016-08-24 09:26:30 -0700 (Wed, 24 Aug 2016)
New Revision: 69252

Modified:
   grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.html
   grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.py
Log:
i.segment.uspo: small bug in non-required parameter handling and improvement of doc


Modified: grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.html
===================================================================
--- grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.html	2016-08-24 15:50:26 UTC (rev 69251)
+++ grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.html	2016-08-24 16:26:30 UTC (rev 69252)
@@ -2,11 +2,15 @@
 
 <p><em>i.segment.uspo</em> provides unsupervised segmentation parameter
 optimization for <em><a href="i.segment.html">i.segment</a></em>. It runs
-segmentation across a user defined set of thresholds and minimum segment sizes
-and then selects the parameters providing the highest values of a given
-optimization function. The number of "best" parameter combinations to provide 
-to the user per <b>region</b> is defined by <b>number_best</b>.
+segmentation across a user defined set of thresholds and minimum segment sizes,
+as well, for the mean shift algorithm, a set of spectral and spatial bandwiths. 
+For the mean shift algorithm, you can also activate adaptive bandwidth using
+the <em>-a</em> flag.
 
+<p>The module then selects the parameters providing the highest values of a
+given optimization function. The number of "best" parameter combinations to 
+provide to the user per <b>region</b> is defined by <b>number_best</b>.
+
 <p>The user provides an imagery <b>group</b> and the name of an <b>output</b>
 text file where parameter and optimization values for all tested segmentations
 are stored. The user can either give a list of thresholds and minimum sizes, or
@@ -54,6 +58,11 @@
 and other types of validation of the results, possibly comparing several of the
 "best" solutions, remain necessary.
 
+<p> Even though the module allows the user to test different <em>minsizes</em>,
+it is probably better to run the module with minsizes=1 and then adapt the 
+minsize in the final run of <a href="i.segment.html">i.segment</a> depending 
+on the desired minimum mapping unit.
+
 <p> In hierarchical segmentation mode, the processes are divided between
 different calls to <a
 href="https://grass.osgeo.org/grass70/manuals/addons/i.segment.hierarchical.html">i.segment.hierarchical</a>.  This

Modified: grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.py
===================================================================
--- grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.py	2016-08-24 15:50:26 UTC (rev 69251)
+++ grass-addons/grass7/imagery/i.segment.uspo/i.segment.uspo.py	2016-08-24 16:26:30 UTC (rev 69252)
@@ -704,7 +704,7 @@
 
     if options['hrs']:
         hrs = [float(x) for x in options['hrs'].split(',')]
-    else:
+    if options['hr_step']:
         step = float(options['hr_step'])
         start = float(options['hr_start'])
         stop = float(options['hr_stop'])
@@ -715,7 +715,7 @@
 
     if options['radiuses']:
         radiuses = [float(x) for x in options['radiuses'].split(',')]
-    else:
+    if options['radius_step']:
         step = float(options['radius_step'])
         start = float(options['radiues_start'])
         stop = float(options['radius_stop'])