Viz for lidar pre processing base implementation - #31
Conversation
brianzheng206
left a comment
There was a problem hiding this comment.
good stuff, couple of small things
|
|
||
| ```bash | ||
| wato_lidar_preprocessing viz --bag <bag_id> --chunk <chunk_id> | ||
| wato_lidar_preprocessing viz --bag <bag_id> --chunk <chunk_id> --backend html |
There was a problem hiding this comment.
some of this is kinda slop, I also think if the html backend is able to provide us everything we need we can ditch open3d, and have that as default.
There was a problem hiding this comment.
that's really fair. I moved open3d to just be a fallback and added the point classification to html directly
| ARG USER_UID=1000 | ||
| ARG USER_GID=1000 | ||
| ARG CLAUDE_CODE=false | ||
| ARG DEV_PYTEST_SPEC=pytest |
There was a problem hiding this comment.
any reason why we are changing this?
There was a problem hiding this comment.
Lowkey added to make sure that the project pytest dependency is always aligned, but you're right. The previous written in hardcode is stable and will be good. I'll fix that
| done | ||
|
|
||
| # shellcheck disable=SC2206 | ||
| COMPOSE_FILES=(${COMPOSE_FILES_STR}) |
There was a problem hiding this comment.
ideally dont change this file, would you be able to define everything with cli.py? If we settle on one viz I think we wont even need this
|
not sure if we documented anywhere either but run |
it's documented in the readme |
📑 Description
Stitched viz.py into existing Open3D pipeline to reduce the brittleness of viz for lidar preprocessing. Currently may still require some fixes on the lidar preprocessing docker image, but no new bugs. Attached below is a video of the html interface for viz.
📹 (Optional) Video Demo of Changes
Recording.2026-07-09.183743.mp4
✅ Checklist
📝 Notes for reviewers