Datasets:
🔍 Are These Cameras in the Same Universe? *(Not a Multiverse… right?)*
Dear organizers and participants,
During an EDA on the Warehouse_003
scene in the MTMC_Tracking_2025 dataset, I met a curious phenomenon that may indicate either a simulation inconsistency or a misalignment in camera synchronization.
Specifically, I was comparing object trajectories across Camera_0014
and Camera_0039
. At first (zero-frame), everything seemed in order — the initial object placements and identities were consistent. However, as time progresses, the motion patterns begin to diverge significantly. What initially appeared to be the same scene captured from different angles slowly transforms into two distinct evolutions of object behavior.
My initial assumption was a frame synchronization issue. However, after closer inspection, the trajectories themselves — particularly of a large man in pink wearing headphones pushing a cart — follow entirely different paths in the two camera views, despite starting from identical initial positions. This divergence appears to go beyond temporal misalignment and suggests a fundamental desynchronization in the underlying simulation.
(🎥 I’ve attached a GIF to visually demonstrate this discrepancy — the subject in question follows notably different trajectories in each view.)
This raises a few questions:
- ❓ Are these two camera views (
Camera_0014
andCamera_0039
) — and potentially other camera pairs in the same scene — intended to be synchronized representations of the same physical space? - 🔁 Could this be due to simulation desynchronization during the synthetic data generation process?
- 🗺️ Is there any metadata (e.g., camera grouping, synchronization domains) that would clarify this behavior?
As a possible explanation, I wonder whether this may be related to non-determinism in Omniverse Replicator. Even when using the same random seed, some aspects of the simulation (e.g., physics, agent policies, rendering order) may produce slightly different results across runs, especially if the simulation for each camera was rendered separately. If that’s the case, this might explain the gradual divergence between seemingly identical scenes.
If I’ve missed anything in the documentation or configuration that could clarify this, I would greatly appreciate any insights.
Thank you again for providing this dataset — it’s a valuable resource for the multi-camera tracking research community.
Best regards,
visionNoob