beakerboy / betamove Goto Github PK

Construct a BetaMove object from the process_data() output.

if the data is required by the src files, it needs to be in src.

Abstract the holds to the moonboard hold ID. The moonboard will be a table of holds, their position and orientations. each hold would track its own difficulty and feature data.

Read the code to understand what they are for.

ideally, each hold would have some sort of geometric information, so that when it is rotated for different hold setups, the data could be similarly rotated. Left and right hand difficulty is tricky without considering body position and direction of movement. Gaston versus side pulls for example, use different parts of a hold with the same hand.

This function is basically a classmethod. Move it to Climb, or make it static.

Currently a hold is removed from the list of available holds once used. This means a hold can never be matched with both hands.

This may require some "state check" to see if any combination of two hands has been performed before in the sequence, as well as a modification to the difficulty when evaluating if a match is possible.

instead of having information on each x-y position, assign metadata to each hold, then assign a hold to a location in the moonboard object. The moonboard would be a table combining hold, location, and orientation.

Create a movement sequence array, each element is a tuple of a hold and a hand. this would reduce the number of indexes being passed around.

The new API includes left, right, and foot designations.