MasterSlave activities and threads

Hi all,

I have been using FBSched for a few days and I have realized that all the slave components are updated serially in FBSched's thread.

I can see no instruction in FBSched's code stating that the slave components should use the master's thread. So I guess code stating that a slave should use the master's thread is inside SetMasterSlaveActivity().

This information is rather crucial but I could not read it anywhere (it is only a guess).

Can anyone confirm? And is there a place I can find more information on this?

PS: from reading old versions' doc it appeared to me that only the task using a SequentialActivity where updated in the same thread (as SequentialActivity does not own a thread of its own)...

Thanks,

Antoine.

MasterSlave activities and threads

A component is not associated to a Thread but to an Activity which may be
driven by a thread.

Typically a periodic activity, a master activity will come with a thread,
but a slave activity does nothing else that providing a public API for the
master activity so that it can be triggered.

2015-08-28 18:34 GMT+02:00 <antoine [dot] rennuit [..] ...>:

> Hi all,
>
> I have been using FBSched for a few days and I have realized that all the
> slave components are updated serially in FBSched's thread.
>
> I can see no instruction in FBSched's code stating that the slave
> components
> should use the master's thread. So I guess code stating that a slave should
> use the master's thread is inside SetMasterSlaveActivity().
>
> This information is rather crucial but I could not read it anywhere (it is
> only a guess).
>
> Can anyone confirm? And is there a place I can find more information on
> this?
>
> PS: from reading old versions' doc it appeared to me that only the task
> using
> a SequentialActivity where updated in the same thread (as
> SequentialActivity
> does not own a thread of its own)...
>
> Thanks,
>
> Antoine.
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>