Try ubuntu install using only standard repos at first.
|# Lucas Walter|
|# source rosrerun.sh my_node_name|
|# only take first match|
|orig_cmd=`ps -eo args | grep "__name:=$node_name" | grep __name | head -n 1`|
sudo apt update && sudo apt upgrade
Install google chrome
sudo apt install gimp guvcview gthumb clinfo curl libbullet-dev blender git meshlab vim ocl-icd-opencl-dev opencl-clhpp-headers libv4l-dev libsdl2-dev geeqie python3-numpy python3-opencv python3-matplotlib jupyter-notebook python3-notebook geeqie kazam openssh-server gnome-session-flashback gnome-tweaks python-pip net-tools
ROS2 - October 2018 - March 2019
There and back again
Started using ROS2 toward end of bouncy release, upgraded to crystal shortly after release, now have returned to ros1.
Maybe will try again when Dashing is release (June 2019?), or will wait for certain key features (some of these maybe already have been achieved, or were already achieved when I was using it but the right way wasn't clear to me):
- ros2 topic echo /image_raw shouldn't take 100% cpu, rqt_image_view shouldn't take 50% cpu. This may be fixed with https://github.com/ros2/rosidl_python/pull/ 35
- ros2 node info should handle namespaces
Visualize the data as a point cloud?
The files look to be mainly csv files.
http://cdn.gea.esac.esa.int/Gaia/gdr2/gaia_source/csv/ has many files.
Updating many repositories to use ros2 bouncy: image_manip, usb_cam, v4l2ucp, imgui_ros
The intent is to develop/learn how to convert ros1 packages first along with the entire workflow of building and debugging and deploying and then take advantage of ros2 features.
No verbose option?
cd into build/package_name then
run make VERBOSE=1 right there.
Does running a release build (using a mixin) then forgetting to specify release the next time clobber all the old built files,