The RemoveKeywordCollisions transform, and it's one child VerilogRename, should error if renaming something marked as don't touch. It's also allowable that this shouldn't rename the offending signal and produce a warning.
Checklist
Did you specify the current behavior?
Did you specify the expected behavior?
Did you provide a code example showing the problem?
Currently the error says there are duplicate landmarks. This is just a check in the constructor that does not allow for this. However, dlib apparently spits out identical landmarks when the prediction fails.
This is a package for extrinsic calibration between a 3D LiDAR and a camera, described in paper: Improvements to Target-Based 3D LiDAR to Camera Calibration. This package is used for Cassie Blue's 3D LiDAR semantic mapping and automation.
Currently, whenever a TU or TO fails, its error message is only showed if Butterfly is run in debug mode. The error message should be printed even in INFO level, but the error stack trace should remain only printed in debug mode.
The
RemoveKeywordCollisionstransform, and it's one childVerilogRename, should error if renaming something marked as don't touch. It's also allowable that this shouldn't rename the offending signal and produce a warning.Checklist