Determine Capture Device Requirements

[sombrero-de-lluvia]

What are my requirements for the device that will capture the data?

[sombrero-de-lluvia]

• Small
• Light
• Visually unobtrusive
• Accurate

[sombrero-de-lluvia]

Likely will be a smartwatch. Need to research options.

[sombrero-de-lluvia]

Continued research.

[sombrero-de-lluvia]

Device will use WearOS, WatchOS, or TizenOS.

GitHub has repositories for related apps.

• WearOS: https://github.com/estherjk/AndroidWearMotionSensors
• WatchOS: https://github.com/degtiarev/MotionCollector/tree/master
• TizenOS:
  • https://github.com/v-datnvt2/Tizen-Accelerometer-Gyroscope-Application
  • https://github.com/genyrosk/TizenAccelerometerApp

TizenOS repos look the same, but posted 4 years apart, and may have some updates? Tizen option gets 10ms sampling rate, and would be least expensive intro option.

NEXT

Assess Tizen repos.

• How to compare two repos?
• How to select a repo?

Will probably need to fork.

[sombrero-de-lluvia]

Comparing Repos

Will use git diff. Learning to use.

• https://stackoverflow.com/questions/27508982/interpreting-git-diff-output
• https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/diffs

Using branches. Branch documentation:

• https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell
• https://git-scm.com/docs/git-branch

NEXT

Read "how to interpret" documents while using the gitreadtest file in the bow-arm-visualization repo.

[sombrero-de-lluvia]

Results:

diff isn't designed to be conveniently human-readable. I can try diffing the two repos, or maybe files in the repos, but before going too far down that rabbit hole, I should look for other strategies for comparing repos.

NEXT

• double check for a more convenient, human-readable way to diff repos.
  • check for a way to make diff human-readable.

[sombrero-de-lluvia]

Human-Readable Diff

this post suggested github.com's diff viewer.

1. create branch.
2. edit branch.
3. create pull request.
4. review diff in pull request online.

NEXT

1. Create new repo (read tizen watch sensor data) (clone from original tizen repo)
2. Create diffbranch (pull from newer repo)
3. Pull request diffbranch into main.
4. Review diffs.

[sombrero-de-lluvia]

Reviewed some of the commits in the newer repo. Looks like the author used ninja to build smalltalk files that replaced a lot of the pure C files from the original author. A Samsung Galaxy S2 Active runs about $80, and this app only works on significantly out of date devices.

NEXT

Determine whether a "sensor logger" exists for WEAR OS, as that's a more consistent and test-able solution.

Check reddit & play store to start.

[sombrero-de-lluvia]

Found WearOS repo: https://github.com/Dhruv-Verma/SensorLoggerWearOS/tree/main

NEXT

• Keep searching for WearOS options.
• Find WearOS watch to purchase.

[sombrero-de-lluvia]

Found repo that can be used for sensor data collection. Not referenced by WearOS app

• https://github.com/GeoTecINIT/WearOSSensors

Found some other repo

• https://github.com/Steppschuh/Sensor-Data-Logger

Buy WearOS watch from https://swappa.com/buy/smartwatch/android

NEXT

Pick a watch

[sombrero-de-lluvia]

Bought watch!

NEXT

Capture Data(?)