If you attempt to rebuild and open a dev container for either the current repo or version 3, you may run into the following two errors.
If you open a dev container for the current repo, then run "obk," it is unable to source ros2/humble since ros2 failed to be installed.
If you open a dev container from version 3, then run "obk," it is able to source ros2/humble. However, if you run "obk-launch config_file_path=dummy_cpp.yaml device_name=onboard," you'll get a GLFW authorization error, so the mujoco simulation fails to be displayed. This occurred on a computer that used Wayland instead of x11. To determine which display server the computer uses, echo $XDG_SESSION_TYPE. Switch to x11 by following the first instructions: https://itsfoss.community/t/switching-from-wayland-to-x11-in-ubuntu-22-04/10723.
Then run "sudo xhost + local:docker," then rebuild the dev container. Source: https://forums.developer.nvidia.com/t/display-issue-x11-and-glfw-in-driveworks-docker-environment-host-pc/231059/3
In obelisk_ws/src/python/obelisk_control_py/obelisk_control_py/example_position_setpoint_controller.py, there's the line "from obelisk_py.zoo.control.example.example_position_setpoint_controller import ExamplePositionSetpointController."
If I right-clicked on ExamplePositionSetpointController and went to the declaration, it brought me to usr/local/lib/python3.10/dist-packages/obelisk_py/zoo/control/example/example_position_setpoint_controller.py. So I CTRL-F'd usr/local in the repository, which brought me to install_sys_deps.sh. Within this file is the text "pip install -e $OBELISK_ROOT/obelisk/python," which installs the package as an editable one. I reran the command in the terminal (with obk activated, although maybe it didn't have to be activated). Thus, when I right-click on ExamplePositionSetpointController and go to the declaration, it brings me to obelisk/python/obelisk_pyzoo/control/example/example_position_setpoint_controller.py.
If you attempt to rebuild and open a dev container for either the current repo or version 3, you may run into the following two errors.
If you open a dev container for the current repo, then run "obk," it is unable to source ros2/humble since ros2 failed to be installed.
If you open a dev container from version 3, then run "obk," it is able to source ros2/humble. However, if you run "obk-launch config_file_path=dummy_cpp.yaml device_name=onboard," you'll get a GLFW authorization error, so the mujoco simulation fails to be displayed. This occurred on a computer that used Wayland instead of x11. To determine which display server the computer uses, echo $XDG_SESSION_TYPE. Switch to x11 by following the first instructions: https://itsfoss.community/t/switching-from-wayland-to-x11-in-ubuntu-22-04/10723.
Then run "sudo xhost + local:docker," then rebuild the dev container. Source: https://forums.developer.nvidia.com/t/display-issue-x11-and-glfw-in-driveworks-docker-environment-host-pc/231059/3
In obelisk_ws/src/python/obelisk_control_py/obelisk_control_py/example_position_setpoint_controller.py, there's the line "from obelisk_py.zoo.control.example.example_position_setpoint_controller import ExamplePositionSetpointController."
If I right-clicked on ExamplePositionSetpointController and went to the declaration, it brought me to usr/local/lib/python3.10/dist-packages/obelisk_py/zoo/control/example/example_position_setpoint_controller.py. So I CTRL-F'd usr/local in the repository, which brought me to install_sys_deps.sh. Within this file is the text "pip install -e $OBELISK_ROOT/obelisk/python," which installs the package as an editable one. I reran the command in the terminal (with obk activated, although maybe it didn't have to be activated). Thus, when I right-click on ExamplePositionSetpointController and go to the declaration, it brings me to obelisk/python/obelisk_pyzoo/control/example/example_position_setpoint_controller.py.