Closed dorezyuk closed 3 years ago
I wouldn't mix the stuff and do the refactoring step by step. Right now there is no correspondent action to publishZeroVelocity for planners failing. We might later refactor the code into
setState(State _state, bool _signalling) {
...
planning_ = !_signalling
}
since we typically want to exit the planning loop if we signal
I wouldn't mix the stuff and do the refactoring step by step. Right now there is no correspondent action to publishZeroVelocity for planners failing. We might later refactor the code into
As long as you follow up this PR with the matching changes for controller and recovery, I'm good approving this
I've moved the condition-variable inside setState, so we can easier trigger it on state-update. This simplifies the code a bit