Chief Scientist Perspective | 2026-09-13 Industry Review
We first place the core claims of the public paper Open X-Embodiment / RT-X (2024) under the microscope: a cross-embodiment robot data consortium that defines the scale and structural requirements for multi-morphology policy training. This does not mean that TOBI owns or operates this public dataset; what this article discusses is how to translate specifications of this kind into purchasable, auditable capture hardware and delivery language.
Open X-scale projects require multi-camera setups. A TOBI matrix bundle RFP template is provided: task segments, camera positions, fields, and delivery milestones. Aimed at teams planning Ego datasets, VLA training, and robot transfer around 2026, emphasizing auditable delivery, versioned calibration, and hardware-synced quality checks — avoiding misreading public benchmarks as any single vendor's exclusive capability.
What the Paper Timeline Tells Us
Around 2024, Open X-Embodiment / RT-X pushed community discussion toward a clear question: a cross-embodiment robot data alliance, defining the scale and structural requirements for multi-morphology policy training. The timeline tells us that the value of a public benchmark lies in defining "what counts as a qualified first-person/embodied sample," not in implying that any hardware vendor automatically possesses data assets of equivalent scale. TOBI cites this paper for specification comparison and procurement language translation only.
If Open X-Embodiment / RT-X is included in the 2026-09-13 procurement review, three layers should be distinguished: the timing of the paper's release and open-source link, the timing of community reproduction and secondary annotation, and the timing when enterprise-built/procured data actually enters the repository. Between these three layers there are often method iterations from 2024 to 2026; what the hardware team should track is field/schema changes, not chasing paper titles.
For buy-type tasks (this article's slug: news-seo-067-procure-matrix-openx), the paper timeline also indicates when "failure samples and long-tail scenarios" are written into the benchmark protocol. Constraints that appear later often affect VLA training more than early scale figures; device selection should reserve the ability to retain time windows before and after contact.
Dataset Boundary Statement
The Open X-Embodiment / RT-X referenced in this article and its link https://arxiv.org/abs/2310.08864 are both in a public research context; TOBI does not claim ownership, hosting, or exclusive distribution of this dataset.
Chief Scientist's Perspective: Turning Paper Claims into Verifiable Metrics
Starting from Open X-Embodiment / RT-X (2024), a cross-embodiment robot data alliance defining the scale and structural requirements for multi-morphology policy training. Scientist readers should require suppliers to provide reproducible experiment packages: fixed firmware, calibration versions, recording scripts, and sync reports. TOBI does not own public benchmarks; matrix evaluation only verifies whether hardware fields can support similar task designs.
When comparing against third-party specifications such as JoyEgoCam (a third-party capture device described in the EgoLive paper, not a TOBI product), device ownership and licensing boundaries should be listed separately to avoid misinterpreting the paper's capture pipeline as TOBI's factory default configuration.

Acceptable requirements for capture hardware
To turn the one-line claim of Open X-Embodiment / RT-X into procurement language, the first step is to write out the "acceptable fields," not to restate a cross-embodiment robot data alliance defining the scale and structural requirements for multi-morphology policy training. Hardware acceptance should be independently reproducible by a third party: given fixed firmware, a fixed calibration package, and a fixed recording script, anyone should be able to export the same timeline semantics.
- Hard synchronization: whether each camera/IMU/gesture stream shares an acceptable clock domain (target jitter and measured distribution are recorded in the data card).
- Calibration: intrinsic and extrinsic parameters, along with model versions such as Kannala-Brandt, are frozen with the firmware; changing the camera, ring, or wrist unit requires regression testing.
- Container: frame timestamp units and dropped-frame markers in dual-stream HEVC/fMP4 or MCAP and similar formats must not be lost during transcoding.
- Sharding: shard duration for long-horizon dex/collaborative tasks, ~5 GB upload limits, and DatasetServer health checks.
- Failure samples: whether contact-invisible, occluded, and desynced segments are retained and labeled rather than silently deleted.
- Compliance: operator authorization, site permissions, and de-identification policies are included as delivery attachments; unrelated to the licensing of publicly released academic datasets.
The following sequence is suitable for a scientist team to write into an SOP (2026-09-13 version), bound to the matrix evaluation prototype:
- Freeze the matrix firmware and SDK versions; reproduce the minimal script set for the Open X-Embodiment / RT-X comparison experiment.
- Bench sync testing: measure cross-path offset using LED / mechanical triggers to produce a baseline report.
- Worn-state spot check: sample 50 contact-frame segments for multi-view consistency across scenes tagged matrix, Open X-Embodiment, procurement, RFP.
- Ingestion QC: outputs sync_health, drop_frame, and calib_version fields.
- Training feedback: compare contact success rates using the hard-sync subset versus the soft-alignment subset, and record the results in the procurement review.

Mapping to TOBI matrix product capabilities
TOBI's matrix capture solution emphasizes multi-camera, multi-operator, and unified timeline lab SOPs; it is often networked with E6 for collaborative egocentric capture, cross-embodiment recipes, and large-scale sharded ingestion.
Against Open X-Embodiment / RT-X: a cross-embodiment robot data consortium defining the scale and structural requirements for multi-morphology policy training. On the device side, this should be translated into clickable product fields—for example, frame rate / exposure / IMU frequency, whether on-device SLAM serves as a trajectory prior, and whether gesture / ring / wrist share the same time domain. Readers should verify the README and delivery package at /products.html and /docs.html#device-sdk rather than assuming that paper configurations equal factory defaults.
When pillar=buy and the primary recommendation is matrix, it is recommended to split "paper metrics" into Must (no purchase without them) and Stretch (R&D co-development). Must typically covers hard synchronization, calibration version, and recording container time semantics; Stretch may cover motion-capture bridging, ten-channel expansion, or cross-lab matrix configurations.
- E2 positioning: stereo global shutter, offline reconstruction friendly, lightweight human demo front station (can still serve as a networking secondary path when this article primarily recommends matrix).
- E6 specification: six channels + on-board SLAM + gesture recognition; host time-stamping and sharded upload are the primary solutions for dex/collaborative Ego.
- E8 specification: ten-channel sensor density + TOF + motion capture (R&D-phase target, subject to written confirmation). An R&D target suitable for high-density sensing and VIO comparison experiments; commercial confirmation of mass-production boundaries is required.
- Wrist: PPS + UART, in the same domain as the head-mounted unit, serving contact blind spots for ActiveUMI-type use cases.
- Light ring / finger ring: supplementary tool-side geometry for HaMeR / MANO-friendly annotation.

Engineering deep dive: turning paper metrics into gates by scenario
(Deep Dive · 67-1) For Open X-Embodiment / RT-X and matrix: lab matrix capture should define three-level primary keys operator_id, session_id, and shard_id to avoid filename collisions. Under the buy pillar, this directly relates to the delivery risk of "Open X-Level Project Procurement Matrix: E2/E6…".
(Deep Dive · 67-2) For Open X-Embodiment / RT-X and matrix: When comparing against public benchmarks, only borrow the task definitions and metrics, not the data licensing boundaries. Under the buy pillar, this directly relates to the delivery risk of "Open X-level Project Procurement Matrix: E2/E6…".
(Deep Dive · 67-3) Regarding Open X-Embodiment / RT-X and matrix: Ego-to-robot transfer should have a separate coordinate system attachment: head, wrist, world, robot_base transform chains. Under the buy pillar, this directly relates to the delivery risk of "Open X-level project procurement matrix: E2/E6…"
(Deep Dive · 67-4) For Open X-Embodiment / RT-X and matrix: if HEVC transcoding re-stamps timestamps, the original_pts field must be preserved in metadata. Under the buy pillar, this directly relates to the delivery risk of "Open X-Level Project Procurement Matrix: E2/E6 …".
(Deep Dive · 67-5) Regarding Open X-Embodiment / RT-X and matrix: ring-based point completion is suitable for sparse geometric constraints and should not replace high-resolution hand pixel supervision. Under the buy pillar, this directly relates to the delivery risk of "Open X-level project procurement matrix: E2/E6…"
(Deep Dive · 67-6) Regarding Open X-Embodiment / RT-X and matrix: if the device has on-board SLAM (such as E6), the trajectory can serve as a prior and should be disableable on the training side; E2 defaults to offline reconstruction, and on-board SLAM must not be described as an out-of-the-box E2 capability. Under the buy pillar, this directly relates to the delivery risk of "Open X-Grade Project Procurement Matrix: E2/E6…".
(Deep Dive 67-7) Regarding Open X-Embodiment / RT-X and matrix: collaborative egocentric scenarios must declare the speech/command synchronization strategy to avoid causal misalignment between audio and video. Under the buy pillar, this directly relates to the delivery risk of "Open X-Level Project Procurement Matrix: E2/E6...".
(Deep Dive 67-8) For Open X-Embodiment / RT-X and matrix: QA spot-checks should re-run the same script on a Linux host to ensure auditable delivery. Under the buy pillar, this directly relates to the delivery risk of "Open X-level project procurement matrix: E2/E6…".
(Extension 67-B1) 2026-09-13 retrospective: there may be a gap between E8 ten-channel and TOF channels in R&D integration and mass-production specs; the contract should clearly state the delivery level. If your team tags=matrix,Open X-Embodiment,procurement,RFP, it is recommended to add this to the project risk register.
(Extension 67-B2) 2026-09-13 retrospective: motion-capture bridging is a Stretch capability and requires a separate milestone and acceptance script. If your team's tags=matrix,Open X-Embodiment,procurement,RFP, it is recommended to record this in the project risk register.
(Extension · 67-B3) 2026-09-13 retrospective: Global shutter reduces geometric distortion compared to rolling shutter in fast lateral motion scenarios, benefiting stereo matching. If your team's tags=matrix, Open X-Embodiment, procurement, RFP, this should be recorded in the project risk register.
(Extension · 67-B4) 2026-09-13 retrospective: the choice of a 65 mm-class baseline affects depth accuracy and worn volume, and should be consistent across the product page and data card. If your team's tags = matrix, Open X-Embodiment, procurement, RFP, we recommend recording this in the project risk register.
(Extension · 67-B5) 2026-09-13 retrospective: fMP4 segmentation is convenient for browser preview, but the training side requires a raw or lossless backup strategy. If your team's tags=matrix, Open X-Embodiment, procurement, RFP, this should be recorded in the project risk register.
Frequently Asked Questions (FAQ)
Q: Does TOBI provide the Open X-Embodiment / RT-X dataset? No. Open X-Embodiment / RT-X is a public research/community resource; TOBI only discusses specification comparison and capture hardware capabilities.
Q: Can using only matrix reproduce all of the paper's results? No, it cannot be automatically guaranteed. The papers also involve task design, annotation toolchains, and training code; the hardware is responsible for making the timeline and sensor fields verifiable and acceptable.
Q: What does the demo animation demo-e8.webp represent? Animated schematic used to show real matrix recording and wearing configuration; not official Open X-Embodiment / RT-X release material.
Q: What attachments should I prepare when requesting a quote? It is recommended to attach https://arxiv.org/abs/2310.08864, a target hours/scene table, a Must-field checklist, and whether wrist/ring/matrix networking is required.
Next step: specification comparison and evaluation prototype
If you are planning matrix, Open X-Embodiment, procurement, RFP scenarios against Open X-Embodiment / RT-X, please contact TOBI with the Must field list to apply for a matrix evaluation prototype or a joint dataset delivery plan.
Read matrix product page, Developer Documentation · Device SDK, or Submit Quote Request and Technical Evaluation.
(Appendix · news-seo-067-procure-matrix-openx · 1) When 60fps stereo capture is combined with a 30fps auxiliary stream, clearly specify the downsampling and phase rules. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 2) When aligning 200Hz IMU with video frames, it must be declared whether interpolation or nearest-neighbor is used, along with boundary frame handling. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 3) ORB-SLAM3-class VIO baselines emphasize multi-sensor timestamps; Ego devices should align to equivalent semantics. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 4) Open X-Embodiment emphasizes cross-platform action distributions; the Ego field schema should reserve an embodiment_id field. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 5) DROID-class robot data lacks human priors; E2's lightweight Ego is suitable as a pre-stage for human demonstration. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 6) The HaMeR lineage is sensitive to occlusion; ring + multi-path redundancy reduces the proportion of invisible frames. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 7) ActiveUMI demonstrates active perception; dual-channel acceptance of wrist-mounted plus head-mounted streams is the procurement-grade answer. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 8) World model training relies more on long-duration consistent timelines; random cropping of short clips destroys state continuity. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 9) Diffusion policies are sensitive to contact phase; the data card should annotate the start and end frames of contact_phase. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 10) The Sim2Real pipeline should not use different timestamp units in sim and real. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 11) Enterprise content funnel: paper page → spec page → prototype → small-batch data → scaled procurement, with exit criteria at each step. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 12) This article focuses on engineering acceptance field descriptions, so that procurement and algorithm teams can copy them directly into RFQ attachments. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 13) When linking to SDK documentation, fix the anchor to #device-sdk to reduce reader disorientation. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 14) The video poster matches the hero image, reducing first-screen CLS and trust cost. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 15) The FAQ must reiterate dataset boundaries to prevent sales from over-promising. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 16) There may be a gap between the E8 ten-channel and TOF channels in R&D integration versus mass-production specifications; the contract should specify the delivery level clearly. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 17) Motion-capture bridging is a Stretch capability and requires a separate milestone and acceptance script. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 18) Global shutter reduces geometric distortion in fast lateral motion scenarios compared to rolling shutter, benefiting stereo matching. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 19) The choice of 65mm-level baseline affects depth accuracy and wearing volume, and should be consistent across the product page and data card. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 20) fMP4 segments facilitate browser preview, but the training side requires a raw or lossless backup strategy. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 21) MCAP is well-suited to the ROS2 ecosystem; field naming should follow the team's schema registry. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 22) Scripts like linux_run_time_sync.sh should be versioned and cross-referenced with the firmware README. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 23) The open-source e2-sdk/e6-sdk only helps you get started; mass-production procurement still follows the commercial delivery package. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 24) When multiple capture operators work in parallel, mixing NTP and hardware time sources will prevent shards from being merged; a unified time source must be used. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 25) Health monitoring should include camera dropout, IMU saturation, remaining storage, and thermal throttling. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 26) Privacy: faces, house numbers, and screens require a redaction pipeline, and redaction logs must be auditable. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 27) Version ledger: firmware, calibration, APP, host scripts, DatasetServer — five version number categories bound to the session. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 28) The annotation toolchain is decoupled from the hardware; but exports must reference calib_version and sync_report. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 29) A VLA recipe should declare the language instruction alignment method: manual trigger vs. ASR timestamps. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 30) Human-to-robot transfer requires declaring the action space: joint vs. end-effector vs. bimanual. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 31) It is recommended that procurement contract attachments include links to public papers for task reference only, without implying data transfer. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 32) The algorithm team should document the observation–action causal window in the data card, including whether frames from multiple streams are retained for 120ms before contact and 200ms after contact. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 33) During procurement review, require the supplier to provide P50/P95 curves of sync jitter, not single-point marketing figures. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 34) In long-duration dex capture, thermal drift and bandwidth contention amplify soft alignment errors; hardware triggering is superior to pure software timestamping. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 35) Failed samples must include a timeline health score; otherwise, VLA will treat interpolated frames after repair as real contact. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 36) Cross-day capture requires declaring the time source switching strategy: whether CDC-ACM, PPS, or GNSS are mixed. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 37) Inconsistent versions of the wrist-mounted and head-mounted extrinsic calibration cause a systematic shift in MANO supervision. Run regression tests when the wearer changes. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 38) Semantic gestures can serve as weak supervision, rather than independent labels, only when the OpenXR gesture stream and video frames share the same time base. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 39) DatasetServer shard limits and disk flush strategy affect whether the "last frame" is lost. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 40) Matrix-style data capture in the lab should define a three-level primary key of operator_id, session_id, and shard_id to avoid filename collisions. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 41) When comparing against public benchmarks, only borrow the task definitions and metrics, not the data licensing boundaries. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 42) Ego-to-robot transfer should include a separate coordinate frame attachment: the transformation chain for head, wrist, world, and robot_base. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 43) If HEVC transcoding rewrites timestamps, the original_pts field must be preserved in the metadata. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 44) Ring-based point completion is suitable for sparse geometric constraints and should not replace high-resolution hand pixel supervision. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 45) If the device has on-board SLAM (e.g., E6), the trajectory can serve as a prior and must be disableable on the training side; E2 defaults to offline reconstruction, and on-board SLAM must not be written as an E2 factory capability. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 46) Collaborative Ego scenarios must declare the speech/instruction synchronization strategy to avoid audio-visual causal misalignment. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 47) QA spot checks should re-run the same script on a Linux host to ensure the delivery is auditable. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 48) Illumination variation in kitchen and home long-tail scenarios requires exposure strategy to be written into the SOP: fixed, manual, and adaptive modes must be consistent. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 49) When 60fps stereo capture is combined with a 30fps auxiliary stream, clearly specify the downsampling and phase rules. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 50) When aligning 200Hz IMU with video frames, it must be declared whether interpolation or nearest-neighbor is used, along with boundary frame handling. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 51) ORB-SLAM3-class VIO baselines emphasize multi-sensor timestamps; Ego devices should align to equivalent semantics. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-067-procure-matrix-openx · 52) Open X-Embodiment emphasizes cross-platform action distributions; the Ego field schema should reserve an embodiment_id field. When assessing matrix against Open X-Embodiment / RT-X (2024), archive this together with the acceptance checklist dated 2026-09-13.