Sunset Development on RCT

[marip8]

Why?

RCT was initially created as an attempt to refine/improve the capabilities of the industrial_calibration repository. We've done a lot of work towards that end, but currently the repository has quite a bit of legacy ROS1 code and porting to support ROS1 and ROS2 (as well as supporting additional OSes beyond Ubuntu 20.04) would be quite a bit of work.

In favor of what?

Over the past few months, I and others have done most of the work needed to make the aforementioned improvements to RCT, but we've done it as a refactor of the industrial_calibration repo. These changes include:

• migrating all of the contents of RCT back to industrial_calibration
• converting the core code to be ROS-agnostic
• reorganizing for improved modularity (in build and distribution) and ease of addition of future calibration data types (e.g., point cloud/laser scanner data)
• adding GUIs for extrinsic hand-eye and intrinsic calibration
• adding ROS-enabled data collection pipelines/utilties in separate industrial_calibration_ros and industrial_calibration_ros2 repos
• supporting builds on Ubuntu Focal, Jammy, and Noble

Proposal

I think the capabilities and format of industrial_calibration are now better than those of this repo, so I would propose moving future development to industrial_calibration and sunsetting development on RCT