#9 Rethink of Pipeline Scheme

[Cinly Ooi]

originally, pipeline schemes are envisaged for
shortcircuiting portion of pipeline which is not
necessary to repeat. The following limitations to the
present system were discovered:

(1)There is no way to separate out pipeline schemes
applying to individual job, i.e., "Pipeline Scheme"
column in input table spreadhsheet, and that meant for
modules that cannot be assigned to individual job, i.e.
control by Run/Launch Dialog.

(2)The compulsary items for the Pipeline Scheme column
of input table spreadsheet, and Pipeline Scheme in
Run/Launch dialog, e.g. RUN_ALL_SCHEME needs cannot be
renamed, and this leads to difficulty in finding an
appropriate name that works across all pipelines.

(3)Whether the provision of these compulsary items are
meaningful. For example, in case of no pipeline scheme
define, is it useful to have JobScheme in Run/Launch
Dialog that ask them whether "RUN_ALL_SCHEME" or
"SKIP_ALL_SCHEME" should be use. In this case, is
disabling Pipeline Scheme for Run/Launch" dialog and
insist on providing only "RUN_ALL_SCHEME" the correct path?

Furthermore,
(a)there is a proposal from Alle-Meije to use pipeline
schemes to "accept" data processed elsewhere and need
not go through certain (earlier) stages. Can this be
merged into pipeline schemes which seems to be a
natural place to hold these information?

Proposed Solutions:
For (1), add a new attributes to jobScheme XML that
allows choosing between "Pipeline Scheme" on input
table spreadsheet and Run/Launch Dialog.

For (2), How about this system: The compulsary items
are linked to RUN_ALL_SCHEME and SKIP_ALL_SCHEME. These
will be provided by default with a default name IF
there is no pipeline scheme proposed. However, if there
are pipeline schemes defined, then users take over
responsibility to define them. The advantage of this
approach, besides solving the problem, is that users
can decide to provide RUN_ALL_SCHEME or SKIP_ALL_SCHEME
as well.

Also filed at CamBA:

http://sourceforge.net/tracker/index.php?func=detail&aid=1546155&group_id=161344&atid=819462

[Cinly Ooi]

Logged In: YES
user_id=783811
Originator: YES

Solution (2) adopted. All problems solved.

Problem (1): added a "group" attribute to differentiate between Individual modules and Group
Problem (2) and (3) solved by Solution (2)

However, solution (1) is still under investigation