input data content: platformdata

[aremazeilles]

Assuming files in raw_data_input are the files onto which we should launch your algorithm,

It seems that the platformdata file is not complete: the header contains much more entries that each of the lines in the file. Could you double check this?

[aremazeilles]

ping

[simomonte]

Hi Anthony! I am starting to revise the Opened issues to solve these problems. What do you mean about this issue? Raw data are composed in this way:

• Column 1 contains the execution time [s];
• Column 2 contains the pendulum_position [deg];
• Column 3 contains the torque measurements [Nm];
• Column 4 contains the contact force [N];
• Column 5 contains the initial UTC, that is recorded before starting the test;
• Column 6 contains the boolean indicating if the robot resists the impact, and it is recorded as the last value. UTC and boolean columns are not empty, but they are updated once each, so most of the column has no values. The UTC contains a value in position 1, and the fallen-boolean contains a value in position "end". Should we change this? We thought of this structure to avoid adding additional files. Let me know if we have to change it. Best regards, Simone

[aremazeilles]

It seems that UTS_time is set only at the first instant, and then never, fallen is never set in these examples.

For the first one, I think this could be placed in a yaml file, once, as it is not an information that is evolving at each timestamp. For fallen, I can't comment. But I would say this is a minor issue.