Skip to content

Commit

Permalink
Changing min_clearing_height to -infinity
Browse files Browse the repository at this point in the history
Similar to raising max_clearing_height to infinity.
A noisy or otherwise slightly incorrect ground plane can cause some clearing
rays to have endpoints with negative height values, but those rays are still
valid for clearing.
  • Loading branch information
aaronhoy committed Feb 4, 2016
1 parent 30d7794 commit 61a194a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion fetch_depth_layer/src/depth_layer.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ void FetchDepthLayer::onInitialize()
// Observation range values for both marking and claering
private_nh.param("min_obstacle_height", min_obstacle_height, 0.0);
private_nh.param("max_obstacle_height", max_obstacle_height, 2.0);
private_nh.param("min_clearing_height", min_clearing_height, 0.0);
private_nh.param("min_clearing_height", min_clearing_height, -std::numeric_limits<double>::infinity());
private_nh.param("max_clearing_height", max_clearing_height, std::numeric_limits<double>::infinity());

marking_buf_ = boost::shared_ptr<costmap_2d::ObservationBuffer> (
Expand Down

0 comments on commit 61a194a

Please sign in to comment.