Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export real-time data into convenient format #14

Closed
pattacini opened this issue Mar 30, 2018 · 2 comments
Closed

Export real-time data into convenient format #14

pattacini opened this issue Mar 30, 2018 · 2 comments
Assignees
Labels
🚀 enhancement New feature or request

Comments

@pattacini
Copy link
Member

For enabling offline reporting of the experiments, it is required to export data acquired in real-time into formats that are general enough for ensuring an appropriate level of post-processing.

We would like to go with https://github.com/tbeu/matio, which guarantees to produce files that are in turn MATLAB/Octave compatible.

@pattacini pattacini added the 🚀 enhancement New feature or request label Mar 30, 2018
@pattacini pattacini added this to the Demo Y1M5 milestone Mar 30, 2018
This was referenced Mar 30, 2018
@vvasco
Copy link

vvasco commented Apr 10, 2018

The class Manager uses matio to produce a file where data are appended at every "session". The final file is saved in the context directory defined by the ResourceFinder.
Currently, a session is defined as 5 seconds session, but the sequencer (#5) will define it.

Exported data are in the following format:

  • Keypoints is a Nx1 struct (N = number of sessions), containing raw data.
    The struct contains 14 fields. Each field has a name corresponding to a keypoint and for each session contains a matrix nx3 (n = time sample) in the following format:
[x1, y1, z1; 
 x2, y2, z2; 
... 
 xn, yn, zn]
  • Time_samples is a nx1 vector containing the time samples at which the keypoints are received
  • Metric name (for example ROM_0) is a Nx1 struct, containing tstart and tend, which indicate the start and the end of a single session, and the following information from the motion repertoire (which might change depending on the metric):
    • ref_joint: reference joint for the considered metric
    • ref_direction: reference direction for the considered metric
    • ref_plane: plane on which the metric has to be evaluated
    • max: max value for the considered metric
    • min: min value for the considered metric

@pattacini
Copy link
Member Author

Very nicely done @vvasco 🏅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants