[geocraft] #939: Algorithm Mapper needs improvement

[geocraft]

#939: Algorithm Mapper needs improvement
---------------------+------------------------------------------------------
Reporter: bob | Owner:
Type: task | Status: new
Priority: major | Milestone: r3a - algorithms
Component: plugin | Version: 1.0
Keywords: | Estimatedhours: 30
Hours: 0 | Billable: 1
Totalhours: 0 |
---------------------+------------------------------------------------------
The algorithm mapper is intended to be used in 2 situations:

1) whenever someone wants a product which is a result of several modules
chained so the output of one becomes the input to the next, but where the
user does not want to save the intermediate data

2) when someone wants test a workflow and visually check results where the
final result is piped directly to the 3D viewer

Presently the algorithm mapper is used in Velocity Flood to allow chaining
several runs together. This works very well except that the chain must be
composed only of Velocity Flood modules. When another non-algorithm
mapper module, like Volume Stretch, is added to the chain, you get the
exception below.

Improvements to the algorithm mapper design that would be helpful are
listed below. These must be implemented so as to have minimal effect on
the current GeoCraft model:

1) change the name "algorithm mapper" to something more meaningful to
users, like workflow or batch builder or batch pipe, etc...

2) if possible, the algorithm mapper should be a workflow builder such
that any module could be included in the flow. However, most modules
would never be used in a batch type of workflow, such as Erase Area,
creating an AOI, Group Multiples, Clip, Decimate, Calculator, Table View,
etc.

3) if someone changes a parameter in one of the modules, like the first in
the chain, the user must go through each remaining module and change the
input and output names and re-run each to get the new result. It would be
a great improvement if the mapper could recognize when a module has been
updated, and then automatically re-run all modules that depend on the
output of this edited module.


!ENTRY org.geocraft.core.common 4 2 2008-08-29 08:30:50.865
!MESSAGE Problems occurred when invoking code from plug-in:
"org.geocraft.core.common".
!STACK 1
org.eclipse.core.runtime.CoreException:
at
org.geocraft.geomath.algorithm.velocity.volumestretch.VolumeStretchTask.convertTraces(VolumeStretchTask.java:131)
at
org.geocraft.geomath.algorithm.velocity.volumestretch.VolumeStretchTask.compute(VolumeStretchTask.java:74)
at
org.geocraft.core.common.progress.SafeTask.run(SafeTask.java:55)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.geocraft.core.common.progress.SafeTask.run(SafeTask.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.geocraft.geomath.algorithm.velocity 4 0 2008-08-29
08:30:50.866

--
Ticket URL: <http://wush.net/trac/geocraft/ticket/939>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Algorithm Mapper needs improvement

-------------------------+--------------------------------------------------

Reporter: bob | Owner:
Type: task | Status: new

Priority: major | Milestone: backlog
Component: plugin | Version: 1.0
Resolution: | Keywords:

Estimatedhours: 30 | Hours: 0
Billable: 1 | Totalhours: 0

-------------------------+--------------------------------------------------
Changes (by mengerw):

* milestone: r3a - algorithms => backlog

--
Ticket URL: <http://wush.net/trac/geocraft/ticket/939#comment:1>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Algorithm Mapper needs redesign
-------------------------+--------------------------------------------------

Reporter: bob | Owner:
Type: task | Status: new

Priority: major | Milestone: backlog
Component: plugin | Version: 1.0

Resolution: | Keywords:

Estimatedhours: 30 | Hours: 0
Billable: 1 | Totalhours: 0

-------------------------+--------------------------------------------------
Changes (by bob):

* summary: Algorithm Mapper needs improvement => Algorithm Mapper needs
redesign

--
Ticket URL: <http://wush.net/trac/geocraft/ticket/939#comment:2>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Algorithm Mapper needs redesign
-------------------------+--------------------------------------------------

Reporter: bob | Owner:
Type: task | Status: new

Priority: major | Milestone: backlog
Component: plugin | Version: 1.0

Resolution: | Keywords:

Estimatedhours: 30 | Hours: 0
Billable: 1 | Totalhours: 0

-------------------------+--------------------------------------------------
Old description:

New description:

The algorithm mapper is intended to be used in 2 situations:

1) whenever someone wants a product which is a result of several modules
chained so the output of one becomes the input to the next, but where the
user does not want to save the intermediate data

2) when someone wants to test a workflow and visually check results where

Ticket URL: <http://wush.net/trac/geocraft/ticket/939#comment:3>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Algorithm Mapper needs redesign

---------------------+------------------------------------------------------
Reporter: bob | Owner:
Type: task | Status: new

Priority: major | Milestone: backlog
Component: plugin | Resolution:

Keywords: | Estimatedhours: 30
Hours: 0 | Billable: 1
Totalhours: 0 |
---------------------+------------------------------------------------------

Old description:

> The algorithm mapper is intended to be used in 2 situations:
>
> 1) whenever someone wants a product which is a result of several modules
> chained so the output of one becomes the input to the next, but where the
> user does not want to save the intermediate data
>

> 2) when someone wants to test a workflow and visually check results where

New description:

'''Summary:''' The algorithm mapper is intended to be used in 2

situations:

1) whenever someone wants a product which is a result of several modules
chained so the output of one becomes the input to the next, but where the
user does not want to save the intermediate data

2) when someone wants to test a workflow and visually check results where

the final result is piped directly to the 3D viewer

Presently the algorithm mapper is used in Velocity Flood to allow chaining
several runs together. This works very well except that the chain must be
composed only of Velocity Flood modules. When another non-algorithm
mapper module, like Volume Stretch, is added to the chain, you get the
exception below.

'''Business Rationale:''' Improvements to the algorithm mapper design that

Ticket URL: <http://wush.net/trac/geocraft/ticket/939#comment:4>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Building workflows needs redesign

---------------------+------------------------------------------------------
Reporter: bob | Owner:
Type: task | Status: new

Priority: major | Milestone: backlog
Component: plugin | Resolution:

Keywords: | Estimatedhours: 30
Hours: 0 | Billable: 1
Totalhours: 0 |
---------------------+------------------------------------------------------

Changes (by bob):

* summary: Algorithm Mapper needs redesign => Building workflows needs
redesign

--
Ticket URL: <http://wush.net/trac/geocraft/ticket/939#comment:5>
geocraft <http://wush.net/trac/geocraft/>

[geocraft]

#939: Building workflows needs redesign

---------------------+------------------------------------------------------
Reporter: bob | Owner:
Type: task | Status: closed
Priority: major | Milestone: backlog
Component: plugin | Resolution: invalid

Keywords: | Estimatedhours: 30
Hours: 0 | Billable: 1
Totalhours: 0 |
---------------------+------------------------------------------------------

Changes (by bob):

* status: new => closed
* resolution: => invalid

--
Ticket URL: <https://wush.net/trac/geocraft/ticket/939#comment:6>
geocraft <http://wush.net/trac/geocraft/>