You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update ROS to Kinetic Kame.
Update Gazebo to Gazebo7.
Update Vagrant provisioning to use supported Ubuntu version (Ubuntu Wily (15.10) or Ubuntu Xenial (16.04 LTS)
Update LidaPy for ROS API changes.
Update document (README.md, etc.) to reflect these changes.
Let the pain begin!
This is a large task, so I may break it up into smaller issues. In particular, there is some "feasibility research" that needs to be done as part of this that may make it a bear.
Possible Complications and Considerations:
When attempting to upgrade to Ubuntu 16.04 several months ago, there were problems with the virtual box. It did not follow box standards and seemed unusable. This needs to be researched and may be a show stopper if we are unable to find a usable box.
It would be great if we could upgrade to Python 3, but I am not sure ROS is fully supporting Python 3 at this point. Additional research is needed.
The text was updated successfully, but these errors were encountered:
The "official" ubuntu 16.04 vagrant box from canonical is still broken. (See bug report).
Fortunately, there is an alternate Ubuntu 16.04 image that I was able to use (bento/ubuntu-16.04) that appears to be stable. Minor changes were needed to the vagrantfile to get it up and running.
I've been able to install ROS Kinetic Kame and Gazebo7. The lidapy examples are currently broken because of API changes in ROS and Gazebo, but I am slowly making progress and addressing all of the broken code.
Hopefully by the end of the week I will have something that is working well enough to check-in.
Update ROS to Kinetic Kame.
Update Gazebo to Gazebo7.
Update Vagrant provisioning to use supported Ubuntu version (Ubuntu Wily (15.10) or Ubuntu Xenial (16.04 LTS)
Update LidaPy for ROS API changes.
Update document (README.md, etc.) to reflect these changes.
Let the pain begin!
This is a large task, so I may break it up into smaller issues. In particular, there is some "feasibility research" that needs to be done as part of this that may make it a bear.
Possible Complications and Considerations:
The text was updated successfully, but these errors were encountered: