Skip to content

Conversation

@philipqueen
Copy link
Collaborator

Based on the request here, this adds documentation of our folder structure and data format. I'm documenting the data in it's current state, but I think this guide will also be useful in deciding which versions of the redundant data we offer that are worth supporting in the future, and identifying potential new data formats that would be helpful

### Data Files
`freemocap_sample_data_frame_name_xyz.npy` is a numpy data array, where the first dimension is the frame number, the second dimension is the keypoint, and the third dimension is the xyz location of the keypoint.

`freemocap_sample_data_by_trajectory.csv` is comma separated values file, where each column is a trajectory of a keypoint in one dimension, and each row is a frame. The first two columns are `timestamp` and `timestamp_by_camera`, giving the timestamps for each frame if they're available. The rest of the columns are the trajectory of each tracked keypoint, split into a column for each xyz dimension. The column names look like `body_nose_x`, `right_forearm_y`, and `full_body_com_z`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does timestamp_by_camera contain? Does it mean that if there are three cameras, this single column contains three timestamps?

@roaldarbol
Copy link

Generally looks really good! Definitely an improvement!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants