refactor person description messages #6
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Face.msg
in favor of identity field inPerson.msg
Person.msg
, so safety logic will be isolated from data modelPerson.msg
, but not removing for compatibilityFaceList.msg
Affected packages
mdr_find_people
: this is part of the refactoring, so I think it's fine to remove thesafe_pose
fieldAdditional comments
After looking through the code in
mcr_people_tracking
, andmcr_leg_detection
, I think they both need major refactoring and documentation if we plan to use them at all. Whilemcr_leg_detection
seems to be a copy of Willow Garage'sleg_detector
,mcr_people_tracking
seems worth some further examination.Since I don't plan to spend time on that at the moment, I decided to add comments about this in
Person.msg
and keep the legacy fields for compatibility, at least until some other people are willing to spend some time and effort looking into it.