#2913: i.segment.hierarchical: why is there a mandatory output option
-------------------------------------------+-------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.4
Component: Addons | Version: unspecified
Keywords: i.segment.hierarchical output | CPU: Unspecified
Platform: Unspecified |
-------------------------------------------+-------------------------
i.segment.hierarchical has the following parameters (among others):
{{{
output Name of output segment raster map
outputs_prefix Name for output raster maps from segment
par défaut: seg__%.2f
}}}
I don't really understand the sens of 'output': The whole idea of the
module is to create multiple output maps containing the results of
hierarchical segmentation. So why would one need one single output map
name ?
#2913: i.segment.hierarchical: why is there a mandatory output option
--------------------------+-------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.4
Component: Addons | Version: unspecified
Resolution: | Keywords: i.segment.hierarchical output
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------------------------
Comment (by zarch):
Replying to [ticket:2913 mlennert]:
> i.segment.hierarchical has the following parameters (among others):
>
>
> {{{
> output Name of output segment raster map
> outputs_prefix Name for output raster maps from segment
> par défaut: seg__%.2f
> }}}
>
> I don't really understand the sens of 'output': The whole idea of the
module is to create multiple output maps containing the results of
hierarchical segmentation. So why would one need one single output map
name ?
Actually I wrote this module to have a single segmented output map!
The idea of the module was to parallelize the i.segment module into cores
and nodes in a cluster on single tiles, once the segmentation per tile is
done then patch the tiles in a unique map and apply i.segment using the
segmented map as seed to obtain as output a large segmented map.
I put also the option outputs_prefix, that probably should be change in
"basename" to define the name of the "temporary" segmented tiles.
#2913: i.segment.hierarchical: why is there a mandatory output option
--------------------------+-------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.4
Component: Addons | Version: unspecified
Resolution: | Keywords: i.segment.hierarchical output
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------------------------
Comment (by mlennert):
Replying to [comment:1 zarch]:
> Replying to [ticket:2913 mlennert]:
> > i.segment.hierarchical has the following parameters (among others):
> >
> >
> > {{{
> > output Name of output segment raster map
> > outputs_prefix Name for output raster maps from segment
> > par défaut: seg__%.2f
> > }}}
> >
> > I don't really understand the sens of 'output': The whole idea of the
module is to create multiple output maps containing the results of
hierarchical segmentation. So why would one need one single output map
name ?
>
> Actually I wrote this module to have a single segmented output map!
Oh, I guess I was fooled by the name. 'hierarchical' evokes several maps
for me...
>
> The idea of the module was to parallelize the i.segment module into
cores and nodes in a cluster on single tiles, once the segmentation per
tile is done then patch the tiles in a unique map and apply i.segment
using the segmented map as seed to obtain as output a large segmented map.
>
Well, it is also very nice to create a series of hierarchically segmented
maps, even without using the parallel processing mode (which actually
fails for me - see #2902).
> I put also the option outputs_prefix, that probably should be change in
"basename" to define the name of the "temporary" segmented tiles.
But if you only create one output map, why go through a whole list of
thresholds for segmentation ?
In my use case, 'output' is not necessary, 'basename' is. So, at least
they should each be optional. BTW, concering this basename, see also #2914. And while you're at it, could you also give your opinion on #2915 ?
#2913: i.segment.hierarchical: why is there a mandatory output option
--------------------------+-------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.4
Component: Addons | Version: unspecified
Resolution: | Keywords: i.segment.hierarchical output
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------------------------
Comment (by zarch):
Replying to [comment:2 mlennert]:
> Replying to [comment:1 zarch]:
> > Replying to [ticket:2913 mlennert]:
> > I put also the option outputs_prefix, that probably should be change
in "basename" to define the name of the "temporary" segmented tiles.
>
> But if you only create one output map, why go through a whole list of
thresholds for segmentation ?
I've used to identify the "best" segment threshold
> In my use case, 'output' is not necessary, 'basename' is. So, at least
they should each be optional.
Yes, indeed they should be both optionals.
> BTW, concering this basename, see also #2914. And while you're at it,
could you also give your opinion on #2915 ?
Actually I did this morning but I realize that my replies were losts,
let's do it again.
