[codex] Add MPPI diagnostics follow-up tooling#200
Merged
Conversation
rsasaki0109
added a commit
that referenced
this pull request
Jun 17, 2026
Add MPPI diagnostics follow-up tooling
rsasaki0109
added a commit
that referenced
this pull request
Jun 17, 2026
Add MPPI diagnostics follow-up tooling
rsasaki0109
added a commit
that referenced
this pull request
Jun 17, 2026
Add MPPI diagnostics follow-up tooling
rsasaki0109
added a commit
that referenced
this pull request
Jun 17, 2026
Add MPPI diagnostics follow-up tooling
rsasaki0109
added a commit
that referenced
this pull request
Jun 17, 2026
Add MPPI diagnostics follow-up tooling
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.
Summary
Adds the post-v0.1.0 MPPI follow-up tooling and documentation:
double_gapandmoving_crossingcuda_mppi_controllerdiagnostics CSV fileslow_overlap,outlier_partial, andlarge_offsetValidation
python3 -m py_compile scripts/render_cuda_mppi_extended_scenarios.py scripts/render_cuda_mppi_diagnostics.py scripts/run_cuda_mppi_bag_eval.py scripts/benchmark_registration_external.py examples/python/mppi_dlpack_costmap.py python/src/cudarobotics/__init__.py python/tests/test_import.pygit diff --checkros2 run cuda_mppi_controller plugin_load_testros2 run cuda_mppi_controller parameter_validation_testpython3 scripts/run_cuda_mppi_bag_eval.py --output-dir /tmp/cuda_mppi_bag_eval_smoke --controller-command 'sleep 5' --duration 0.2 --settle-seconds 0 --no-record --no-render-diagnosticscontroller_benchmarkfordouble_gap cpu_gpuandmoving_crossing quick, then rendereddocs/results/cuda_mppi_extended_scenarios_2026-06-12.{csv,md}Notes
The Python DLPack example requires an installed
cudaroboticspackage and either CUDA PyTorch or CuPy at runtime. The registration stress benchmark also requires the same external benchmark environment as the existing registration report.