Trey Smith

Hi, Marina- Big picture thought: I designed `rosbag_fix_all.py` with a particular use case in mind, namely that it could be something the Astrobee Facility team could run on raw bag...

> Please note that this PR is a Draft and not suitable for review. My idea for the final form would address your comments. I still want to make it...

Without necessarily slowing down the process on this PR -- I think that going forward, whenever we update calibration parameters for a robot, we should add a comment about the...

> I added some more details to the PR message. The pointed locations have all the mentioned analysis performed (I organized things there that it should stay static to the...

Thanks for testing and iterating! I think we should merge the debug script into this repo to make it accessible as open source, and after it makes it into a...

Closed by #536 . Thanks, Marina!

Both of these make sense, but I think we are talking about different things: 1. Calibration info which is hopefully static fits perfectly into the standard ROS `sensor_msgs/CameraInfo` message. (Typically...

> What is the status of this after closing the haz cam PR? The original comment potentially covers timestamps for telemetry from basically all of the hardware. I did a...

And below are some other possible components I evaluated but don't think are important to work on right now. - `pico_driver` (HazCam/PerchCam) - DONE - #413 - `epson_imu` - Action:...

> ... Because of this, we decided not to use the getTimestamp() method. Thanks @kbrowne15. Sorry if we previously discussed this, but did you try to evaluate the `getTimestamp()` quality?...