{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":668333905,"defaultBranch":"main","name":"vrpn_client_ros","ownerLogin":"smartroboticslab","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-07-19T14:57:53.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/45238128?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1689780251.0","currentOid":""},"activityList":{"items":[{"before":"c2403b7c7afbff6dfe973d543ce65b2ae3af8c3f","after":"5bf300442b0bc56f6a906203c7f55d9b94e5e4f1","ref":"refs/heads/main","pushedAt":"2023-07-19T15:25:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sotpapathe","name":"Sotiris Papatheodorou","path":"/sotpapathe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16228680?s=80&v=4"},"commit":{"message":"Change the way ROS message timestamps are produced\n\nThe old behavior was problematic for both values of use_server_time:\n\n* When use_server_time is true the ROS message timestamps are the\n  OptiTrack server timestamps. However the OptiTrack server clock counts\n  from the program start and not from the UNIX epoch so the timestamps\n  can't be used for synchronizing with messages from other sources.\n* When use_server_time is false the ROS messages are timestamped on the\n  computer where the node is running using ros::Time::now(). Due to\n  network buffering and delays this can cause multiple messages to have\n  almost the same timestamps, causing issues in systems relying on them.\n\nRemoved the use_server_time parameter completely since it's now unused.","shortMessageHtmlLink":"Change the way ROS message timestamps are produced"}},{"before":"ea669b6e38532d9ca2817f0014ecab1e365aecee","after":"c2403b7c7afbff6dfe973d543ce65b2ae3af8c3f","ref":"refs/heads/main","pushedAt":"2023-07-19T15:24:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sotpapathe","name":"Sotiris Papatheodorou","path":"/sotpapathe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16228680?s=80&v=4"},"commit":{"message":"Change the way ROS message timestamps are produced\n\nThe old behavior was problematic for both values of use_server_time:\n\n* When use_server_time is true the ROS message timestamps are the\n  OptiTrack server timestamps. However the OptiTrack server clock counts\n  from the program start and not from the UNIX epoch so the timestamps\n  can't be used for synchronizing with messages from other sources.\n* When use_server_time is false the ROS messages are timestamped on the\n  computer where the node is running using ros::Time::now(). Due to\n  network buffering and delays this can cause multiple messages to have\n  almost the same timestamps, causing issues in systems relying on them.\n\nRemoved the use_server_time parameter completely since it's now unused.","shortMessageHtmlLink":"Change the way ROS message timestamps are produced"}},{"before":"54a66fc859478ffb33f242598cdf0a2e47c52ed4","after":null,"ref":"refs/heads/foxy-devel","pushedAt":"2023-07-19T15:24:11.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"sotpapathe","name":"Sotiris Papatheodorou","path":"/sotpapathe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16228680?s=80&v=4"}},{"before":null,"after":"ea669b6e38532d9ca2817f0014ecab1e365aecee","ref":"refs/heads/main","pushedAt":"2023-07-19T15:23:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"sotpapathe","name":"Sotiris Papatheodorou","path":"/sotpapathe","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/16228680?s=80&v=4"},"commit":{"message":"Change the way ROS message timestamps are produced\n\nThe old behavior was problematic for both values of use_server_time:\n\n* When use_server_time is true the ROS message timestamps are the\n  OptiTrack server timestamps. However the OptiTrack server clock counts\n  from the program start and not from the UNIX epoch so the timestamps\n  can't be used for synchronizing with messages from other sources.\n* When use_server_time is false the ROS messages are timestamped on the\n  computer where the node is running using ros::Time::now(). Due to\n  network buffering and delays this can cause multiple messages to have\n  almost the same timestamps, causing issues in systems relying on them.\n\nRemoved the use_server_time parameter completely since it's now unused.","shortMessageHtmlLink":"Change the way ROS message timestamps are produced"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADWN91zwA","startCursor":null,"endCursor":null}},"title":"Activity · smartroboticslab/vrpn_client_ros"}