[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [geclipse-dev] Parametric Jobs and Workflows
|
Hello!
Stuempert, Mathias IWR pisze:
Just for curiosity, what happens if I add a parametric JSDL as a
workflow job to a workflow?
Sweep-extension will be ignored. Workflow will be submitted as it would
be without parameters.
I’m thinking of the use case where
scientists run the same simulation many times with different input
parameters and afterwards run a job that collects all these results and
calculates the “mean results” (for instance in weather forecast). So
normally such a workflow would consist of many jobs in layer A with
their output ports connected to one job in layer B. Such a workflow
would be hard to set up, thinking about 1000 or more jobs in layer A.
But with a parametric JSDL it would be just one job in layer A.
So any comments on that? Could this be implemented?
Yes - it can be possible to implement parametric workflow.
In this solution, user should define JSDL with parameters and add this
JSDL to the workflow.
Then during workflow submission we can duplicate such JSDL using param
values. Assuming that job A is parametric and job B isn't and both are
connected by link: A -> B, then B should has duplicated input port.
Of course links also should be duplicated.
So we should get something like this: A1 -> B; A2 -> B; A3 -> B ...
In case when both A and B are parametric and connected, we will get
cartesian product:
A1->B1; A1->B2; A1->B2; A2->B2; A3->B1; A3->B2
Whole magic: parametric workflow -> not_parametric, would be done during
submission on client site and would be middleware independent.
All parameters would be defined on JSDL level (not on workflow level).
Generation parametric JSDL -> instantiated JSDLs is already implemented.
What has to be implemented: adding instantiated JSDLs to the workflow
and copying ports/links. So this is part for workflow team.
Workflow + parametric jobs = powerful tool.
But it will be also very complicated to use and understand.
So I would set to this task low priority.
First let both functionalities: workflows and param jobs be more stable.
If this workflow + parametric jobs is desired I can create feature
request in bugzilla.
--
Regards,
Mariusz Wojtysiak
