Comments (4)
Maybe a "SpeedCritic" will be best way to explicitly desire trajectories/cmds that lead to a target speed... IOW vx_max?
from navigation2.
I'm not entirely sure how to read this ticket's request. If you'd like to make some kind of system for auto-tuning or testing, I'm all for it, but that is going to be something that probably makes sense as a separate repository if its going to be extremely involved.
Maybe a "SpeedCritic" will be best way to explicitly desire trajectories/cmds that lead to a target speed... IOW vx_max?
Sure, its plugin based for a reason, you can add any plugins your like that optimize for what's important to you. I did remark on that a bit in your other ticket #4219 The defaults I set to run at about 0.5m/s so you'd need to retune for higher velocity regimes. I'm sure its possible, you just need to make sure you have a large enough costmap to be able to handle that (i.e. if you have a prediction horizon of 5 seconds at 3.5 m/s, that's a costmap size of 35 meters) and thus a computer which can handle computing long trajectories like this in real-time. With speed comes increased computational burden.
I suppose you could try to either have a very low prediction horizon to stay inside a smaller costmap or keep it longer but have a good chunk of the trajectory off of the costmap, but those are both not optimal setups. Perhaps we need to adjust a couple of the critics to enable that, since right now we prune the path off of the costmap for alignment longer-term and cost critic values off of the costmap are set to max. We could have settings which lets you preform more actions outside of the costmap horizon (and don't negatively score when off of it) but then you run the risk of having collision issues if you only know about an obstacle once its too late to react to it. You'd need a strong low-level safety system to catch such situations and want to run the controller pretty fast (50+hz) to have the best chance of getting around those situations before they become a safety issue once the obstacle gets inside of the costmap window. The costmap size should at the bare minimum be the length of deceleration from full speed to a total stop (2x for both direction) - but you'd want it to be larger to be able to catch obstacle information earlier to plan around it before its a safety issue.
Another direction is if you had vectorized detections rather than relying solely on costmap information, we could include that in a new MPPI critic so that it would take into account collision information outside of the costmap window (i.e. if you have AI detectors, Radar, etc). That would be a general purpose and valuable improvement to MPPI that wouldn't be particularly hard to implement.
Another yet direction is improving the runtime performance so it can run over the larger time horizons, but that is probably going to require a GPU and a bit of effort on your part to GPU-ize MPPI.
from navigation2.
Hey - any updates / thoughts here?
from navigation2.
Closing without update
from navigation2.
Related Issues (20)
- Hi, I am building the package of nav2_waypoint_follower and facing that errors, HOT 2
- New "Configure" transition for the LifecycleManager HOT 2
- Accessing waypoints inside a controller plugin HOT 3
- Fix flaky spin test
- Nav2 Stalling on Multiple Robots? HOT 9
- Robot using nav2 begins pathfollowing but never finishes HOT 3
- MPPI cannot follow global path accurately HOT 1
- [Collision_monitor] Approach polygon time=0 step is not processed HOT 7
- The lidar point cloud of NAV2 shifted significantly after being stationary for 5 minutes. HOT 5
- Errors with controller_server using GPS for Navigation HOT 4
- Obstacle Position Shift in Map after Loading HOT 2
- Full footprint collsion distance in MPPI obstacle critic and use of collision_margin_distance. HOT 13
- local_costmap does not respect the use_sim_time parameter HOT 12
- Vector polygon - Collision Monitor is not available for ROS2 humble HOT 5
- [collision_monitor] Add temporal axis to min_points behavior HOT 2
- [ERROR] [1716697697.080277840] [rviz2]: Lookup would require extrapolation into the future. Requested time 1716697697.040514 but the latest data is at time 1716697697.039929, when looking up transform from frame [laser_frame] to frame [odom]
- Laser Scan rotates with robot ------- [ERROR] [1716697697.080277840] [rviz2]: Lookup would require extrapolation into the future. Requested time 1716697697.040514 but the latest data is at time 1716697697.039929, when looking up transform from frame [laser_frame] to frame [odom] HOT 1
- [for help] action `follow_path` doesn't work (humble) HOT 7
- Changing the params file HOT 1
- Understand MPPI Critics and parameters HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from navigation2.