NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #485 (new enhancement)

Opened 2011-05-03T10:51:03-05:00

Last modified 2013-01-23T09:42:36-06:00

Apply Plugin Operation to Stack

Reported by: gharris Owned by: curtis
Priority: major Milestone: imagej2-unscheduled
Component: Core Version:
Severity: major Keywords:
Cc: Blocked By:
Blocking: #1632

Description (last modified by gharris)

  • Add an option to the input dialog to apply operation to stack
  • Decide how to declare or decide is an operation can be applied to a stack?
  • May need to be able to designate what dimensions to apply it to.

Change History

comment:1 Changed 2011-05-03T12:19:17-05:00 by gharris

  • Description modified

comment:2 Changed 2011-05-03T14:13:48-05:00 by gharris

May need to be able to designate what dimensions to apply it to.

comment:3 Changed 2011-05-03T14:20:59-05:00 by gharris

  • Description modified
  • Summary changed from Stack Operations to Apply Plugin Operation to Stack

comment:4 Changed 2011-05-23T10:23:48-05:00 by curtis

  • Milestone changed from biweekly-2011: May-09 to May-20 to imagej-2.0-beta1

comment:5 Changed 2011-10-18T15:19:19-05:00 by curtis

  • Milestone changed from imagej-2.0-beta1 to imagej-2.0-beta3

comment:6 Changed 2012-07-19T21:47:05-05:00 by dscho

  • Blocking 1333 added

comment:7 Changed 2012-09-07T11:21:45-05:00 by bdezonia

  • Blocking 1460 added; 1333 removed
  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5

comment:8 Changed 2012-09-10T15:30:01-05:00 by bdezonia

Is this something we want to do? Maybe I'm misunderstanding what the ticket represents. I say this is not an issue. Can I get some clarification?

comment:9 Changed 2012-09-10T17:20:59-05:00 by dscho

It looks like Process>Batch>Macro... to me, except that it would take a plugin instead of a macro to apply to the stack.

However, this is not very precise. A more precise description would probably be something like this: provide a meta-plugin that can iterate along one or more axes and execute *another* plugin on the sub-stack (view) at each step. It would make it possible, for example, to blur a multi-channel image without blurring between channels (but instead blurring all channels individually).

I disagree however that this should be part of the input dialog.

comment:10 Changed 2013-01-23T09:42:36-06:00 by bdezonia

  • Blocking 1632 added; 1460 removed
  • Milestone changed from imagej2-b7-ndim-data to imagej2-unscheduled