robotInterface and robot-specific files within app/robots/$YARP_ROBOT_NAME

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

robotInterface and robot-specific files within app/robots/$YARP_ROBOT_NAME

Giovanni Saponaro-2
Dear Hackers,

We are just getting to know the robotInterface program and relevant
configuration files, distributed in a number of subdirectories inside
our $YARP_ROBOT_NAME dir: namely calibrators/, cartesian/, hardware/
and /wrappers.

The following question has to do with personal organization of files,
aesthetics and best practices, but here goes anyway:

In the past (iCubInterface), we used to store our .ini files inside
conf/, and .xml files inside scripts/, both subdirs being inside
$YARP_ROBOT_NAME.

Now with the new structure, do you have any suggestion or guideline
regarding where to commit our .ini and .xml files? I.e., should we put
them all in icub-main/app/robots/iCubLisboa01 directly (that seems to
be the case for iCubGenova*, but wouldn't it quickly create a messy
directory as the number of files increases?) or shall we create
subdirectories with a name of our choice?

Sorry if it's a futile discussion :), just want to follow good
practices following the deployment of robotInterface on our robot.

Thanks,
-Giovanni

------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Robotcub-hackers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/robotcub-hackers
Reply | Threaded
Open this post in threaded view
|

Re: robotInterface and robot-specific files within app/robots/$YARP_ROBOT_NAME

pattacini
Hi Giovanni,

Given the current ResourceFinder strategy, I think the following applies.

The "shadowing mechanism" lets any module load automatically a file from the robot directory instead of its own context directory: that's useful for those files containing robot specific options. Thus, to make this mechanism work and to keep the module agnostic about the actual place from where the file is loaded (either from context or from robot dir), you must ensure that configuration files stored in the robot directory will be copied into the $YARP_ROBOT_NAME context at cmake time.

To recap: whatever branching hierarchy you choose under main/app/robots/iCubLisboa01, make sure that in the CMakeLists.txt you put the correct directives to copy your files into $YARP_ROBOT_NAME (i.e. without any branching therein).

Ciao,
Ugo

> -----Original Message-----
> From: Giovanni Saponaro [mailto:[hidden email]]
> Sent: 29 September 2014 20:26
> To: RobotCub Mailinglist
> Subject: [rc-hackers] robotInterface and robot-specific files within
> app/robots/$YARP_ROBOT_NAME
>
> Dear Hackers,
>
> We are just getting to know the robotInterface program and relevant
> configuration files, distributed in a number of subdirectories inside our
> $YARP_ROBOT_NAME dir: namely calibrators/, cartesian/, hardware/ and
> /wrappers.
>
> The following question has to do with personal organization of files,
> aesthetics and best practices, but here goes anyway:
>
> In the past (iCubInterface), we used to store our .ini files inside conf/,
> and .xml files inside scripts/, both subdirs being inside $YARP_ROBOT_NAME.
>
> Now with the new structure, do you have any suggestion or guideline regarding
> where to commit our .ini and .xml files? I.e., should we put them all in
> icub-main/app/robots/iCubLisboa01 directly (that seems to be the case for
> iCubGenova*, but wouldn't it quickly create a messy directory as the number
> of files increases?) or shall we create subdirectories with a name of our
> choice?
>
> Sorry if it's a futile discussion :), just want to follow good practices
> following the deployment of robotInterface on our robot.
>
> Thanks,
> -Giovanni
>
> -----------------------------------------------------------------------------
> -
> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> Robotcub-hackers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/robotcub-hackers

------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Robotcub-hackers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/robotcub-hackers