Arisole Fusion brings video, wearable, sensor and telemetry streams into a shared Motion Session, creating one structured context for multimodal movement.
Optical video remains the most accessible human-movement input. Fusion treats video as one source type among several, so a later IMU or wearable stream can sit on the same session instead of living in a disconnected file.
Wearable activity and daily-summary context can join a movement session through the Motion API wearable source type, giving inertial and activity context beside video.
Inertial measurement units report acceleration and angular rate. Those samples can be ingested as sensor sources (CSV or JSON) with optional sample-rate metadata. Fusion does not require a branded IMU SKU to describe this signal class.
Force describes how a body or robot interacts with the environment. Teams can attach force-related channels as sensor or telemetry observations. Availability depends on the capture setup; video alone is not a force plate.
Pressure maps how load is distributed under a foot or contact surface. Pressure is a supported signal class in the multimodal model. StrideIQ video analysis does not claim pressure-sensor precision from pixels.
Multimodal movement means more than one source contributing to the same Motion Session: for example video plus IMU, or robot video plus ROS2 telemetry. Fusion is the product name for that layer. Downstream evaluation still happens in MotionBench or in human reports in StrideIQ.
| Signal class | Typical role | How it enters Arisole |
|---|---|---|
| Video | Visible kinematics | StrideIQ capture or a video Motion Source |
| Wearable | Activity and session context | Wearable source type on a Motion Session |
| IMU | Inertial samples | Sensor source, CSV or JSON ingest |
| Force | Contact and load | Sensor or telemetry observations |
| Pressure | Distributed load | Sensor observations when a pressure stream exists |
| Telemetry | Machine motion | Telemetry source, including ROS2 via ros-bridge |
Arisole Fusion is the multimodal motion layer. It connects cameras, wearables, IMU, force, pressure and telemetry as sources on a shared Motion Session.
Fusion represents video, wearable, IMU, force, pressure and telemetry as source types on a Motion Session. Named device integrations are listed on product pages when they are live.
Motion API exposes sessions, sources and observations. Fusion is the product language for combining those sources. Developers work through authenticated /v1/motion routes.
Loading Arisole. If the interactive app does not start, continue with the public links above.