Anthropomorphic, humanoid and testbed file class

[aremazeilles]

from Nevio:

I am not sure if this file, the "Humanoid anthropometric measures" file and the "Testbed-related data" file should be included in the "Pre-Processed Data Files" class or in a different class of files.

[aremazeilles]

ping @alfonsotecnalia @flxalr @DavidPintoFernandez @alfonsotecnalia

I think Nevio remarks is very relevant: it might be good making distinction in between these different types of file. We would thus have:

• bipedal system specification: we are targetting the use of urdf file for describing any robotic system, and also human subjects
• testbed configuration: that could be related to the controlled variables defined in the protocol sheet. I assume yaml structure could be used for such configuration information. Also, this file can be common for all experimental run, but also, in other case, associated to a subset of runs.
• Pre-processed data: data captured during the experimentation. Mainly by sensors, but not necessarily only. I think such files are all likely to be timestamped.

Would this make sense to you?

[DavidPintoFernandez]

I agree. I also see that bipedal system's specifications and testbed's configuration could be the same for different experiments and runs, but as I see, pre-processed data has to be different in all runs, it makes sense to not include all in the same group.

[aremazeilles]

The other, does this dinstinction bipedal system, testbed configuration and pre-processed data makes sense? If yes, I would then split the documentation into these 3 (new) subsections.

[flxalr]

I agree with the proposed separation of file types. In fact, we are currently implementing it exactly as you described it, @aremazeilles.

[aremazeilles]

Ok, perfect. I will work on that as soon as I can

[aremazeilles]

You can have a look at #33.