[kepler-dev] 1st and 2nd run of the same workflow give different outputs

[Edward A. Lee]

This is how PortParameter works.

When an input arrives on the port during a run, its value
is stored in the corresponding parameter, overwriting the
previous value. Thus, by the end of the run, there is no
longer any record of the initial value.

It is arguable whether it should actually work this way,
but the fact is, this is how it works.

Edward


On 4/16/10 10:34 AM, Gongjing Cao wrote:
> Hi,
>
> I came to an interesting workflow when I try to use PortParameter. It
> generates different outputs at the 1st run and the 2nd (and after) run.
>
> Seems the PortParameter only take the default value in the 1st run,
> instead of taking the value which is passed from the previous actor.
>
> Does anybody know why? How can I let this workflow always give the right
> output as in 2nd run.
>
> Thanks!
>
> Gongjing
>
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eal.vcf
Type: text/x-vcard
Size: 351 bytes
Desc: not available
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100416/953df538/attachment.vcf>