The frame number column is still manually specified since I saw it varied between the two types of output I sent in the email. But determining x/y and the associated body part is done through the header information.
I wasn't sure what to do with the scorer row so I ignored it but it would also be simple to merge it into bodypart string or nest the map again and bucket the bodyparts by scorer.
Relevant issue #34
Similar to
load_points_from_csvReturn: map of mapped frames/points, e.g.:
Notes: There's no way in the GUI to use this
The frame number column is still manually specified since I saw it varied between the two types of output I sent in the email. But determining x/y and the associated body part is done through the header information.
I wasn't sure what to do with the scorer row so I ignored it but it would also be simple to merge it into bodypart string or nest the map again and bucket the bodyparts by scorer.