search

ipa320 / ipa_coverage_planning

Algorithms for floor plan segmentation and systematic coverage driving patterns
269 stars 106 forks source link

Trajectory starting point issue #28

Open JaehyunShim opened 1 year ago

JaehyunShim commented 1 year ago

Hi,

Even if I change the starting_position param to other values, trajectories are generated from the same starting point. I even hardcoded the start_pos variable in the room_exploration_action_client.cpp file but it didn't solve the issue. Is this a bug or am I using it incorrectly?

Regards, Jaehyun

ipa-foj commented 1 year ago

Hello @JaehyunShim, could you provide us with some details about how you tried to use our software, s.t. we can replicate your issue? So especially in which line you hard-coded the robot position in the action client and a bit of insight in your map setup (so if the starting_position is a free point in your occupancy grid map) would be nice.