-
Notifications
You must be signed in to change notification settings - Fork 23
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
Module for graphnav #44
Conversation
heuristicus
commented
Jun 29, 2023
•
edited
Loading
edited
- Potentially needs to integrate Fast graph uploading #28 Add graph download/upload/clear methods #30 Fix logging output of graph_nav_util.py #31 Add localization interface and cancelable navigation methods #40, but hopefully hold those until this has been merged?
- Partial regression because some of the functions used try_claim: navigate_to, _navigate_to, and navigate_route
* use pytest instead * add pytest dependency * fail test on purpose * remove failing test
…pot_ros2 (bdaiinstitute#7) Co-authored-by: Andrew Messing <[email protected]>
* simple led brightness control, only able to set all leds to same value * Add power control, but unclear if it is actually possible to set power for aux and external mic * most basic functional image stream publisher with webrtc * add compositor to handle IR and webrtc stream selection with services Add timestamp for the webrtc images Add compressed version of the webrtc image stream * Add health wrapper, move body of robotToLocalTime out of spot wrapper object robotToLocalTime now takes the timestamp and a robot object, which allows it to be used by the spot cam wrapper as well. * add handler and wrapper for audio commands * update webrtc_client to 3.2 version * add stream quality wrapper and ros handler * initial implementation of ptz wrapper and handler, can list ptzs * ptz handler publishes position and velocity of ptzs, can set position and velocity * add egg info to gitignore
@kaiyu-zheng can you either test this or work with @smayorga-bdai to test this? we're starting to get blocked on this so let's try and get it in. |
I think theres some regressions. I was able to run our test_graphnav_services script on our internal repo "main" but after checking out heuristicus/modular-graphnav I got the following errors when uploading the graph.
|
Oh yeah we need to update |
@baxelrod-bdai fyi |
The main change needed should be to call functions using graphnav with |
I'm admittedly confused to the status of this. When I talked to @amessing-bdai, he mentioned there were multiple PRs blocking other things throughout this whole process. That's mainly why I've been hestitant to test it; I just don't know exactly what is dependent on what, so I don't know what order I'm supposed to be evaluating changes. |
@bhung-bdai My understanding of what's going on (from @amessing-bdai who is on vacation) is that:
So I think we need to:
I'm hoping the spot ros2 change is somewhat trivial but I haven't actually looked at it... |
I'll talk to Kaiyu about it. Andrew mentioned that he had a HIL test for
graphnav.
Brandon
…On Wed, Aug 2, 2023, 3:11 PM jbarry-bdai ***@***.***> wrote:
@bhung-bdai <https://github.com/bhung-bdai> My understanding of what's
going on (from @amessing-bdai <https://github.com/amessing-bdai> who is
on vacation) is that:
- We're not accepting any new PRs involving graph_nav into spot
wrapper or spot ros2 until this PR goes in. That is blocking several PRs
- This PR can't go in until we test it and update spot ros2 to call it
correctly. I originally thought we could test it without updating spot ros2
but actually thinking about it more I don't see how.
So I think we need to:
1. Update spot ros2 to be compatible with this PR
2. Test that PR and this PR together
3. Commit them at essentially the same time
I'm hoping the spot ros2 change is somewhat trivial but I haven't actually
looked at it...
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAW5F4P4GP4RZBI2GT3PU7DXTKQ77ANCNFSM6AAAAAAZYWB6UE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bhung-bdai he does and the above is the output I believe from running that test (which @smayorga-bdai did with @kaiyu-zheng 's guidance so he can help test this out now!). The problem is that it relies on spot ros2, which isn't compatible with this PR :( |
I can get on this. If it was like the spot_images modular change, then it
should be fairly simple to change spot_ros2 to work with it.
Brandon
…On Wed, Aug 2, 2023, 3:24 PM jbarry-bdai ***@***.***> wrote:
@bhung-bdai <https://github.com/bhung-bdai> he does and the above is the
output I believe from running that test (which @smayorga-bdai
<https://github.com/smayorga-bdai> did with @kaiyu-zheng
<https://github.com/kaiyu-zheng> 's guidance so he can help test this out
now!). The problem is that it relies on spot ros2, which isn't compatible
with this PR :(
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAW5F4MAMIGEFKZNQMAYTWLXTKSQRANCNFSM6AAAAAAZYWB6UE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bhung-bdai it looks like the last merge of the main branch into this branch unintentionally reintroduced some of the graphnav functions to the wrapper. I will revert and merge correctly. |
Ah, that explains a lot. Thanks! I apologize for the spam.
Brandon
…On Thu, Aug 3, 2023, 10:58 AM Michal Staniaszek ***@***.***> wrote:
@bhung-bdai <https://github.com/bhung-bdai> it looks like the last merge
of the main branch into this branch unintentionally reintroduced some of
the graphnav functions to the wrapper. I will revert and merge correctly.
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAW5F4J6333O6GAOKLMLABDXTO4CZANCNFSM6AAAAAAZYWB6UE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
b16ddc3
to
ae55ef4
Compare
Should be corrected now. |
…pper.py. Will get rid of these comments upon final revision
Localization HIL test works with the update |
Tested our HIL test with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
assert self.name_to_id["Node1"] == "ABCDE" | ||
assert self.name_to_id["Node2"] == "DE" | ||
|
||
def test_two_waypoints_with_edge_and_localization(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a difference between this test and the test above? I'm not as familiar with this code so maybe I'm missing something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see it now with the self.localization_id set differently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM s