[Rock-dev] Syskit Feedback
Chris Mueller
christoph.mueller at dfki.de
Tue Mar 19 17:06:35 CET 2013
Am 19.03.2013 16:43, schrieb Sylvain Joyeux:
> On 03/19/2013 04:10 PM, Chris Mueller wrote: def intialize(*arguments)
>> super
>> depends_on(..., :role => 'orientation')
>> end
> You mean that the scripting block that you have defined works on
> Roby::Task but not on compositions ?
Exactly.
>> 3) DataService are not shadowing the actual task in this szenario.
>>
>> # profile ...
>> use Base::Motion2DControlledSystemSrv => aria_dev
>>
>> class ConstantMovement < Syskit::Composition
>> add Base::Motion2DControlledSystemSrv, :as => 'system'
>>
>> on :start do |ev|
>> puts "#{system_child}" ==> returns the concrete Task (in my
>> case Aria::Task)
>> system_child.command_in_port => throws an error because the
>> port command_in does not exists in Aria::Task
>> end
>> end
> This is "intended". There are issues with both options, and I am
> personally not really sure which one is best. Needs more discussions.
Is there any option to reference in this case to the model? e.g.
system_child.model ? (for having a uniform port_interface)
More information about the Rock-dev
mailing list