aws-robotics / aws-robomaker-sample-application-cloudwatch Goto Github PK

This sample application have been affected by a conversion error on the cloudwatch_metrics_collector node. We have detected the problem, and we are working on deploying a fix, that should be available by the end of next week.

Hi,

Previously I've successfully deployed hello_world_robot application to turtlebot3 (raspberry pi3 with ubuntu 18.04 lts) in AWS Robomaker.
Currently I'm experiencing the following error while deploying cloudwatch_robot application:

`ERROR: 2020/09/09 13:00:27 Command failed: exit status 1: �[31mResource not found: turtlebot3_bringup
ROS path [0]=/opt/ros/melodic/share/ros
ROS path [1]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/cloudwatch_robot/share
ROS path [2]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/turtlebot3_description_reduced_mesh/share
ROS path [3]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/health_metric_collector/share
ROS path [4]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/cloudwatch_metrics_collector/share
ROS path [5]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/ros_monitoring_msgs/share
ROS path [6]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/cloudwatch_logger/share
ROS path [7]=/home/ggc_user/roboMakerDeploymentPackage/5cfcd2f27528023cc10db945a8ffbec132539e78bb31c1c0efb6cfcb92d06961/opt/built_workspace/aws_ros1_common/share
ROS path [8]=/home/ggc_user/roboMakerDeploymentPackage/a4a7bacbb19213c72caa6c3cf1379e7e314efde0eca77c61ed3dfda0069bdcfe/opt/ros/melodic/share
ROS path [9]=/opt/ros/melodic/share�[0m
�[31mThe traceback for the exception was written to the log file�[0m

`

I discovered that in hello_world_robot in turtlebot3_bringup.pc the prefix is set to /opt/ros/melodic, however in cloudwatch_robot it is set to prefix=/home/ubuntu/environment/CloudWatch/simulation_ws/install/turtlebot3_bringup

Could it be the issue and could you please fix that?

There is currently an issue with the LaserScan messages emitted from the gazebo lidar plugin not being received by the monitor_obstacle_distance node. This has been added to the known issues section of the README in #46. Opening this ticket to track the issue until it is resolved.

See #54

I am a newbie and might sound stupid.
I would like to build a robot musician which would try to synchronize with other multiple human musicians to play music like a musical ensemble. I would use coupling oscillator models and multiple machine learning models to predict the musical beats and musician movements to address the synchronization challenge in realtime.
I would be grateful if you can elaborately tell exactly -
1.Will it be possible to design such models? What services should we take along with Robomaker to make it?
2. will this be possible to simulate? what are the tools or methods needed to create the environment?
3. How to deploy this model.

I would grateful to hear a detailed answer. As I am planning to use for my research.
My email- [email protected]

We now know that the turtlebot3_model.rviz files are located at:

• ROS1: <package root>/share/cloudwatch_robot/rviz/turtlebot3_navigation.rviz
• ROS2: <package root>/rviz/turtlebot3_navigation.rviz
  because of differences between rospack find <package name> and ros2 pkg prefix <package name>

TODO:

• Check if the turtlebot3_model.rviz file under robot_ws is necessary at all.
• Confirm that having no .rviz files under simulation_ws is okay.

The source files in this repo are under the MIT-0 license, unless otherwise specified in the source header (there are at least some source files that are Apache 2.0).

This issue is to track the cleanup of the license headers in the source files of this repo, so that it passes ament_copyright checks.

#25 was made for pulling in the fix at ROBOTIS-GIT/turtlebot3#402, but once the fix is released and made available in the ros-melodic-turtlebot3-navigation apt package, #25 should be reverted.

It looks like ever since the release of this sample app (6469dad#diff-55f9bb07b4449f6eb1c9e3c8685e55a4R4), the cloud extensions that it depends on have been fetched via source, even after said cloud extensions have already been bloom released. Installing the bloom released cloud extensions via rosdep/apt should be overwhelmingly preferred.

This issue is to track the removal of the cloud extension sources from the .rosinstall file.