-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split controller into planning #1
Open
hemangandhi
wants to merge
425
commits into
master
Choose a base branch
from
split-controller-into-planning
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add comparators needed by visionmanager
Two key issues: webstack client and planning clients' exceptions headers needed different include guards and we need GetTransform.
In particular, the heartbeat socket just subscribes to the heartbeat port and polls, whereas the command just publishes to the command port (_zmqPort). In my... wisdom, I'd conflated these.
More ZMQ foolishness. Turns out we have a lot more types of socket than I was accounting for, but it's the ZMQ_REQ type we want, probably -- see the old code here: https://git.mujin.co.jp/dev/controllerclientcpp/-/blob/master/src/mujinzmq.cpp#L395 (note: the github has something outdated).
… split-controller-into-planning Note: for some reason the header wasn't properly merged. But the cpp should have the necessary history.
There's some minor renaming, the addition of a CopyableRapidJsonDocument, and a unit field.
… split-controller-into-planning This is to recover new definitions in the RegisterMinViableRegionInfo struct.
…commit/a910b423c1e5f4527c06c08e0a77329dcbf1c686. In particular, I didn't propogate the changes to deseralize the RegisterMinViableInfo using its method.
hemangandhi
pushed a commit
that referenced
this pull request
Aug 25, 2023
Note: #1 will remote the need for this by just having a ZMQ client, but that's more refactoring than strictly needed for the split, so we'll use this factory function briefly.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(I'm a bit shocked this is mergeable automatically.) This is also so we have the diffs in one place.
This might be a bit more taxing than the webstack merge -- in particular, the planning client definitely doesn't have good files you can base diffs off since
binpickingtask
andbinpickingzmqtask
are merged into one functionality. I can try to get that as a separate branch first, so that this merge just has the follow-on renaming, perhaps.There's some decisions about removing some of the files here that I need to walk back for sure, but we might actually want them in the webstack client, so will discuss those.