moticon-opengo
Moticon-OpenGo is a Python library which makes it easy to work with Moticon OpenGo data.
It improves the productivity of researchers and motion analysts, helping in the phase in between data collection and final outcome assessment.
The library provides functionality both for working with raw data collected using Moticon OpenGo Sensor Insoles, and also the report data generated by the different report modules of the OpenGo Software.
This documentation incluces simple examples, encouraging also less experienced script programmers to go beyond spreadsheet-based data processing.
1. Installation
To install Moticon-OpenGo, run the following command in your Python environment:
pip install moticon-opengo
2. Feature Overview
The Moticon-OpenGo library provides functions for processing the data output of the OpenGo Software.
Text Export Data
Assume we have a bunch of .txt files exported from a .go file using the
OpenGo Software's text export. This library allows you to load and process
these .txt files as demonstrated in the example
examples/demo_text_export_grf_curves.py.
If the measurement contains manually set events, then these events are also
contained in the text export, and made available by the Python library. The
example examples/demo_text_export_events.py shows how this can be used for
convenient slicing of measurement data.
Gait Report Data
Assume we have a bunch of .xlsx files exported using the OpenGo Software's
gait report. This library allows you to load and process these files as
demonstrated in the example examples/demo_gait_report.py.
3. Library Development
This section is for contributors who want to adapt/extend the Moticon-OpenGo library. If you only want to make use of Moticon-OpenGo as-is for processing your sensor insole data, then you can skip this section.
Build
For development, install Moticon-OpenGo as follows:
pip install -e ."[test,dev]"
Testing
To run the tests, make sure you have the package installed with test extra
(see section "Build" above). Run the tests as follows:
pytest
Metadata
Release files for moticon-opengo 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| moticon_opengo-1.0.3.tar.gz | 940.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moticon_opengo-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 961.5 kB
Release files / moticon_opengo-1.0.3.tar.gz
| Download URL | moticon_opengo-1.0.3.tar.gz |
|---|---|
| Size | 940.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35ae14bbe79d9512967a098f1d07fbcadbf433fe3b4c0fae77e11e4bad828dbe
|
|
BLAKE2b-256 checksum How to use checksums |
8846dbe981d90a72bf746af7416c891c636627e980398846c18806ac82b79482
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.1
|
Release files / moticon_opengo-1.0.3-py3-none-any.whl
| Download URL | moticon_opengo-1.0.3-py3-none-any.whl |
|---|---|
| Size | 20.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b94f5d1cea55d6aef903a036e2fb376e460c376eca82cdfa1949b65a849e306f
|
|
BLAKE2b-256 checksum How to use checksums |
f49e336243c508ddbfe8ee03b1081851e28aeb546c1c5093b0f34ca1dc26d6de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.1
|
Security for moticon-opengo 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.