List view
**Code name**: _I detect, you detect, we detect_. This release will start the development of the analysis module. We would like to provide task event detection algorithm as well as outcome computations.
No due date•0/2 issues closed**Code name**: _Did you say biomechanical models?_ This release will contain THE major feature expected by lots of users: the possibility to compute joint kinematics and kinetics for existing and published marker sets! You will have access to all the objects to model a multi body system (segments, joint, inertial parameters, etc.), as well as different pose estimator (non-optimal, least square) and more!
No due date•2/30 issues closed**Code name**: _Let's introduce raw data processing_. The `processing` module will be proposed for this release. You will have access for example to: - Trim/cut/resize operation on trial; - Reorientation of a trial (e.g modify the vertical axis); - Butterworth filter on `TimeSequence` objects; - GCV filter on `TimeSequence` objects; - _Analog_ data processing (e.g rectification, envelope).
No due date•0/2 issues closed**Code name**: _OpenMA + SWIG = R bindings_. This milestone will provide OpenMA within R. The bindings will provide an API close to the C++ one. A special attention will be taken to provide a behavior identical to a pure R library using native types (e.g. Matrix, List).
No due date**Code name**: _I can do like Biomechanical ToolKit_. At this point, most of the features implemented in BTK will be proposed in OpenMA. Functions to merge and concatenate trials will be provided. All the file formats available in BTK will be integrated in OpenMA.
No due date•1/7 issues closed**Code name**: _OpenMA + SWIG = Matlab bindings_. This milestone will provide OpenMA within Matlab. The bindings will provide an API close to the C++ one. A special attention will be taken to provide a behavior identical to a pure Matlab toolbox using native types (e.g. Matrix, Cell).
No due date•2/3 issues closed**Code name**: _OpenMA + SWIG = Python bindings_. This milestone will provide OpenMA within Python. The bindings will provide an API close to the C++ one. A special attention will be taken to provide a behavior identical to a pure Python package using native types (e.g. list, array, NumPy).
No due date•3/7 issues closed**Code name**: _Let simplify third party integration_. With this version we would like to create a dynamic plugin system to add easily new file formats and new hardwares. The documentation will be adapted in consequence.
No due date•0/1 issues closed**Code name**: _Knock knock, I am ready for a first release_. The goal is to propose a data structure able to represent and store the content of a movement acquisition in a flexible and generic way. For example. Only three major kinds of objects will represent the content of a movement acquisition: - A `ma::Trial` object stores the configuration and all the data acquired. - `ma::TimeSequence`s objects store acquired data (e.g. marker, analog, event, force, pose). - `ma::Hardware` (e.g. force plate) objects store a configuration, knows the associated input data (`ma::TimeSequence` objects) as well as how to generate output results. This structure will be documented and tested against the reading and writing of C3D files.
No due date•6/19 issues closed**Code name**: _What is this Multibody Kinematic Optimization?_. We would like to introduce the possibility to have kinematic constraint on joint (e.g. hinge joint, universal joint, sphere joint, etc.)
No due date•2/4 issues closed