All rapyuta.io docs are open source. See something that's wrong or unclear? Submit a pull request.Make a contribution
If you want to record the topics for any ROS component of a package, you can follow the steps below
Pre-requisite: Ensure that you have selected the component runtime as cloud or device (device runtime must be docker) while creating a package and Is ROS Component is selected during package creation.
Under the Components tab on the Create New Package page, click Add ROS Bag Job.
In the Name field, type a name for the ROS bag job.
In the Topic Names field, type the name of the topic that you want to record.
Optionally, if you want to record all the topics available in the component, click the All Topics? toggle-button.
Optionally, if you want to record a series of topics that should match a regular expression value or regex, type the regex in the Include Regex field.
Optionally, if you want to exclude the recording of a series of topics that should match a regular expression value or regex, type the regex in the Exclude Regex field.
If you have enabled the All Topics? toggle-button, Topic Name and Include Regex fields are disabled.
You can also provide either BZ2 or LZ4 compression to the recorded topics based on your requirement and available disk sizes. BZ2 generally produces smaller bags than LZ4. For more information about ROS compression, click here.
The advanced option allows you to record the topics with a more granular report. Optionally, to use the advanced option, click Show Advanced Option and do the following.
a. In the Node Name field, type the node for which you want to record all the topics subscribed by the specific node.S b. In the No. of Message field, type the number of messages that you want to store for each topic. c. Max Splits field defines the maximum number of splits of the ROS bag files that are saved. Older splits are deleted after the Max Splits count is reached. To split the ROS bag file, in the Max Splits field, type the number of splits that you want to allow.
Maximum 10 splits are allowed for each ROS bag job. After the message recording reaches the maximum allowed splits, the older split files are deleted to maintain the specified memory limit.
d. Split Size is the file size after which the file is split. In the Split Size field, type the memory size for each split of the recorded messages in MB.
Each split size must be more than 10 MB and less than 1024 MB or 1GB.
Maximum 10 splits are allowed with the split size of more than 10 MB and less than 1 GB. However, the disk storage for the ROS bag file can not go beyond 5120 MB (5 GB). For example, you can configure 10 splits and each split can store up to 500 MB (10X500 MB=5 GB) of recorded data or you configure 5 splits and each split can store up to 1024 MB (5x1024 MB=5 GB) of recorded data. After the message recording reaches the maximum allowed splits, the older splits are deleted to maintain the specified memory limit.
f. To add the ROS bag job and start recording the defined topics, click Add.
You can also update the value of the ROS bag jobs during the time of deployment. The values added during the deployments override the values added during the package creation.
The rapyuta.io platform lists all the available ROS bag jobs under each component. To view the details of a ROS bag job, click the ROS bag job and then click the Job Details tab. You can view the ROS bag details, for example, the topics that are being recorded by the job or the message compression detail as displayed in the following image.
A ROS bag file is uploaded to the platform automatically if the ROS bag job is stopped or if the deployment is de-provisioned. To stop the ROS bag job, click Stop next to the ROS bag job name. A pop-up warning message appears. Click Yes. The platform takes some time and the details of the recorded topics are available. You can view the following details. The ROS Bag Jobs tab lists all the running ROS bag jobs for the deployment.
Bag Name: Displays the name of the ROS bag file.
Status: Displays whether the recorded ROS bag file is uploading, uploaded, or in the error state. If the status is Uploading, it implies that the ROS bag file is getting uploaded to the platform after the ROS bag job is stopped or the deployment is de-provisioned. If the status is Uploaded, it implies that the file is uploaded to the platform successfully and you can download the file to your local system for further analysis and troubleshooting. If the status is in Error state, it implies that the recording of the ROS bag file is not successful and the ROS bag file is not available. If the ROS bag job goes into error state, click the Error link to raise a support ticket for a resolution.
Messages: Displays the number of recorded messages.
Size: Displays the file size.
Start: Displays the start time of the recording.
End: Displays when the recording is stopped.
Duration: Displays the total time duration for the ROS bag job that was run.
Indexed: If the Indexed field is marked with a green tick icon, it implies that the ROS bag file is indexed and contains valid recordings of topics. If the Indexed field is marked with a red cross icon, it implies that the ROS bag file is not indexed and does not contain valid recordings of topics.
Actions: You can either download the ROS bag file or delete the file.
After a running ROS bag job is uploaded to the platform, you can perform the following available actions.