I duplicated the UAV GCS DeepNote notebook and tried running it. While the solver does find a reasonable looking trajectory for the generated layout (when visualized by plotting), it seems like actually running the simulator errors out when AdvanceTo() is called:
In particular, it seems like this happens when the UAV is about to enter the house -- see attached image from the default provided seed of 8.
I've found that this occurs in other seeds as well, and suspect it's due to collisions or something -- for seed 9, it looks like it crashes right as the drone's about to clip the side of the house:
For reference, here's the full generated trajectory plotted in 2D:
This looks correct, based on inspecting the rendered crashed environment's visualization of the random household (though I guess I don't know where the goal location for the UAV is in the household, since unlike the original gcs-science-robotics version, it doesn't have a cube marking the goal?)
Both the above examples are from just visualizing the baseline trajectory, not the shortest path one. I haven't changed anything in any of the cells, except to comment out the shortest path stuff and to only animate the baseline (though running the unaltered notebook similarly crashes at this point):
I duplicated the UAV GCS DeepNote notebook and tried running it. While the solver does find a reasonable looking trajectory for the generated layout (when visualized by plotting), it seems like actually running the simulator errors out when
AdvanceTo()
is called:In particular, it seems like this happens when the UAV is about to enter the house -- see attached image from the default provided seed of 8.
I've found that this occurs in other seeds as well, and suspect it's due to collisions or something -- for seed 9, it looks like it crashes right as the drone's about to clip the side of the house: For reference, here's the full generated trajectory plotted in 2D: This looks correct, based on inspecting the rendered crashed environment's visualization of the random household (though I guess I don't know where the goal location for the UAV is in the household, since unlike the original gcs-science-robotics version, it doesn't have a cube marking the goal?)
Both the above examples are from just visualizing the baseline trajectory, not the shortest path one. I haven't changed anything in any of the cells, except to comment out the shortest path stuff and to only animate the baseline (though running the unaltered notebook similarly crashes at this point):
I've also tried the Docker installation of the older gcs-science-robotics repo, and that seems to work.