Is it really necessary to define the buff_size? Close #393

atom_calibration/scripts/dataset_playback

@@ -39,8 +39,7 @@ def keyPressedCallback(key, selection, dataset, args):
     idx_collection = int(selection['collection_key'])
     idx_max_collection = len(dataset['collections'].keys()) - 1
 
-    output_file = '/'.join(args['json_file'].split('/')
-                           [:-1]) + '/dataset_corrected.json'
+    output_file = '/'.join(args['json_file'].split('/')[:-1]) + '/dataset_corrected.json'
 
     # Convert from type to string to keep uniform.
     key = str(key)
@@ -166,16 +165,16 @@ def main():
         selectedPointsCallback, selection=selection, dataset=dataset), queue_size=1, buff_size=52428800)
 
     rospy.Subscriber("/rviz_selected_border_points", PointCloud2,
-                     partial(selectedPointsBorderCallback, selection=selection, dataset=dataset), queue_size=1,
-                     buff_size=52428800)  # TODO #393 Is it really necessary to define the buff_size?
+                     partial(selectedPointsBorderCallback, selection=selection, dataset=dataset),
+                     queue_size=1)  # TODO #393 Is it really necessary to define the buff_size?
 
     rospy.Subscriber("/rviz_selected_remove_points", PointCloud2,
-                     partial(selectedPointsRemoveCallback, selection=selection, dataset=dataset), queue_size=1,
-                     buff_size=52428800)
+                     partial(selectedPointsRemoveCallback, selection=selection, dataset=dataset),
+                     queue_size=1)
 
     rospy.Subscriber("/rviz_selected_clear_all_points", PointCloud2,
-                     partial(selectedPointsClearAllCallback, selection=selection, dataset=dataset), queue_size=1,
-                     buff_size=52428800)
+                     partial(selectedPointsClearAllCallback, selection=selection, dataset=dataset),
+                     queue_size=1)
 
     # ---------------------------------------
     # --- Depth modality subscribers