Re: dynamic wiring
| Newsgroups | gmane.science.robotics.orocos.user |
|---|---|
| Message-ID | <Pine.LNX.4.44.0212131727140.13056-100000@pc067.mech.kuleuven.ac.be> |
On Fri, 13 Dec 2002 [email protected] wrote: [...] > > > Think of components like a mapping component, a path > > > planning component and a motion control component on a mobile platform. > > These correspond to our Observer, Generator and Control components at > > the real-time level. > > Ok, at the level of the Observer, Generator etc. it is exactly the > same level as in SmartSoft. I was first thinking on dynamic wiring at > the level of hot spots ... The hot spots are (by definition) out of the scope of Orocos :-) The programmer of a particular system must provide an implementation of the device-independent API to Orocos. Which isn't fully defined yet... > And I agree, that the "dynamic wiring" in that sense is an important > aspect which is mainly raised by robotics people. It therefore really > might be worth it to call it THE robotics pattern ... > I prefer that people outside of the Orocos group would start calling it like this. Or rather, the "Orocos pattern" for short :-) Herman -- K.U.Leuven, Mechanical Engineering, Robotics Research Group <http://people.mech.kuleuven.ac.be/~bruyninc> Tel: +32 16 322480