[kepler-dev] Kepler 2.0.0 and director development

[Colin Enticott]

Hi Edward,

Yes, I am using an unmodified Ramp actor. The postfire method calls
update() and then adds getToken() to the current output token for the
next fire call. My best guess is getToken() is returning a nil/null or
a number token of value 0. I have tried setting the step value to
something else and also passed in a value to the port with no change.

Regards,
Colin

On 24 June 2010 21:50, Edward A. Lee <eal at eecs.berkeley.edu> wrote:
>
> Are you calling update() on the PortParameter in your fire() method?
>
> Edward
>
>
> On 6/24/10 1:56 AM, Colin Enticott wrote:
>>
>> Hi,
>>
>> I've finally started to test the Nimrod/K director with Keper 2.0 and
>> besides some small changes in the Ptolemy API with method definitions
>> and workflow locks, I've been able to get it mostly working. The
>> problem that I am seeing now is that ParameterPort's getToken()
>> doesn't return the correct value. It works under the other directors
>> and it also works with the Nimrod/K director under Kepler 1.0. For
>> example, two actors, Ramp and Display with the Ramp actor set to
>> iterate 5 times will show 0,1,2,3,4. Under Nimrod/K, it shows
>> 0,0,0,0,0. Another possible symptom is the Display actor will not show
>> its name in the title bar with Nimrod/K. I've checked that I am call
>> preinitialize and initialize before firing the actors, but this has me
>> confused. Has there been any changes with the environment that
>> requires changes to a director? If not, is there something else common
>> between these two symptoms? And if not, then they could be two
>> unrelated issues. :-(
>>
>> Thanks,
>> Colin
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>



-- 
Colin