Repository navigation
Conversation
1 task
Nabla7
added this pull request to stack #4731
October 20, 2026 18:51
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why do we need this?
An instantaneous ideal cloud is insufficient to exercise a lidar-inertial estimator. Mid360 requires per-return timing, motion history and aligned IMU acquisition.
What is this feature?
Reuses main's Fourier/return-response implementation; retains explicit G1 and Go2 calibrations. Adds rolling raw clouds, corrected clouds, 200 Hz IMU, history invalidation and uniform IMU sampling with 500 Hz Go2 physics. No Point-LIO changes. Calibration/noise are approximations, not a claim of full real-sensor equivalence.
Depends on #4727. Review against
pim/refactor/sim2-go2, not main.Incremental diff: 6 files, +910/-19. Head:
2096bd6dd1d2e0137303ddd4d736596353fa75ad.How to manually run this
Verification
Both calibration tests and the actual native Point-LIO stage canary pass with and without a 640x480 camera. 10-second measurement, 0.6 m motion, zero dropped scans/IMU. Not a ten-minute or complex-scene performance guarantee. Build pointlio_native or set SIM2_POINTLIO_BINARY for that optional canary.
Draft review: final commits use
[skip ci]; local evidence is recorded instead of starting the long CI matrix. Hardware changes still need physical-robot review before merge.Which issue(s) does this PR close?
None. This is a dependent migration stack, not an independent replacement for the upstream connection work.
Earlier layers:
Checklist