Yarp namespace policy

[traversaro]

In IIT Genoa we have the policy of having different yarp namespaces for the iCub robots (icub01, icub02, ..) on the different robots. Is there any policy on yarp namespace for iCub setups outside Genova?

[gsaponaro]

In Lisbon we haven't really thought about that, and I am not aware of any official policy.

We only have one full-body iCub robot with namespace "icub" (it was configured like that when delivered from IIT), and a couple of iCub heads with their own laptop/yarpserver/namespace.

Personally, if I were to decide a policy I would make the namespace coincident with YARP_ROBOT_NAME (if defined) -> one less thing to remember

[pattacini]

is there any particular reason why we need a policy for that?

[lornat75]

We do not have a policy. IIT's robot have different namespaces because at some point in the past I think they shared the same network. This temporary solution got cast in stone :) (as it is often the case)

[myl1ne]

Yep in Barcelona we had the same network for two different yarp setups (XIM & iCub). This is great to avoid conflicts, or if you have "students" doing a hands on....

-----Original Message-----
From: "Lorenzo Natale" [email protected]
Sent: ‎20/‎02/‎2015 21:34
To: "robotology/QA" [email protected]
Subject: Re: [QA] Yarp namespace policy (#16)

We do not have a policy. IIT's robot have different namespaces because at some point in the past I think they shared the same network. This temporary solution got cast in stone :) (as it is often the case)
—
Reply to this email directly or view it on GitHub.

[traversaro]

@pattacini No particular reason, we were just cleaning the setup here in paris and we wanted to streamline the setup as much as possible. Given that there is no convention, we will keep the namespace already in use here, namely to have the namespace coincident with the YARP_ROBOT_NAME, that by chance is the same thing @gsaponaro proposed.