Opened 5 years ago

Closed 6 months ago

#2483 closed defect (wontfix)

adding output to groups

Reported by: mlennert Owned by: grass-dev@…
Priority: normal Milestone: 7.2.4
Component: Imagery Version: svn-trunk
Keywords: i.maxlik, group, subgroup Cc:
CPU: Unspecified Platform: Unspecified

Description

i.maxlik adds its output to the input group. This is an interesting feature as it then allows to treat this output together with the input (export the group, reproject, etc). Since it does not add the map to the subgroup, this does not perturb future use of the group with i.maxlik and similar.

However, other modules, most notably i.segment, do not ask for a subgroup, but only a group. And if the user does not pay attention, the output of i.maxlik is then included into the analysis.

I see two possible solutions:

  • impose the use of subgroups in all modules where this is relevant
  • make the inclusion of the output an option in i.maxlik with the default being not to include

Change History (9)

comment:1 in reply to:  description ; Changed 5 years ago by wenzeslaus

Keywords: subgroup added

I would ask for adding description of this and reasons for using subgroups to manuals of the modules which are using them, so that it clear to everybody. Note there was once an idea to remove subgroups as too complicated but perhaps we just miss a better manual and explanations on places where subgroups are used. Perhaps the other reason for removing subgroups was that there is no consensus on how actually knows who to use them.

comment:2 in reply to:  1 Changed 5 years ago by mlennert

Replying to wenzeslaus:

I would ask for adding description of this and reasons for using subgroups to manuals of the modules which are using them, so that it clear to everybody. Note there was once an idea to remove subgroups as too complicated but perhaps we just miss a better manual and explanations on places where subgroups are used. Perhaps the other reason for removing subgroups was that there is no consensus on how actually knows who to use them.

The general idea is that you have certain operations (georeferencing, projection, export, etc) which you want to apply, for example, to all bands of a satellite image, but other operations (classification, etc) only to a limited selection. You can thus have a group that combines all bands and subgroups that you can create for any specific needs.

I like this feature, but there might be a better way to solve this, and thus get rid of subgroups if they are deemed to be more of a nuisance.

Moritz

comment:3 Changed 3 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:4 Changed 3 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:5 Changed 2 years ago by martinl

Milestone: 7.2.17.2.2

comment:6 Changed 2 years ago by neteler

Milestone: 7.2.27.2.3

Ticket retargeted after milestone closed

comment:7 Changed 19 months ago by martinl

Milestone: 7.2.3

Ticket retargeted after milestone closed

comment:8 Changed 19 months ago by martinl

Milestone: 7.2.4

comment:9 Changed 6 months ago by mlennert

Resolution: wontfix
Status: newclosed

I think this is rather a no fix. Maybe one day we will rework the whole logic, but until then, i.maxlik and i.segment users just have to watch out...

Note: See TracTickets for help on using tickets.