Implement the joint position tracking application

[GiulioRomualdi]

This PR should be seen as the porting of https://github.com/GiulioRomualdi/joint-position-tracking-test inside the framework

[DanielePucci]

CC @dic-iit/dynamic-interaction-control

[traversaro]

Nitpick: binaries get installed in a shared location (<prefix>/bin) and so they are sensitive to name collisions. For this reason, it could make sense to prepend all the binaries installed by blf with a common prefix.

[GiulioRomualdi]

@traversaro

Nitpick: binaries get installed in a shared location (/bin) and so they are sensitive to name collisions. For this reason, it could make sense to prepend all the binaries installed by blf with a common prefix.

Just to understand the prefix should be in the name of the application? E.g. JointPositionTracking -> BipedalLocomotionJointPositionTracking

[traversaro]

@traversaro

Nitpick: binaries get installed in a shared location (/bin) and so they are sensitive to name collisions. For this reason, it could make sense to prepend all the binaries installed by blf with a common prefix.

Just to understand the prefix should be in the name of the application? E.g. JointPositionTracking -> BipedalLocomotionJointPositionTracking

Yes, that is the strategy used for example by all the git related tools that start with git- . However, feel free to ignore the suggestion, as clearly it render the names longer (unless you use an acronym such as blf- or BLF ) and the actual risk of collision (especially if you use complex names) is not actually so high.

[GiulioRomualdi]

@traversaro

Nitpick: binaries get installed in a shared location (/bin) and so they are sensitive to name collisions. For this reason, it could make sense to prepend all the binaries installed by blf with a common prefix.

Just to understand the prefix should be in the name of the application? E.g. JointPositionTracking -> BipedalLocomotionJointPositionTracking

Yes, that is the strategy used for example by all the git related tools that start with git- . However, feel free to ignore the suggestion, as clearly it render the names longer (unless you use an acronym such as blf- or BLF ) and the actual risk of collision (especially if you use complex names) is not actually so high.

I think that blf-joint-position-tracking is fine. What do you think @traversaro and @S-Dafarra ?

[S-Dafarra]

@traversaro

Nitpick: binaries get installed in a shared location (/bin) and so they are sensitive to name collisions. For this reason, it could make sense to prepend all the binaries installed by blf with a common prefix.

Just to understand the prefix should be in the name of the application? E.g. JointPositionTracking -> BipedalLocomotionJointPositionTracking

Yes, that is the strategy used for example by all the git related tools that start with git- . However, feel free to ignore the suggestion, as clearly it render the names longer (unless you use an acronym such as blf- or BLF ) and the actual risk of collision (especially if you use complex names) is not actually so high.

I think that blf-joint-position-tracking is fine. What do you think @traversaro and @S-Dafarra ?

Like it!

[traversaro]

I also prefer not-camel case commands !

[GiulioRomualdi]

Thanks to 9eaa522 and f173345 the name of the application is blf-joint-position-tracking

[GiulioRomualdi]

Thanks to @traversaro it's now possible to run the script from any folder. Please check c4d4e39. I also updated the README in 16f0c92